Amazon Web Services has added MQTT session data to the connectivity status API in AWS IoT Device Management, enabling users to troubleshoot connectivity issues and audit connection patterns across their IoT device fleets.

This launch brings AWS IoT Device Management’s existing connectivity status API to full parity with AWS IoT Core’s recently launched GetConnection API, enabling users to retrieve detailed connection and MQTT session information for the IoT device by its thing name.

In addition to the connection status, timestamp and disconnect reason already available, users now get visibility into MQTT session timeout and session expiry values, along with optional socket level details such as source and destination IP addresses, ports, and client VPC endpoint ID. Access to socket information is controlled through granular IAM policies, so users can restrict it to the teams that need it.

An advantage of the connectivity status API over AWS IoT Core’s GetConnection API is data retention. While GetConnection retains connection and session details for 30 minutes after a device disconnects, the connectivity status API stores this information indefinitely. This means users can investigate disconnect reasons, review session metadata and troubleshoot issues long after a device goes offline.

This enhancement is available in all AWS regions where AWS IoT Device Management (aws.amazon.com/iot-device-management/) is supported. AWS IoT Device Management only supports devices registered in the AWS IoT Core Thing Registry. To learn more, visit the AWS IoT Device Management documentation (docs.aws.amazon.com/iot/latest/developerguide/device-connectivity-status.html) and reference guide (docs.aws.amazon.com/iot/latest/apireference/Welcome.html).