Store application events in S3 with near-real-time delivery.
Custom consumers and arbitrary-position replay are unnecessary; minimize delivery operations.
Which service is most appropriate?
Use Amazon Data Firehose for managed buffering, delivery, retry, and transformation to S3.
Detailed explanation
OpenSearch is useful for indexed search, not as the managed raw-data delivery path to S3.
OpenSearch is useful for indexed search, not as the managed raw-data delivery path to S3.
Streams are appropriate for multiple consumers and replay positions but require more delivery operations.
Streams are appropriate for multiple consumers and replay positions but require more delivery operations.
Connections, batching, retries, and scaling would be custom work and do not match S3 delivery.
Connections, batching, retries, and scaling would be custom work and do not match S3 delivery.
Firehose manages buffering, retries, and delivery to destinations such as S3.
Firehose manages buffering, retries, and delivery to destinations such as S3.
Check official documentation
Compare the following points with the official documentation.
Amazon Data FirehoseとKinesis Data Streamsの用途・バッファ・保持・コンシューマーの公式説明を確認する。
What to confirm
ストリーム保持基盤と、宛先配信サービスの選定条件を説明できる。
Key points
- Data Firehose
- Buffering
- Delivery stream
- Destination
Notes
- Environment: AWS公式DEA-C01試験ガイドと各サービスの公式ドキュメントの確認
- Confirm current AWS service behavior in the official DEA-C01 documentation.
Foundation review
Delivery versus stream
Firehose simplifies destination delivery; Data Streams provides consumer control and retention.
Retry behavior
Destination errors, buffering, transformation, and duplicate handling should be part of the delivery design.