AWS iot documentation change
Summary
Updated multiple documentation links to fix URL formatting (added double slashes)
Security assessment
Changes are purely URL syntax corrections. References to S3 versioning and logging best practices are existing content; no new security documentation added.
Diff
diff --git a/iot/latest/developerguide/binary-payloads.md b/iot/latest/developerguide/binary-payloads.md index 2f8849261..f5e58220e 100644 --- a//iot/latest/developerguide/binary-payloads.md +++ b//iot/latest/developerguide/binary-payloads.md @@ -200 +200 @@ After you create your descriptor files `<FILENAME>.desc`, upload the descriptor -After you upload the descriptor files to your Amazon S3 bucket, configure a [Rule](https://docs.aws.amazon.com/iot/latest/developerguide/iot-create-rule.html) that can decode your protobuf message payload format using the [decode(value, decodingScheme)](./iot-sql-functions.html#iot-sql-decode-base64) SQL function. A detailed function signature and example can be found in the [decode(value, decodingScheme)](./iot-sql-functions.html#iot-sql-decode-base64) SQL function of the _AWS IoT SQL reference_. +After you upload the descriptor files to your Amazon S3 bucket, configure a [Rule](https://docs.aws.amazon.com//iot/latest/developerguide/iot-create-rule.html) that can decode your protobuf message payload format using the [decode(value, decodingScheme)](./iot-sql-functions.html#iot-sql-decode-base64) SQL function. A detailed function signature and example can be found in the [decode(value, decodingScheme)](./iot-sql-functions.html#iot-sql-decode-base64) SQL function of the _AWS IoT SQL reference_. @@ -224 +224 @@ AWS IoT Core Rules support protobuf with the following limitations: - * Decoding protobuf message payloads within [substitution templates](https://docs.aws.amazon.com/iot/latest/developerguide/iot-substitution-templates.html) is not supported. + * Decoding protobuf message payloads within [substitution templates](https://docs.aws.amazon.com//iot/latest/developerguide/iot-substitution-templates.html) is not supported. @@ -241 +241 @@ Here are some best practices and troubleshooting tips. -It's a good practice to back up your proto files in case something goes wrong. For example, if you incorrectly modify the proto files without backups when running protoc, this can cause issues in your production stack. There are multiple ways to back up your files in an Amazon S3 bucket. For example, you can [use versioning in S3 buckets](https://docs.aws.amazon.com/AmazonS3/latest/userguide/Versioning.html). For more information about how to back up files in Amazon S3 buckets, refer to the _[Amazon S3 Developer Guide](https://docs.aws.amazon.com/aws-backup/latest/devguide/recovery-points.html)_. +It's a good practice to back up your proto files in case something goes wrong. For example, if you incorrectly modify the proto files without backups when running protoc, this can cause issues in your production stack. There are multiple ways to back up your files in an Amazon S3 bucket. For example, you can [use versioning in S3 buckets](https://docs.aws.amazon.com//AmazonS3/latest/userguide/Versioning.html). For more information about how to back up files in Amazon S3 buckets, refer to the _[Amazon S3 Developer Guide](https://docs.aws.amazon.com//aws-backup/latest/devguide/recovery-points.html)_. @@ -245 +245 @@ It's a good practice to back up your proto files in case something goes wrong. F -It's a good practice to configure AWS IoT logging so that you can check AWS IoT logs for your account in CloudWatch. When a rule's SQL query calls an external function, AWS IoT Core Rules generates a log entry with an `eventType` of `FunctionExecution`, which contains the reason field that will help you troubleshoot failures. Possible errors include an Amazon S3 object not found, or invalid protobuf file descriptor. For more information about how to configure AWS IoT logging and see the log entries, see [Configure AWS IoT logging](https://docs.aws.amazon.com/iot/latest/developerguide/configure-logging.html) and [Rules engine log entries](https://docs.aws.amazon.com/iot/latest/developerguide/cwl-format.html#log-rules-fn-exec). +It's a good practice to configure AWS IoT logging so that you can check AWS IoT logs for your account in CloudWatch. When a rule's SQL query calls an external function, AWS IoT Core Rules generates a log entry with an `eventType` of `FunctionExecution`, which contains the reason field that will help you troubleshoot failures. Possible errors include an Amazon S3 object not found, or invalid protobuf file descriptor. For more information about how to configure AWS IoT logging and see the log entries, see [Configure AWS IoT logging](https://docs.aws.amazon.com//iot/latest/developerguide/configure-logging.html) and [Rules engine log entries](https://docs.aws.amazon.com//iot/latest/developerguide/cwl-format.html#log-rules-fn-exec).