AWS codepipeline documentation change
Summary
Consistently changed 'AWS CloudFormation' to 'CloudFormation' throughout Lambda function documentation
Security assessment
Purely stylistic changes to standardize product naming. Security-related content about Lambda permissions and resource management remains unchanged. No vulnerabilities addressed or security features added.
Diff
diff --git a/codepipeline/latest/userguide/actions-invoke-lambda-function.md b/codepipeline/latest/userguide/actions-invoke-lambda-function.md index b6f20df70..65e4e13b8 100644 --- a//codepipeline/latest/userguide/actions-invoke-lambda-function.md +++ b//codepipeline/latest/userguide/actions-invoke-lambda-function.md @@ -17 +17 @@ Here are some ways Lambda functions can be used in pipelines: - * To create resources on demand in one stage of a pipeline using AWS CloudFormation and delete them in another stage. + * To create resources on demand in one stage of a pipeline using CloudFormation and delete them in another stage. @@ -428 +428 @@ The following sample Lambda functions demonstrate additional functionality you c -The following sample shows a function that creates or updates a stack based on a supplied AWS CloudFormation template. The template creates an Amazon S3 bucket. It is for demonstration purposes only, to minimize costs. Ideally, you should delete the stack before you upload anything to the bucket. If you upload files to the bucket, you cannot delete the bucket when you delete the stack. You must manually delete everything in the bucket before you can delete the bucket itself. +The following sample shows a function that creates or updates a stack based on a supplied CloudFormation template. The template creates an Amazon S3 bucket. It is for demonstration purposes only, to minimize costs. Ideally, you should delete the stack before you upload anything to the bucket. If you upload files to the bucket, you cannot delete the bucket when you delete the stack. You must manually delete everything in the bucket before you can delete the bucket itself. @@ -430 +430 @@ The following sample shows a function that creates or updates a stack based on a -This Python sample assumes you have a pipeline that uses an Amazon S3 bucket as a source action, or that you have access to a versioned Amazon S3 bucket you can use with the pipeline. You create the AWS CloudFormation template, compress it, and upload it to that bucket as a .zip file. You must then add a source action to your pipeline that retrieves this .zip file from the bucket. +This Python sample assumes you have a pipeline that uses an Amazon S3 bucket as a source action, or that you have access to a versioned Amazon S3 bucket you can use with the pipeline. You create the CloudFormation template, compress it, and upload it to that bucket as a .zip file. You must then add a source action to your pipeline that retrieves this .zip file from the bucket. @@ -447 +447 @@ This sample demonstrates: -To use this sample Lambda function, the policy for the Lambda execution role must have `Allow` permissions in AWS CloudFormation, Amazon S3, and CodePipeline, as shown in this sample policy: +To use this sample Lambda function, the policy for the Lambda execution role must have `Allow` permissions in CloudFormation, Amazon S3, and CodePipeline, as shown in this sample policy: @@ -494 +494 @@ JSON -To create the AWS CloudFormation template, open any plain-text editor and copy and paste the following code: +To create the CloudFormation template, open any plain-text editor and copy and paste the following code: @@ -519 +519 @@ Save this as a JSON file with the name `template.json` in a directory named `tem -The sample Lambda function expects these file names and compressed structure. However, you can substitute your own AWS CloudFormation template for this sample. If you use your own template, make sure you modify the policy for the Lambda execution role to allow any additional functionality required by your AWS CloudFormation template. +The sample Lambda function expects these file names and compressed structure. However, you can substitute your own CloudFormation template for this sample. If you use your own template, make sure you modify the policy for the Lambda execution role to allow any additional functionality required by your CloudFormation template. @@ -923 +923 @@ Under **Input artifacts** , choose `MyTemplate`. In **UserParameters** , you mus - * AWS CloudFormation template name and path to the file + * CloudFormation template name and path to the file