Build a real-time temperature excursion alerting pipeline from IoT logger telemetry using AWS IoT Core rules and SNS for cold-chain pharmaceutical lanes

Steps

1. Provision IoT devices in AWS IoT Core and generate X.509 certificates for each temperature logger; configure logger firmware to publish readings as JSON to a topic path pattern such as coldchain/{shipment_id}/{device_id}/telemetry
2. Create an AWS IoT Core topic rule with a SQL rule that selects temperature, humidity, device_id, shipment_id, and timestamp from the topic pattern; add a WHERE clause filter for temperature outside the target range, e.g. WHERE temperature NOT BETWEEN 2 AND 8 to trigger only on excursions
3. Configure the rule action to publish the filtered excursion event to an SNS topic with a structured JSON message including all telemetry fields plus an excursion_type label; subscribe both an email endpoint and an SQS queue to the SNS topic
4. From the SQS queue, a Lambda function consumes excursion events and performs enrichment: look up the shipment record to get the product, lot number, and QA contact; compute excursion duration by querying the last in-range reading from a DynamoDB telemetry store
5. Emit the enriched excursion alert to PagerDuty or a QA ticketing system via HTTPS POST; include the device ID, shipment ID, product, lot, excursion start time, current temperature, and MKT running total to date
6. Persist all raw telemetry readings (not just excursions) to a DynamoDB table with device_id + timestamp as the composite key; enable DynamoDB Streams to feed a Kinesis Data Firehose for long-term S3 archival and downstream MKT batch computation