A city’s 311 analytics team wants a managed path that continuously batches streaming complaint events into an Amazon S3 data lake and optionally into Amazon OpenSearch Service for near-real-time dashboards, without operating custom consumer fleets. Which service best fits?
Select an answer to reveal the explanation.
Short Explanation
Firehose is the “set the destination and let AWS batch it” hose for streams. Point it at S3 for the lake and OpenSearch for searchable 311 dashboards without babysitting consumer fleets. Custom MQ workers, weekly Snowball trucks, and CloudFront upload links miss managed stream delivery.
Full Explanation
Amazon Data Firehose best fits the 311 analytics team’s need for a managed path that continuously batches streaming complaint events into Amazon S3 and optionally into Amazon OpenSearch Service. Firehose handles buffering, optional transformation, and delivery retries so city staff avoid operating custom consumer fleets while still landing a data lake copy and searchable near-real-time dashboards. Amazon MQ brokers that require city staff to write and scale custom delivery workers for every destination shift operational burden back onto the municipality; MQ is a message broker, not a managed stream-to-S3/OpenSearch delivery service. AWS Snowball Edge devices rotated weekly between field offices and the data center address physical data migration or edge compute scenarios, not continuous streaming complaint ingest. Amazon CloudFront signed URLs that citizens use to upload individual JSON files to OpenSearch misuse a CDN edge-delivery pattern as an ingest pipeline and would bypass controlled batching, schema handling, and lake landing. Exam caveat: Firehose delivery streams have destination-specific limits and buffering intervals; tune buffer size/interval for dashboard freshness versus PUT efficiency, and remember OpenSearch destinations need appropriate domain access and IAM. Operational check: send a test 311 event stream, confirm objects appear in the expected S3 prefix with the intended format, verify OpenSearch indices update, and review CloudWatch delivery success/failure metrics before cutover.