AWS managedservices documentation change
Summary
Updated terminology from 'review required' to 'managed automation' in drift remediation change type documentation
Security assessment
The changes involve terminology updates for process automation levels but do not address security vulnerabilities or introduce new security controls. The modification appears focused on clarifying operational processes rather than security.
Diff
diff --git a/managedservices/latest/onboardingguide/ex-rfc-updates-and-dd.md b/managedservices/latest/onboardingguide/ex-rfc-updates-and-dd.md index 3787b5d16..95602ddf4 100644 --- a//managedservices/latest/onboardingguide/ex-rfc-updates-and-dd.md +++ b//managedservices/latest/onboardingguide/ex-rfc-updates-and-dd.md @@ -15 +15 @@ For a list of update change types, use the console filter. -Questions and answers on AMS drift remediation. There are two change types that you can use to initiate drift remediation, one is execution mode=manual or "review required," the other is execution mode=automated. +Questions and answers on AMS drift remediation. There are two change types that you can use to initiate drift remediation, one is execution mode=manual or "managed automation," the other is execution mode=automated. @@ -19 +19 @@ Questions and answers on AMS drift remediation. There are two change types that -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. @@ -54 +54 @@ Drift remediation modifies the stack template and/or parameters and it is mandat -The no review required, automated, CT (ct-3kinq0u4l33zf) supports remediating only 10 resources per RFC. To remediate remaining resources in batches of 10 create new RFCs until all resources are remediated. +The no managed automation, automated, CT (ct-3kinq0u4l33zf) supports remediating only 10 resources per RFC. To remediate remaining resources in batches of 10 create new RFCs until all resources are remediated. @@ -59 +59 @@ Which drift remediation change type should I use? -We recommend using the **no review required** , automated CT (ct-3kinq0u4l33zf) when: +We recommend using the **no managed automation** , automated CT (ct-3kinq0u4l33zf) when: @@ -63 +63 @@ We recommend using the **no review required** , automated CT (ct-3kinq0u4l33zf) - * You used an Update CT in the past and it failed as the stack was DRIFTED. You do not need to attempt an update again and can use the review required, manual, CT instead. + * You used an Update CT in the past and it failed as the stack was DRIFTED. You do not need to attempt an update again and can use the managed automation, manual, CT instead. @@ -68 +68 @@ We recommend using the **no review required** , automated CT (ct-3kinq0u4l33zf) -We recommend using the **review required** , manual CT (ct-34sxfo53yuzah) only when drifted resource types are not supported by the drift remediation no review required, automated, CT (ct-3kinq0u4l33zf), or when the drift remediation no review required, automated, CT fails. +We recommend using the **managed automation** , manual CT (ct-34sxfo53yuzah) only when drifted resource types are not supported by the drift remediation no managed automation, automated, CT (ct-3kinq0u4l33zf), or when the drift remediation no managed automation, automated, CT fails.