AWS codepipeline documentation change
Summary
Updated references from 'AWS CloudFormation' to 'CloudFormation' in Lambda integration model documentation
Security assessment
The change only modifies branding terminology (removing 'AWS' prefix from CloudFormation references). No security implications or security-related content changes are present. The permissions guidance remains functionally identical.
Diff
diff --git a/codepipeline/latest/userguide/action-types.md b/codepipeline/latest/userguide/action-types.md index d36c9667e..6ce537964 100644 --- a//codepipeline/latest/userguide/action-types.md +++ b//codepipeline/latest/userguide/action-types.md @@ -74 +74 @@ Choose your integration model and then create the configuration for that model. - * For the Lambda integration model, you create a Lambda function and add permissions. Add permissions to your integrator Lambda function to provide the CodePipeline service with permissions to invoke it using the CodePipeline service principal: `codepipeline.amazonaws.com`. The permissions can be added using AWS CloudFormation or the command line. + * For the Lambda integration model, you create a Lambda function and add permissions. Add permissions to your integrator Lambda function to provide the CodePipeline service with permissions to invoke it using the CodePipeline service principal: `codepipeline.amazonaws.com`. The permissions can be added using CloudFormation or the command line. @@ -76 +76 @@ Choose your integration model and then create the configuration for that model. - * Example for adding permissions using AWS CloudFormation: + * Example for adding permissions using CloudFormation: