Key points

• Firehose is delivery-oriented and minimizes administration of scaling, buffering, and destination retries.
• Buffering affects delivery latency and object size; it is not a custom replayable stream for arbitrary consumers.
• Protect producer access and destination roles, and monitor failed or backed-up delivery.

Best-known use cases

• Deliver logs or events continuously to S3 and other supported analytics destinations.
• Build low-operations streaming delivery when custom consumer control is unnecessary.

What candidates often confuse it with

• Firehose manages destination delivery; Kinesis Data Streams provides retained records and custom consumers/replay.
• Firehose moves stream data to destinations; SQS buffers discrete work for workers.

Key takeaway

Use Data Firehose when managed streaming delivery matters more than custom stream-consumer control.

Related services

• Amazon Kinesis
• Amazon S3
• AWS Glue

Relevant exam tasks

• D3.5

Learn more

• Amazon Data Firehose