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 is abstract cannot be instantiated
- DynamoDB No Provisioned Throughput specified for the table
- dynamodb cannot read property '0' of undefined
- DynamoDB Scan Not Working
- appsync dynamodb not seeing all fields
- DynamoDB Key element does not match the schema
- failed to begin subsegment named 'amazondynamodbv2': segment cannot be found.
- dynamodb ttl not deleting / erasing items
- dynamodb items page not authorized with read access
- DynamoDB Failed To Compute Node presentation
- DynamoDB Internal Server Error
- sls dynamodb install not working
- dynamodb-admin command not found
- boto3 dynamodb unable to locate credentials
- DynamoDB Code Working In Node But Not SAM
Login to the AWS Console less. Use Dynobase.
Start your 7-day free trial today
Product Features
DynamoDB Tools
DynamoDB Info
© 2025 Dynobase