1 Answer
- Newest
- Most votes
- Most comments
2
Q1: It should be pretty much immediate
Q2: Here are some things to check:
- That the security group is correctly assigned to the instance and that the rules match the protocol (eg. ICMP) as well as port and source IP range
- The inbound and outbound rules for the network ACL are correct and assigned to the right VPC
- Any firewall rules (eg. Windows firewall) on the instance are set correctly
- That the service you're trying to connect to (eg. a webserver) is up and running correctly on the instance
Finally you may consider using the AWS VPC Reachability Analyzer: https://aws.amazon.com/blogs/aws/new-vpc-insights-analyzes-reachability-and-visibility-in-vpcs/
answered 2 years ago
Thank you for your reply. I have isolated the issue down to the image. Some instances built with Windows Server 2019 or 2002 had firewall off while other instances it was on and I had to modify it or turn it odd completely for troubleshooting purposes. So really the last steps Are to check the image is configured for the services and modify the Windows firewall accordingly. Thus , I see that not all images are made equal. Best Regards!
Relevant content
- asked 7 months ago
- asked 6 months ago
AWS OFFICIALUpdated 6 months ago- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated 2 years ago
Thank you for the reply. If every step above is followed and the public address is still not reachable , what else could cause the issue ?
Some more detailed troubleshooting tips can be found here: https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/TroubleshootingInstancesConnecting.html
It might also be worth creating a small instance in the same subnet to check that the instance is responding there before working backwards through the internet facing configurations.