Store images and PDFs associated with customer records.
Keep database backups and I/O manageable while serving files over HTTP.
Which configuration is most appropriate?
Store object bodies in S3 and keep customer IDs, S3 keys, and searchable attributes in RDS.
Detailed explanation
S3 handles large objects while RDS handles searchable relationships and metadata.
S3 handles large objects while RDS handles searchable relationships and metadata.
SQS is for message delivery and is not a durable random-access object store.
SQS is for message delivery and is not a durable random-access object store.
Operational logs are not an appropriate high-volume file store.
Operational logs are not an appropriate high-volume file store.
Large binaries increase database size, backup cost, I/O, and delivery overhead.
Large binaries increase database size, backup cost, I/O, and delivery overhead.
Check official documentation
Compare the following points with the official documentation.
Amazon S3オブジェクト、RDSメタデータ設計、署名付きURLの公式説明を確認する。
What to confirm
BLOBをDBへ埋め込む方式と、オブジェクト・メタデータ分離を比較できる。
Key points
- S3 objects
- RDS metadata
- Object separation
- HTTP delivery
Notes
- Environment: AWS公式DEA-C01試験ガイドと各サービスの公式ドキュメントの確認
- Confirm current AWS service behavior in the official DEA-C01 documentation.
Foundation review
Body and metadata
Separate file delivery and lifecycle from transactional lookup and relationship management.
Backup boundary
Keeping large binaries outside the database reduces backup and operational pressure.