AWS systems-manager documentation change
Summary
Clarified patch compliance report behavior and updated documentation links
Security assessment
Improved documentation clarity about compliance data generation but no direct security vulnerability fixes or new security features documented.
Diff
diff --git a/systems-manager/latest/userguide/patch-manager-compliance-reports.md b/systems-manager/latest/userguide/patch-manager-compliance-reports.md index 9a2578a63..cd56b0db2 100644 --- a//systems-manager/latest/userguide/patch-manager-compliance-reports.md +++ b//systems-manager/latest/userguide/patch-manager-compliance-reports.md @@ -24 +24,3 @@ The information in the following topics apply no matter which method or type of -If you have multiple types of operations in place to scan your instances for patch compliance, note that each scan overwrites the patch compliance data of previous scans. As a result, you might end up with unexpected results in your patch compliance data. For more information, see [Avoiding unintentional patch compliance data overwrites](./patch-manager-compliance-data-overwrites.html). +Patch compliance reports are point-in-time snapshots generated only by successful patching operations. Each report contains a capture time that identifies when the compliance status was calculated. + +If you have multiple types of operations in place to scan your instances for patch compliance, note that each scan overwrites the patch compliance data of previous scans. As a result, you might end up with unexpected results in your patch compliance data. For more information, see [Identifying the execution that created patch compliance data](./patch-manager-compliance-data-overwrites.html). @@ -36 +38 @@ To verify which patch baseline was used to generate the latest compliance inform - * [Avoiding unintentional patch compliance data overwrites](./patch-manager-compliance-data-overwrites.html) + * [Identifying the execution that created patch compliance data](./patch-manager-compliance-data-overwrites.html)