AWS iot: Fix broken documentation links for AWS IoT Core service quotas
Summary
Corrected URL paths in multiple references to AWS IoT Core service quotas documentation by removing duplicate slashes.
Security assessment
The change only fixes broken hyperlinks in documentation by correcting URL syntax (removing '//' duplicates). No security-related content was added, modified, or referenced.
Evidence
+ * `client_id` is unique identifier of the MQTT client to send the message to. Client IDs must not exceed 128 characters and can't start with a dollar sign ($). MQTT client IDs must be URL encoded (percent-encoded) when they contain characters that are not valid in HTTP requests, such as spaces, forward slashes (/), and UTF-8 characters. For more information, see [AWS IoT Core message broker and protocol limits and quotas](https://docs.aws.amazon.com/general/latest/gr/iot-core.html#message-broker-limits).
Diff
diff --git a/iot/latest/developerguide/direct-messaging.md b/iot/latest/developerguide/direct-messaging.md index 233eb48c0..af48eeb3d 100644 --- a//iot/latest/developerguide/direct-messaging.md +++ b//iot/latest/developerguide/direct-messaging.md @@ -43 +43 @@ Senders can send Direct Messages by making HTTP POST requests to a client-specif - * `client_id` is unique identifier of the MQTT client to send the message to. Client IDs must not exceed 128 characters and can't start with a dollar sign ($). MQTT client IDs must be URL encoded (percent-encoded) when they contain characters that are not valid in HTTP requests, such as spaces, forward slashes (/), and UTF-8 characters. For more information, see [AWS IoT Core message broker and protocol limits and quotas](https://docs.aws.amazon.com//general/latest/gr/iot-core.html#message-broker-limits). + * `client_id` is unique identifier of the MQTT client to send the message to. Client IDs must not exceed 128 characters and can't start with a dollar sign ($). MQTT client IDs must be URL encoded (percent-encoded) when they contain characters that are not valid in HTTP requests, such as spaces, forward slashes (/), and UTF-8 characters. For more information, see [AWS IoT Core message broker and protocol limits and quotas](https://docs.aws.amazon.com/general/latest/gr/iot-core.html#message-broker-limits). @@ -45 +45 @@ Senders can send Direct Messages by making HTTP POST requests to a client-specif - * `topic_name` is the topic on which the receiver receives the message, URL-encoded. Must not start with $. Must not be an AWS IoT Core Reserved Topic. Refer to the AWS IoT Core service quotas page for topic length and depth limits. For more information, see [AWS IoT Core message broker and protocol limits and quotas](https://docs.aws.amazon.com//general/latest/gr/iot-core.html#message-broker-limits). + * `topic_name` is the topic on which the receiver receives the message, URL-encoded. Must not start with $. Must not be an AWS IoT Core Reserved Topic. Refer to the AWS IoT Core service quotas page for topic length and depth limits. For more information, see [AWS IoT Core message broker and protocol limits and quotas](https://docs.aws.amazon.com/general/latest/gr/iot-core.html#message-broker-limits). @@ -64,2 +64,2 @@ SendDirectMessage API response status codes HTTP code | Recommended action -413 Payload Too Large | Payload exceeds maximum size allowed. Reduce the payload size and retry. See [AWS IoT Core service quotas](https://docs.aws.amazon.com//general/latest/gr/iot-core.html). -429 Too Many Requests | This means the account has exceeded the SendDirectMessage requests-per-second limit or the receiver connection has exceeded the outbound publish limit. Review the HTTP response message or CloudWatch logs for the specific reason, reduce the request rate and implement exponential backoff. See [AWS IoT Core service quotas](https://docs.aws.amazon.com//general/latest/gr/iot-core.html). +413 Payload Too Large | Payload exceeds maximum size allowed. Reduce the payload size and retry. See [AWS IoT Core service quotas](https://docs.aws.amazon.com/general/latest/gr/iot-core.html). +429 Too Many Requests | This means the account has exceeded the SendDirectMessage requests-per-second limit or the receiver connection has exceeded the outbound publish limit. Review the HTTP response message or CloudWatch logs for the specific reason, reduce the request rate and implement exponential backoff. See [AWS IoT Core service quotas](https://docs.aws.amazon.com/general/latest/gr/iot-core.html).