AWS managedservices documentation change
Summary
Changed references from 'review required' to 'managed automation' for drift remediation processes
Security assessment
Operational process terminology update. While drift remediation can impact security posture, this change doesn't directly address security vulnerabilities or introduce security controls.
Diff
diff --git a/managedservices/latest/ctref/management-custom-stack-from-cloudformation-template-remediate-drift.md b/managedservices/latest/ctref/management-custom-stack-from-cloudformation-template-remediate-drift.md index 7cc7c5155..2d1dd708f 100644 --- a//managedservices/latest/ctref/management-custom-stack-from-cloudformation-template-remediate-drift.md +++ b//managedservices/latest/ctref/management-custom-stack-from-cloudformation-template-remediate-drift.md @@ -29 +29 @@ Execution mode | Automated -These are the resources that are supported by the drift remediation change type, (ct-3kinq0u4l33zf). For remediation of any resource, use the "review required" (ct-34sxfo53yuzah) change type instead. +These are the resources that are supported by the drift remediation change type, (ct-3kinq0u4l33zf). For remediation of any resource, use the "managed automation" (ct-34sxfo53yuzah) change type instead. @@ -155 +155 @@ For more details, including a list of _Limitations_ , see [Drift remediation FAQ -When using "review required" CTs, AMS recommends that you use the ASAP **Scheduling** option (choose **ASAP** in the console, leave start and end time blank in the API/CLI) as these CTs require an AMS operator to examine the RFC, and possibly communicate with you before it can be approved and run. If you schedule these RFCs, be sure to allow at least 24 hours. If approval does not happen before the scheduled start time, the RFC is rejected automatically. +When using manual CTs, AMS recommends that you use the ASAP **Scheduling** option (choose **ASAP** in the console, leave start and end time blank in the API/CLI) as these CTs require an AMS operator to examine the RFC, and possibly communicate with you before it can be approved and run. If you schedule these RFCs, be sure to allow at least 24 hours. If approval does not happen before the scheduled start time, the RFC is rejected automatically.