AWS iot documentation change
Summary
Adjusted API reference URLs to include an extra slash for proper formatting
Security assessment
Changes are purely cosmetic fixes to hyperlinks. No security implications or documentation additions identified.
Diff
diff --git a/iot/latest/developerguide/retained-message-policy-examples.md b/iot/latest/developerguide/retained-message-policy-examples.md index f81431407..6c8f0c4c9 100644 --- a//iot/latest/developerguide/retained-message-policy-examples.md +++ b//iot/latest/developerguide/retained-message-policy-examples.md @@ -101 +101 @@ The following policy document grants all clients permission to connect and publi -Services and applications can access retained messages without the need to support an MQTT client by calling [`ListRetainedMessages`](https://docs.aws.amazon.com/iot/latest/apireference/API_iotdata_ListRetainedMessages.html) and [`GetRetainedMessage`](https://docs.aws.amazon.com/iot/latest/apireference/API_iotdata_GetRetainedMessage.html). The services and applications that call these actions must be authorized by using a policy such as the following example. +Services and applications can access retained messages without the need to support an MQTT client by calling [`ListRetainedMessages`](https://docs.aws.amazon.com//iot/latest/apireference/API_iotdata_ListRetainedMessages.html) and [`GetRetainedMessage`](https://docs.aws.amazon.com//iot/latest/apireference/API_iotdata_GetRetainedMessage.html). The services and applications that call these actions must be authorized by using a policy such as the following example.