Error: requested resource not found aws dynamodb

Answered by Rafal Wilinski
What's Causing This Error
This error occurs due to various reasons. However, in most cases, it happens when the table you are trying to access is either being created or does not exist on DynamoDB in the specified region.
Additionally, you may encounter this error if you use an invalid access key to access the table.
Solution - Here's How To Resolve It
First, visit the DynamoDB console and verify that the table is created to resolve this error. You should see the status as "Active."

Figure - Verifying the status of the table
Then, ensure that the table name specified on your code matches the table name provisioned in your DynamoDB Console.
Finally, ensure that your AWS profile has a valid access key to your table in the given region.
Other Common DynamoDB Errors (with Solutions)
- DynamoDB Invalid UpdateExpression Syntax Error Token
- DynamoDB no attribute schema defined
- DynamoDB Local NoClassDefFoundError
- DynamoDB Internal Server Error
- dynamodb botocore.exceptions.nocredentialserror unable to locate credentials
- AWS Lambda DynamoDB Stream Error
- DynamoDB FilterExpression Not Working
- dynamodb getItem() is not a function
- AWS DynamoDB errors ResourceNotFoundException
- failed to begin subsegment named 'amazondynamodbv2': segment cannot be found.
- DynamoDB Update Not Working
- dynamodb list_append returns true but does not work
- dynamodb put function not working
- CORS Error DynamoDB
- aws.dynamodb.documentclient is not a constructor
Tired of switching accounts and regions? Use Dynobase.
Start your 7-day free trial today
Product Features
DynamoDB Tools
DynamoDB Info
© 2025 Dynobase