AWS AmazonCloudWatch documentation change
Summary
Updated canary runtime upgrade instructions, including dry-run validation to test updates safely.
Security assessment
The dry-run feature improves operational safety but is not explicitly tied to security. The changes focus on preventing runtime errors rather than addressing vulnerabilities or documenting security features.
Diff
diff --git a/AmazonCloudWatch/latest/monitoring/CloudWatch_Synthetics_Canaries_Library.md b/AmazonCloudWatch/latest/monitoring/CloudWatch_Synthetics_Canaries_Library.md index eb893a018..6e1bb02a3 100644 --- a//AmazonCloudWatch/latest/monitoring/CloudWatch_Synthetics_Canaries_Library.md +++ b//AmazonCloudWatch/latest/monitoring/CloudWatch_Synthetics_Canaries_Library.md @@ -15 +15 @@ We recommend that you always use the most recent runtime version for your canari -When you create a canary, one of the layers created is a Synthetics layer prepended with `Synthetics`. This layer is owned by the Synthetics service account and contains the runtime code. +When you create a canary, one of the layers created is a Synthetics layer prefixed with `Synthetics`. This layer is owned by the Synthetics service account and contains the runtime code. @@ -19 +19 @@ When you create a canary, one of the layers created is a Synthetics layer prepen -Whenever you upgrade a canary to use a new version of the the Synthetics runtime, all Synthetics library functions that your canary uses are also automatically upgraded to the same version of NodeJS that the Synthetics runtime supports. +Whenever you a canary to use a new version of the Synthetics runtime, all Synthetics library functions that your canary uses are also automatically u to the same version of NodeJS that the Synthetics runtime supports. @@ -46 +46,3 @@ You can update a canary’s runtime version by using the CloudWatch console, AWS -You can verify the upgrade by first cloning the canary using the CloudWatch console and updating its runtime version. This creates another canary which is a clone of your original canary. Once you have verified your canary with the new runtime version, you can update the runtime version of your original canary and delete the clone canary. +You can verify the update by first testing your update before committing the runtime update. When updating the runtime versions, choose the **Start Dry Run** or **Validate and save later** options in the CloudWatch console to create a dry run of the original canary along with any changes you made to the configuration. The dry run will update and execute the canary to validate whether the runtime update is safe for the canary. Once you have verified your canary with the new runtime version, you can update the runtime version of your canary. For more information, see [Performing safe canary updates](./performing-safe-canary-upgrades.html). + +Alternatively, you can verify the update by first cloning the canary using the CloudWatch console and updating the runtime version. This creates another canary which is a clone of your original canary. Once you have verified your canary with the new runtime version, you can update the runtime version of your original canary and delete the clone canary.