AWS systems-manager documentation change
Summary
Updated references from 'AWS CloudFormation' to 'CloudFormation' throughout documentation
Security assessment
Changes are stylistic/terminology updates to use service product name 'CloudFormation' instead of 'AWS CloudFormation'. No security-related content was added or modified. The IAM role permissions (AWS-QuickSetup-LocalExecutionRole) and security considerations around StackSet limitations remain unchanged.
Diff
diff --git a/systems-manager/latest/userguide/quick-setup-getting-started.md b/systems-manager/latest/userguide/quick-setup-getting-started.md index 2db1799ec..c308a5f96 100644 --- a//systems-manager/latest/userguide/quick-setup-getting-started.md +++ b//systems-manager/latest/userguide/quick-setup-getting-started.md @@ -24 +24 @@ Use the information in this topic to help you prepare to use Quick Setup. -Quick Setup launched a new console experience and a new API. Now you can interact with this API using the console, AWS CLI, AWS CloudFormation, and SDKs. If you opt in to the new experience, your existing configurations are recreated using the new API. Depending on the number of existing configurations in your account, this process can take several minutes. +Quick Setup launched a new console experience and a new API. Now you can interact with this API using the console, AWS CLI, CloudFormation, and SDKs. If you opt in to the new experience, your existing configurations are recreated using the new API. Depending on the number of existing configurations in your account, this process can take several minutes. @@ -206 +206 @@ During onboarding, Quick Setup creates the following AWS Identity and Access Man - * `AWS-QuickSetup-LocalExecutionRole` – Grants AWS CloudFormation permissions to use any template, excluding the patch policy template, and create the necessary resources. + * `AWS-QuickSetup-LocalExecutionRole` – Grants CloudFormation permissions to use any template, excluding the patch policy template, and create the necessary resources. @@ -234 +234 @@ For information about AWS Organizations account types, see [AWS Organizations te -Quick Setup uses AWS CloudFormation StackSets to deploy your configurations across AWS accounts and Regions. If the number of target accounts multiplied by the number of Regions exceeds 10,000, the configuration fails to deploy. We recommend reviewing your use case and creating configurations that use fewer targets to accommodate the growth of your organization. Stack instances aren't deployed to your organization's management account. For more information, see [Considerations when creating a stack set with service-managed permissions](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/stacksets-getting-started-create.html?icmpid=docs_cfn_console#stacksets-orgs-considerations). +Quick Setup uses CloudFormation StackSets to deploy your configurations across AWS accounts and Regions. If the number of target accounts multiplied by the number of Regions exceeds 10,000, the configuration fails to deploy. We recommend reviewing your use case and creating configurations that use fewer targets to accommodate the growth of your organization. Stack instances aren't deployed to your organization's management account. For more information, see [Considerations when creating a stack set with service-managed permissions](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/stacksets-getting-started-create.html?icmpid=docs_cfn_console#stacksets-orgs-considerations). @@ -242 +242 @@ If you use the console to work with Quick Setup, the service handles onboarding - 1. Activate trusted access for AWS CloudFormation with Organizations. This provides the management account with the permissions needed to create and manage StackSets for your organization. You can use AWS CloudFormation's `ActivateOrganizationsAccess` API action to complete this step. For more information, see [ActivateOrganizationsAccess](https://docs.aws.amazon.com/AWSCloudFormation/latest/APIReference/API_ActivateOrganizationsAccess.html) in the _AWS CloudFormation API Reference_. + 1. Activate trusted access for CloudFormation with Organizations. This provides the management account with the permissions needed to create and manage StackSets for your organization. You can use CloudFormation's `ActivateOrganizationsAccess` API action to complete this step. For more information, see [ActivateOrganizationsAccess](https://docs.aws.amazon.com/AWSCloudFormation/latest/APIReference/API_ActivateOrganizationsAccess.html) in the _AWS CloudFormation API Reference_. @@ -278 +278 @@ JSON - 5. Create the required IAM roles for AWS CloudFormation StackSets to use. You must create an _execution_ role and an _administration_ role. + 5. Create the required IAM roles for CloudFormation StackSets to use. You must create an _execution_ role and an _administration_ role.