EC2 reachability check failed (Linux) from launch instance from snapshot

Question

Launch instance from a clone AMI and the status check fails. Unable to ssh in the ec2 instance checked the Private IPv4 addresses and it's correct for the current VPC and the correct security group inbound ports is open ie..port 22.

Click on Get instance screenshot and the IP showing in the login screen is incorrect.

example..ec2 intance IP: 10.2.68.xx screenshot IP: 10.1.x.x

This will happen with any flavor of Linux ie..centos, redhat, ubuntu etc

I did shut down the ec2 instance and still had the incorrect private IP

Answer

Hi.

Can you share the logs from the console output

To get console output

1. Open the Amazon EC2 console at https://console.aws.amazon.com/ec2/

2. In the left navigation pane, choose Instances, and select the instance.

3. Choose Actions, Monitor and troubleshoot, Get system log.

If the instance is showing the incorrect IP, I recommend opening up a support case to EC2 Linux to further review your instance.

Answer

We cant open any support case with AWS my current organization does not have this support. I'm trying to see if anyone has seen this error in the past and fixed the issue.

EC2 reachability check failed (Linux) from launch instance from snapshot

Relevant questions

Instance reachability check failed on ec2 ubunut 18.04

AWS Nitro Enclave instance does not have public ipv4 address

Unable to connect to instance from a newly created ami: Failed to start Service for snap ap…amazon-ssm-agent.amazon-ssm-agent

Ubuntu 18.04 AMI with "ubuntu-desktop" pkg fails to connect (networking)

Debian 11 fails status check with instance type i3

Instance reachability check failed

Linux instance has failed its instance check and I cannot connect to it

System reachability check passed Instance reachability failed!

EC2 reachability check failed (Linux) from launch instance from snapshot

can't create AutoScaling group from launch template