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.

您尚未登入。 登入 去張貼答案。

一個好的回答可以清楚地回答問題並提供建設性的意見回饋,同時有助於提問者的專業成長。

回答問題指南