AWS controltower documentation change
Summary
Multiple replacements of 'AWS CloudFormation' with 'CloudFormation' in troubleshooting guidance
Security assessment
Style/branding updates to service names. The troubleshooting content about STS regions and StackSet failures remains operationally similar with no new security implications.
Diff
diff --git a/controltower/latest/userguide/troubleshooting.md b/controltower/latest/userguide/troubleshooting.md index 40c70bb3a..005ef5d42 100644 --- a//controltower/latest/userguide/troubleshooting.md +++ b//controltower/latest/userguide/troubleshooting.md @@ -50 +50 @@ Common causes of landing zone launch failure: - * AWS CloudFormation StackSet failure. + * CloudFormation StackSet failure. @@ -61 +61 @@ If you encounter this issue, check your email. You might have been sent confirma -**Failed StackSets** : Another possible cause of landing zone launch failure is AWS CloudFormation StackSet failure. AWS Security Token Service (STS) regions must be enabled in the management account for all AWS Regions that AWS Control Tower is governing, so that the provisioning can be successful; otherwise, stack sets will fail to launch. +**Failed StackSets** : Another possible cause of landing zone launch failure is CloudFormation StackSet failure. AWS Security Token Service (STS) regions must be enabled in the management account for all AWS Regions that AWS Control Tower is governing, so that the provisioning can be successful; otherwise, stack sets will fail to launch. @@ -69 +69 @@ Be sure to enable all of your required AWS Security Token Service [ (STS) endpoi - 1. Navigate to the AWS CloudFormation console in the appropriate AWS Region. + 1. Navigate to the CloudFormation console in the appropriate AWS Region. @@ -206 +206 @@ Try again to provision your account, without specifying any of those options. Fo - * Look for AWS CloudFormation StackSets operations that are still running. + * Look for CloudFormation StackSets operations that are still running.