Error: dynamodb index not found

“Index not found” means the query target and the deployed index metadata do not agree. First identify whether the response is a DynamoDB service error or a wrapper’s message. Then inspect the exact table the client is using.

aws dynamodb describe-table --table-name Orders --region us-east-1 \
  --query 'Table.{Arn:TableArn,Indexes:GlobalSecondaryIndexes[*].{Name:IndexName,Status:IndexStatus},Local:LocalSecondaryIndexes[*].IndexName}'

Use the returned index name verbatim. Do not pass the index ARN, a table name, or a key attribute name as IndexName. If the GSI is being created, wait for IndexStatus=ACTIVE. If it is absent, check deployment events rather than repeatedly retrying the same query.

A table with the same name in another account, Region, or local endpoint can have different indexes. Use the application’s identity for diagnosis. An authorization denial needs a policy fix, while an empty successful Query means the index exists but no visible item matched. These outcomes require different fixes.

See GSI queries and AWS documentation.