Raw data is read frequently during its first month but rarely after 90 days.
Retain it for seven years and reduce storage cost as access frequency falls.
Which configuration is most appropriate?
Use an S3 Lifecycle rule to transition objects by age or tag to lower-cost storage classes and expire them after retention.
Detailed explanation
The workload continues paying the frequent-access price after reads have declined.
The workload continues paying the frequent-access price after reads have declined.
DynamoDB TTL applies to items and does not transition S3 objects.
DynamoDB TTL applies to items and does not transition S3 objects.
Objects can move by age or tags to Standard-IA or Glacier classes and later expire.
Objects can move by age or tags to Standard-IA or Glacier classes and later expire.
Audit retention does not alter an S3 object's storage class.
Audit retention does not alter an S3 object's storage class.
Check official documentation
Compare the following points with the official documentation.
Amazon S3 Lifecycle、Storage Class、Transition、Expirationの公式説明を確認する。
What to confirm
S3オブジェクトとDynamoDB項目・監査ログのライフサイクルを区別できる。
Key points
- S3 Lifecycle
- Storage class
- Transition
- Expiration
Notes
- Environment: AWS公式DEA-C01試験ガイドと各サービスの公式ドキュメントの確認
- Confirm current AWS service behavior in the official DEA-C01 documentation.
Foundation review
Cost by access
Frequent access and archival access have different cost and retrieval trade-offs.
Retention boundary
Expiration must not remove data before legal, business, or recovery requirements are met.