AWS managedservices documentation change
Summary
Updated two instances of 'AWS CloudFormation' to 'CloudFormation'
Security assessment
Terminology standardization without altering security posture. References to IAM roles and resource retention remain unchanged.
Diff
diff --git a/managedservices/latest/accelerate-guide/acc-offboard.md b/managedservices/latest/accelerate-guide/acc-offboard.md index 826786d80..110cbe829 100644 --- a//managedservices/latest/accelerate-guide/acc-offboard.md +++ b//managedservices/latest/accelerate-guide/acc-offboard.md @@ -19 +19 @@ While preparing to offboard from Accelerate, keep the following considerations i - * **Access** : The `ams-access-management` AWS CloudFormation stack that defines the `ams-access-management` AWS Identity and Access Management role isn't deleted. After offboarding, these resources remain, but are unused by other components that are left behind. You can delete the stack and role at your convenience. + * **Access** : The `ams-access-management` CloudFormation stack that defines the `ams-access-management` AWS Identity and Access Management role isn't deleted. After offboarding, these resources remain, but are unused by other components that are left behind. You can delete the stack and role at your convenience. @@ -56 +56 @@ While preparing to offboard from Accelerate, keep the following considerations i -Customized AWS CloudFormation stacks that deploy configurations related to Alarm Manager or Resource Tagger, along with the AMS-supplied Alarm Manager and Resource Tagger configuration stacks, remain in your account when you offboard from AWS Managed Services. +Customized CloudFormation stacks that deploy configurations related to Alarm Manager or Resource Tagger, along with the AMS-supplied Alarm Manager and Resource Tagger configuration stacks, remain in your account when you offboard from AWS Managed Services.