// the find
Abhiram-127/FreeRTOS-AWS-Machine-Telemetry
Industrial IoT Machine Health Monitoring System using ESP32-S3, AWS IoT Core, FreeRTOS and React Dashboard.
A portfolio-style ESP32-S3 project pairing FreeRTOS firmware with an AWS IoT Core pipeline (Lambda, DynamoDB, API Gateway) and a React dashboard. It's aimed at students or engineers who want a worked example of multi-task embedded firmware talking to a cloud telemetry stack, not at anyone looking to actually deploy machine monitoring.
The task design is documented with an actual sequence diagram, not just a bullet list — it shows the mutex being held only long enough to copy the shared struct, with the MQTT publish itself happening outside the lock, which is the right pattern for not blocking the sensor tasks on network I/O. The priority split between the IMU task (prio 5) and the DHT/MQTT tasks (prio 4) reflects a real decision about which sensor needs tighter timing. The project also goes end-to-end — firmware, TLS-secured MQTT, an IoT rule triggering Lambda, DynamoDB storage, and a REST-fed React dashboard — which is more system thinking than most single-board IoT demos bother with.
The actual firmware source isn't in the repo: there's a CMakeLists.txt and the directory tree shows only the default ESP-IDF placeholder files (include/README, lib/README) with no main/ directory containing the task implementations the README describes in detail. node_modules is committed under dashboard/, which bloats the repo and will conflict with package-lock.json the moment someone runs npm install. There's no discussion anywhere of WiFi drop or MQTT reconnect handling, which is a real gap for anything billed as 'industrial' monitoring — a disconnected ESP32 should not silently stop reporting. The README itself is structured like a resume ('Skills Demonstrated', 'Key Learning Outcomes') rather than documentation a future user or contributor would actually need, like build/flash instructions or AWS setup steps.