Table settings

Table settings is where you change everything DynamoDB lets you change on an existing table: capacity mode, throughput, TTL, streams and deletion protection.

Opening table settings

Right-click a table in the table list and choose Settings. The modal loads the table’s current configuration and seeds each control from it.

At the top, a read-only summary shows the table’s keys (🔑 PK, 🔸 SK), item count and size on disk.

Each section has its own apply button — you change one section and apply it independently, without touching the others.

Deletion protection

🔒 Blocks DeleteTable until you turn it off. The card shows the current state (activated / deactivated) and a button to toggle it. This is the same flag offered at create time and surfaced in the schema view.

Capacity mode

⚡ Switch between:

• On-demand (PAY_PER_REQUEST)
• Provisioned — reveals RCU and WCU inputs (minimum 1 each)

The card shows the current mode. Adjust and click apply; a ✓ confirms success.

TTL (time-to-live)

⏱ Toggle TTL on or off and name the attribute that holds the expiry timestamp.

• The attribute value must be a Unix epoch in seconds; items past that time are deleted by DynamoDB automatically.
• Turn the toggle on, enter the attribute (e.g. expiresAt), and apply.

On AWS, enabling/disabling TTL can take up to ~1h to take effect, and AWS enforces a cooldown between TTL changes. If you change TTL again too soon, Tablyne shows a friendly note explaining the cooldown — wait and retry. On DynamoDB Local it’s effectively instant.

DynamoDB Streams

🌊 Enable a change stream that captures INSERT / MODIFY / REMOVE events in order. When enabled, pick a view type:

View type	Captured
NEW_AND_OLD_IMAGES	both before and after images (default)
NEW_IMAGE	item after the change
OLD_IMAGE	item before the change
KEYS_ONLY	only the key attributes

Apply to save. To actually read the stream, use the Streams panel.

What can’t be edited here

Two things are intentionally not editable from this modal because DynamoDB’s API doesn’t allow it on an existing table:

• Key schema (PK/SK names and types) — fixed at creation; restructuring requires a new table and a migration.
• GSIs — adding or dropping a Global Secondary Index is a separate operation. See Indexes & GSIs.

A note at the bottom of the modal reminds you of this.

How applies behave

Each section issues a single, scoped update so you never accidentally revert another section. After an apply succeeds, the underlying schema is re-read — but Tablyne is careful to seed the form only once per table, so an apply on one section won’t snap your unsaved changes in another section back to server state.

For the concepts behind these settings, see the table-settings learn guide. To delete or empty a table instead, see Deleting & truncating tables.