AWS organizations documentation change
Summary
Updated documentation to use 'CloudFormation' instead of 'AWS CloudFormation' throughout the text for consistency
Security assessment
The changes are purely branding/naming convention updates (removing redundant 'AWS' prefix from CloudFormation references). No security-related content was added, modified, or removed. The security implications of service-linked roles and trusted access remain unchanged.
Diff
diff --git a/organizations/latest/userguide/services-that-can-integrate-cloudformation.md b/organizations/latest/userguide/services-that-can-integrate-cloudformation.md index a7e6ec585..349354d06 100644 --- a//organizations/latest/userguide/services-that-can-integrate-cloudformation.md +++ b//organizations/latest/userguide/services-that-can-integrate-cloudformation.md @@ -9 +9 @@ Service-linked rolesService principalsEnable trusted accessDisable trusted acces -AWS CloudFormation StackSets enables you to create, update, or delete stacks across multiple AWS accounts and AWS Regions with a single operation. StackSets integration with AWS Organizations enables you to create stack sets with service-managed permissions, using a service-linked role that has the relevant permission in each member account. This lets you deploy stack instances to member accounts in your organization. You don't have to create the necessary AWS Identity and Access Management roles; StackSets creates the IAM role in each member account on your behalf. +CloudFormation StackSets enables you to create, update, or delete stacks across multiple AWS accounts and AWS Regions with a single operation. StackSets integration with AWS Organizations enables you to create stack sets with service-managed permissions, using a service-linked role that has the relevant permission in each member account. This lets you deploy stack instances to member accounts in your organization. You don't have to create the necessary AWS Identity and Access Management roles; StackSets creates the IAM role in each member account on your behalf. @@ -25 +25 @@ Use the following information to help you integrate AWS CloudFormation StackSets -The following [service-linked role](https://docs.aws.amazon.com/IAM/latest/UserGuide/using-service-linked-roles.html) is automatically created in your organization's management account when you enable trusted access. This role allows AWS CloudFormation Stacksets to perform supported operations within your organization's accounts in your organization. +The following [service-linked role](https://docs.aws.amazon.com/IAM/latest/UserGuide/using-service-linked-roles.html) is automatically created in your organization's management account when you enable trusted access. This role allows CloudFormation Stacksets to perform supported operations within your organization's accounts in your organization. @@ -27 +27 @@ The following [service-linked role](https://docs.aws.amazon.com/IAM/latest/UserG -You can delete or modify this role only if you disable trusted access between AWS CloudFormation Stacksets and Organizations, or if you remove the member account from the organization. +You can delete or modify this role only if you disable trusted access between CloudFormation Stacksets and Organizations, or if you remove the member account from the organization. @@ -45 +45 @@ For more details about creating stack sets, see [Working with AWS CloudFormation -The service-linked role in the previous section can be assumed only by the service principals authorized by the trust relationships defined for the role. The service-linked roles used by AWS CloudFormation Stacksets grant access to the following service principals: +The service-linked role in the previous section can be assumed only by the service principals authorized by the trust relationships defined for the role. The service-linked roles used by CloudFormation Stacksets grant access to the following service principals: @@ -58 +58 @@ You can modify or delete this role from an account only if you first disable tru -## Enabling trusted access with AWS CloudFormation Stacksets +## Enabling trusted access with CloudFormation Stacksets @@ -62 +62 @@ For information about the permissions needed to enable trusted access, see [Perm -Only an administrator in the Organizations management account has permissions to enable trusted access with another AWS service. You can enable trusted access using either the AWS CloudFormation console or the Organizations console. +Only an administrator in the Organizations management account has permissions to enable trusted access with another AWS service. You can enable trusted access using either the CloudFormation console or the Organizations console. @@ -66 +66 @@ You can only enable trusted access using AWS CloudFormation StackSets. -To enable trusted access using the AWS CloudFormation Stacksets console, see [Enable Trusted Access with AWS Organizations](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/stacksets-orgs-enable-trusted-access.html) in the AWS CloudFormation User Guide. +To enable trusted access using the CloudFormation Stacksets console, see [Enable Trusted Access with AWS Organizations](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/stacksets-orgs-enable-trusted-access.html) in the AWS CloudFormation User Guide. @@ -68 +68 @@ To enable trusted access using the AWS CloudFormation Stacksets console, see [En -## Disabling trusted access with AWS CloudFormation Stacksets +## Disabling trusted access with CloudFormation Stacksets @@ -74 +74 @@ Only an administrator in an Organizations management account has permissions to -You can disable trusted access using either the AWS CloudFormation console or the Organizations console. +You can disable trusted access using either the CloudFormation console or the Organizations console. @@ -78 +78 @@ You can disable trusted access using either the AWS CloudFormation console or th -If you disable trusted access programmatically (e.g with AWS CLI or with an API), be aware that this will remove the permission. It is better to disable trusted access with the AWS CloudFormation console. +If you disable trusted access programmatically (e.g with AWS CLI or with an API), be aware that this will remove the permission. It is better to disable trusted access with the CloudFormation console. @@ -123 +123 @@ This command produces no output when successful. -## Enabling a delegated administrator account for AWS CloudFormation Stacksets +## Enabling a delegated administrator account for CloudFormation Stacksets @@ -125 +125 @@ This command produces no output when successful. -When you designate a member account as a delegated administrator for the organization, users and roles from that account can perform administrative actions for AWS CloudFormation Stacksets that otherwise can be performed only by users or roles in the organization's management account. This helps you to separate management of the organization from management of AWS CloudFormation Stacksets. +When you designate a member account as a delegated administrator for the organization, users and roles from that account can perform administrative actions for CloudFormation Stacksets that otherwise can be performed only by users or roles in the organization's management account. This helps you to separate management of the organization from management of CloudFormation Stacksets. @@ -127 +127 @@ When you designate a member account as a delegated administrator for the organiz -For instructions on how to designate a member account as a delegated administrator of AWS CloudFormation Stacksets in the organization, see [Register a delegated administrator](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/stacksets-orgs-delegated-admin.html) in the _AWS CloudFormation User Guide_. +For instructions on how to designate a member account as a delegated administrator of CloudFormation Stacksets in the organization, see [Register a delegated administrator](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/stacksets-orgs-delegated-admin.html) in the _AWS CloudFormation User Guide_.