AWS iot documentation change
Summary
Updated protocol reference from 'HTTPS' to 'HTTPS publish' in device communication documentation
Security assessment
Clarifies protocol usage without introducing new security controls or addressing vulnerabilities. Maintains existing security documentation about X.509 certificates.
Diff
diff --git a/iot/latest/developerguide/iot-jobs-security.md b/iot/latest/developerguide/iot-jobs-security.md index df66bb3ba..62711ccd1 100644 --- a//iot/latest/developerguide/iot-jobs-security.md +++ b//iot/latest/developerguide/iot-jobs-security.md @@ -22 +22 @@ To authorize AWS IoT Jobs operations that can be performed both on the control p -The devices must now be authorized on the data plane by using AWS IoT Core policies to connect securely to the device gateway. The device gateway enables devices to securely communicate with AWS IoT, receive job executions, and update the job execution status. Device communication is secured by using secure [MQTT](./mqtt.html) or [HTTPS](./http.html) communication protocols. These protocols use [X.509 client certificates](./x509-client-certs.html) that are provided by AWS IoT to authenticate the device connections. +The devices must now be authorized on the data plane by using AWS IoT Core policies to connect securely to the device gateway. The device gateway enables devices to securely communicate with AWS IoT, receive job executions, and update the job execution status. Device communication is secured by using secure [MQTT](./mqtt.html) or [HTTPS publish](./http.html) communication protocols. These protocols use [X.509 client certificates](./x509-client-certs.html) that are provided by AWS IoT to authenticate the device connections.