TTL attribute setup in DynamoDB - Step-by-Step Execution

Concept Flow - TTL attribute setup

Enable TTL on Table

↓

Specify TTL Attribute Name

↓

DynamoDB Monitors TTL Attribute

↓

Item TTL Timestamp Reached?

No→Wait

Yes↓

DynamoDB Deletes Expired Item

↓

Item Removed from Table

This flow shows how enabling TTL on a DynamoDB table works: you enable TTL, specify the attribute holding expiration time, DynamoDB checks items, and deletes expired ones automatically.

Execution Sample

DynamoDB

aws dynamodb update-time-to-live \
  --table-name MyTable \
  --time-to-live-specification Enabled=true,AttributeName=expireAt

This command enables TTL on 'MyTable' using the attribute 'expireAt' to store expiration timestamps.

Execution Table

Step	Action	TTL Attribute Present?	TTL Timestamp Value	TTL Expired?	Result
1	Enable TTL on table with attribute 'expireAt'	N/A	N/A	N/A	TTL enabled, monitoring starts
2	Insert item with expireAt=1700000000	Yes	1700000000	No (current time < 1700000000)	Item stored, not deleted
3	Insert item without expireAt attribute	No	N/A	N/A	Item stored, TTL ignored
4	Current time reaches 1700000000	Yes	1700000000	Yes	Item deleted automatically
5	Check item without expireAt	No	N/A	N/A	Item remains, no TTL applied

💡 TTL deletes items only when current time >= TTL attribute timestamp; items without TTL attribute remain.

Variable Tracker

Variable	Start	After Step 2	After Step 3	After Step 4	Final
TTL Enabled	false	true	true	true	true
Item1 expireAt	N/A	1700000000	1700000000	deleted	deleted
Item2 expireAt	N/A	N/A	N/A	N/A	exists

Key Moments - 2 Insights

Why doesn't DynamoDB delete items without the TTL attribute?

Because TTL only works on items that have the specified TTL attribute. As shown in execution_table row 3 and 5, items without 'expireAt' are ignored by TTL.

When exactly does DynamoDB delete an item based on TTL?

DynamoDB deletes an item only when the current time is equal or greater than the TTL timestamp in the attribute, as shown in execution_table row 4.

Visual Quiz - 3 Questions

Look at the execution_table, what is the TTL Enabled state after step 2?

A unknown

B false

C true

D not set

💡 Hint

Check variable_tracker row 'TTL Enabled' after step 2

At which step does DynamoDB delete an item due to TTL expiration?

A Step 4

B Step 3

C Step 2

D Step 5

💡 Hint

See execution_table row where 'Result' says 'Item deleted automatically'

If an item has no TTL attribute, what happens to it according to the execution_table?

A It is deleted immediately

B It remains in the table

C It is deleted after some time

D It causes an error

💡 Hint

Look at rows 3 and 5 in execution_table where TTL attribute is missing

Concept Snapshot

Enable TTL on a DynamoDB table by specifying an attribute name.
This attribute holds a Unix epoch timestamp (in seconds) for expiration.
DynamoDB automatically deletes items when current time >= TTL value.
Items without the TTL attribute are not affected.
TTL helps clean up expired data without manual deletion.

Full Transcript

This visual execution trace shows how TTL attribute setup works in DynamoDB. First, TTL is enabled on a table with a chosen attribute name, for example 'expireAt'. When items are inserted, if they have this attribute with a timestamp in the future, they remain stored. If the timestamp is reached or passed, DynamoDB automatically deletes the item. Items without the TTL attribute are ignored by TTL and stay in the table. The execution table walks through enabling TTL, inserting items with and without TTL attribute, and the automatic deletion process when the TTL expires. The variable tracker shows the TTL enabled state and item attribute values changing over steps. Key moments clarify why items without TTL attribute are not deleted and when deletion happens. The quiz tests understanding of TTL enabled state, deletion timing, and behavior for items missing TTL attribute. The snapshot summarizes the TTL setup and behavior simply.