Error: dynamodb index does not exist

An index that “does not exist” is usually absent from the table your application actually reached, or named differently in the request. Inspect DescribeTable with the application’s credentials, Region, and endpoint before attempting to recreate anything.

1. Compare IndexName against GlobalSecondaryIndexes and LocalSecondaryIndexes. An attribute named status does not automatically create an index named status.
2. Check deployment outputs and migrations. A declared GSI may not have been deployed to this stage, or it may still be CREATING. Wait for the GSI itself to become ACTIVE.
3. If using DynamoDB Local, confirm the same database namespace and endpoint. A local table and an AWS table are separate resources.
4. Treat AccessDeniedException separately: missing permissions do not mean you should create a replacement index.

Once the index exists, Query must use its key schema. GetItem cannot target an index; use Query to find base-table keys and then retrieve the table items as needed. A GSI can be added later, whereas an LSI requires a new table design and data migration.

See secondary index behavior and AWS documentation.