How do I troubleshoot the "ResourceNotFoundException" error in DynamoDB?

Short description

DynamoDB responds with the ResourceNotFoundException when the operation or API tries to access a table or index that doesn't exist. The resource might not be correctly specified, or the status of the resource might not be ACTIVE.

To resolve this error in DynamoDB, complete the following tasks:

• Check the state of the table or index
• Change your AWS Account and AWS Region
• Update your request

Based on your setup, you can use the DynamoDB console, AWS Command Line Interface (AWS CLI), or AWS SDK to complete these tasks.

Resolution

Note: If you receive errors when you run AWS CLI commands, then see Troubleshoot AWS CLI errors. Also, make sure that you're using the most recent AWS CLI version.

To troubleshoot the ResourceNotFoundException error, complete the following tasks.

Check the state of the table or index

While the DynamoDB table or index is in the CREATING state, you might get the error when you try to access the table or index. To resolve this issue, wait for the table or index to be in an ACTIVE state. For more information, see DynamoDBClient on the AWS SDK for JavaScript v3 website.

Change your Account or Region

If the table doesn't exist in the Account or Region that you try to access it from, then you might get the error. Before you request information from a table of index, make sure to select the correct Account or Region. Or, make sure that you have the appropriate cross-account permissions to access the table or index.

Update your request

If the table name for your request is misspelled or isn't case-sensitive, then you might get the error. Make sure that your request parameters are correct. If you use the AWS SDK or the AWS CLI, then make sure your request uses the correct Region and configurations.

Related information

Best practices for designing and architecting with DynamoDB

Requesting a table import in DynamoDB