AWS systems-manager documentation change
Summary
Updated documentation link title regarding patch compliance data overwrites
Security assessment
Link title change without security content impact
Diff
diff --git a/systems-manager/latest/userguide/quick-setup-patch-manager.md b/systems-manager/latest/userguide/quick-setup-patch-manager.md index 8d59f98b1..8192e0bcc 100644 --- a//systems-manager/latest/userguide/quick-setup-patch-manager.md +++ b//systems-manager/latest/userguide/quick-setup-patch-manager.md @@ -17 +17 @@ To define a patch policy for a node using Quick Setup, the node must be a _manag -**Patch compliance scanning methods** – Systems Manager supports several methods for scanning managed nodes for patch compliance. If you implement more than one of these methods at a time, the patch compliance information you see is always the result of the most recent scan. Results from previous scans are overwritten. If the scanning methods use different patch baselines, with different approval rules, the patch compliance information can change unexpectedly. For more information, see [Avoiding unintentional patch compliance data overwrites](./patch-manager-compliance-data-overwrites.html). +**Patch compliance scanning methods** – Systems Manager supports several methods for scanning managed nodes for patch compliance. If you implement more than one of these methods at a time, the patch compliance information you see is always the result of the most recent scan. Results from previous scans are overwritten. If the scanning methods use different patch baselines, with different approval rules, the patch compliance information can change unexpectedly. For more information, see [Identifying the execution that created patch compliance data](./patch-manager-compliance-data-overwrites.html).