Accompany is building an application to collect and transmit sensor data from a factory. The application will use AWS IoT Core to send data from hundreds of devices to an Amazon S3 data lake. The…

Creating a standard topic in AWS IoT Core for data ingestion and then configuring an AWS IoT rule to invoke an AWS Lambda function is the most cost-effective and flexible solution for data enrichment. The Lambda function performs the required processing and then writes the enriched data to the Amazon S3 data lake, meeting the sub-30-minute availability requirement.

Using AWS IoT Core Basic Ingest and sending *raw* data to S3 via an IoT rule action does not fulfill the critical requirement to enrich the data before storage.

While creating a topic for ingestion is correct, sending *raw* data directly to S3 via an IoT rule action fails to meet the requirement for data enrichment prior to storage.

Although Basic Ingest can save on message costs, for custom processing like enrichment, the standard topic with a Lambda rule action (Option A) is a generally applicable and cost-effective pattern, and Basic Ingest bypasses the message broker which may not always be desired.