DynamoOps
Schema and infrastructure

Index manager (GSI)

Inspect the primary key, local and global secondary indexes of a table, create new global secondary indexes with any projection, and delete the ones you no longer need.

Opening the Index manager

Click Indexes in the table info bar. The dialog Indexes — <table> lists one card per index.

The Index manager lists the primary key and every secondary index.
CardContents
PRIMARYThe table’s own key schema. Always ACTIVE, cannot be deleted.
LSILocal secondary indexes with their sort key and projection. Read-only: LSIs can only be defined at table creation.
GSIGlobal secondary indexes with live status (CREATING, ACTIVE, UPDATING, DELETING), keys, projection, capacity or On-demand, size and item count, plus a Delete button.

Each card breaks down Keys (partition and sort key with types), Projection (ALL, KEYS_ONLY or INCLUDE with its attribute chips) and Capacity / Size.

Creating a GSI

Click Add Global Secondary Index to switch to the create form.

Creating a GSI with an INCLUDE projection.
Index Nametextrequired
For example email-index. Must be unique within the table.
Partition Keytextrequired
The attribute to index on, with its type (S, N or B).
Sort Keytext
Optional range key for the index, with its type.
Projectionradio
ALL copies every attribute; KEYS_ONLY copies only the index and table keys; INCLUDE copies the keys plus the attributes you list, comma-separated.
  1. Fill in the keys and projection

    Inline validation asks for the name, the partition key and, for INCLUDE, at least one attribute.

  2. Click Create GSI

    DynamoOps sends an UpdateTable with a Create action. The toast reads “GSI creation started — may take a few minutes.” and the list view returns with the new index in CREATING.

  3. Check the status later

    The status is read when the dialog opens or the table is reloaded; reopen the dialog or re-select the table to see it turn ACTIVE. Backfilling a large table can take a long time.

Provisioned tables
The form does not collect provisioned throughput. On tables in PROVISIONED billing mode AWS requires read and write capacity for each GSI, so creation there fails with a validation error; create the index with capacity in the console or IaC instead. On-demand tables work as expected.

Deleting a GSI

Click Delete on an index card, or the ✕ on the index tag in the table info bar. Confirm in the dialog. The toast “GSI deletion started.” appears and the index shows DELETING until AWS finishes.

  • Deleting an index does not touch table data, only the index copy.
  • AWS allows one index create or delete in flight per table; wait for the previous operation to finish.
  • Queries that target the deleted index will fail; check the Query form’s Index selector in open tabs.

Choosing a projection

ProjectionStorage and write costUse when
ALLHighest — every attribute is duplicatedQueries on the index need arbitrary attributes and you want to avoid a second lookup.
KEYS_ONLYLowestYou only need to find keys and then fetch items from the base table.
INCLUDEIn betweenA known handful of attributes satisfies the access pattern.

Related

Query by key and index
Fetch items by partition key, add a sort-key condition with any supported operator, and target global or local secondary indexes without writing an expression.
Export Schema (IaC)
Turn a live table into infrastructure code. Copy its schema as CloudFormation YAML, Terraform HCL or Pulumi TypeScript, including attributes, keys, GSIs, LSIs and TTL.
Sidebar, table info bar and toolbar
Find tables fast, read the key schema and indexes at a glance, and learn what every button in the info bar and toolbar does.
Previous
Truncating and deleting tables
Next
Export Schema (IaC)