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.

Practice

1. What does TTL (Time To Live) do in DynamoDB?

easy

A. Encrypts data stored in the table.

B. Backs up data periodically.

C. Automatically deletes items after their expiration time.

D. Indexes data for faster queries.

Solution

1. Step 1: Understand TTL purpose

   TTL is designed to remove expired data automatically to save storage and keep data fresh.

2. Step 2: Identify TTL behavior

   It deletes items after their expiration timestamp passes, not encrypting or backing up data.

3. Final Answer:

   Automatically deletes items after their expiration time. -> Option C

4. Quick Check:

   TTL = automatic deletion [OK]

Hint: TTL means automatic deletion after expiry [OK]

Common Mistakes:

• Thinking TTL encrypts data
• Confusing TTL with backup
• Assuming TTL speeds up queries

2. Which attribute type must the TTL attribute have in DynamoDB?

easy

A. String representing a date in ISO format

B. Number representing Unix epoch time in seconds

C. Boolean indicating if item is expired

D. List of timestamps

Solution

1. Step 1: Recall TTL attribute format

   The TTL attribute must be a number storing the expiration time as Unix epoch seconds.

2. Step 2: Eliminate other types

   Strings, booleans, or lists are not valid for TTL expiration timestamps.

3. Final Answer:

   Number representing Unix epoch time in seconds -> Option B

4. Quick Check:

   TTL attribute = Unix epoch seconds [OK]

Hint: TTL attribute stores expiration as Unix epoch seconds [OK]

Common Mistakes:

• Using string dates instead of numbers
• Using boolean instead of timestamp
• Trying to store multiple timestamps

3. If an item has a TTL attribute set to 1650000000 (Unix epoch seconds), when will DynamoDB delete it?

medium

A. Within 48 hours after 1650000000 seconds

B. Exactly at 1650000000 seconds

C. Immediately after setting the TTL attribute

D. Only when manually deleted

Solution

1. Step 1: Understand TTL deletion timing

   DynamoDB deletes expired items approximately after the TTL timestamp, not exactly at that second.

2. Step 2: Recall deletion delay

   Deletion can take up to 48 hours after the expiration time to occur.

3. Final Answer:

   Within 48 hours after 1650000000 seconds -> Option A

4. Quick Check:

   TTL deletion delay = up to 48 hours [OK]

Hint: TTL deletion can be delayed up to 48 hours [OK]

Common Mistakes:

• Expecting deletion exactly at expiration time
• Thinking deletion is immediate
• Assuming manual deletion is required

4. You set TTL on an attribute but notice expired items are not deleted after 3 days. What is a likely cause?

medium

A. TTL attribute is not a number with Unix epoch seconds

B. TTL is enabled but the table is in a different AWS region

C. You forgot to enable encryption on the table

D. The table has no primary key

Solution

1. Step 1: Check TTL attribute format

   If the TTL attribute is not a number with Unix epoch seconds, DynamoDB ignores it for expiration.

2. Step 2: Verify other options

   Region difference, encryption, or primary key absence do not prevent TTL deletion.

3. Final Answer:

   TTL attribute is not a number with Unix epoch seconds -> Option A

4. Quick Check:

   TTL attribute format error blocks deletion [OK]

Hint: TTL attribute must be Unix epoch number [OK]

Common Mistakes:

• Assuming region affects TTL
• Thinking encryption affects TTL
• Ignoring TTL attribute data type

5. You want to ensure items expire exactly after 24 hours using TTL. Which approach is best considering DynamoDB's TTL behavior?

hard

A. Disable TTL and run a scheduled job to delete expired items

B. Set TTL attribute to current time + 86400 seconds and manually delete items after 24 hours

C. Use a string date format for TTL attribute for precise timing

D. Set TTL attribute to current time + 86400 seconds and accept up to 48-hour deletion delay

Solution

1. Step 1: Understand TTL timing limits

   DynamoDB TTL deletes items approximately after expiration, with up to 48 hours delay.

2. Step 2: Choose best practical approach

   Setting TTL attribute to current time + 86400 seconds (24 hours) is correct; manual deletion adds complexity and string format is invalid.

3. Step 3: Consider alternatives

   Disabling TTL and scheduling deletes is possible but less efficient than TTL's automatic deletion.

4. Final Answer:

   Set TTL attribute to current time + 86400 seconds and accept up to 48-hour deletion delay -> Option D

5. Quick Check:

   TTL delay means accept approximate expiry [OK]

Hint: TTL deletion timing is approximate, plan accordingly [OK]

Common Mistakes:

• Expecting exact deletion timing
• Using string instead of number for TTL
• Disabling TTL unnecessarily