AWS codepipeline documentation change
Summary
Changed 'AWS CloudFormation stack' to 'CloudFormation stack' in cross-account deployment documentation
Security assessment
The modification is a naming convention update. The security-relevant content about KMS keys and cross-account policies remains unchanged and was not enhanced or modified.
Diff
diff --git a/codepipeline/latest/userguide/integrations-general.md b/codepipeline/latest/userguide/integrations-general.md index 16cd6c14f..25dcda527 100644 --- a//codepipeline/latest/userguide/integrations-general.md +++ b//codepipeline/latest/userguide/integrations-general.md @@ -40 +40 @@ The following AWS service integrations are not based on CodePipeline action type - * To create a pipeline from one AWS account that deploys an AWS CloudFormation stack to another AWS account, you must create a customer-managed KMS key, add the key to the pipeline, and set up account policies and roles to deploy the stack to another AWS account. For more information, see [How do I use CodePipeline to deploy an AWS CloudFormation stack in a different account?](https://aws.amazon.com/premiumsupport/knowledge-center/codepipeline-deploy-cloudformation/) + * To create a pipeline from one AWS account that deploys an CloudFormation stack to another AWS account, you must create a customer-managed KMS key, add the key to the pipeline, and set up account policies and roles to deploy the stack to another AWS account. For more information, see [How do I use CodePipeline to deploy an AWS CloudFormation stack in a different account?](https://aws.amazon.com/premiumsupport/knowledge-center/codepipeline-deploy-cloudformation/)