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
demandé il y a 7 mois446 vues
1 réponse
1
Réponse acceptée

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
répondu il y a 7 mois
profile picture
EXPERT
vérifié il y a 7 jours
profile picture
EXPERT
vérifié il y a 2 mois
profile pictureAWS
EXPERT
vérifié il y a 7 mois
  • If you have vpc endpoints you’ll want private dns names. S3 gateway endpoint behaves differently.

Vous n'êtes pas connecté. Se connecter pour publier une réponse.

Une bonne réponse répond clairement à la question, contient des commentaires constructifs et encourage le développement professionnel de la personne qui pose la question.

Instructions pour répondre aux questions