Error: AWS DynamoDB errors ResourceNotFoundException

ResourceNotFoundException means DynamoDB cannot find the requested table, index or other resource in the context of the request. A table in a different account, Region or local endpoint is a different resource even when its name matches.

1. Check the exact TableName and IndexName, including capitalization. Use the physical table name from deployment outputs, not the logical infrastructure identifier.
2. Confirm which identity and Region the application actually uses. A terminal profile can differ from a Lambda execution role or a container credential provider.
3. Describe the table using those same settings. After creating it, wait for it to become ACTIVE before reading or writing; for a new GSI, check IndexStatus too.
4. Check endpoint overrides. DynamoDB Local and LocalStack do not share data with the AWS service.

aws sts get-caller-identity --profile app
aws dynamodb describe-table --table-name Orders --profile app --region us-east-1
aws dynamodb wait table-exists --table-name Orders --profile app --region us-east-1

Replace the example profile and Region with the application's settings. If DescribeTable fails with AccessDeniedException instead, investigate IAM permissions separately. Do not grant full access as a fix for a misspelled table name. For a missing stream, compare its ARN with the table's current LatestStreamArn; re-enabling a stream creates a new ARN.

See table creation guidance and AWS documentation.