2 Answers
- Newest
- Most votes
- Most comments
0
Am not sure I understand your issue correctly, but you can use the rateability analyzer to check if the EC2 (ENI for the EC2) is reachable on a specific port from a specific IP/gateway/ENI.
That will let you know whether there is anything up until you instance blocking traffic or if indeed the traffic flows through end to end.
answered a year ago
0
The issue has resolved by itself after I created an image of the instance (I attempted to just launch another instance instead of thinking what's wrong with the old one). And after I created the image, the website suddenly can be accessed. I have no idea why and how but think it's a good idea to leave this piece of information in case any one facing the same situation and needing a solution. Thanks!
answered a year ago
Relevant content
- asked a year ago
- AWS OFFICIALUpdated 3 months ago
- AWS OFFICIALUpdated 2 years ago
- I host a website on an EC2 instance. How do I allow my users to connect on HTTP (80) or HTTPS (443)?AWS OFFICIALUpdated 2 years ago
Thanks for your kind reply. I tried many different paths, and it seemed like the instance public IP is not reachable in any port (with the detail saying NO_PATH), while the private IP can be reached through port 22 and port 80 (I didn't try 443). The documentation for NO_PATH doesn't seem to be very helpful. Do you have any suggestion for what I can do next?