Error: dynamodb global secondary index does not project
Answered by Rafal Wilinski
Last updated: October 23rd, 2026
Solution
A global secondary index contains its keys, the base-table primary key and the attributes selected by its projection. Querying that index cannot retrieve arbitrary non-projected attributes from the base table.
Choose KEYS_ONLY, INCLUDE or ALL when creating the index. You cannot change an existing GSI projection with UpdateTable. Either query the index then fetch the base-table items by their full keys, or create a replacement index with the required projection and migrate readers after backfill completes.
Review GSI projections and the AWS GSI guide.
Other Common DynamoDB Errors (with Solutions)
- dynamodb index not found
- dynamodb system errors metric
- dynamodb value cannot be null. (parameter 'type')
- dynamodb global secondary index not working
- DynamoDB Scan Not Working
- an expression attribute name used in the document path is not defined
- dynamodb query key condition not supported
- DynamoDB - The Security Token Included In The Request Is Invalid
- DynamoDB Key element does not match the schema
- dynamodb could not connect to the endpoint url
- dynamodb connection timeout
- DynamoDB BatchWriteItem error
- name key is not defined dynamodb
- DynamoDB aliasing is not supported
- dynamodb botocore.exceptions.nocredentialserror unable to locate credentials
Dynobase is a Professional GUI Client for DynamoDB
Start your 7-day free trial today
Product Features
DynamoDB Tools
- SSH GUI Client
- Chat With Cloud
- MongoDB GUI Client
- AWS Cost Monitoring
- DynamoDB Query Builder
- DynamoDB Code Examples
- DynamoDB Node.js Queries
- DynamoDB JSON Converter
- DynamoDB UUID Generator
- DynamoDB Local Admin GUI
- DynamoDB Pricing Calculator
- DynamoDB Single-Table Design
- Best DynamoDB GUI Clients
- Dynobase vs DynoTable
DynamoDB Info
© 2026 Dynobase