IoT water meters stream telemetry that must be ingested and processed in near real time as a continuous data stream. Which AWS service family is commonly chosen for that real-time streaming pattern?

IoT water meters that stream telemetry for near-real-time ingestion and processing call for a streaming data service family—commonly Amazon Kinesis at Cloud Practitioner depth. Kinesis services ingest and process continuous data streams so civic operations can react to flow anomalies, leak indicators, or usage spikes without waiting for nightly batch file drops. When the stem emphasizes continuous telemetry in motion, Kinesis is the family to name.

AWS Storage Gateway tape gateways present virtual tape hybrid storage; they are not a real-time stream bus for meter telemetry. Amazon Glacier vault lock policies enforce archival compliance retention; they do not ingest per-second streams. AWS Artifact delivers compliance reports; it is unrelated to streaming telemetry. Those options fail because they are storage, archive governance, or compliance document services—not stream ingestion platforms.

Exam caveat: Kinesis covers streaming ingestion/processing patterns; MSK is managed Kafka for teams standardized on Kafka; SQS is queues for decoupled messages (often discrete work items); IoT Core connects devices. CLF often expects Kinesis when the story is real-time streaming data at identify level.

Operational check for water telemetry: land device data through an appropriate ingest path (often IoT Core into streaming/analytics), shard or scale the stream for meter cardinality, retain data long enough for replay, alarm on anomalous readings feeding operations dashboards, secure device credentials, and load-test storm scenarios so a citywide event does not drop critical meter messages.