You need to deliver streaming clickstream data to S3 with no consumer code to maintain. What fits best?
Why C is the answer
Amazon Data Firehose
Firehose loads streams into S3 and other destinations with no consumers to manage.
In detail
- Data Firehose delivers streams to S3 with no consumer code.
- Firehose suits delivery, not custom low-latency processing.
Use case
An illustrative scenario, not a real incident.
A web team sends click events to S3 for analysis. Firehose batches and delivers them, so nobody writes or runs a consumer.
See it in different ways
flowchart TD
A{"What do you need?"} -->|"Deliver to S3 or Redshift, no consumer code"| B["Amazon Data Firehose"]
A -->|"Custom consumers and replay"| C["Kinesis Data Streams"]
A -->|"Kafka compatibility"| D["Amazon MSK"]mindmap
root((Ingestion))
Streams
Kinesis Data Streams
Amazon MSK
Delivery
Data Firehose
Databases
AWS DMS
Files
S3 eventsflowchart LR S0["Clickstream"] --> S1["Amazon Data Firehose"] --> S2["Amazon S3"]
Key point: Firehose delivers streams with no consumers.
Why the other options are wrong
- A. Amazon EBS snapshots
- Snapshots back up volumes.
- B. A nightly AWS Glue crawler
- A crawler reads metadata, and delivers nothing.
- D. A self-managed Kafka cluster on EC2
- A Kafka cluster is a lot to run.