Internal DNS resolves to wrong IP address

0

Since this morning my EC2 machines in Ohio are unable to connect to the secrets manager: the default us-east-2.compute.internal DNS resolves to a private IP but the connection cannot be established, while it succeeds if I try from my local machine using the public IP address.

$ wget -O- "https://secretsmanager.us-east-2.amazonaws.com/"                    
--2024-03-19 13:06:18--  https://secretsmanager.us-east-2.amazonaws.com/
Resolving secretsmanager.us-east-2.amazonaws.com (secretsmanager.us-east-2.amazonaws.com)... 10.11.10.200, 10.11.1.144, 10.11.13.68
Connecting to secretsmanager.us-east-2.amazonaws.com (secretsmanager.us-east-2.amazonaws.com)|10.11.10.200|:443... ^C

I think some configuration was changed during the night and the DNS is still pointing to the old IP addresses but I have no idea how to refresh them.

Does anyone have a suggestion or experienced a similar problem in the past?

  • please accept the answer if it was useful for you

1개 답변
1

If the SSM service is resolved to Private IP, you have a VPC endpoint for the SSM. You need to check a security group attached to the VPC endpoint.

Check this article as well. It explains the whole configuration way https://repost.aws/knowledge-center/ec2-systems-manager-vpc-endpoints

profile picture
전문가
답변함 4달 전
profile picture
전문가
Artem
검토됨 4달 전
profile picture
전문가
Kallu
검토됨 4달 전

로그인하지 않았습니다. 로그인해야 답변을 게시할 수 있습니다.

좋은 답변은 질문에 명확하게 답하고 건설적인 피드백을 제공하며 질문자의 전문적인 성장을 장려합니다.

질문 답변하기에 대한 가이드라인

관련 콘텐츠