Error: resourcenotfoundexception dynamodb nodejs
Answered by Rafal Wilinski
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)
- aws.dynamodb.documentclient is not a constructor
- DynamoDB sorting is not supported for scan expressions
- DynamoDB error cannot find module build/Release/DTraceProviderBindings
- dynamodb ttl not deleting / erasing items
- KMS Key Access Denied Error DynamoDB
- requested resource not found aws dynamodb
- ImportError: No module named boto3 (DynamoDB)
- DynamoDB Local Missing Authentication Token
- lambda function not triggering from dynamodb
- could not unmarshal the value dynamodb
- could not load profile default dynamodb
- DynamoDB Auto Scaling Not Working
- dynamodb docker unable to open database file
- CORS Error DynamoDB
- name key is not defined dynamodb