2 Answers
- Newest
- Most votes
- Most comments
2
Good morning ;)
You need to associate the Elastic IP with your instance or with the instance's ENI (Elastic Network Interface).
Also your instance needs to be in a public subnet, i.e. one with a route to an IGW (Internet Gateway).
1
- Associate the Elastic IP with Your Instance
- Ensure Security Groups and Network ACLs Allow Traffic
Verify the Association:
- In the Elastic IPs section, verify that the IP is associated with your instance.
- In the Instances section, verify that the Public IP field shows the Elastic IP.
Update DNS Zone:
- In your DNS management console (whether it's Route 53 or another provider), create or update an A record to point to your Elastic IP.
For More Please follow the link https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/elastic-ip-addresses-eip.html
Relevant content
- AWS OFFICIALUpdated 4 years ago
Thank you very much for the response.
However, I have already associated the IP with the instance, and still, I can't figure out what is wrong, but it is not working. Through DNS, it can reach the instance, but even with the public IP, it does not.
Could it be something related to security that I am overlooking?
If the subnet default route is correctly to an IGW, then the problem is likely to be your instance's Security Group or the subnet's NACL. Make sure your Security Group has in inbound (ingress) rule allowing your client address, or 0.0.0.0/0 for the protocol you're using (likely to be TCP/HTTPS, or maybe ICMP if you're trying to ping). Make sure the subnet NACL has a similar ingress rule if it's not simply allowing all traffic. Also, because NACLs are stateless, you need an egress rule for either all traffic or at a minimum the ephemeral port range applicable to the client, typically 1024 to 65535.