What's Causing This Error
This error occurs in Node.js when you are trying to access a DynamoDB table, GSI, or LSI that does not exist is being created or is in a different region.
Solution - Here's How To Resolve It
You can try the following solutions and see what works for you.
1. Verify Region Validity
Verify that the region you provide while initializing the SDK is the same region on which you have provisioned the DynamoDB tables.
2. Verify Resource Name
Verify that you provide the correct table, LSI, or GSI name for the DynamoDB resource. You can confirm it by visiting the DynamoDB console.
3. Verify Creation Status
Ensure that the table has already been created. For example, if the table, LSI, or GSI is in the "CREATING" status, you will run into this error.
Figure - Observing the table status in the DynamoDB console
Other Common DynamoDB Errors (with Solutions)
- DynamoDB string set may not be empty
- Unable to start DynamoDB Local process
- DynamoDB Error Message KeyError item is not JSON serializable
- DynamoDB Local Missing Authentication Token
- DynamoDB error cannot find module build/Release/DTraceProviderBindings
- dynamodb cannot read properties of undefined
- dynamodb converter not found for enhancedtype
- dynamodb query is not null
- could not connect to the endpoint URL dynamodb
- failed to list tables not authorized dynamodb
- DynamoDB Error 413
- can't pickle thread.lock objects typeerror boto3 python dynamodb
- aws lambda dynamodb nodejs not working after few puts
- dynamodb user errors metric
- dynamodb the table does not have the specified index