AWS codepipeline documentation change
Summary
Updated documentation to replace 'AWS CloudFormation' with 'CloudFormation' throughout the file, including titles, descriptions, and operational references. No functional changes were made to permissions, capabilities, or deployment processes.
Security assessment
The changes are purely branding/nomenclature updates (removing 'AWS' from 'AWS CloudFormation'). No modifications to security configurations, permissions models, vulnerability mitigations, or security features were introduced. References to IAM roles, permissions requirements, and failure tolerance remain unchanged in substance.
Diff
diff --git a/codepipeline/latest/userguide/action-reference-StackSets.md b/codepipeline/latest/userguide/action-reference-StackSets.md index 0082a7ea5..0aadbc87f 100644 --- a//codepipeline/latest/userguide/action-reference-StackSets.md +++ b//codepipeline/latest/userguide/action-reference-StackSets.md @@ -5 +5 @@ -How AWS CloudFormation StackSets actions work How to structure StackSets actions in a pipelineThe CloudFormationStackSet actionThe CloudFormationStackInstances actionService role permissions: CloudFormationStackSet actionService role permissions: CloudFormationStackInstances actionPermissions models for stack set operationsTemplate parameter data typesSee also +How CloudFormation StackSets actions work How to structure StackSets actions in a pipelineThe CloudFormationStackSet actionThe CloudFormationStackInstances actionService role permissions: CloudFormationStackSet actionService role permissions: CloudFormationStackInstances actionPermissions models for stack set operationsTemplate parameter data typesSee also @@ -7 +7 @@ How AWS CloudFormation StackSets actions work How to structure StackSets actions -# AWS CloudFormation StackSets deploy action reference +# CloudFormation StackSets deploy action reference @@ -9 +9 @@ How AWS CloudFormation StackSets actions work How to structure StackSets actions -CodePipeline offers the ability to perform AWS CloudFormation StackSets operations as part of your CI/CD process. You use a stack set to create stacks in AWS accounts across AWS Regions by using a single AWS CloudFormation template. All the resources included in each stack are defined by the stack set’s AWS CloudFormation template. When you create the stack set, you specify the template to use, as well as any parameters and capabilities that the template requires. +CodePipeline offers the ability to perform CloudFormation StackSets operations as part of your CI/CD process. You use a stack set to create stacks in AWS accounts across AWS Regions by using a single CloudFormation template. All the resources included in each stack are defined by the stack set’s CloudFormation template. When you create the stack set, you specify the template to use, as well as any parameters and capabilities that the template requires. @@ -11 +11 @@ CodePipeline offers the ability to perform AWS CloudFormation StackSets operatio -For more information about concepts for AWS CloudFormation StackSets, see [StackSets concepts](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/stacksets-concepts.html) in the _AWS CloudFormation User Guide_. +For more information about concepts for CloudFormation StackSets, see [StackSets concepts](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/stacksets-concepts.html) in the _AWS CloudFormation User Guide_. @@ -13 +13 @@ For more information about concepts for AWS CloudFormation StackSets, see [Stack -You integrate your pipeline with AWS CloudFormation StackSets through two distinct action types that you use together: +You integrate your pipeline with CloudFormation StackSets through two distinct action types that you use together: @@ -30 +30 @@ To deploy to target AWS Organizations accounts or organizational unit IDs and us - * How AWS CloudFormation StackSets actions work + * How CloudFormation StackSets actions work @@ -51 +51 @@ To deploy to target AWS Organizations accounts or organizational unit IDs and us -## How AWS CloudFormation StackSets actions work +## How CloudFormation StackSets actions work @@ -260 +260 @@ Indicates that the template can create and update resources, depending on the ty -You must use this property if you have IAM resources in your stack template or you create a stack directly from a template containing macros. For the AWS CloudFormation action to successfully operate in this way, you must use one of the following capabilities: +You must use this property if you have IAM resources in your stack template or you create a stack directly from a template containing macros. For the CloudFormation action to successfully operate in this way, you must use one of the following capabilities: @@ -282 +282 @@ Valid values are: - * `SERVICE_MANAGED`: AWS CloudFormation StackSets automatically creates the IAM roles required to deploy to accounts managed by AWS Organizations. This requires an account to be a member of an Organization. + * `SERVICE_MANAGED`: CloudFormation StackSets automatically creates the IAM roles required to deploy to accounts managed by AWS Organizations. This requires an account to be a member of an Organization. @@ -296 +296 @@ This parameter can only be changed when no stack instances exist in the stack se -Because AWS CloudFormation StackSets performs operations across multiple accounts, you must define the necessary permissions in those accounts before you can create the stack set. +Because CloudFormation StackSets performs operations across multiple accounts, you must define the necessary permissions in those accounts before you can create the stack set. @@ -313 +313 @@ The name may contain alphanumeric characters, any of the following characters: _ -Because AWS CloudFormation StackSets performs operations across multiple accounts, you must define the necessary permissions in those accounts before you can create the stack set. +Because CloudFormation StackSets performs operations across multiple accounts, you must define the necessary permissions in those accounts before you can create the stack set. @@ -332 +332 @@ This parameter is optional for the SERVICE_MANAGED permissions model and is not -Describes whether AWS CloudFormation StackSets automatically deploys to AWS Organizations accounts that are added to a target organization or organizational unit (OU). If `OrganizationsAutoDeployment` is specified, do not specify `DeploymentTargets` and `Regions`. +Describes whether CloudFormation StackSets automatically deploys to AWS Organizations accounts that are added to a target organization or organizational unit (OU). If `OrganizationsAutoDeployment` is specified, do not specify `DeploymentTargets` and `Regions`. @@ -342 +342 @@ Valid values are: -StackSets automatically deploys additional stack instances to AWS Organizations accounts that are added to a target organization or organizational unit (OU) in the specified Regions. If an account is removed from a target organization or OU, AWS CloudFormation StackSets deletes stack instances from the account in the specified Regions. +StackSets automatically deploys additional stack instances to AWS Organizations accounts that are added to a target organization or organizational unit (OU) in the specified Regions. If an account is removed from a target organization or OU, CloudFormation StackSets deletes stack instances from the account in the specified Regions. @@ -444 +444 @@ Required: No -The percentage of accounts per Region for which this stack operation can fail before AWS CloudFormation stops the operation in that Region. If the operation is stopped in a Region, AWS CloudFormation doesn't attempt the operation in subsequent Regions. When calculating the number of accounts based on the specified percentage, AWS CloudFormation rounds _down_ to the next whole number. +The percentage of accounts per Region for which this stack operation can fail before CloudFormation stops the operation in that Region. If the operation is stopped in a Region, CloudFormation doesn't attempt the operation in subsequent Regions. When calculating the number of accounts based on the specified percentage, CloudFormation rounds _down_ to the next whole number. @@ -451 +451 @@ Required: No -The maximum percentage of accounts in which to perform this operation at one time. When calculating the number of accounts based on the specified percentage, AWS CloudFormation rounds _down_ to the next whole number. If rounding down would result in zero, AWS CloudFormation sets the number as one instead. Although you use this setting to specify the _maximum_ , for large deployments the actual number of accounts acted upon concurrently may be lower due to service throttling. +The maximum percentage of accounts in which to perform this operation at one time. When calculating the number of accounts based on the specified percentage, CloudFormation rounds _down_ to the next whole number. If rounding down would result in zero, CloudFormation sets the number as one instead. Although you use this setting to specify the _maximum_ , for large deployments the actual number of accounts acted upon concurrently may be lower due to service throttling. @@ -472 +472 @@ Required: No -The concurrency mode allows you to choose how the concurrency level behaves during stack set operations, whether with strict or soft failure tolerance. **Strict Failure Tolerance** lowers the deployment speed as stack set operation failures occur because concurrency decreases for each failure. **Soft Failure Tolerance** prioritizes deployment speed while still leveraging AWS CloudFormation safety capabilities. +The concurrency mode allows you to choose how the concurrency level behaves during stack set operations, whether with strict or soft failure tolerance. **Strict Failure Tolerance** lowers the deployment speed as stack set operation failures occur because concurrency decreases for each failure. **Soft Failure Tolerance** prioritizes deployment speed while still leveraging CloudFormation safety capabilities. @@ -848 +848 @@ Required: No -The percentage of accounts per Region for which this stack operation can fail before AWS CloudFormation stops the operation in that Region. If the operation is stopped in a Region, AWS CloudFormation doesn't attempt the operation in subsequent Regions. When calculating the number of accounts based on the specified percentage, AWS CloudFormation rounds _down_ to the next whole number. +The percentage of accounts per Region for which this stack operation can fail before CloudFormation stops the operation in that Region. If the operation is stopped in a Region, CloudFormation doesn't attempt the operation in subsequent Regions. When calculating the number of accounts based on the specified percentage, CloudFormation rounds _down_ to the next whole number. @@ -855 +855 @@ Required: No -The maximum percentage of accounts on which to perform this operation at one time. When calculating the number of accounts based on the specified percentage, AWS CloudFormation rounds _down_ to the next whole number. If rounding down would result in zero, AWS CloudFormation sets the number as one instead. Although you specify the _maximum_ , for large deployments the actual number of accounts acted upon concurrently may be lower due to service throttling. +The maximum percentage of accounts on which to perform this operation at one time. When calculating the number of accounts based on the specified percentage, CloudFormation rounds _down_ to the next whole number. If rounding down would result in zero, CloudFormation sets the number as one instead. Although you specify the _maximum_ , for large deployments the actual number of accounts acted upon concurrently may be lower due to service throttling. @@ -876 +876 @@ Required: No -The concurrency mode allows you to choose how the concurrency level behaves during stack set operations, whether with strict or soft failure tolerance. **Strict Failure Tolerance** lowers the deployment speed as stack set operation failures occur because concurrency decreases for each failure. **Soft Failure Tolerance** prioritizes deployment speed while still leveraging AWS CloudFormation safety capabilities. +The concurrency mode allows you to choose how the concurrency level behaves during stack set operations, whether with strict or soft failure tolerance. **Strict Failure Tolerance** lowers the deployment speed as stack set operation failures occur because concurrency decreases for each failure. **Soft Failure Tolerance** prioritizes deployment speed while still leveraging CloudFormation safety capabilities. @@ -1054 +1054 @@ JSON -For AWS CloudFormation StackSets actions, the following minimum permissions are required. +For CloudFormation StackSets actions, the following minimum permissions are required. @@ -1088 +1088 @@ For the `CloudFormationStackInstances` action, add the following to your policy -Because AWS CloudFormation StackSets performs operations across multiple accounts, you must define the necessary permissions in those accounts before you can create the stack set. You can define permissions through self-managed permissions or service-managed permissions. +Because CloudFormation StackSets performs operations across multiple accounts, you must define the necessary permissions in those accounts before you can create the stack set. You can define permissions through self-managed permissions or service-managed permissions. @@ -1094 +1094 @@ With self-managed permissions, you create the two IAM roles required by StackSet -Because AWS CloudFormation StackSets performs operations across multiple accounts, you must define the necessary permissions in those accounts before you can create the stack set. +Because CloudFormation StackSets performs operations across multiple accounts, you must define the necessary permissions in those accounts before you can create the stack set. @@ -1173 +1173 @@ To use the Amazon Web Services Documentation, Javascript must be enabled. Please -AWS CloudFormation deploy action reference +CloudFormation deploy action reference