The sort key can be string, number, or binary table attributes. The partition key of the index is an attribute shared with the table partition key. The index partition key and sort key can consist of string, number, or binary table attributes. It uses a simple or composite primary key. Consider the differences between the two presented in the following table − Quality The best type of index to use depends on application needs. Its “local” nature results from all of its partitions scoping to a table partition with identical partition key value. Local Secondary Index − This index shares a partition key with the table, but uses a different sort key. It uses the label “global” due to the capability of queries/scans on the index to span all table data, and over all partitions. Global Secondary Index − This index includes a partition key and sort key, which may differ from the source table. On item operations, such as adding or deleting, it updates any indexes on the target table.ĭynamoDB offers two types of secondary indexes −

After performing these tasks, you simply use a query/scan as if performing on a table.ĭynamoDB automatically maintains all secondary indices. DynamoDB then performs a copy of the attributes into the index, including primary key attributes sourced from the table. In creation, you define an alternate key for the index, and any attributes you wish to project in the index. Its contents include attributes you project or copy. You use it through either a query or scan operation, which targets the index.

Secondary IndexĪ secondary index holds an attribute subset and an alternate key. They accelerate application accesses and data retrieval, and support better performance by reducing application lag.

DynamoDB uses indexes for primary key attributes to improve accesses.

Local dynamodb rebuild indices