AWS whitepapers documentation change

Service: whitepapers · 2026-05-04 · Documentation low

File: whitepapers/latest/designing-mqtt-topics-aws-iot-core/applications-on-aws.md

Summary

Added IoT device communication details showing passcode generation and client ID usage in images

Security assessment

Illustrates secure command handling and authentication mechanisms in IoT workflows, enhancing documentation of existing security practices.

Diff

diff --git a/whitepapers/latest/designing-mqtt-topics-aws-iot-core/applications-on-aws.md b/whitepapers/latest/designing-mqtt-topics-aws-iot-core/applications-on-aws.md
index 47bb74f6a..9cf311275 100644
--- a//whitepapers/latest/designing-mqtt-topics-aws-iot-core/applications-on-aws.md
+++ b//whitepapers/latest/designing-mqtt-topics-aws-iot-core/applications-on-aws.md
@@ -52 +52 @@ The single level wildcard command is backward compatible as the IoT application
-![Cloud icon connected to microchip icon, representing IoT device communication.](/images/whitepapers/latest/designing-mqtt-topics-aws-iot-core/images/image9.png)
+![AWS IoT Core sending command to Smart Lock 1 with JSON payload for passcode generation.](/images/whitepapers/latest/designing-mqtt-topics-aws-iot-core/images/image9.png)
@@ -58 +58 @@ Because a home can have multiple authorized homeowners, the client ID determines
-![Icons representing cloud and microchip, indicating connection between cloud services and IoT devices.](/images/whitepapers/latest/designing-mqtt-topics-aws-iot-core/images/image9b.png)
+![Smart Lock publishing response with client ID, session ID, passcode, and success code to AWS IoT Core.](/images/whitepapers/latest/designing-mqtt-topics-aws-iot-core/images/image9b.png)
@@ -68 +68 @@ In this workflow, the application used a command topic for a single device. Howe
-![Smartphone icon connected to a cloud icon with tree symbol, representing device-cloud interaction.](/images/whitepapers/latest/designing-mqtt-topics-aws-iot-core/images/image10.png)
+![Mobile client sending request to AWS IoT Core with JSON payload containing client ID, session ID, passcode, TTL, and response code.](/images/whitepapers/latest/designing-mqtt-topics-aws-iot-core/images/image10.png)
@@ -95 +95 @@ Each occupancy sensor publishes an occupancy reading once per minute and wheneve
-![Occupancy sensor data flow from sensor to AWS IoT Greengrass core device.](/images/whitepapers/latest/designing-mqtt-topics-aws-iot-core/images/image15.png)
+![Occupancy sensor publishing to dt/acme/building-fresco/room4/occupancy-1 topic to AWS IoT Greengrass.](/images/whitepapers/latest/designing-mqtt-topics-aws-iot-core/images/image15.png)
@@ -105 +105 @@ AWS IoT Greengrass adds building information to each message to show the overall
-![Diagram showing data flow from IoT device to cloud, with message augmentation steps.](/images/whitepapers/latest/designing-mqtt-topics-aws-iot-core/images/image16.png)
+![AWS IoT Greengrass publishing JSON payload with occupancy data to AWS IoT Core topic.](/images/whitepapers/latest/designing-mqtt-topics-aws-iot-core/images/image16.png)