AWS iot: Fixed broken URLs in device shadows documentation
Summary
Corrected invalid URLs by removing extra slashes in links to AWS IoT policies and authorization references.
Security assessment
The change only fixes broken URLs; it does not alter security guidance, address vulnerabilities, or introduce new security content.
Evidence
+With named shadows, you can create different views of a thing object’s state. For example, you could divide a thing object with many properties into shadows with logical groups of properties, each identified by its shadow name. You could also limit access to properties by grouping them into different shadows and using policies to control access. For more information about policies to use with device shadows, see [Actions, resources, and condition keys for AWS IoT](https://docs.aws.amazon.com/service-authorization/latest/reference/list_awsiot.html) and [AWS IoT Core policies](https://docs.aws.amazon.com/iot/latest/developerguide/iot-policies.html).
Diff
diff --git a/iot/latest/developerguide/iot-device-shadows.md b/iot/latest/developerguide/iot-device-shadows.md index 6748b0ed3..617a0dfb0 100644 --- a//iot/latest/developerguide/iot-device-shadows.md +++ b//iot/latest/developerguide/iot-device-shadows.md @@ -23 +23 @@ When a device goes offline, an app can still communicate with AWS IoT and the de -If your devices are frequently offline and you would like to configure your devices to receive delta messages after they reconnect, you can use the persistent session feature. For more information about the persistent session expiry period, see [Persistent session expiry period](https://docs.aws.amazon.com//general/latest/gr/iot-core.html#message-broker-limits). +If your devices are frequently offline and you would like to configure your devices to receive delta messages after they reconnect, you can use the persistent session feature. For more information about the persistent session expiry period, see [Persistent session expiry period](https://docs.aws.amazon.com/general/latest/gr/iot-core.html#message-broker-limits). @@ -31 +31 @@ A thing object can have both named and unnamed shadows at the same time; however -With named shadows, you can create different views of a thing object’s state. For example, you could divide a thing object with many properties into shadows with logical groups of properties, each identified by its shadow name. You could also limit access to properties by grouping them into different shadows and using policies to control access. For more information about policies to use with device shadows, see [Actions, resources, and condition keys for AWS IoT](https://docs.aws.amazon.com//service-authorization/latest/reference/list_awsiot.html) and [AWS IoT Core policies](https://docs.aws.amazon.com//iot/latest/developerguide/iot-policies.html). +With named shadows, you can create different views of a thing object’s state. For example, you could divide a thing object with many properties into shadows with logical groups of properties, each identified by its shadow name. You could also limit access to properties by grouping them into different shadows and using policies to control access. For more information about policies to use with device shadows, see [Actions, resources, and condition keys for AWS IoT](https://docs.aws.amazon.com/service-authorization/latest/reference/list_awsiot.html) and [AWS IoT Core policies](https://docs.aws.amazon.com/iot/latest/developerguide/iot-policies.html).