Scenario: An AI developer needs a scalable, secure way to collect telemetry data (temperature, pressure) from devices in remote locations with…

This solution provides a fully managed, serverless, and highly scalable pipeline for IoT data ingestion. Message Queuing Telemetry Transport (MQTT) is a lightweight protocol ideal for devices with constrained resources and unreliable network connectivity, as it supports different Quality of Service (QoS) levels to ensure message delivery. AWS IoT Core securely handles device communication at scale. The IoT Core rule engine can directly forward messages to an Amazon Data Firehose stream without any custom code. Firehose is a fully managed service that automatically batches, compresses, and encrypts the data before reliably delivering it to Amazon S3, perfectly aligning with the requirement to minimize infrastructure management.

B. While AWS IoT Greengrass is excellent for edge processing and managing intermittent connectivity, this option requires writing and maintaining custom AWS SDK code on each device for S3 uploads, increasing management overhead compared to a managed cloud pipeline.

C. Using Amazon API Gateway with HTTP is less suitable for this scenario. HTTP is less efficient than MQTT for telemetry and does not handle intermittent network connectivity as gracefully, requiring more complex client-side retry logic.

D. This option is overly complex for the stated requirements. While functional, it uses an Amazon Kinesis Data Stream and an AWS Lambda function to perform a task that Amazon Data Firehose is specifically designed to handle out-of-the-box, thus failing the "minimize infrastructure management" principle.

1. AWS IoT Core Developer Guide, "Choosing a protocol": This guide explains the benefits of using MQTT for IoT applications, stating, "MQTT is a lightweight binary protocol... Because it's lightweight, it can be used on devices with limited CPU and memory resources and in networks with limited bandwidth." This supports the choice of MQTT for remote devices.

2. AWS IoT Core Developer Guide, "Amazon Data Firehose action": The documentation details the direct, configuration-based integration between IoT Core and Firehose. It states, "The Amazon Data Firehose action sends data from an MQTT message to an Amazon Data Firehose stream," demonstrating the streamlined pipeline in option A.

3. Amazon Kinesis Data Firehose Developer Guide, "What Is Amazon Kinesis Data Firehose?": This document highlights the service's purpose: "Amazon Kinesis Data Firehose is the easiest way to reliably load streaming data into data lakes, data stores... You don't need to write applications or manage resources." This directly supports option A's adherence to minimizing infrastructure management.

4. AWS Documentation, "FAQ: Amazon Kinesis": In comparing Kinesis Data Streams and Kinesis Data Firehose, AWS clarifies: "Use Amazon Kinesis Data Firehose if you want to deliver data to Amazon S3... Kinesis Data Firehose handles all of the underlying stream management." This confirms that Firehose (Option A) is simpler than Kinesis Data Streams + Lambda (Option D) for this use case.