AWS iot-mi documentation change
Summary
Clarified device provisioning process wording for automation and security
Security assessment
The change improves clarity but does not introduce new security features or address vulnerabilities.
Diff
diff --git a/iot-mi/latest/devguide/getting-started-hub-connected-device-onboarding.md b/iot-mi/latest/devguide/getting-started-hub-connected-device-onboarding.md index 34bddca54..e5fab5480 100644 --- a//iot-mi/latest/devguide/getting-started-hub-connected-device-onboarding.md +++ b//iot-mi/latest/devguide/getting-started-hub-connected-device-onboarding.md @@ -87 +87 @@ APIs used in this step: -Device provisioning establishes a link between your device or fleet of devices and managed integrations for future bidirectional communication. Call the `CreateProvisioningProfile` API to create a provisioning template and claim certificate. A provisioning template is a document that defines the set of resources and policies applied to a device during the provisioning process. It specifies how devices should be registered and configured when they connect to managed integrations for the first time, automating the device setup process to ensure that each device is securely and consistently integrated into AWS IoT with the appropriate permissions, policies, and configurations. A claim certificate is a temporary certificate used during fleet provisioning and only when the unique device certificate is not preinstalled on the device during manufacturing before delivered to the end-user. +Device provisioning establishes a link between your device or fleet of devices and managed integrations for future bidirectional communication. Call the `CreateProvisioningProfile` API to create a provisioning template and claim certificate. A provisioning template is a document that defines the set of resources and policies applied to a device during the provisioning process. It specifies how devices should be registered and configured when they connect to managed integrations for the first time. This process automates the device setup process to ensure that each device is securely and consistently integrated into AWS IoT with the appropriate permissions, policies, and configurations. A claim certificate is a temporary certificate used during fleet provisioning and only when the unique device certificate is not preinstalled on the device during manufacturing before delivered to the end-user.