Time to live (TTL) for expiration in AWS - Step-by-Step Execution

Process Flow - Time to live (TTL) for expiration

Set TTL attribute on item

↓

Item stored in database

↓

Time passes

↓

Check current time vs TTL

↓

Delete item

↓

Item removed from DB

This flow shows how an item with a TTL attribute is stored, checked over time, and deleted automatically when expired.

Execution Sample

AWS

PutItem with TTL=1672531199
Wait time passes
DynamoDB checks TTL
If current time > TTL, delete item

Stores an item with a TTL timestamp; DynamoDB automatically deletes it after expiration.

Process Table

Step	Action	TTL Value	Current Time	Expired?	Result
1	Put item with TTL	1672531199	1672530000	No	Item stored
2	Time passes	1672531199	1672531198	No	Item remains
3	Time passes	1672531199	1672531200	Yes	Item deleted
4	Check after deletion	1672531199	1672531300	Yes	Item not found

💡 Item deleted when current time exceeds TTL value

Status Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	Final
TTL	null	1672531199	1672531199	1672531199	1672531199
Current Time	null	1672530000	1672531198	1672531200	1672531300
Item Exists	No	Yes	Yes	No	No

Key Moments - 3 Insights

Why does the item still exist at step 2 even though TTL is set?

Because the current time (1672531198) is still less than the TTL (1672531199), so the item is not expired yet (see execution_table row 2).

What happens exactly when current time passes TTL?

At step 3, when current time (1672531200) exceeds TTL (1672531199), DynamoDB deletes the item automatically (see execution_table row 3).

Does TTL delete the item immediately at expiration time?

TTL deletion is automatic but may not be instantaneous; DynamoDB runs background checks and deletes expired items shortly after TTL passes.

Visual Quiz - 3 Questions

Look at the execution table, what is the 'Item Exists' state at step 3?

A Unknown

B Yes

C No

D Pending

💡 Hint

Check the 'Result' column at step 3 in the execution_table.

At which step does the current time first exceed the TTL?

A Step 3

B Step 2

C Step 1

D Step 4

💡 Hint

Compare 'Current Time' and 'TTL Value' columns in execution_table rows.

If the TTL was set to a later time, how would the 'Item Exists' state change at step 3?

A It would still be 'No'

B It would be 'Yes'

C It would be 'Unknown'

D It would be 'Pending'

💡 Hint

Refer to variable_tracker and execution_table to see how TTL affects item existence.

Concept Snapshot

Time to Live (TTL) sets an expiration timestamp on data.
Data remains until current time passes TTL.
After expiration, data is deleted automatically.
TTL helps clean up old data without manual deletion.
Set TTL as a Unix timestamp attribute on items.

Full Transcript

Time to live (TTL) in AWS DynamoDB is a way to automatically delete items after a set expiration time. When you store an item, you add a TTL attribute with a timestamp. DynamoDB checks this timestamp against the current time. If the current time is greater than the TTL, the item is deleted automatically. This process helps keep your database clean by removing old or unused data without manual intervention. The deletion happens shortly after expiration, not exactly at the TTL time. This visual trace shows the item stored with TTL, time passing, and the item being deleted once expired.

Practice

1. What is the main purpose of Time to Live (TTL) in AWS DynamoDB?

easy

A. Backup data to another region

B. Encrypt data at rest for security

C. Automatically delete expired items to save storage space

D. Increase read capacity for faster queries

Solution

1. Step 1: Understand TTL function

   TTL is designed to remove items automatically after a set expiration time.

2. Step 2: Identify the main benefit

   This automatic deletion helps save storage space and reduces manual cleanup.

3. Final Answer:

   Automatically delete expired items to save storage space -> Option C

4. Quick Check:

   TTL purpose = automatic deletion [OK]

Hint: TTL deletes expired data automatically to save space [OK]

Common Mistakes:

