Temporary sessions in DynamoDB have an expiresAt timestamp.
Avoid a scheduled delete job and observe the deletion event when it occurs.
Which feature is most appropriate?
Configure DynamoDB TTL on the expiresAt attribute; account for asynchronous deletion timing.
Detailed explanation
Frequent scans add read and write load and are difficult to scale economically.
Frequent scans add read and write load and are difficult to scale economically.
S3 Lifecycle manages objects and cannot delete DynamoDB items.
S3 Lifecycle manages objects and cannot delete DynamoDB items.
Audit retention does not control item expiration.
Audit retention does not control item expiration.
DynamoDB removes expired items asynchronously without an application-wide scan job.
DynamoDB removes expired items asynchronously without an application-wide scan job.
Check official documentation
Compare the following points with the official documentation.
DynamoDB TTL、期限削除の遅延、Streams連携の公式説明を確認する。
What to confirm
DynamoDB TTLとS3 Lifecycle・Scan削除・監査保持の違いを説明できる。
Key points
- DynamoDB TTL
- Unix epoch
- Expiry
- Streams
Notes
- Environment: AWS公式DEA-C01試験ガイドと各サービスの公式ドキュメントの確認
- Confirm current AWS service behavior in the official DEA-C01 documentation.
Foundation review
Asynchronous deletion
TTL is not an exact-time scheduler, so business expiry and physical deletion are separate.
Application behavior
Reads, streams, and metrics should tolerate an item remaining briefly after its expiry time.