AWS wellarchitected documentation change
Summary
Added AWS Health integration guidance and warning about consequences of missing lifecycle events
Security assessment
Emphasizes using AWS Health for patch management planning to avoid emergency changes, which improves operational security but doesn't address a specific vulnerability
Diff
diff --git a/wellarchitected/latest/framework/ops_dev_integ_patch_mgmt.md b/wellarchitected/latest/framework/ops_dev_integ_patch_mgmt.md index 2b7af1471..5a07e6453 100644 --- a//wellarchitected/latest/framework/ops_dev_integ_patch_mgmt.md +++ b//wellarchitected/latest/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. +