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
已提问 7 个月前446 查看次数
1 回答
1
已接受的回答

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
已回答 7 个月前
profile picture
专家
已审核 7 天前
profile picture
专家
已审核 2 个月前
profile pictureAWS
专家
已审核 7 个月前
  • If you have vpc endpoints you’ll want private dns names. S3 gateway endpoint behaves differently.

您未登录。 登录 发布回答。

一个好的回答可以清楚地解答问题和提供建设性反馈,并能促进提问者的职业发展。

回答问题的准则