ec2.us-east-1.amazonaws.com endpoint resolving to private IP address

0

While troubleshooting an issue our developers noticed that in one of our subnets ec2.us-east-1.amazonaws.com is resolving to private IP addresses in our subnet instead of the normal public IP addresses. Strangely enough it appears that it is only happening for the ec2.us-east-1.amazonaws.com endpoint. The s3.us-east-1.amazonaws.com resolves correctly as does the ec2.us-east-2.amazonaws.com endpoint.

Is there anything we can do on our end to resolve this other than tearing down this subnet and recreating a new one?

Ray
asked 6 months ago398 views
1 Answer
0
Accepted Answer

I found the answer, it appears that it created a private DNS endpoint to the EC2 instance by default when creating the VPC endpoints. I deleted that private DNS name and it is working now.

Ray
answered 6 months ago
profile picture
EXPERT
reviewed a month ago
profile pictureAWS
EXPERT
reviewed 6 months ago
  • If you have vpc endpoints you’ll want private dns names. S3 gateway endpoint behaves differently.

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