Error: dynamodb botocore.exceptions.nocredentialserror unable to locate credentials

Answered by Rafal Wilinski
What's Causing This Error
You may run into this error when the AWS SDK cannot locate your AWS credentials (AWS Access Key and Secret Access Key).
Solution: Here's How To Resolve It
There is no well-defined way to solve the error. However, you can try the following to see which works for you.
- Ensure that your AWS credentials (access key and secret key) are set up correctly and have the correct permissions to access DynamoDB and execute the operation you wish to perform.
- You can also check the credentials file (usually located at
~/.aws/credentials) to ensure that it contains the correct access and secret keys. - If you are running your application on an EC2 instance or Lambda, you can also check that the IAM Role attached to the service has an identity-based policy that allows it to access DynamoDB.
- Ensure that the region you are trying to access DynamoDB is the same as the region in which the credentials are created.
- Make sure that the certificates you are using are not expired.
Other Common DynamoDB Errors (with Solutions)
- dynamodb local unable to open database file
- DynamoDB is missing the key id in the item
- dynamodb unable to parse base64 string
- dynamodb value cannot be null. (parameter 'type')
- dynamodb streams missing events
- dynamodb unable to execute http request
- DynamoDB local error unable to access JAR file dynamodblocal.jar
- DynamoDB error 400
- DynamoDB consistent read not working
- DynamoDB type is not supported
- dynamodb global secondary index not working
- DynamoDB batch write is not working
- DynamoDB stream not working
- com amazonaws services dynamodbv2 model resourcenotfoundexception
- failed to list tables not authorized dynamodb
Login to the AWS Console less. Use Dynobase.
First 7 days are on us. No strings attached.
Product Features
DynamoDB Tools
DynamoDB Info
© 2026 Dynobase