1 Answer
- Newest
- Most votes
- Most comments
0
Hello.
What kind of access would fail?
Also, what error do you get when connecting?
Are the necessary communications allowed by the inbound rules of the security group set in EC2?
Also, is the route to the Internet gateway set in the route table of the subnet where EC2 is running?
Please also check the following documents.
https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/instance-console.html
https://repost.aws/knowledge-center/ec2-instance-hosting-unresponsive-website
Relevant content
- Accepted Answerasked 5 months ago
- Accepted Answerasked 4 months ago
AWS OFFICIALUpdated a year ago- AWS OFFICIALUpdated 2 months ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated 2 years ago
This was the error that I was getting 'ssh: connect to host ec2-34-204-5-151.compute-1.amazonaws.com port 22: Connection timed out' when using a custom VPC that I created in the us-east-1 region, hence I decided to use the default VPC, and it still failed to connect. Based on the above scenario, I decided to move to us-west-1 and I was able to connect using the default VPC. After I read your response. I decided to go back and retry the process in the us-east-1 region, using the default VPC and it worked. Not sure if my ISP had anything to do with it.