TTL behavior and timing in DynamoDB - Step-by-Step Execution

Concept Flow - TTL behavior and timing

Item with TTL attribute set

↓

Current time passes

↓

TTL timestamp reached?

No→Item remains

Yes↓

DynamoDB marks item expired

↓

Background process deletes item

↓

Item removed from table

Items with TTL attribute are checked against current time; when expired, DynamoDB marks them and later deletes them asynchronously.

Execution Sample

DynamoDB

PutItem with TTL=1672531200
Wait current time > 1672531200
Check if item exists
Background deletes expired item

Shows how an item with a TTL timestamp is eventually deleted after expiration time passes.

Execution Table

Step	Current Time (Unix)	TTL Attribute	TTL Expired?	Action	Item State
1	1672530000	1672531200	No (1672530000 < 1672531200)	Item remains	Exists
2	1672531200	1672531200	Yes (1672531200 >= 1672531200)	Marked expired by DynamoDB	Exists but expired
3	1672531300	1672531200	Yes	Background process deletes item	Deleted
4	1672531400	1672531200	Yes	No item found	Deleted

💡 Item deleted after TTL timestamp passed and background process removed it

Variable Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	Final
Current Time	1672530000	1672530000	1672531200	1672531300	1672531400
Item State	Exists	Exists	Exists but expired	Deleted	Deleted

Key Moments - 3 Insights

Why doesn't the item get deleted exactly at the TTL timestamp?

Because DynamoDB deletes expired items asynchronously in the background, not immediately at the TTL time (see execution_table steps 2 and 3).

What happens if the current time is less than the TTL attribute?

The item remains in the table and is not deleted (see execution_table step 1).

Can you rely on TTL to delete items instantly after expiration?

No, TTL deletion timing is approximate and depends on background processing, so items may persist briefly after expiration (see execution_table step 3).

Visual Quiz - 3 Questions

Look at the execution_table, at which step does DynamoDB mark the item as expired?

A Step 1

B Step 3

C Step 2

D Step 4

💡 Hint

Check the 'Action' column for when the item is marked expired.

According to variable_tracker, what is the item state after step 3?

A Exists

B Deleted

C Exists but expired

D Not created yet

💡 Hint

Look at the 'Item State' row under 'After Step 3'.

If the current time never reaches the TTL timestamp, what will happen to the item?

A It will remain in the table

B It will be deleted immediately

C It will be marked expired but not deleted

D It will cause an error

💡 Hint

Refer to execution_table step 1 where TTL expired is 'No'.

Concept Snapshot

TTL (Time To Live) in DynamoDB lets you set an expiration timestamp on items.
DynamoDB checks current time against TTL attribute.
When expired, items are marked and deleted asynchronously.
Deletion timing is approximate, not immediate.
Items remain until background process removes them.

Full Transcript

This visual execution shows how DynamoDB TTL works. An item is created with a TTL attribute set to a future Unix timestamp. As time passes, DynamoDB compares the current time to the TTL. Before the TTL time, the item remains in the table. When the current time reaches or passes the TTL, DynamoDB marks the item as expired. However, the item is not deleted instantly. Instead, a background process later deletes the expired item asynchronously. This means there can be a delay between expiration and deletion. The execution table traces these steps with current time, TTL check, actions taken, and item state. The variable tracker shows how current time and item state change over steps. Key moments clarify common confusions about TTL timing and deletion behavior. The quiz tests understanding of when marking and deletion happen and what occurs if TTL is not reached. The snapshot summarizes TTL behavior as approximate expiration and asynchronous deletion in DynamoDB.