AWS wellarchitected documentation change
Summary
Added guidance about using AWS Health for lifecycle events and a risk statement about unawareness of critical updates
Security assessment
While patch management is security-adjacent, this change emphasizes operational best practices rather than addressing specific vulnerabilities. The added content helps maintain security through proper maintenance but doesn't document security features or address active threats.
Diff
diff --git a/wellarchitected/2025-02-25/framework/ops_dev_integ_patch_mgmt.md b/wellarchitected/2025-02-25/framework/ops_dev_integ_patch_mgmt.md index dc5897981..e6a24b2c0 100644 --- a//wellarchitected/2025-02-25/framework/ops_dev_integ_patch_mgmt.md +++ b//wellarchitected/2025-02-25/framework/ops_dev_integ_patch_mgmt.md @@ -12,0 +13,2 @@ Patch and vulnerability management are part of your benefit and risk management +[AWS Health](https://aws.amazon.com/premiumsupport/technology/aws-health/) is the authoritative source of information about planned lifecycle events and other action-required events that affect the health of your AWS Cloud resources. You should be aware of upcoming changes and updates that should be performed. Major planned lifecycle events are sent at least six months in advance. + @@ -34,0 +37,2 @@ Patching should not be performed on production systems without first testing in + * You are not aware of critical actions needed to maintain your resources, such as mandatory version updates because you do not review upcoming planned lifecycle events and other information. You lose critical time for planning and execution, resulting in emergency changes for your teams and potential impact or unexpected downtime. +