Try connecting to EC2 directly, and if it is not connected, check whether the EC2 firewall or web server is running well. If the connection is good, if you are connected to an ELB, you should connect to the ELB access address to check if the connection is good. If it goes well so far, it will be a connection problem with route53, so check if the dns name server connection is normal through dns lookup, etc It might be a dns cache problem, so if you do window based (ipconfig/flushdns...), the cache will be cleared. Sometimes, the domain connection is not good on a PC with a dns server connected to kornet dns, but it can be solved by replacing the DNS server on the PC with 8.8.8.8 Google dns. And it doesn't matter if you connect only one instance to ELB.
Because AMI stores the EC2 state at the time the image was created (if you created the image after installation) Ruby, etc. are installed. For user data, it is a script that downloads the source code and runs the web application. For example, if you only installed web programs except for the source code at the time of generating AMI, The source code should be downloaded from git when creating an instance with AMI, as in userdata... The reason for this is that if you put the source code in the state at the time you created the AMI, it is not up to date without any subsequent changes. And in the case of ruby on rails, I don't know if I know ruby, but like node.js, the example above, we can make the ruby project run in the path of the project. http://guides.rubyonrails.org/command_line.html Looking at the example here, it seems like you're doing it as follows. $ $ cd commandsapp $ $ bin/rails server
There were a lot of questions, so I just answered them as I thought of them. One thing I would like to advise you is to break the above problems into small units and solve them one at a time. Then you'll understand the whole flow and structure.
© 2024 OneMinuteCode. All rights reserved.