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?
AWS 공식업데이트됨 2년 전