• Confusing TTL with encryption
• Thinking TTL backs up data
• Assuming TTL improves query speed

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

easy

A. Number representing Unix epoch time in seconds

B. Binary data with expiration timestamp

C. Boolean indicating expired or not

D. String containing date in ISO format

Solution

1. Step 1: Check TTL attribute requirements

   DynamoDB TTL requires a Number attribute representing expiration time as Unix epoch seconds.

2. Step 2: Eliminate other types

   String, Boolean, or Binary types are not valid for TTL expiration timestamps.

3. Final Answer:

   Number representing Unix epoch time in seconds -> Option A

4. Quick Check:

   TTL attribute = Number (epoch seconds) [OK]

Hint: TTL attribute must be a number with epoch seconds [OK]

Common Mistakes:

• Using string dates instead of numbers
• Setting TTL attribute as Boolean
• Trying to use binary data for TTL

3. Given this DynamoDB item with TTL attribute expireAt: 1700000000 (Unix epoch seconds), what happens when current time is 1700000001?

medium

A. Item remains until manually deleted

B. Item's TTL attribute is reset to current time

C. Item is archived to S3 automatically

D. Item is immediately deleted by DynamoDB TTL process

Solution

1. Step 1: Compare current time with TTL value

   The current time (1700000001) is greater than the TTL attribute (1700000000), so the item is expired.

2. Step 2: Understand TTL behavior on expiration

   DynamoDB TTL automatically deletes expired items shortly after expiration time passes.

3. Final Answer:

   Item is immediately deleted by DynamoDB TTL process -> Option D

4. Quick Check:

   Current time > TTL = item deleted [OK]

Hint: Item deletes soon after TTL time passes [OK]

Common Mistakes:

• Thinking TTL deletes instantly at exact second
• Assuming manual deletion is needed
• Believing TTL archives data instead of deleting

4. You enabled TTL on attribute expiry but items are not deleting after expiration. What is the most likely cause?

medium

A. DynamoDB table is in a different region

B. TTL attribute expiry is missing or has wrong data type

C. TTL only works on primary key attributes

D. TTL requires manual activation every 24 hours

Solution

1. Step 1: Check TTL attribute correctness

   If the TTL attribute is missing or not a Number with epoch seconds, TTL won't delete items.

2. Step 2: Verify other options

   TTL works regardless of region, does not require manual activation, and does not need to be primary key.

3. Final Answer:

   TTL attribute expiry is missing or has wrong data type -> Option B

4. Quick Check:

   Wrong TTL attribute = no deletion [OK]

Hint: TTL attribute must exist and be correct type [OK]

Common Mistakes:

• Thinking TTL depends on table region
• Believing TTL needs manual daily activation
• Assuming TTL attribute must be primary key

5. You want to store session data that expires exactly 30 minutes after creation using DynamoDB TTL. Which approach correctly sets the TTL attribute?

hard

A. Set TTL attribute to current Unix epoch time in seconds plus 1800 seconds

B. Set TTL attribute to current time as ISO string plus 30 minutes

C. Set TTL attribute to Boolean true when session expires

D. Set TTL attribute to current Unix epoch time in milliseconds plus 1800000

Solution

1. Step 1: Calculate TTL value correctly

   TTL attribute must be a Number in seconds, so add 1800 seconds (30 minutes) to current epoch seconds.

2. Step 2: Eliminate incorrect formats

   ISO strings, Booleans, or milliseconds are invalid for TTL attribute in DynamoDB.

3. Final Answer:

   Set TTL attribute to current Unix epoch time in seconds plus 1800 seconds -> Option A

4. Quick Check:

   TTL = epoch seconds + 1800 [OK]

Hint: TTL value = current epoch seconds + 1800 for 30 minutes [OK]

Common Mistakes:

• Using ISO date strings instead of epoch seconds
• Using milliseconds instead of seconds
• Setting TTL as Boolean instead of number