A workload frequently reads and writes large temporary intermediate files in one Availability Zone.
Prioritize request performance and low latency while keeping source data in a separate S3 layer.
Which data store is most appropriate?
Consider S3 Express One Zone for a high-frequency, low-latency temporary data layer when the single-AZ constraint is acceptable.
Detailed explanation
Mixing file processing with database transactions increases database and backup pressure.
Mixing file processing with database transactions increases database and backup pressure.
This single-AZ directory-bucket class is designed for frequent, low-latency object access.
This single-AZ directory-bucket class is designed for frequent, low-latency object access.
A queue is for message delivery, not random-access analytical files.
A queue is for message delivery, not random-access analytical files.
Archive retrieval latency is unsuitable for frequently accessed intermediate files.
Archive retrieval latency is unsuitable for frequently accessed intermediate files.
Check official documentation
Compare the following points with the official documentation.
Amazon S3 Express One Zone、Directory Bucket、可用性・料金の公式説明を確認する。
What to confirm
標準S3・アーカイブ・DB・キューと高性能一時ストレージを比較できる。
Key points
- S3 Express One Zone
- Directory bucket
- Low latency
- Temporary data
Notes
- Environment: AWS公式DEA-C01試験ガイドと各サービスの公式ドキュメントの確認
- Confirm current AWS service behavior in the official DEA-C01 documentation.
Foundation review
Tier separation
Use performance storage for regenerable intermediates and durable storage for source records.
Availability trade-off
A single-AZ class requires a copy or regeneration plan when the Availability Zone is unavailable.