Trouble with s3: Failed to open TCP connection to 169.254.169.254 due to missing secret access key

The AWS client is attempting to connect to the EC2 metadata service to retrieve its instance profile credentials.

If that worked, it would then use these credentials to attempt to connect to the bucket.

But, it can’t connect to the metadata service. It isn’t even trying to connect to the bucket yet, it’s failing before that.

Is this on AWS? If not, that explains why it can’t talk to the metadata service.

The new install does not see any credentials, that’s why the AWS SDK is attempting to connect to the metadata service to retrieve them.

1 Like