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)
- dynamodb cannot pickle '\_thread.lock' object
- DynamoDB Item Does Not Exist
- DynamoDB Not Supported Requires @DynamoDBTyped Or @DynamoDBTypeConverted
- Boto3 DynamoDB KeyError
- DynamoDB Update Not Working
- dynamodb 1 validation error detected value
- DynamoDB scan limit not working
- dynamodb does not support null values
- dynamodb the parameter cannot be converted to a numeric value
- dynamodb unable to find storage information for property
- a bytes-like object is required not binary dynamodb
- dynamodb system error cloudwatch
- dynamodb cannot read property 's' of undefined
- DynamoDB Missing Authentication Token
- One or more parameter values were invalid: some AttributeDefinitions are not used