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
feita há 7 meses446 visualizações
1 Resposta
1
Resposta aceita

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
respondido há 7 meses
profile picture
ESPECIALISTA
avaliado há 7 dias
profile picture
ESPECIALISTA
avaliado há 2 meses
profile pictureAWS
ESPECIALISTA
avaliado há 7 meses
  • If you have vpc endpoints you’ll want private dns names. S3 gateway endpoint behaves differently.

Você não está conectado. Fazer login para postar uma resposta.

Uma boa resposta responde claramente à pergunta, dá feedback construtivo e incentiva o crescimento profissional de quem perguntou.

Diretrizes para responder a perguntas