Periodic update - 07/25/22

Author: darlaker

Diff for: doc_source/S3-artifact-encryption.md

@@ -52,7 +52,7 @@ For more information about AWS KMS, see the [AWS Key Management Service Develope
 + [View your AWS managed key](#S3-view-default-keys)
 + [Configure server\-side encryption for S3 buckets using AWS CloudFormation or the AWS CLI](#S3-rotate-customer-key)
 
-### View your AWS managed key<a name="S3-view-default-keys"></a>
+## View your AWS managed key<a name="S3-view-default-keys"></a>
 
 When you use the **Create Pipeline** wizard to create your first pipeline, an S3 bucket is created for you in the same Region you created the pipeline\. The bucket is used to store pipeline artifacts\. When a pipeline runs, artifacts are put into and retrieved from the S3 bucket\. By default, CodePipeline uses server\-side encryption with AWS KMS using the AWS managed key for Amazon S3 \(the `aws/s3` key\)\. This AWS managed key is created and stored in your AWS account\. When artifacts are retrieved from the S3 bucket, CodePipeline uses the same SSE\-KMS process to decrypt the artifact\.
 
@@ -72,7 +72,7 @@ When you use the **Create Pipeline** wizard to create your first pipeline, an S3
 
 
 
-### Configure server\-side encryption for S3 buckets using AWS CloudFormation or the AWS CLI<a name="S3-rotate-customer-key"></a>
+## Configure server\-side encryption for S3 buckets using AWS CloudFormation or the AWS CLI<a name="S3-rotate-customer-key"></a>
 
 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 owncustomer managed key\. You can also use your own keys instead of the AWS managed key\. Some reasons to choose your own key include:
 + You want to rotate the key on a schedule to meet business or security requirements for your organization\.

Diff for: doc_source/action-reference-AppConfig.md

@@ -33,7 +33,7 @@ Required: No
 The AWS AppConfig deployment strategy to use for deployment\.
 
 ## Input artifacts<a name="action-reference-AppConfig-input"></a>
-+ **Number of Artifacts:** `1`
++ **Number of artifacts:** `1`
 + **Description:** The input artifact for the deploy action\.
 
 ## Output artifacts<a name="action-reference-AppConfig-output"></a>

Diff for: doc_source/action-reference-CloudFormation.md

@@ -2,6 +2,8 @@
 
 Executes an operation on an AWS CloudFormation stack\. A stack is a collection of AWS resources that you can manage as a single unit\. The resources in a stack are defined by the stack's AWS CloudFormation template\. A change set creates a comparison that can be viewed without altering the original stack\. For information about the types of AWS CloudFormation actions that can be performed on stacks and change sets, see the `ActionMode` parameter\.
 
+**Note**  
+
 **Topics**
 + [Action type](#action-reference-CloudFormation-type)
 + [Configuration parameters](#action-reference-CloudFormation-config)
@@ -107,14 +109,14 @@ The template configuration file name follows this format:
 ```
 
 ## Input artifacts<a name="action-reference-CloudFormation-input"></a>
-+ **Number of Artifacts:** `0 to 10`
++ **Number of artifacts:** `0 to 10`
 + **Description:** As input, the AWS CloudFormation action optionally accepts artifacts for these purposes:
   + To provide the stack template file to execute\. \(See the `TemplatePath` parameter\.\)
   + To provide the template configuration file to use\. \(See the `TemplateConfiguration` parameter\.\) For more information about the template configuration file format, see [AWS CloudFormation Artifacts](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/continuous-delivery-codepipeline-cfn-artifacts.html)\. 
   + To provide the artifact for a Lambda function to be deployed as part of the AWS CloudFormation stack\.
 
 ## Output artifacts<a name="action-reference-CloudFormation-output"></a>
-+ **Number of Artifacts:** `0 to 1` 
++ **Number of artifacts:** `0 to 1` 
 + **Description:** If the `OutputFileName` parameter is specified, there is an output artifact produced by this action that contains a JSON file with the specified name\. The JSON file contains the contents of the Outputs section from the AWS CloudFormation stack\.
 
   For more information about the outputs section you can create for your AWS CloudFormation action, see [Outputs](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/outputs-section-structure.html)\.

Diff for: doc_source/action-reference-CodeBuild.md

@@ -54,15 +54,15 @@ When you enter the `name`, `value`, and `type` for your environment variables co
 For more information, see [ EnvironmentVariable](https://docs.aws.amazon.com/codebuild/latest/APIReference/API_EnvironmentVariable.html)\.
 
 ## Input artifacts<a name="action-reference-CodeBuild-input"></a>
-+ **Number of Artifacts:** `1 to 5`
++ **Number of artifacts:** `1 to 5`
 + **Description:** CodeBuild looks for the build spec file and runs the build spec commands from the directory of the primary source artifact\. When more than one input source is specified for the CodeBuild action, this artifact must be set using the `PrimarySource` action configuration parameter in CodePipeline\. 
 
   Each input artifact is extracted to its own directory, the locations of which are stored in environment variables\. The directory for the primary source artifact is made available with `$CODEBUILD_SRC_DIR`\. The directories for all other input artifacts are made available with `$CODEBUILD_SRC_DIR_yourInputArtifactName`\.
 **Note**  
 The artifact configured in your CodeBuild project becomes the input artifact used by the CodeBuild action in your pipeline\.
 
 ## Output artifacts<a name="action-reference-CodeBuild-output"></a>
-+ **Number of Artifacts:** `0 to 5` 
++ **Number of artifacts:** `0 to 5` 
 + **Description:** These can be used to make the artifacts that are defined in the CodeBuild build spec file available to subsequent actions in the pipeline\. When only one output artifact is defined, this artifact can be defined directly under the `artifacts` section of the build spec file\. When more than one output artifact is specified, all artifacts referenced must be defined as secondary artifacts in the build spec file\. The names of the output artifacts in CodePipeline must match the artifact identifiers in the build spec file\.
 **Note**  
 The artifact configured in your CodeBuild project becomes the CodePipeline input artifact in your pipeline action\.

Diff for: doc_source/action-reference-CodeCommit.md

@@ -54,11 +54,11 @@ The `CODEBUILD_CLONE_REF` option can only be used by CodeBuild downstream action
 If you choose this option, you need to add the `codecommit:GitPull` permission to your CodeBuild service role as shown in [Add CodeBuild GitClone permissions for CodeCommit source actions](troubleshooting.md#codebuild-role-codecommitclone)\. You also need to add the `codecommit:GetRepository` permission to your CodePipeline service role as shown in [Add permissions to the CodePipeline service role](security-iam.md#how-to-update-role-new-services)\. For a tutorial that shows you how to use the **Full clone** option, see [Tutorial: Use full clone with a CodeCommit pipeline source](tutorials-codecommit-gitclone.md)\.
 
 ## Input artifacts<a name="action-reference-CodeCommit-input"></a>
-+ **Number of Artifacts:** `0`
++ **Number of artifacts:** `0`
 + **Description:** Input artifacts do not apply for this action type\.
 
 ## Output artifacts<a name="action-reference-CodeCommit-output"></a>
-+ **Number of Artifacts:** `1` 
++ **Number of artifacts:** `1` 
 + **Description:** The output artifact of this action is a ZIP file that contains the contents of the configured repository and branch at the commit specified as the source revision for the pipeline execution\. The artifacts generated from the repository are the output artifacts for the CodeCommit action\. The source code commit ID is displayed in CodePipeline as the source revision for the triggered pipeline execution\.
 
 ## Output variables<a name="action-reference-CodeCommit-variables"></a>
@@ -89,7 +89,7 @@ For more information about the difference between an author and a committer in G
 
 ## Example action configuration<a name="action-reference-CodeCommit-example"></a>
 
-### Example for default output artifact format<a name="w23aac44c29c25b3"></a>
+### Example for default output artifact format<a name="w23aac42c31c25b3"></a>
 
 ------
 #### [ YAML ]
@@ -147,7 +147,7 @@ Actions:
 
 ------
 
-### Example for full clone output artifact format<a name="w23aac44c29c25b5"></a>
+### Example for full clone output artifact format<a name="w23aac42c31c25b5"></a>
 
 ------
 #### [ YAML ]

Diff for: doc_source/action-reference-CodeDeploy.md

@@ -3,23 +3,23 @@
 You use an AWS CodeDeploy action to deploy application code to your deployment fleet\. Your deployment fleet can consist of Amazon EC2 instances, on\-premises instances, or both\.
 
 **Note**  
-This reference topic describes the CodeDeploy deployment action for CodePipeline where the deployment platform is Amazon EC2\. For reference information about Amazon Elastic Container Service to CodeDeploy blue/green deployment actions in CodePipeline, see [Amazon Elastic Container Service and CodeDeploy Blue\-Green](action-reference-ECSbluegreen.md)\.
+This reference topic describes the CodeDeploy deployment action for CodePipeline where the deployment platform is Amazon EC2\. For reference information about Amazon Elastic Container Service to CodeDeploy blue/green deployment actions in CodePipeline, see [Amazon Elastic Container Service and CodeDeploy blue\-green](action-reference-ECSbluegreen.md)\.
 
 **Topics**
-+ [Action Type](#action-reference-CodeDeploy-type)
-+ [Configuration Parameters](#action-reference-CodeDeploy-config)
-+ [Input Artifacts](#action-reference-CodeDeploy-input)
-+ [Output Artifacts](#action-reference-CodeDeploy-output)
-+ [Action Declaration](#action-reference-CodeDeploy-example)
-+ [See Also](#action-reference-CodeDeploy-links)
-
-## Action Type<a name="action-reference-CodeDeploy-type"></a>
++ [Action type](#action-reference-CodeDeploy-type)
++ [Configuration parameters](#action-reference-CodeDeploy-config)
++ [Input artifacts](#action-reference-CodeDeploy-input)
++ [Output artifacts](#action-reference-CodeDeploy-output)
++ [Action declaration](#action-reference-CodeDeploy-example)
++ [See also](#action-reference-CodeDeploy-links)
+
+## Action type<a name="action-reference-CodeDeploy-type"></a>
 + Category: `Deploy`
 + Owner: `AWS`
 + Provider: `CodeDeploy`
 + Version: `1`
 
-## Configuration Parameters<a name="action-reference-CodeDeploy-config"></a>
+## Configuration parameters<a name="action-reference-CodeDeploy-config"></a>
 
 **ApplicationName**  
 Required: Yes  
@@ -29,8 +29,8 @@ The name of the application that you created in CodeDeploy\.
 Required: Yes  
 The deployment group that you created in CodeDeploy\.
 
-## Input Artifacts<a name="action-reference-CodeDeploy-input"></a>
-+ **Number of Artifacts:** `1`
+## Input artifacts<a name="action-reference-CodeDeploy-input"></a>
++ **Number of artifacts:** `1`
 + **Description:** The AppSpec file that CodeDeploy uses to determine:
   + What to install onto your instances from your application revision in Amazon S3 or GitHub\.
   + Which lifecycle event hooks to run in response to deployment lifecycle events\.
@@ -39,11 +39,11 @@ The deployment group that you created in CodeDeploy\.
 
 
 
-## Output Artifacts<a name="action-reference-CodeDeploy-output"></a>
-+ **Number of Artifacts:** `0` 
+## Output artifacts<a name="action-reference-CodeDeploy-output"></a>
++ **Number of artifacts:** `0` 
 + **Description:** Output artifacts do not apply for this action type\.
 
-## Action Declaration<a name="action-reference-CodeDeploy-example"></a>
+## Action declaration<a name="action-reference-CodeDeploy-example"></a>
 
 ------
 #### [ YAML ]
@@ -103,7 +103,7 @@ Actions:
 
 ------
 
-## See Also<a name="action-reference-CodeDeploy-links"></a>
+## See also<a name="action-reference-CodeDeploy-links"></a>
 
 The following related resources can help you as you work with this action\.
 + [Tutorial: Create a simple pipeline \(S3 bucket\)](tutorials-simple-s3.md) – This tutorial walks you through the creation of a source bucket, EC2 instances, and CodeDeploy resources to deploy a sample application\. You then build your pipeline with a CodeDeploy deployment action that deploys code maintained in your S3 bucket to your Amazon EC2 instance\.

Diff for: doc_source/action-reference-CodestarConnectionSource.md

@@ -3,7 +3,7 @@
 Triggers a pipeline when a new commit is made on a third\-party source code repository\. The source action retrieves code changes when a pipeline is manually run or when a webhook event is sent from the source provider\. 
 
 **Note**  
-This feature is not available in the Asia Pacific \(Hong Kong\) or Europe \(Milan\) Region\. To use other source actions available in that Region, see [Source action integrations](integrations-action-type.md#integrations-source)\.
+This feature is not available in the Asia Pacific \(Hong Kong\) and Europe \(Milan\) Regions\. To reference other available actions, see [Product and service integrations with CodePipeline](integrations.md)\.
 
 Connections can associate your AWS resources with the following third\-party repositories:
 + Bitbucket Cloud \(through the **Bitbucket** provider option in the CodePipeline console\)
@@ -72,11 +72,11 @@ Controls automatically starting your pipeline when a new commit is made on the c
 + `false`: CodePipeline does not start your pipeline on new commits\.
 
 ## Input artifacts<a name="action-reference-CodestarConnectionSource-input"></a>
-+ **Number of Artifacts:** `0`
++ **Number of artifacts:** `0`
 + **Description:** Input artifacts do not apply for this action type\.
 
 ## Output artifacts<a name="action-reference-CodestarConnectionSource-output"></a>
-+ **Number of Artifacts:** `1` 
++ **Number of artifacts:** `1` 
 + **Description:** The artifacts generated from the repository are the output artifacts for the `CodeStarSourceConnection` action\. The source code commit ID is displayed in CodePipeline as the source revision for the triggered pipeline execution\. You can configure the output artifact of this action in:
   + A ZIP file that contains the contents of the configured repository and branch at the commit specified as the source revision for the pipeline execution\.
   + A JSON file that contains a URL reference to the repository so that downstream actions can perform Git commands directly\.

Diff for: doc_source/action-reference-DeviceFarm.md

@@ -2,21 +2,23 @@
 
 In your pipeline, you can configure a test action that uses AWS Device Farm to run and test your application on devices\. Device Farm uses test pools of devices and testing frameworks to test applications on specific devices\. For information about the types of testing frameworks supported by the Device Farm action, see [Working with Test Types in AWS Device Farm](https://docs.aws.amazon.com/devicefarm/latest/developerguide/test-types.html)\.
 
+**Note**  
+
 **Topics**
-+ [Action Type](#action-reference-DeviceFarm-type)
-+ [Configuration Parameters](#action-reference-DeviceFarm-config)
-+ [Input Artifacts](#action-reference-DeviceFarm-input)
-+ [Output Artifacts](#action-reference-DeviceFarm-output)
-+ [Action Declaration](#action-reference-DeviceFarm-example)
-+ [See Also](#action-reference-DeviceFarm-links)
-
-## Action Type<a name="action-reference-DeviceFarm-type"></a>
++ [Action type](#action-reference-DeviceFarm-type)
++ [Configuration parameters](#action-reference-DeviceFarm-config)
++ [Input artifacts](#action-reference-DeviceFarm-input)
++ [Output artifacts](#action-reference-DeviceFarm-output)
++ [Action declaration](#action-reference-DeviceFarm-example)
++ [See also](#action-reference-DeviceFarm-links)
+
+## Action type<a name="action-reference-DeviceFarm-type"></a>
 + Category: `Test`
 + Owner: `AWS`
 + Provider: `DeviceFarm`
 + Version: `1`
 
-## Configuration Parameters<a name="action-reference-DeviceFarm-config"></a>
+## Configuration parameters<a name="action-reference-DeviceFarm-config"></a>
 
 **AppType**  
 Required: Yes  
@@ -138,15 +140,15 @@ The latitude of the device expressed in geographic coordinate system degrees\.
 Required: No  
 The longitude of the device expressed in geographic coordinate system degrees\.
 
-## Input Artifacts<a name="action-reference-DeviceFarm-input"></a>
-+ **Number of Artifacts:** `1`
+## Input artifacts<a name="action-reference-DeviceFarm-input"></a>
++ **Number of artifacts:** `1`
 + **Description:** The set of artifacts to be made available to the test action\. Device Farm looks for the built application and test definitions to use\.
 
-## Output Artifacts<a name="action-reference-DeviceFarm-output"></a>
+## Output artifacts<a name="action-reference-DeviceFarm-output"></a>
 + **Number of Artifacts:** `0` 
 + **Description:** Output artifacts do not apply for this action type\.
 
-## Action Declaration<a name="action-reference-DeviceFarm-example"></a>
+## Action declaration<a name="action-reference-DeviceFarm-example"></a>
 
 ------
 #### [ YAML ]
@@ -215,7 +217,7 @@ Actions:
 
 ------
 
-## See Also<a name="action-reference-DeviceFarm-links"></a>
+## See also<a name="action-reference-DeviceFarm-links"></a>
 
 The following related resources can help you as you work with this action\.
 + [Working with Test Types in Device Farm](https://docs.aws.amazon.com/devicefarm/latest/developerguide/test-types.html) – This reference chapter in the *Device Farm Developer Guide* provides more description about the Android, iOS, and Web Application testing frameworks supported by Device Farm\.

Diff for: doc_source/action-reference-ECR.md

@@ -33,11 +33,11 @@ The tag used for the image\.
 If a value for `ImageTag` is not specified, the value defaults to `latest`\.
 
 ## Input artifacts<a name="action-reference-ECR-input"></a>
-+ **Number of Artifacts:** `0`
++ **Number of artifacts:** `0`
 + **Description:** Input artifacts do not apply for this action type\.
 
 ## Output artifacts<a name="action-reference-ECR-output"></a>
-+ **Number of Artifacts:** `1` 
++ **Number of artifacts:** `1` 
 + **Description:** This action produces an artifact that contains an `imageDetail.json` file that contains the URI for the image that triggered the pipeline execution\. For information about the `imageDetail.json` file, see [imageDetail\.json file for Amazon ECS blue/green deployment actions](file-reference.md#file-reference-ecs-bluegreen)\.
 
 ## Output variables<a name="action-reference-ECR-variables"></a>