07:10:41,609 - MainThread - botocore.utils - DEBUG - Caught exception while trying to retrieve credentials: HTTPConnectionPool(host='169.254.169.254', port=80): Max retries exceeded with url: /latest/meta-data/iam/security-credentials/ (Caused by ConnectTimeoutError(, 'Connection to 169.254.169.254 timed out. It runs it under the Docker Network that was created by. What this command is doing is that it’s running a container based of the amazon/dynamodb-local image. 07:10:40,606 - MainThread - botocore.credentials - DEBUG - Looking for credentials via: iam-role To create the DynamoDB container we need to run this command: docker run -d -p 8000:8000 -networklocal-api-network -name dynamo-local amazon/dynamodb-local. The error in the debug dump shows the following: The aws s3 command works 100% of the time but the aws ssm get-paramater doesn't.Īnd for the truly confusing part, If I wait for it to complete the spin up process and ssh into the machine and run the command manually it works!
Awscli credentials for local dynamodb install#
Pip install https: //s3./cloudformation-examples/Īpt install -y php7.2 php7.2-fpm php7.2-bcmath php7.2-curl php7.2-mysql php7.2-mbstring php7.2-xml php7.2-zip I have a autoscaling policy that spins up a bunch of ec2 instances and runs the following user data: Not sure if anyone else had any similar experiences or can recommend any additional research I can do to discover why this suddenly started happening.
The issue appears to be intermittent as other instances launched today via the same cloud-formation script, using the same IAM role and launched from the same AMI have worked properly. It was in this short bootstrap script where the log showed the "Unable to locate credentials" error and the CF launch failed.
Awscli credentials for local dynamodb download#
All used a short bootstrap script passed in via cloud-formation UserData whose sole purpose was to download a larger script from s3 during init. We've had multiple ec2 instances encountering an "Unable to locate credentials" error today when trying to execute the AWS CLI (aws s3 cp) despite the instance being launched with an IAM role that grants appropriate policies and had worked without issue prior to today.Įach instance that exhibited the issue had the expected IAM role displayed on the Console Instance Description screen.
0 kommentar(er)
