AWS codepipeline documentation change
Summary
Updated references from 'AWS CloudFormation' to 'CloudFormation' in documentation about S3 bucket encryption configuration
Security assessment
The changes are purely editorial/branding updates to use the shortened 'CloudFormation' name rather than 'AWS CloudFormation'. No security-related content was added, removed, or modified beyond terminology. The encryption configuration guidance remains unchanged.
Diff
diff --git a/codepipeline/latest/userguide/S3-artifact-encryption.md b/codepipeline/latest/userguide/S3-artifact-encryption.md index bb4ad9743..982acc59f 100644 --- a//codepipeline/latest/userguide/S3-artifact-encryption.md +++ b//codepipeline/latest/userguide/S3-artifact-encryption.md @@ -5 +5 @@ -View your AWS managed keyConfigure server-side encryption for S3 buckets using AWS CloudFormation or the AWS CLI +View your AWS managed keyConfigure server-side encryption for S3 buckets using CloudFormation or the AWS CLI @@ -73 +73 @@ For more information about AWS KMS, see the [AWS Key Management Service Develope - * Configure server-side encryption for S3 buckets using AWS CloudFormation or the AWS CLI + * Configure server-side encryption for S3 buckets using CloudFormation or the AWS CLI @@ -99 +99 @@ For more information about the Regions and endpoints available for CodePipeline, -## Configure server-side encryption for S3 buckets using AWS CloudFormation or the AWS CLI +## Configure server-side encryption for S3 buckets using CloudFormation or the AWS CLI @@ -101 +101 @@ For more information about the Regions and endpoints available for CodePipeline, -When you use AWS CloudFormation or the AWS CLI to create a pipeline, you must configure server-side encryption manually. Use the sample bucket policy above, and then create your own customer managed key. You can also use your own keys instead of the AWS managed key. Some reasons to choose your own key include: +When you use CloudFormation or the AWS CLI to create a pipeline, you must configure server-side encryption manually. Use the sample bucket policy above, and then create your own customer managed key. You can also use your own keys instead of the AWS managed key. Some reasons to choose your own key include: