By using AWS re:Post, you agree to the Terms of Use
/Tried everything to connect to EC2 Elastic IP from browser but its erroring out/

Tried everything to connect to EC2 Elastic IP from browser but its erroring out

0

I followed all the instructions found on the AWS user guide to set up the Public IP that is accessible from the web. When I type my Public Elastic IP address on the browser URL. Its saying this site can't be reached. I set up the security groups at instance, VPC, ASL Network level to allow port HTTP, HTTPS, SSH. I even tried turning off windows firewall but then also I am not able to get to the localhost webpage.

I am new to amazon AWS , can any one help me with this?

3 Answers
0

Does your network ACL have all outbound ports open or at least the ephemeral ports 1024-65535? NACLs, unlike Security Groups, are stateless.

answered 3 months ago
0

Few things you can check to make sure you have the correct networking logic running.

  1. Check your subnet route table if you have 0.0.0.0/0 with target (next-hop) pointing to IGW(Internet Gateway). You have to create one if you don't have IGW.
  2. Check the correct subnet association of the route 0.0.0.0/0 is with your subnet. This will make sure your instance can return traffic to the internet.
  3. You can check from you can access internet by ping (default should allow any outbound traffic) any host that is accessible from the internet.

The above steps help you verify the outbound(return) traffic for the request respond. Then you can further check your inbound access control (NACL, SG, Firewall, etc).

One thing keep in mind that if your subnet is private with the use of NAT gateway to access the internet, then your EC2 instance cannot publish the "public IP" even you associated with. You have to use public subnet with IGW.

If you new to AWS Networking, there is a workshop you can take a look and play around to get more experience. https://networking.workshop.aws/

answered 3 months ago
0

Here is an example that creates a publicly reachable EC2 instance. You can set this and then:

  1. Verify you can reach it. If you cannot, then there is likely something outside of AWS that is blocking you
  2. If you can reach it, then compare it to your own configuration to spot the problem
answered 3 months ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions