When I check the logs of my EC2 instance after assigning an elastic IP (e.g., new elastic ip is = ip-111-111-111-111) and rebooting, I get the following at the end of my EC2 logs (Found by going to
"Actions"->"Instance Settings"->"Get System Logs")
Ubuntu 16.04.5 LTS ip-123-456-123-456 ttyS0: ip-123-456-123-456 login:
ip-123-456-123-456 is the private IP and
ip-111-111-111-111 is the new elastic IP.
My EC2 instance is just sitting there and I am unable to ssh into the box and I'm unable to interact with the machine to enter the password for the private IP login it is asking for. Is this a common occurrence? What can I do to get my EC2 instance past this state?
UPDATE: I also modified some DNS settings in an attempt to point a domain name from GoDaddy to this EC2 instance's elastic IP. Is it possible this screwed something up and has caused the login to fail?
UPDATE 02: I am loath to include a screenshot but this is where it is at after taking a screenshot of the machine, where the machine is stuck, asking for the private IP login. All of my ssh requests timeout, I think due to this.