AWS codepipeline documentation change
Summary
Updated terminology from 'AWS CloudFormation' to 'CloudFormation' throughout the document for consistency
Security assessment
Changes are branding/terminology updates without altering security implications. No evidence of addressing vulnerabilities or modifying security configurations.
Diff
diff --git a/codepipeline/latest/userguide/pipelines-trigger-source-repo-changes-cfn.md b/codepipeline/latest/userguide/pipelines-trigger-source-repo-changes-cfn.md index 98d8c53e1..bf78d6c65 100644 --- a//codepipeline/latest/userguide/pipelines-trigger-source-repo-changes-cfn.md +++ b//codepipeline/latest/userguide/pipelines-trigger-source-repo-changes-cfn.md @@ -5 +5 @@ -# Create an EventBridge rule for a CodeCommit source (AWS CloudFormation template) +# Create an EventBridge rule for a CodeCommit source (CloudFormation template) @@ -7 +7 @@ -To use AWS CloudFormation to create a rule, update your template as shown here. +To use CloudFormation to create a rule, update your template as shown here. @@ -9 +9 @@ To use AWS CloudFormation to create a rule, update your template as shown here. -###### To update your pipeline AWS CloudFormation template and create EventBridge rule +###### To update your pipeline CloudFormation template and create EventBridge rule @@ -11 +11 @@ To use AWS CloudFormation to create a rule, update your template as shown here. - 1. In the template, under `Resources`, use the `AWS::IAM::Role` AWS CloudFormation resource to configure the IAM role that allows your event to start your pipeline. This entry creates a role that uses two policies: + 1. In the template, under `Resources`, use the `AWS::IAM::Role` CloudFormation resource to configure the IAM role that allows your event to start your pipeline. This entry creates a role that uses two policies: @@ -17 +17 @@ To use AWS CloudFormation to create a rule, update your template as shown here. -**Why am I making this change?** Adding the `AWS::IAM::Role` resource enables AWS CloudFormation to create permissions for EventBridge. This resource is added to your AWS CloudFormation stack. +**Why am I making this change?** Adding the `AWS::IAM::Role` resource enables CloudFormation to create permissions for EventBridge. This resource is added to your CloudFormation stack. @@ -96 +96 @@ JSON - 2. In the template, under `Resources`, use the `AWS::Events::Rule` AWS CloudFormation resource to add an EventBridge rule. This event pattern creates an event that monitors push changes to your repository. When EventBridge detects a repository state change, the rule invokes `StartPipelineExecution` on your target pipeline. + 2. In the template, under `Resources`, use the `AWS::Events::Rule` CloudFormation resource to add an EventBridge rule. This event pattern creates an event that monitors push changes to your repository. When EventBridge detects a repository state change, the rule invokes `StartPipelineExecution` on your target pipeline. @@ -98 +98 @@ JSON -**Why am I making this change?** Adding the `AWS::Events::Rule` resource enables AWS CloudFormation to create the event. This resource is added to your AWS CloudFormation stack. +**Why am I making this change?** Adding the `AWS::Events::Rule` resource enables CloudFormation to create the event. This resource is added to your CloudFormation stack. @@ -231 +231 @@ JSON - 4. Save the updated template to your local computer, and then open the AWS CloudFormation console. + 4. Save the updated template to your local computer, and then open the CloudFormation console. @@ -235 +235 @@ JSON - 6. Upload the template, and then view the changes listed in AWS CloudFormation. These are the changes to be made to the stack. You should see your new resources in the list. + 6. Upload the template, and then view the changes listed in CloudFormation. These are the changes to be made to the stack. You should see your new resources in the list.