AWS IoT Temperature Monitoring

02 / PROBLEM

The engineering question.

IoT data must reach the correct cloud service safely and consistently while separate team members develop event processing, storage and notifications.

03 / METHOD

What I built and evaluated.

1. Implemented the documented Member 1 ingestion workstream: Python temperature simulator, AWS IoT Thing, certificate/policy setup, MQTT topic and controlled test publishing.
2. Used X.509 authentication over TLS and an explicit JSON payload with device ID, room, temperature and ISO timestamp.
3. Coordinated the interface with the team's AWS IoT Rule, Lambda, DynamoDB, SNS and CloudWatch design and its intended normal/abnormal event tests.
4. Reviewed the committed AWS CloudWatch screenshot, which records received events, payload validation and normal/high/low temperature classification.

04 / MEASURED FINDINGS

What the evidence shows.

• The repository documents successfully published simulated 24°C, 35°C and 12°C readings through AWS IoT Core.
• Committed CloudWatch evidence illustrates Lambda-side event classification; this is evidence of that part of the shared group system, not proof that I independently developed Lambda.
• The README still lists storage, alerts and end-to-end integration as remaining work. Those broader components are therefore described as team design or pending rather than fully verified delivery.

05 / LIMITATIONS

Where the claims stop.

This was a group assessment, not a deployed commercial IoT product. The published record is incomplete for DynamoDB persistence, SNS alert delivery and end-to-end acceptance. Device credentials and private AWS account data are not copied.