- Newest
- Most votes
- Most comments
Hello.
Was it possible to originally connect to the target EC2 using SSH?
For example, have you changed the route table settings for the EC2 subnet or changed the network ACL settings and are now unable to connect?
By the way, have you tried restarting EC2?
https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/troubleshoot-unreachable-instance.html
Also try restoring from a snapshot.
https://docs.aws.amazon.com/prescriptive-guidance/latest/backup-recovery/restore.html
I also think it would be possible to mount the root volume of the EC2 in question on a normal EC2, extract the necessary data, and restore it.
https://docs.aws.amazon.com/ebs/latest/userguide/ebs-using-volumes.html
Hi, Does your EC2 instance has internet connectivity? If your instance is in a private subnet or doesn't have connectivity, you need either to configure a VPC endpoint for Systems Manager or use a NAT gateway.
Relevant content
- asked 3 days ago
- asked a year ago
- asked 10 months ago
- asked 3 years ago
Hi,
I have tried restarting the EC2 but it has not worked. Actually this ec2 instance is a node of an application which is in cluster and so we can't restore a snapshot else we will have to go through the entire process of configuring the application again. Attaching the root volume of current ec2 instance to a new ec2 instance will only help me in getting the data and our goal is to access the instance, installing ssh or via session manager.
Is EC2 registered as a managed instance in the Systems Manager Fleet Manager console? Also, if registered, is the status online? If you are not online, you cannot connect with Session Manager. If neither SSH nor a session manager can be used, it will be difficult to connect to the OS.