AWS iot documentation change
Summary
Improved connectivity detection documentation and added note about LWT message ordering limitations
Security assessment
Changes focus on connectivity state management reliability rather than security mechanisms. The LWT note addresses operational reliability, not vulnerabilities.
Diff
diff --git a/iot/latest/developerguide/device-shadow-comms-app.md b/iot/latest/developerguide/device-shadow-comms-app.md index 49086782b..48b80ef5e 100644 --- a//iot/latest/developerguide/device-shadow-comms-app.md +++ b//iot/latest/developerguide/device-shadow-comms-app.md @@ -5 +5 @@ -Initializing the app or service on connection to AWS IoTProcessing state changes while the app or service is connected to AWS IoTDetecting a device is connected +Initializing the app or service on connection to AWS IoTProcessing state changes while the app or service is connected to AWS IoTDetecting if a device is connected @@ -57 +57 @@ When an end user interacts with the app or service to change the state of the de -## Detecting a device is connected +## Detecting if a device is connected @@ -119,0 +120,4 @@ MQTT LWT messages sent to AWS IoT reserved topics (topics that begin with $) are +###### Note + +Due to the asynchronous nature of disconnect processing, LWT messages are not guaranteed to be dispatched in order during reconnection. We recommend that you use [lifecycle events](./life-cycle-events.html) to improve the accuracy of connectivity state detection, as these events provide attributes to manage out-of-order events. +