Overview
Who should read these docs?
Device-Triggered Rotation
The device should initiate rotation of its operational certificate when it detects that the certificate is approaching expiration. The device should run this check on every boot and complete any in-flight MQTT operations before disconnecting to rotate. Because the operational certificate has a 1-year lifetime and the rotation window opens at 30 days, there is no urgency within a single session; the device does not need to interrupt an active operation.
Platform-Triggered Rotation
The rotation itself is identical to device-triggered rotation. The device connects with the bootstrap certificate, runs the Phase 2 Fleet Provisioning flow, and reconnects with the new certificate. The difference is the trigger and the wrapper: instead of detecting expiry locally, the device discovers the rotation request as an AWS IoT Job and must report the outcome (SUCCEEDED or FAILED) back via the Jobs API.