Application logs must be aggregated in S3 with near-real-time delivery.
Avoid operating custom consumers and buffer or retry code.
Which service is most appropriate?
Use an Amazon Data Firehose delivery stream with S3 as the destination.
Detailed explanation
Firehose buffers incoming records and manages delivery, retries, and optional transformation.
Firehose buffers incoming records and manages delivery, retries, and optional transformation.
This can work, but it adds responsibility for buffering, delivery retries, and consumer operations.
This can work, but it adds responsibility for buffering, delivery retries, and consumer operations.
The application must manage connections, batching, retries, and scaling, which conflicts with low operational overhead.
The application must manage connections, batching, retries, and scaling, which conflicts with low operational overhead.
DMS is intended for data-store migration and replication, not general application-event delivery.
DMS is intended for data-store migration and replication, not general application-event delivery.
Check official documentation
Compare the following points with the official documentation.
Amazon Data FirehoseのS3配信、バッファ、再試行の公式説明を確認する。
What to confirm
ストリーム保持基盤と、宛先配信をマネージドで行うサービスを使い分けられる。
Key points
- Amazon Data Firehose
- S3 delivery
- Buffering
- Operational overhead
Notes
- Environment: AWS公式DEA-C01試験ガイドと各サービスの公式ドキュメントの確認
- Confirm current AWS service behavior in the official DEA-C01 documentation.
Foundation review
Delivery versus stream
Firehose focuses on destination delivery; Data Streams focuses on retained records and custom consumers.
Operational boundary
Managed buffering and retries reduce application code but still require destination and error-prefix planning.