Troubleshooting device fleet disconnects - Amazon IoT Core
Services or capabilities described in Amazon Web Services documentation might vary by Region. To see the differences applicable to the China Regions, see Getting Started with Amazon Web Services in China (PDF).

Troubleshooting device fleet disconnects

Help us improve this topic

Let us know what would help make it better

Amazon IoT device fleet disconnects can happen for multiple reasons. This article explains how to diagnose a disconnect reason and how to handle disconnects caused by regular maintenance of Amazon IoT service or a throttling limit.

To diagnose the disconnect reason

You can check the AWSIotLogsV2 log group in CloudWatch to identify the disconnect reason in the disconnectReason field of the log entry.

You can also use Amazon IoT's lifecycle events feature to identify the disconnect reason. If you’ve subscribed to lifecycle's disconnect event ($aws/events/presence/disconnected/clientId), you’ll get a notification from Amazon IoT when the disconnect happens. You can identify the disconnect reason in the disconnectReason field of the notification.

For more information, see CloudWatch Amazon IoT log entries and Lifecycle events.

To troubleshoot disconnects due to Amazon IoT service maintenance

Disconnects caused by Amazon IoT's service maintenance are logged as SERVER_INITIATED_DISCONNECT in Amazon IoT's lifecycle event and CloudWatch. To handle these disconnects, adjust your client-side setup to make sure your devices can be automatically reconnected to the Amazon IoT platform.

To troubleshoot disconnects due to a throttling limit

Disconnects caused by a throttling limit are logged as THROTTLED in Amazon IoT's lifecycle event and CloudWatch. To handle these disconnects, you can request message broker limit increases as the device count grows.

For more information, see Amazon IoT Core Message Broker.