id
stringlengths 14
16
| text
stringlengths 1
2.43k
| source
stringlengths 99
229
|
|---|---|---|
f4c6cab664cd-2 | }
}
},
. . .
```
+ To view all action executions in a pipeline execution, run the list\-action\-executions command, specifying the unique name of the pipeline and the execution ID\. For example, to view action executions for an *Execution\_ID*, enter the following:
```
aws codepipeline list-action-executions --pipeline-name MyFirstPipeline --filter pipelineExecutionId=Execution_ID
```
+ The following shows a portion of sample output for this command:
```
{
"actionExecutionDetails": [
{
"stageName": "Beta",
"pipelineVersion": 8,
"actionName": "Build",
"status": "Failed",
"lastUpdateTime": 1552958312.034,
"input": {
"configuration": {
"ProjectName": "java-project"
},
"region": "us-east-1",
"actionTypeId": {
"owner": "AWS",
"category": "Build",
"provider": "CodeBuild",
"version": "1"
},
"inputArtifacts": [
{ | https://github.com/siagholami/aws-documentation/tree/main/documents/aws-codepipeline-user-guide/doc_source/pipelines-view-cli.md |
f4c6cab664cd-3 | "version": "1"
},
"inputArtifacts": [
{
"s3location": {
"bucket": "codepipeline-us-east-1-ID",
"key": "MyFirstPipeline/MyApp/Object.zip"
},
"name": "MyApp"
}
]
},
. . .
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/aws-codepipeline-user-guide/doc_source/pipelines-view-cli.md |
317df10ef28c-0 | You can use AWS CodePipeline to easily configure a continuous integration flow in which your app is tested each time the source bucket changes\. This tutorial shows you how to create and configure a pipeline to test your built iOS app from an S3 bucket\. The pipeline detects the arrival of a saved change through Amazon CloudWatch Events, and then uses [Device Farm](https://docs.aws.amazon.com/devicefarm/latest/developerguide/welcome.html) to test the built application\.
**Important**
Many of the actions you add to your pipeline in this procedure involve AWS resources that you need to create before you create the pipeline\. AWS resources for your source actions must always be created in the same AWS Region where you create your pipeline\. For example, if you create your pipeline in the US East \(Ohio\) Region, your CodeCommit repository must be in the US East \(Ohio\) Region\.
You can add cross\-region actions when you create your pipeline\. AWS resources for cross\-region actions must be in the same AWS Region where you plan to execute the action\. For more information, see [Add a cross\-Region action in CodePipeline](actions-create-cross-region.md)\.
You can try this out using your existing iOS app, or you can use the [sample iOS app](samples/s3-ios-test-1.zip)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/aws-codepipeline-user-guide/doc_source/tutorials-codebuild-devicefarm-S3.md |
317df10ef28c-1 | You can try this out using your existing iOS app, or you can use the [sample iOS app](samples/s3-ios-test-1.zip)\.
![\[The Step 2: Source page in the CodePipeline pipeline wizard\]](http://docs.aws.amazon.com/codepipeline/latest/userguide/images/codepipeline-push-build-test-S3.png)![\[The Step 2: Source page in the CodePipeline pipeline wizard\]](http://docs.aws.amazon.com/codepipeline/latest/userguide/)![\[The Step 2: Source page in the CodePipeline pipeline wizard\]](http://docs.aws.amazon.com/codepipeline/latest/userguide/)
****
| | | | | |
| --- |--- |--- |--- |--- |
| Configure | Add definitions | Upload | Test | Report |
| Configure pipeline resources | Add test definitions to your package | Upload \.zip to your bucket | Test output artifact kicked off automatically | View test results |
**Before you begin**
1. Sign in to the AWS Device Farm console and choose **Create a new project**\.
1. Choose your project\. In the browser, copy the URL of your new project\. The URL contains the project ID\.
1. Copy and retain this project ID\. You use it when you create your pipeline in CodePipeline\. | https://github.com/siagholami/aws-documentation/tree/main/documents/aws-codepipeline-user-guide/doc_source/tutorials-codebuild-devicefarm-S3.md |
317df10ef28c-2 | 1. Copy and retain this project ID\. You use it when you create your pipeline in CodePipeline\.
Here is an example URL for a project\. To extract the project ID, copy the value after `projects/`\. In this example, the project ID is `eec4905f-98f8-40aa-9afc-4c1cfexample`\.
```
https://<region-URL>/devicefarm/home?region=us-west-2#/projects/eec4905f-98f8-40aa-9afc-4c1cfexample/runs
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/aws-codepipeline-user-guide/doc_source/tutorials-codebuild-devicefarm-S3.md |
47c6936b251f-0 | 1. Create or use an S3 bucket with versioning enabled\. Follow the instructions in [Step 1: Create an S3 bucket for your application](tutorials-simple-s3.md#s3-create-s3-bucket) to create an S3 bucket\.
1. In the Amazon S3 console for your bucket, choose **Upload**, and follow the instructions to upload your \.zip file\.
Your sample application must be packaged in a \.zip file\.
1. To create your pipeline and add a source stage, do the following:
1. Sign in to the AWS Management Console and open the CodePipeline console at [https://console\.aws\.amazon\.com/codepipeline/](https://console.aws.amazon.com/codepipeline/)\.
1. Choose **Create pipeline**\. On the **Step 1: Choose pipeline settings** page, in **Pipeline name**, enter the name for your pipeline\.
1. In **Service role**, leave **New service role** selected, and leave **Role name** unchanged\. You can also choose to use an existing service role, if you have one\.
**Note** | https://github.com/siagholami/aws-documentation/tree/main/documents/aws-codepipeline-user-guide/doc_source/tutorials-codebuild-devicefarm-S3.md |
47c6936b251f-1 | **Note**
If you use a CodePipeline service role that was created before July 2018, you must add permissions for Device Farm\. To do this, open the IAM console, find the role, and then add the following permissions to the role's policy\. For more information, see [Add permissions to the CodePipeline service role](security-iam.md#how-to-update-role-new-services)\.
```
{
"Effect": "Allow",
"Action": [
"devicefarm:ListProjects",
"devicefarm:ListDevicePools",
"devicefarm:GetRun",
"devicefarm:GetUpload",
"devicefarm:CreateUpload",
"devicefarm:ScheduleRun"
],
"Resource": "*"
}
```
1. Leave the settings under **Advanced settings** at their defaults, and then choose **Next**\.
1. On the **Step 2: Add source stage** page, in **Source provider**, choose **Amazon S3**\.
1. In **Amazon S3 location**, enter the bucket and object key for your \.zip file\. | https://github.com/siagholami/aws-documentation/tree/main/documents/aws-codepipeline-user-guide/doc_source/tutorials-codebuild-devicefarm-S3.md |
47c6936b251f-2 | 1. In **Amazon S3 location**, enter the bucket and object key for your \.zip file\.
![\[\]](http://docs.aws.amazon.com/codepipeline/latest/userguide/images/codepipeline-add-source-S3.png)
1. Choose **Next**\.
1. In **Build**, create a placeholder build stage for your pipeline\. This allows you to create the pipeline in the wizard\. After you use the wizard to create your two\-stage pipeline, you no longer need this placeholder build stage\. After the pipeline is completed, this second stage is deleted and the new test stage is added in step 5\.
1. In **Build provider**, choose **Add Jenkins**\. This build selection is a placeholder\. It is not used\.
1. In **Provider name**, enter a name\. The name is a placeholder\. It is not used\.
1. In **Server URL**, enter text\. The text is a placeholder\. It is not used\.
1. In **Project name**, enter a name\. The name is a placeholder\. It is not used\.
![\[\]](http://docs.aws.amazon.com/codepipeline/latest/userguide/images/codepipeline-ios-define-build-S3.png)
1. Choose **Next**\. | https://github.com/siagholami/aws-documentation/tree/main/documents/aws-codepipeline-user-guide/doc_source/tutorials-codebuild-devicefarm-S3.md |
47c6936b251f-3 | 1. Choose **Next**\.
1. On the **Step 4: Add deploy stage** page, choose **Skip deploy stage**, and then accept the warning message by choosing **Skip** again\.
1. On **Step 5: Review**, choose **Create pipeline**\. You should see a diagram that shows the source and build stages\.
![\[\]](http://docs.aws.amazon.com/codepipeline/latest/userguide/images/codepipeline-view-pipeline-S3.png)
1. Add a Device Farm test action to your pipeline as follows:
1. In the upper right, choose **Edit**\.
1. Choose **Edit stage**\. Choose **Delete**\. This deletes the placeholder stage now that you no longer need it for pipeline creation\.
1. At the bottom of the diagram, choose **\+ Add stage**\.
1. In Stage name, enter a name for the stage, such as Test, and then choose **Add stage**\.
1. Choose **\+ Add action group**\.
1. In **Action name**, enter a name, such as DeviceFarmTest\.
1. In **Action provider**, choose **AWS Device Farm**\. Allow **Region** to default to the pipeline Region\. | https://github.com/siagholami/aws-documentation/tree/main/documents/aws-codepipeline-user-guide/doc_source/tutorials-codebuild-devicefarm-S3.md |
47c6936b251f-4 | 1. In **Action provider**, choose **AWS Device Farm**\. Allow **Region** to default to the pipeline Region\.
1. In **Input artifacts**, choose the input artifact that matches the output artifact of the stage that comes before the test stage, such as `SourceArtifact`\.
In the AWS CodePipeline console, you can find the name of the output artifact for each stage by hovering over the information icon in the pipeline diagram\. If your pipeline tests your app directly from the **Source** stage, choose **SourceArtifact**\. If the pipeline includes a **Build** stage, choose **BuildArtifact**\.
1. In **ProjectId**, choose your Device Farm project ID\. Use the steps at the start of this tutorial to retrieve your project ID\.
1. In **DevicePoolArn**, enter the ARN for the device pool\. To get the available device pool ARNs for the project, including the ARN for Top Devices, use the AWS CLI to enter the following command:
```
aws devicefarm list-device-pools --arn arn:aws:devicefarm:us-west-2:account_ID:project:project_ID
```
1. In **AppType**, enter **iOS**\.
![\[\]](http://docs.aws.amazon.com/codepipeline/latest/userguide/images/codepipeline-choose-test-provider-S3.png) | https://github.com/siagholami/aws-documentation/tree/main/documents/aws-codepipeline-user-guide/doc_source/tutorials-codebuild-devicefarm-S3.md |
47c6936b251f-5 | The following is a list of valid values for **AppType**:
+ **iOS**
+ **Android**
+ **Web**
1. In **App**, enter the path of the compiled app package\. The path is relative to the root of the input artifact for the test stage\. Typically, this path is similar to `ios-test.ipa`\.
1. In **TestType**, enter your type of test, and then in **Test**, enter the path of the test definition file\. The path is relative to the root of the input artifact for your test\.
If you're using one of the built\-in Device Farm tests, enter the type of test configured in your Device Farm project, such as BUILTIN\_FUZZ\. In **FuzzEventCount**, enter a time in milliseconds, such as 6000\. In **FuzzEventThrottle**, enter a time in milliseconds, such as 50\.
If you aren't using one of the built\-in Device Farm tests, enter your type of test, and then in **Test**, enter the path of the test definition file\. The path is relative to the root of the input artifact for your test\.
The following is a list of valid values for **TestType**:
+ **APPIUM\_JAVA\_JUNIT**
+ **APPIUM\_JAVA\_TESTNG**
+ **APPIUM\_PYTHON** | https://github.com/siagholami/aws-documentation/tree/main/documents/aws-codepipeline-user-guide/doc_source/tutorials-codebuild-devicefarm-S3.md |
47c6936b251f-6 | + **APPIUM\_JAVA\_TESTNG**
+ **APPIUM\_PYTHON**
+ **APPIUM\_WEB\_JAVA\_JUNIT**
+ **APPIUM\_WEB\_JAVA\_TESTNG**
+ **APPIUM\_WEB\_PYTHON**
+ **BUILTIN\_EXPLORER**
+ **BUILTIN\_FUZZ**
+ **CALABASH**
+ **INSTRUMENTATION**
+ **UIAUTOMATION**
+ **UIAUTOMATOR**
+ **WEB\_PERFORMANCE\_PROFILE**
+ **XCTEST**
+ **XCTEST\_UI**
**Note**
Custom environment nodes are not supported\.
1. In the remaining fields, provide the configuration that is appropriate for your test and application type\.
1. \(Optional\) In **Advanced**, provide configuration information for your test run\.
1. Choose **Save**\.
1. On the stage you are editing, choose **Done**\. In the AWS CodePipeline pane, choose **Save**, and then choose **Save** on the warning message\.
1. To submit your changes and start a pipeline execution, choose **Release change**, and then choose **Release**\. | https://github.com/siagholami/aws-documentation/tree/main/documents/aws-codepipeline-user-guide/doc_source/tutorials-codebuild-devicefarm-S3.md |
47c6936b251f-7 | 1. To submit your changes and start a pipeline execution, choose **Release change**, and then choose **Release**\.
![\[\]](http://docs.aws.amazon.com/codepipeline/latest/userguide/images/codepipeline-ios-final-view-pipeline.png) | https://github.com/siagholami/aws-documentation/tree/main/documents/aws-codepipeline-user-guide/doc_source/tutorials-codebuild-devicefarm-S3.md |
37b86359a39b-0 | 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)\.
**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) | https://github.com/siagholami/aws-documentation/tree/main/documents/aws-codepipeline-user-guide/doc_source/action-reference-DeviceFarm.md |
5cd990d507c1-0 | + Category: `Test`
+ Owner: `AWS`
+ Provider: `DeviceFarm`
+ Version: `1` | https://github.com/siagholami/aws-documentation/tree/main/documents/aws-codepipeline-user-guide/doc_source/action-reference-DeviceFarm.md |
2bf82c6dcd2b-0 | **AppType**
Required: Yes
The OS and type of application you are testing\. The following is a list of valid values:
+ `iOS`
+ `Android`
+ `Web`
**ProjectId**
Required: Yes
The Device Farm project ID\.
To find your project ID, in the Device Farm console, choose your project\. In the browser, copy the URL of your new project\. The URL contains the project ID\. The project ID is the value in the URL after `projects/`\. In the following example, the project ID is `eec4905f-98f8-40aa-9afc-4c1cfexample`\.
```
https://<region-URL>/devicefarm/home?region=us-west-2#/projects/eec4905f-98f8-40aa-9afc-4c1cfexample/runs
```
**App**
Required: Yes
The name and location of the application file in your input artifact\. For example: `s3-ios-test-1.ipa`
**AppiumVersion**
Required: Yes
The version of Appium test framework to use for this test\.
The AppiumVersion field value is not processed\. The default value is processed instead\.
**DevicePoolArn**
Required: Yes | https://github.com/siagholami/aws-documentation/tree/main/documents/aws-codepipeline-user-guide/doc_source/action-reference-DeviceFarm.md |
2bf82c6dcd2b-1 | The AppiumVersion field value is not processed\. The default value is processed instead\.
**DevicePoolArn**
Required: Yes
The Device Farm device pool ARN\.
To get the available device pool ARNs for the project, including the ARN for Top Devices, use the AWS CLI to enter the following command:
```
aws devicefarm list-device-pools --arn arn:aws:devicefarm:us-west-2:account_ID:project:project_ID
```
**TestType**
Required: Yes
Specifies the supported testing framework for your test\. The following is a list of valid values for `TestType`:
+ **APPIUM\_JAVA\_JUNIT**
+ **APPIUM\_JAVA\_TESTNG**
+ **APPIUM\_PYTHON**
+ **APPIUM\_WEB\_JAVA\_JUNIT**
+ **APPIUM\_WEB\_JAVA\_TESTNG**
+ **APPIUM\_WEB\_PYTHON**
+ **BUILTIN\_EXPLORER**
+ **BUILTIN\_FUZZ**
+ **CALABASH**
+ **INSTRUMENTATION**
+ **UIAUTOMATION**
+ **UIAUTOMATOR**
+ **WEB\_PERFORMANCE\_PROFILE** | https://github.com/siagholami/aws-documentation/tree/main/documents/aws-codepipeline-user-guide/doc_source/action-reference-DeviceFarm.md |
2bf82c6dcd2b-2 | + **UIAUTOMATION**
+ **UIAUTOMATOR**
+ **WEB\_PERFORMANCE\_PROFILE**
+ **XCTEST**
+ **XCTEST\_UI**
The following test types are not supported by the action in CodePipeline: `WEB_PERFORMANCE_PROFILE`, `APPIUM_NODE`, `APPIUM_RUBY`, `APPIUM_WEB_NODE`, `APPIUM_WEB_RUBY`, `REMOTE_ACCESS_RECORD`, and `REMOTE_ACCESS_REPLAY`\.
For information about Device Farm test types, see [Working with Test Types in AWS Device Farm](https://docs.aws.amazon.com/devicefarm/latest/developerguide/test-types.html)\.
**RadioBluetoothEnabled**
Required: No
A Boolean value that indicates whether to enable Bluetooth at the beginning of the test\.
**RecordAppPerformanceData**
Required: No
A Boolean value that indicates whether to record device performance data such as CPU, FPS, and memory performance during the test\.
**RecordVideo**
Required: No
A Boolean value that indicates whether to record video during the test\.
**RadioWifiEnabled**
Required: No
A Boolean value that indicates whether to enable Wi\-Fi at the beginning of the test\.
**RadioNfcEnabled**
Required: No | https://github.com/siagholami/aws-documentation/tree/main/documents/aws-codepipeline-user-guide/doc_source/action-reference-DeviceFarm.md |
2bf82c6dcd2b-3 | **RadioNfcEnabled**
Required: No
A Boolean value that indicates whether to enable NFC at the beginning of the test\.
**RadioGpsEnabled**
Required: No
A Boolean value that indicates whether to enable GPS at the beginning of the test\.
**Test**
Required: No
The name and path of the test definition file in your source location\. The path is relative to the root of the input artifact for your test\.
**FuzzEventCount**
Required: No
The number of user interface events for the fuzz test to perform, between 1 and 10,000\.
**FuzzEventThrottle**
Required: No
The number of milliseconds for the fuzz test to wait before performing the next user interface event, between 1 and 1,000\.
**FuzzRandomizerSeed**
Required: No
A seed for the fuzz test to use for randomizing user interface events\. Using the same number for subsequent fuzz tests results in identical event sequences\.
**CustomHostMachineArtifacts**
Required: No
The location on the host machine where custom artifacts will be stored\.
**CustomDeviceArtifacts**
Required: No
The location on the device where custom artifacts will be stored\.
**UnmeteredDevicesOnly**
Required: No | https://github.com/siagholami/aws-documentation/tree/main/documents/aws-codepipeline-user-guide/doc_source/action-reference-DeviceFarm.md |
2bf82c6dcd2b-4 | The location on the device where custom artifacts will be stored\.
**UnmeteredDevicesOnly**
Required: No
A Boolean value that indicates whether to only use your unmetered devices when running tests in this step\.
**JobTimeoutMinutes**
Required: No
The number of minutes a test run will execute per device before it times out\.
**Latitude**
Required: No
The latitude of the device expressed in geographic coordinate system degrees\.
**Longitude**
Required: No
The longitude of the device expressed in geographic coordinate system degrees\. | https://github.com/siagholami/aws-documentation/tree/main/documents/aws-codepipeline-user-guide/doc_source/action-reference-DeviceFarm.md |
f4c983062b74-0 | + **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\. | https://github.com/siagholami/aws-documentation/tree/main/documents/aws-codepipeline-user-guide/doc_source/action-reference-DeviceFarm.md |
91d3f58461b5-0 | + **Number of Artifacts:** `0`
+ **Description:** Output artifacts do not apply for this action type\. | https://github.com/siagholami/aws-documentation/tree/main/documents/aws-codepipeline-user-guide/doc_source/action-reference-DeviceFarm.md |
4b34afcb2fc1-0 | ------ | https://github.com/siagholami/aws-documentation/tree/main/documents/aws-codepipeline-user-guide/doc_source/action-reference-DeviceFarm.md |
7c73ead8c8ee-0 | ```
Name: Test
Actions:
- Name: TestDeviceFarm
ActionTypeId:
category: Test
owner: AWS
provider: DeviceFarm
version: '1'
RunOrder: 1
Configuration:
App: s3-ios-test-1.ipa
AppType: iOS
DevicePoolArn: >-
arn:aws:devicefarm:us-west-2::devicepool:0EXAMPLE-d7d7-48a5-ba5c-b33d66efa1f5
FuzzEventCount: '6000'
FuzzEventThrottle: '50'
ProjectId: eec4905f-98f8-40aa-9afc-4c1cfEXAMPLE
TestType: BUILTIN_FUZZ
OutputArtifacts: []
InputArtifacts:
- Name: SourceArtifact
Region: us-west-2
```
------ | https://github.com/siagholami/aws-documentation/tree/main/documents/aws-codepipeline-user-guide/doc_source/action-reference-DeviceFarm.md |
0f644d01e424-0 | ```
{
"Name": "Test",
"Actions": [
{
"Name": "TestDeviceFarm",
"ActionTypeId": {
"category": "Test",
"owner": "AWS",
"provider": "DeviceFarm",
"version": "1"
},
"RunOrder": 1,
"Configuration": {
"App": "s3-ios-test-1.ipa",
"AppType": "iOS",
"DevicePoolArn": "arn:aws:devicefarm:us-west-2::devicepool:0EXAMPLE-d7d7-48a5-ba5c-b33d66efa1f5",
"FuzzEventCount": "6000",
"FuzzEventThrottle": "50",
"ProjectId": "eec4905f-98f8-40aa-9afc-4c1cfEXAMPLE",
"TestType": "BUILTIN_FUZZ"
},
"OutputArtifacts": [],
"InputArtifacts": [
{
"Name": "SourceArtifact"
}
], | https://github.com/siagholami/aws-documentation/tree/main/documents/aws-codepipeline-user-guide/doc_source/action-reference-DeviceFarm.md |
0f644d01e424-1 | {
"Name": "SourceArtifact"
}
],
"Region": "us-west-2"
}
]
},
```
------ | https://github.com/siagholami/aws-documentation/tree/main/documents/aws-codepipeline-user-guide/doc_source/action-reference-DeviceFarm.md |
633e5695d4b3-0 | 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\.
+ [Actions in Device Farm](https://docs.aws.amazon.com/devicefarm/latest/APIReference/Welcome.html) – The API calls and parameters in the *Device Farm API Reference* can help you work with Device Farm projects\.
+ [Tutorial: Create a pipeline that builds and tests your Android app when a commit is pushed to your GitHub repository](tutorials-codebuild-devicefarm.md) – This tutorial provides a sample build spec file and sample application to create a pipeline with a GitHub source that builds and tests an Android app with CodeBuild and Device Farm\.
+ [Tutorial: Create a pipeline that tests your iOS app after a change in your S3 bucket](tutorials-codebuild-devicefarm-S3.md) – This tutorial provides a sample application to create a pipeline with an Amazon S3 source that tests a built iOS app with Device Farm\. | https://github.com/siagholami/aws-documentation/tree/main/documents/aws-codepipeline-user-guide/doc_source/action-reference-DeviceFarm.md |
f4e4e5fd6fb4-0 | You can use Amazon CloudWatch Events to trigger pipelines to start when rule or schedule criteria are met\. For pipelines with an Amazon S3 or CodeCommit source, an Amazon CloudWatch Events rule detects source changes and then starts your pipeline\. When you use the console to create or change a pipeline, the rule and all associated resources are created for you\. If you create or change an Amazon S3 or CodeCommit pipeline in the AWS CLI or AWS CloudFormation, you must use these steps to create the Amazon CloudWatch Events rule and all associated resources manually\.
In Amazon CloudWatch Events, you create a rule to detect and react to changes in the state of the pipeline's defined source\.
**To create the rule**
1. Create an Amazon CloudWatch Events rule that uses the pipeline's source repository as the event source\.
1. Add CodePipeline as the target\.
1. Grant permissions to Amazon CloudWatch Events to start the pipeline\.
As you build your rule, the **Event Pattern Preview** pane in the console \(or the `--event-pattern` output in the AWS CLI\) displays the event fields, in JSON format\. The following sample CodeCommit event pattern uses this JSON structure:
```
{
"source": [ "aws.codecommit" ],
"detail-type": [ "CodeCommit Repository State Change" ],
"resources": [ "CodeCommitRepo_ARN" ],
"detail": {
"event": [ | https://github.com/siagholami/aws-documentation/tree/main/documents/aws-codepipeline-user-guide/doc_source/triggering.md |
f4e4e5fd6fb4-1 | "resources": [ "CodeCommitRepo_ARN" ],
"detail": {
"event": [
"referenceCreated",
"referenceUpdated"],
"referenceType":["branch"],
"referenceName": ["branch_name"]
}
}
```
The event pattern uses these fields:
+ `source:` should contain `aws.codecommit` as the event source\.
+ `detail-type:` displays the available event type \(`CodeCommit Repository State Change`\)\.
+ `resources:` contains the repository ARN\.
+ `detail:` contains the repository branch information, `referenceType` and `referenceName`\.
**Topics**
+ [Create a CloudWatch Events rule for a CodeCommit source \(console\)](pipelines-trigger-source-repo-changes-console.md)
+ [Create a CloudWatch Events rule for a CodeCommit source \(CLI\)](pipelines-trigger-source-repo-changes-cli.md)
+ [Create a CloudWatch Events rule for a CodeCommit source \(AWS CloudFormation template\)](pipelines-trigger-source-repo-changes-cfn.md) | https://github.com/siagholami/aws-documentation/tree/main/documents/aws-codepipeline-user-guide/doc_source/triggering.md |
c086825b22ac-0 | The CodePipeline console requires the `ListRepositories` permission to display a list of repositories for your AWS account in the AWS Region where you are signed in\. The console also includes a **Go to resource** function to quickly perform a case insensitive search for resources\. This search is performed in your AWS account in the AWS Region where you are signed in\. The following resources are displayed across the following services:
+ AWS CodeBuild: Build projects
+ AWS CodeCommit: Repositories
+ AWS CodeDeploy: Applications
+ AWS CodePipeline: Pipelines
To perform this search across resources in all services, you must have the following permissions:
+ CodeBuild: `ListProjects`
+ CodeCommit: `ListRepositories`
+ CodeDeploy: `ListApplications`
+ CodePipeline: `ListPipelines`
Results are not returned for a service's resources if you do not have permissions for that service\. Even if you have permissions for viewing resources, some resources are not returned if there is an explicit `Deny` to view those resources\. | https://github.com/siagholami/aws-documentation/tree/main/documents/aws-codepipeline-user-guide/doc_source/security-iam-resources-console.md |
254f7d92f70e-0 | Before you create a pipeline with the AWS CLI or AWS CloudFormation, create a CodePipeline service role for your pipeline\.
1. Use the IAM console or the AWS CLI to create a role and attach the service role policy\. To view the default service role policy, use the procedure in [Create the CodePipeline service role \(console\)](pipelines-create-service-role-console.md) to create the service role and view the default policy in the IAM console\. The policy name format is normally the same as the role name format\.
1. Use the service role ARN when you create your pipeline with the AWS CLI or AWS CloudFormation\.
1. After you create it, your pipeline service role is available to view in your list of IAM roles, and you can view the service role ARN associated to a pipeline by running the `get-pipeline` command with the AWS CLI\. | https://github.com/siagholami/aws-documentation/tree/main/documents/aws-codepipeline-user-guide/doc_source/pipelines-create-service-role-cli.md |
7496466f4144-0 | Before you use IAM to manage access to CodePipeline, you should understand what IAM features are available to use with CodePipeline\. To get a high\-level view of how CodePipeline and other AWS services work with IAM, see [AWS Services That Work with IAM](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_aws-services-that-work-with-iam.html) in the *IAM User Guide*\.
**Topics**
+ [CodePipeline identity\-based policies](#security_iam_service-with-iam-id-based-policies)
+ [CodePipeline resource\-based policies](#security_iam_service-with-iam-resource-based-policies)
+ [Authorization based on CodePipeline tags](#security_iam_service-with-iam-tags)
+ [CodePipeline IAM roles](#security_iam_service-with-iam-roles) | https://github.com/siagholami/aws-documentation/tree/main/documents/aws-codepipeline-user-guide/doc_source/security_iam_service-with-iam.md |
ce9d4e2e46ab-0 | With IAM identity\-based policies, you can specify allowed or denied actions and resources as well as the conditions under which actions are allowed or denied\. CodePipeline supports specific actions, resources, and condition keys\. To learn about all of the elements that you use in a JSON policy, see [IAM JSON Policy Elements Reference](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_elements.html) in the *IAM User Guide*\. | https://github.com/siagholami/aws-documentation/tree/main/documents/aws-codepipeline-user-guide/doc_source/security_iam_service-with-iam.md |
ea687af09269-0 | The `Action` element of an IAM identity\-based policy describes the specific action or actions that will be allowed or denied by the policy\. Policy actions usually have the same name as the associated AWS API operation\. The action is used in a policy to grant permissions to perform the associated operation\.
Policy actions in CodePipeline use the following prefix before the action: `codepipeline:`\.
For example, to grant someone permission to view the existing pipelines in the account, you include the `codepipeline:GetPipeline` action in their policy\. Policy statements must include either an `Action` or `NotAction` element\. CodePipeline defines its own set of actions that describe tasks that you can perform with this service\.
To specify multiple actions in a single statement, separate them with commas as follows:
```
"Action": [
"codepipeline:action1",
"codepipeline:action2"
```
You can specify multiple actions using wildcards \(\*\)\. For example, to specify all actions that begin with the word `Get`, include the following action:
```
"Action": "codepipeline:Get*"
```
For a list of CodePipeline actions, see [Actions Defined by AWS CodePipeline](https://docs.aws.amazon.com/IAM/latest/UserGuide/list_awscodepipeline.html#awscodepipeline-actions-as-permissions) in the *IAM User Guide*\. | https://github.com/siagholami/aws-documentation/tree/main/documents/aws-codepipeline-user-guide/doc_source/security_iam_service-with-iam.md |
66e8e11fcb3a-0 | The `Resource` element specifies the object or objects to which the action applies\. Statements must include either a `Resource` or a `NotResource` element\. You specify a resource using an ARN or using the wildcard \(\*\) to indicate that the statement applies to all resources\. | https://github.com/siagholami/aws-documentation/tree/main/documents/aws-codepipeline-user-guide/doc_source/security_iam_service-with-iam.md |
35ae4516cd50-0 | In CodePipeline, the primary resource is a pipeline\. In a policy, you use an Amazon Resource Name \(ARN\) to identify the resource that the policy applies to\. CodePipeline supports other resources that can be used with the primary resource, such as stages, actions, and custom actions\. These are referred to as subresources\. These resources and subresources have unique Amazon Resource Names \(ARNs\) associated with them\. For more information about ARNs, see [Amazon Resource Names \(ARN\) and AWS Service Namespaces](https://docs.aws.amazon.com/general/latest/gr/aws-arns-and-namespaces.html) in the *Amazon Web Services General Reference*\. To get the pipeline ARN associated with your pipeline, you can find the pipeline ARN under **Settings** in the console\. For more information, see [View the pipeline ARN and service role ARN \(console\)](pipelines-view-console.md#pipelines-settings-console)\.
| Resource Type | ARN Format |
| --- | --- |
| Pipeline | arn:aws:codepipeline:*region*:*account*:*pipeline\-name* |
| Stage | arn:aws:codepipeline:*region*:*account*:*pipeline\-name*/*stage\-name* |
| Action | arn:aws:codepipeline:*region*:*account*:*pipeline\-name*/*stage\-name*/*action\-name* | | https://github.com/siagholami/aws-documentation/tree/main/documents/aws-codepipeline-user-guide/doc_source/security_iam_service-with-iam.md |
35ae4516cd50-1 | | Custom action | arn:aws:codepipeline:region:account:actionType:owner/category/provider/version |
| All CodePipeline resources | arn:aws:codepipeline:\* |
| All CodePipeline resources owned by the specified account in the specified Region | arn:aws:codepipeline:*region*:*account*:\* |
**Note**
Most services in AWS treat a colon \(:\) or a forward slash \(/\) as the same character in ARNs\. However, CodePipeline uses an exact match in event patterns and rules\. Be sure to use the correct ARN characters when creating event patterns so that they match the ARN syntax in the pipeline you want to match\.
In CodePipeline, there are API calls that support resource\-level permissions\. Resource\-level permissions indicate whether an API call can specify a resource ARN, or whether the API call can only specify all resources using the wildcard\. See [CodePipeline permissions reference](permissions-reference.md) for a detailed description of resource\-level permissions and a listing of the CodePipeline API calls that support resource\-level permissions\.
For example, you can indicate a specific pipeline \(*myPipeline*\) in your statement using its ARN as follows:
```
"Resource": "arn:aws:codepipeline:us-east-2:111222333444:myPipeline"
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/aws-codepipeline-user-guide/doc_source/security_iam_service-with-iam.md |
35ae4516cd50-2 | ```
You can also specify all pipelines that belong to a specific account by using the \(\*\) wildcard character as follows:
```
"Resource": "arn:aws:codepipeline:us-east-2:111222333444:*"
```
To specify all resources, or if a specific API action does not support ARNs, use the \(\*\) wildcard character in the `Resource` element as follows:
```
"Resource": "*"
```
**Note**
When you create IAM policies, follow the standard security advice of granting least privilege—that is, granting only the permissions required to perform a task\. If an API call supports ARNs, then it supports resource\-level permissions, and you do not need to use the \(\*\) wildcard character\.
Some CodePipeline API calls accept multiple resources \(for example, `GetPipeline`\)\. To specify multiple resources in a single statement, separate their ARNs with commas, as follows:
```
"Resource": ["arn1", "arn2"]
```
CodePipeline provides a set of operations to work with the CodePipeline resources\. For a list of available operations, see [CodePipeline permissions reference](permissions-reference.md)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/aws-codepipeline-user-guide/doc_source/security_iam_service-with-iam.md |
4c2efd2ee45a-0 | The `Condition` element \(or `Condition` *block*\) lets you specify conditions in which a statement is in effect\. The `Condition` element is optional\. You can create conditional expressions that use [condition operators](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_elements_condition_operators.html), such as equals or less than, to match the condition in the policy with values in the request\.
If you specify multiple `Condition` elements in a statement, or multiple keys in a single `Condition` element, AWS evaluates them using a logical `AND` operation\. If you specify multiple values for a single condition key, AWS evaluates the condition using a logical `OR` operation\. All of the conditions must be met before the statement's permissions are granted\.
You can also use placeholder variables when you specify conditions\. For example, you can grant an IAM user permission to access a resource only if it is tagged with their IAM user name\. For more information, see [IAM Policy Elements: Variables and Tags](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_variables.html) in the *IAM User Guide*\.
CodePipeline defines its own set of condition keys and also supports using some global condition keys\. To see all AWS global condition keys, see [AWS Global Condition Context Keys](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_condition-keys.html) in the *IAM User Guide*\. | https://github.com/siagholami/aws-documentation/tree/main/documents/aws-codepipeline-user-guide/doc_source/security_iam_service-with-iam.md |
4c2efd2ee45a-1 | All Amazon EC2 actions support the `aws:RequestedRegion` and `ec2:Region` condition keys\. For more information, see [Example: Restricting Access to a Specific Region](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ExamplePolicies_EC2.html#iam-example-region)\.
To see a list of CodePipeline condition keys, see [Condition Keys for AWS CodePipeline](https://docs.aws.amazon.com/IAM/latest/UserGuide/list_awscodepipeline.html#awscodepipeline-policy-keys) in the *IAM User Guide*\. To learn with which actions and resources you can use a condition key, see [Actions Defined by AWS CodePipeline](https://docs.aws.amazon.com/IAM/latest/UserGuide/list_awscodepipeline.html#awscodepipeline-actions-as-permissions)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/aws-codepipeline-user-guide/doc_source/security_iam_service-with-iam.md |
9a2e0ba5406a-0 | To view examples of CodePipeline identity\-based policies, see [AWS CodePipeline identity\-based policy examples](security_iam_id-based-policy-examples.md)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/aws-codepipeline-user-guide/doc_source/security_iam_service-with-iam.md |
ee34e4204812-0 | CodePipeline does not support resource\-based policies\. However, a resource\-based policy example for the S3 service related to CodePipeline is provided\. | https://github.com/siagholami/aws-documentation/tree/main/documents/aws-codepipeline-user-guide/doc_source/security_iam_service-with-iam.md |
da842743d121-0 | To view examples of CodePipeline resource\-based policies, see [AWS CodePipeline resource\-based policy examples](security_iam_resource-based-policy-examples.md), | https://github.com/siagholami/aws-documentation/tree/main/documents/aws-codepipeline-user-guide/doc_source/security_iam_service-with-iam.md |
406c7bd21fd8-0 | You can attach tags to CodePipeline resources or pass tags in a request to CodePipeline\. To control access based on tags, you provide tag information in the [condition element](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_elements_condition.html) of a policy using the `codepipeline:ResourceTag/key-name`, `aws:RequestTag/key-name`, or `aws:TagKeys` condition keys\. For more information about tagging CodePipeline resources, see [Tagging resources](tag-resources.md)\.
To view an example identity\-based policy for limiting access to a resource based on the tags on that resource, see [Using tags to control access to CodePipeline resources](tag-based-access-control.md)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/aws-codepipeline-user-guide/doc_source/security_iam_service-with-iam.md |
b1c7ec0cbc06-0 | An [IAM role](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles.html) is an entity in your AWS account that has specific permissions\. | https://github.com/siagholami/aws-documentation/tree/main/documents/aws-codepipeline-user-guide/doc_source/security_iam_service-with-iam.md |
12d129d10af5-0 | You can use temporary credentials to sign in with federation, assume an IAM role, or to assume a cross\-account role\. You obtain temporary security credentials by calling AWS STS API operations such as [AssumeRole](https://docs.aws.amazon.com/STS/latest/APIReference/API_AssumeRole.html) or [GetFederationToken](https://docs.aws.amazon.com/STS/latest/APIReference/API_GetFederationToken.html)\.
CodePipeline supports the use of temporary credentials\. | https://github.com/siagholami/aws-documentation/tree/main/documents/aws-codepipeline-user-guide/doc_source/security_iam_service-with-iam.md |
3ac267ec3d0d-0 | CodePipeline allows a service to assume a [service role](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_terms-and-concepts.html#iam-term-service-role) on your behalf\. This role allows the service to access resources in other services to complete an action on your behalf\. Service roles appear in your IAM account and are owned by the account\. This means that an IAM administrator can change the permissions for this role\. However, doing so might break the functionality of the service\.
CodePipeline supports service roles\. | https://github.com/siagholami/aws-documentation/tree/main/documents/aws-codepipeline-user-guide/doc_source/security_iam_service-with-iam.md |
a123635e3e26-0 | The following AWS service integrations are not based on CodePipeline action types\.
| | |
| --- |--- |
| AWS CloudTrail | [CloudTrail](https://docs.aws.amazon.com/awscloudtrail/latest/userguide/) captures AWS API calls and related events made by or on behalf of an AWS account and delivers log files to an Amazon S3 bucket that you specify\. You can configure CloudTrail to capture API calls from the CodePipeline console, CodePipeline commands from the AWS CLI, and from the CodePipeline API\. Learn more: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/codepipeline/latest/userguide/integrations-general.html) |
| Amazon CloudWatch | [Amazon CloudWatch](https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/) monitors your AWS resources\. Learn more: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/codepipeline/latest/userguide/integrations-general.html) | | https://github.com/siagholami/aws-documentation/tree/main/documents/aws-codepipeline-user-guide/doc_source/integrations-general.md |
a123635e3e26-1 | | Amazon CloudWatch Events | [Amazon CloudWatch Events](https://docs.aws.amazon.com/AmazonCloudWatch/latest/events/) is a web service that detects changes in your AWS services based on rules that you define and invokes an action in one or more specified AWS services when a change occurs\.[\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/codepipeline/latest/userguide/integrations-general.html) |
| AWS CodeStar Notifications | You can set up notifications to make users aware of important changes, such as when a pipeline starts execution\. For more information, see [Create a notification rule](notification-rule-create.md)\. | | https://github.com/siagholami/aws-documentation/tree/main/documents/aws-codepipeline-user-guide/doc_source/integrations-general.md |
a123635e3e26-2 | | AWS Key Management Service | [AWS KMS](https://docs.aws.amazon.com/kms/latest/developerguide/) is a managed service that makes it easy for you to create and control the encryption keys used to encrypt your data\. By default, CodePipeline uses AWS KMS to encrypt artifacts for pipelines stored in Amazon S3 buckets\. Learn more: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/codepipeline/latest/userguide/integrations-general.html) For an AWS KMS key, you can use the key ID, the key ARN, or the alias ARN\. Aliases are recognized only in the account that created the customer master key \(CMK\)\. For cross\-account actions, you can only use the key ID or key ARN to identify the key\. | | https://github.com/siagholami/aws-documentation/tree/main/documents/aws-codepipeline-user-guide/doc_source/integrations-general.md |
18f30b24467c-0 | A pipeline describes the release process that you want AWS CodePipeline to follow, including stages and actions that must be completed\. You can edit a pipeline to add or remove these elements\. However, when you edit a pipeline, values such as the pipeline name or pipeline metadata cannot be changed\.
Unlike creating a pipeline, editing a pipeline does not rerun the most recent revision through the pipeline\. If you want to run the most recent revision through a pipeline you've just edited, you must manually rerun it\. Otherwise, the edited pipeline runs the next time you make a change to a source location configured in the source stage\. For information, see [Start a pipeline manually in AWS CodePipeline](pipelines-rerun-manually.md)\.
You can add actions to your pipeline that are in an AWS Region different from your pipeline\. When an AWS service is the provider for an action, and this action type/provider type are in a different AWS Region from your pipeline, this is a cross\-Region action\. For more information about cross\-Region actions, see [Add a cross\-Region action in CodePipeline](actions-create-cross-region.md)\.
CodePipeline uses change detection methods to start your pipeline when a source code change is pushed\. These detection methods are based on source type:
+ CodePipeline uses Amazon CloudWatch Events to detect changes in your CodeCommit source repository or your Amazon S3 source bucket\.
+ CodePipeline uses webhooks to detect changes in your GitHub source repository and branch\.
**Note** | https://github.com/siagholami/aws-documentation/tree/main/documents/aws-codepipeline-user-guide/doc_source/pipelines-edit.md |
18f30b24467c-1 | + CodePipeline uses webhooks to detect changes in your GitHub source repository and branch\.
**Note**
Change detection resources are created automatically when you use the console\. When you use the console to create or edit a pipeline, the additional resources are created for you\. If you use the AWS CLI to create the pipeline, you must create the additional resources yourself\. For more information about creating or updating a CodeCommit pipeline, see [Create a CloudWatch Events rule for a CodeCommit source \(CLI\)](pipelines-trigger-source-repo-changes-cli.md)\. For more information about using the CLI to create or update an Amazon S3 pipeline, see [Create a CloudWatch Events rule for an Amazon S3 source \(CLI\)](create-cloudtrail-S3-source-cli.md)\. For more information about creating or updating a GitHub pipeline, see [Use webhooks to start a pipeline \(GitHub source\)](pipelines-webhooks.md)\.
**Topics**
+ [Edit a pipeline \(console\)](#pipelines-edit-console)
+ [Edit a pipeline \(AWS CLI\)](#pipelines-edit-cli) | https://github.com/siagholami/aws-documentation/tree/main/documents/aws-codepipeline-user-guide/doc_source/pipelines-edit.md |
39efd500e932-0 | You can use the CodePipeline console to add, edit, or remove stages in a pipeline and to add, edit, or remove actions in a stage\.
**To edit a pipeline**
1. Sign in to the AWS Management Console and open the CodePipeline console at [http://console\.aws\.amazon\.com/codesuite/codepipeline/home](http://console.aws.amazon.com/codesuite/codepipeline/home)\.
The names of all pipelines associated with your AWS account are displayed\.
1. In **Name**, choose the name of the pipeline you want to edit\. This opens a detailed view of the pipeline, including the state of each of the actions in each stage of the pipeline\.
1. On the pipeline details page, choose **Edit**\.
1. On the **Edit** page, do one of the following:
+ To edit a stage, choose **Edit stage**\. You can add actions in serial and parallel with existing actions:
You can also edit actions in this view by choosing the edit icon for those actions\. To delete an action, choose the delete icon on that action\.
+ To edit an action, choose the edit icon for that action, and then on **Edit action**, change the values\. Items marked with an asterisk \(**\***\) are required\. | https://github.com/siagholami/aws-documentation/tree/main/documents/aws-codepipeline-user-guide/doc_source/pipelines-edit.md |
39efd500e932-1 | + For a CodeCommit repository name and branch, a message appears showing the Amazon CloudWatch Events rule to be created for this pipeline\. If you remove the CodeCommit source, a message appears showing the Amazon CloudWatch Events rule to be deleted\.
+ For an Amazon S3 source bucket, a message appears showing the Amazon CloudWatch Events rule and AWS CloudTrail trail to be created for this pipeline\. If you remove the Amazon S3 source, a message appears showing the Amazon CloudWatch Events rule and AWS CloudTrail trail to be deleted\. If the AWS CloudTrail trail is in use by other pipelines, the trail is not removed and the data event is deleted\.
+ For a GitHub source, the following are added for the pipeline:
+ CodePipeline uses an OAuth token to create an authorized application that is managed by CodePipeline\.
**Note**
In GitHub, there is a limit to the number of OAuth tokens you can use for an application, such as CodePipeline\. If you exceed this limit, retry the connection to allow CodePipeline to reconnect by reusing existing tokens\. For more information, see [Pipeline error: I receive a pipeline error that says: "Could not access the GitHub repository" or "Unable to connect to the GitHub repository"](troubleshooting.md#troubleshooting-gs2)\.
+ CodePipeline creates a webhook in GitHub to detect source changes and then start your pipeline when a change occurs\. CodePipeline creates the following along with the webhook:
+ A secret is randomly generated and used to authorize the connection to GitHub\. | https://github.com/siagholami/aws-documentation/tree/main/documents/aws-codepipeline-user-guide/doc_source/pipelines-edit.md |
39efd500e932-2 | + A secret is randomly generated and used to authorize the connection to GitHub\.
+ The webhook URL is generated using the public endpoint for the Region\.
+ The webhook is registered with GitHub\. This subscribes the URL to receive repository events\.
If you delete a GitHub source action, the webhook is deregistered and deleted for you\.
+ To add a stage, choose **\+ Add stage** at the point in the pipeline where you want to add a stage\. Provide a name for the stage, and then add at least one action to it\. Items marked with an asterisk \(**\***\) are required\.
+ To delete a stage, choose the delete icon on that stage\. The stage and all of its actions are deleted\.
For example, if you wanted to add a serial action to a stage in a pipeline:
1. In the stage where you want to add your action, choose **Edit stage**, and then choose **\+ Add action group**\. | https://github.com/siagholami/aws-documentation/tree/main/documents/aws-codepipeline-user-guide/doc_source/pipelines-edit.md |
39efd500e932-3 | 1. In the stage where you want to add your action, choose **Edit stage**, and then choose **\+ Add action group**\.
1. In **Edit action**, in **Action name**, enter the name of your action\. The **Action provider** list displays provider options by category\. Look for the category \(for example, **Deploy**\)\. Under the category, choose the provider \(for example, **AWS CodeDeploy**\)\. In **Region**, choose the AWS Region where the resource is created or where you plan to create it\. The **Region** field designates where the AWS resources are created for this action type and provider type\. This field only displays for actions where the action provider is an AWS service\. The **Region** field defaults to the same AWS Region as your pipeline\.
For more information about the requirements for actions in CodePipeline, including names for input and output artifacts and how they are used, see [Action structure requirements in CodePipeline](reference-pipeline-structure.md#action-requirements)\. For examples of adding action providers and using the default fields for each provider, see [Create a pipeline \(console\)](pipelines-create.md#pipelines-create-console)\.
To add CodeBuild as a build action or test action to a stage, see [Use CodePipeline with CodeBuild to Test Code and Run Builds](https://docs.aws.amazon.com/codebuild/latest/userguide/how-to-create-pipeline.html) in the *CodeBuild User Guide*\. | https://github.com/siagholami/aws-documentation/tree/main/documents/aws-codepipeline-user-guide/doc_source/pipelines-edit.md |
39efd500e932-4 | **Note**
Some action providers, such as GitHub, require you to connect to the provider's website before you can complete the configuration of the action\. When you connect to a provider's website, make sure you use the credentials for that website\. Do not use your AWS credentials\.
1. When you have finished configuring your action, choose **Save**\.
**Note**
You cannot rename a stage in the console view\. You can add a stage with the name you want to change, and then delete the old one\. Make sure you have added all the actions you want in that stage before you delete the old one\.
1. When you have finished editing your pipeline, choose **Save** to return to the summary page\.
**Important**
After you save your changes, you cannot undo them\. You must edit the pipeline again\. If a revision is running through your pipeline when you save your changes, the run is not completed\. If you want a specific commit or change to run through the edited pipeline, you must manually run it through the pipeline\. Otherwise, the next commit or change runs automatically through the pipeline\.
1. To test your action, choose **Release change** to process that commit through the pipeline and commit a change to the source specified in the source stage of the pipeline\. Or follow the steps in [Start a pipeline manually in AWS CodePipeline](pipelines-rerun-manually.md) to use the AWS CLI to manually release a change\. | https://github.com/siagholami/aws-documentation/tree/main/documents/aws-codepipeline-user-guide/doc_source/pipelines-edit.md |
afa8ff390342-0 | You can use the update\-pipeline command to edit a pipeline\.
**Important**
Although you can use the AWS CLI to edit pipelines that include partner actions, you must not manually edit the JSON of a partner action\. If you do so, the partner action fails after you update the pipeline\.
**To edit a pipeline**
1. Open a terminal session \(Linux, macOS, or Unix\) or command prompt \(Windows\) and run the get\-pipeline command to copy the pipeline structure into a JSON file\. For example, for a pipeline named **MyFirstPipeline**, enter the following command:
```
aws codepipeline get-pipeline --name MyFirstPipeline >pipeline.json
```
This command returns nothing, but the file you created should appear in the directory where you ran the command\.
1. Open the JSON file in any plain\-text editor and modify the structure of the file to reflect the changes you want to make to the pipeline\. For example, you can add or remove stages, or add another action to an existing stage\.
The following example shows how you would add another deployment stage in the pipeline\.json file\. This stage runs after the first deployment stage named *Staging*\.
**Note**
This is just a portion of the file, not the entire structure\. For more information, see [CodePipeline pipeline structure reference](reference-pipeline-structure.md)\.
```
,
{ | https://github.com/siagholami/aws-documentation/tree/main/documents/aws-codepipeline-user-guide/doc_source/pipelines-edit.md |
afa8ff390342-1 | ```
,
{
"name": "Staging",
"actions": [
{
"inputArtifacts": [
{
"name": "MyApp"
}
],
"name": "Deploy-CodeDeploy-Application",
"actionTypeId": {
"category": "Deploy",
"owner": "AWS",
"version": "1",
"provider": "CodeDeploy"
},
"outputArtifacts": [],
"configuration": {
"ApplicationName": "CodePipelineDemoApplication",
"DeploymentGroupName": "CodePipelineDemoFleet"
},
"runOrder": 1
}
]
},
{
"name": "Production",
"actions": [
{
"inputArtifacts": [
{
"name": "MyApp"
}
],
"name": "Deploy-Second-Deployment",
"actionTypeId": {
"category": "Deploy",
"owner": "AWS", | https://github.com/siagholami/aws-documentation/tree/main/documents/aws-codepipeline-user-guide/doc_source/pipelines-edit.md |
afa8ff390342-2 | "actionTypeId": {
"category": "Deploy",
"owner": "AWS",
"version": "1",
"provider": "CodeDeploy"
},
"outputArtifacts": [],
"configuration": {
"ApplicationName": "CodePipelineDemoApplication",
"DeploymentGroupName": "CodePipelineProductionFleet"
},
"runOrder": 1
}
]
}
]
}
```
The following example shows how you would add a source stage that uses a GitHub repository as its source action\. For more information about how CodePipeline integrates with GitHub, see [Source action integrations](integrations-action-type.md#integrations-source)\.
**Note**
This is just a portion of the file, not the entire structure\. For more information, see [CodePipeline pipeline structure reference](reference-pipeline-structure.md)\.
```
{
"name": "Source",
"actions": [
{
"inputArtifacts": [],
"name": "Source",
"actionTypeId": {
"category": "Source",
"owner": "ThirdParty", | https://github.com/siagholami/aws-documentation/tree/main/documents/aws-codepipeline-user-guide/doc_source/pipelines-edit.md |
afa8ff390342-3 | "actionTypeId": {
"category": "Source",
"owner": "ThirdParty",
"provider": "GitHub",
"version": "1"
},
"outputArtifacts": [
{
"name": "MyApp"
}
],
"configuration": {
"Owner": "MyGitHubAccountName",
"Repo": "MyGitHubRepositoryName",
"PollForSourceChanges": "false",
"Branch": "master",
"OAuthToken": "****"
},
"runOrder": 1
}
]
},
```
The value for `OAuthToken` remains masked because CodePipeline uses it to access the GitHub repository\. You can use a personal access token for this value\. To create a personal access token, see [Configure your pipeline to use a personal access token \(GitHub and CLI\)](GitHub-create-personal-token-CLI.md)\.
**Note** | https://github.com/siagholami/aws-documentation/tree/main/documents/aws-codepipeline-user-guide/doc_source/pipelines-edit.md |
afa8ff390342-4 | **Note**
Some edits, such as moving an action from one stage to another stage, delete the last known state history for the action\. If a pipeline contains one or more secret parameters, such as an OAuth token for an action, that token is masked by a series of asterisks \(\*\*\*\*\)\. These secret parameters are left unchanged unless you edit that portion of the pipeline \(for example, if you change the name of the action that includes the OAuth token or the name of the stage that contains an action that uses an OAuth token\)\. If you make a change that affects an action that includes an OAuth token, you must include the value of the token in the edited JSON\. For more information, see [Configure your pipeline to use a personal access token \(GitHub and CLI\)](GitHub-create-personal-token-CLI.md)\. It is a security best practice to rotate your personal access token on a regular basis\. For more information, see [Use GitHub and the CodePipeline CLI to create and rotate your GitHub personal access token on a regular basis](GitHub-authentication.md#GitHub-rotate-personal-token-CLI)\.
For information about using the CLI to add an approval action to a pipeline, see [Add a manual approval action to a pipeline in CodePipeline ](approvals-action-add.md)\.
Make sure the `PollForSourceChanges` parameter in your JSON file is set as follows:
```
"PollForSourceChanges": "false", | https://github.com/siagholami/aws-documentation/tree/main/documents/aws-codepipeline-user-guide/doc_source/pipelines-edit.md |
afa8ff390342-5 | ```
"PollForSourceChanges": "false",
```
CodePipeline uses Amazon CloudWatch Events to detect changes in your CodeCommit source repository and branch or your Amazon S3 source bucket\. CodePipeline uses webhooks to detect changes in your GitHub source repository and branch\. The next step includes instructions for creating these resources manually\. Setting the flag to `false` disables periodic checks, which are not required when you use the recommended change detection methods\.
1. To add a build, test, or deploy action in a Region different from your pipeline, you must add the following to your pipeline structure\. For detailed instructions, see [Add a cross\-Region action in CodePipeline](actions-create-cross-region.md)\.
+ Add the `Region` parameter to your action's pipeline structure\.
+ Use the `artifactStores` parameter to specify an artifact bucket for each Region where you have an action\.
1. If you are working with the pipeline structure retrieved using the get\-pipeline command, you must modify the structure in the JSON file\. You must remove the `metadata` lines from the file so the update\-pipeline command can use it\. Remove the section from the pipeline structure in the JSON file \(the `"metadata": { }` lines and the `"created"`, `"pipelineARN"`, and `"updated"` fields\)\.
For example, remove the following lines from the structure:
```
"metadata": { | https://github.com/siagholami/aws-documentation/tree/main/documents/aws-codepipeline-user-guide/doc_source/pipelines-edit.md |
afa8ff390342-6 | For example, remove the following lines from the structure:
```
"metadata": {
"pipelineArn": "arn:aws:codepipeline:region:account-ID:pipeline-name",
"created": "date",
"updated": "date"
}
```
Save the file\.
1. If you use the CLI to edit a pipeline, you must manually manage the recommended change detection resources for your pipeline:
+ For a CodeCommit repository, you must create the CloudWatch Events rule, as described in [Create a CloudWatch Events rule for a CodeCommit source \(CLI\)](pipelines-trigger-source-repo-changes-cli.md)\.
+ For an Amazon S3 source, you must create the CloudWatch Events rule and AWS CloudTrail trail, as described in [Use CloudWatch Events to start a pipeline \(Amazon S3 source\)](create-cloudtrail-S3-source.md)\.
+ For a GitHub source, you must create the webhook, as described in [Use webhooks to start a pipeline \(GitHub source\)](pipelines-webhooks.md)\.
1. To apply your changes, run the update\-pipeline command, specifying the pipeline JSON file:
**Important**
Be sure to include `file://` before the file name\. It is required in this command\.
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/aws-codepipeline-user-guide/doc_source/pipelines-edit.md |
afa8ff390342-7 | Be sure to include `file://` before the file name\. It is required in this command\.
```
aws codepipeline update-pipeline --cli-input-json file://pipeline.json
```
This command returns the entire structure of the edited pipeline\.
**Note**
The update\-pipeline command stops the pipeline\. If a revision is being run through the pipeline when you run the update\-pipeline command, that run is stopped\. You must start the pipeline manually to run that revision through the updated pipeline\.
1. Open the CodePipeline console and choose the pipeline you just edited\.
The pipeline shows your changes\. The next time you make a change to the source location, the pipeline runs that revision through the revised structure of the pipeline\.
1. To manually run the last revision through the revised structure of the pipeline, run the start\-pipeline\-execution command\. For more information, see [Start a pipeline manually in AWS CodePipeline](pipelines-rerun-manually.md)\.
For more information about the structure of a pipeline and expected values, see [CodePipeline pipeline structure reference](reference-pipeline-structure.md) and [AWS CodePipeline API Reference](http://docs.aws.amazon.com/codepipeline/latest/APIReference)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/aws-codepipeline-user-guide/doc_source/pipelines-edit.md |
98bd0a171dd3-0 | 1. Sign in to the AWS Management Console and open the CodePipeline console at [http://console\.aws\.amazon\.com/codesuite/codepipeline/home](http://console.aws.amazon.com/codesuite/codepipeline/home)\.
Choose **Create pipeline** and complete the **Step 1: Choose pipeline settings** page in the pipeline creation wizard\.
**Note**
After you create a pipeline, you cannot change its name\. For information about other limitations, see [Quotas in AWS CodePipeline](limits.md)\.
1. In **Service role**, do one of the following:
+ Choose **New service role** to allow CodePipeline to create a new service role in IAM\. In **Role name**, the role and policy name both default to this format: AWSCodePipelineServiceRole\-*region*\-*pipeline\_name*\. For example, this is the service role created for this tutorial: AWSCodePipelineServiceRole\-eu\-west\-2\-MyFirstPipeline\.
+ Choose **Existing service role** to use a service role already created in IAM\. In **Role name**, choose your service role from the list\.
**Note**
In the console, service roles created before September 2018 are created with the name "oneClick\_AWS\-CodePipeline\-Service\_*ID\-Number*"\. | https://github.com/siagholami/aws-documentation/tree/main/documents/aws-codepipeline-user-guide/doc_source/pipelines-create-service-role-console.md |
98bd0a171dd3-1 | Service roles created after September 2018 use the service role name format "AWSCodePipelineServiceRole\-*Region*\-*Pipeline\_Name*"\. For example, for a pipeline named MyFirstPipeline created in the console in eu\-west\-2, the service role named "AWSCodePipelineServiceRole\-eu\-west\-2\-MyFirstPipeline" is created\. The policy name format is the same as the role name format\.
1. Complete the pipeline creation\. Your pipeline service role is available to view in your list of IAM roles, and you can view the service role ARN associated to a pipeline by running the `get-pipeline` command with the AWS CLI\. | https://github.com/siagholami/aws-documentation/tree/main/documents/aws-codepipeline-user-guide/doc_source/pipelines-create-service-role-console.md |
b22ed51d841a-0 | Cloud security at AWS is the highest priority\. As an AWS customer, you benefit from a data center and network architecture that is built to meet the requirements of the most security\-sensitive organizations\.
Security is a shared responsibility between AWS and you\. The [shared responsibility model](https://aws.amazon.com/compliance/shared-responsibility-model/) describes this as security *of* the cloud and security *in* the cloud:
+ **Security of the cloud** – AWS is responsible for protecting the infrastructure that runs AWS services in the AWS Cloud\. AWS also provides you with services that you can use securely\. Third\-party auditors regularly test and verify the effectiveness of our security as part of the [AWS compliance programs](https://aws.amazon.com/compliance/programs/)\. To learn about the compliance programs that apply to AWS CodePipeline, see [AWS Services in Scope by Compliance Program](https://aws.amazon.com/compliance/services-in-scope/)\.
+ **Security in the cloud** – Your responsibility is determined by the AWS service that you use\. You are also responsible for other factors, including the sensitivity of your data, your company’s requirements, and applicable laws and regulations\.
This documentation helps you understand how to apply the shared responsibility model when using CodePipeline\. The following topics show you how to configure CodePipeline to meet your security and compliance objectives\. You also learn how to use other AWS services that help you to monitor and secure your CodePipeline resources\.
**Topics** | https://github.com/siagholami/aws-documentation/tree/main/documents/aws-codepipeline-user-guide/doc_source/security.md |
b22ed51d841a-1 | **Topics**
+ [Data protection in AWS CodePipeline](data-protection.md)
+ [Identity and access management for AWS CodePipeline](security-iam.md)
+ [Logging and monitoring in CodePipeline](incident-response.md)
+ [Compliance validation for AWS CodePipeline](SERVICENAME-compliance.md)
+ [Resilience in AWS CodePipeline](disaster-recovery-resiliency.md)
+ [Infrastructure security in AWS CodePipeline](infrastructure-security.md)
+ [Security best practices](security-best-practices.md) | https://github.com/siagholami/aws-documentation/tree/main/documents/aws-codepipeline-user-guide/doc_source/security.md |
9f5e9430b0ba-0 | Identity\-based policies are very powerful\. They determine whether someone can create, access, or delete CodePipeline resources in your account\. These actions can incur costs for your AWS account\. When you create or edit identity\-based policies, follow these guidelines and recommendations:
+ **Get Started Using AWS Managed Policies** – To start using CodePipeline quickly, use AWS managed policies to give your employees the permissions they need\. These policies are already available in your account and are maintained and updated by AWS\. For more information, see [Get Started Using Permissions With AWS Managed Policies](https://docs.aws.amazon.com/IAM/latest/UserGuide/best-practices.html#bp-use-aws-defined-policies) in the *IAM User Guide*\.
+ **Grant Least Privilege** – When you create custom policies, grant only the permissions required to perform a task\. Start with a minimum set of permissions and grant additional permissions as necessary\. Doing so is more secure than starting with permissions that are too lenient and then trying to tighten them later\. For more information, see [Grant Least Privilege](https://docs.aws.amazon.com/IAM/latest/UserGuide/best-practices.html#grant-least-privilege) in the *IAM User Guide*\. | https://github.com/siagholami/aws-documentation/tree/main/documents/aws-codepipeline-user-guide/doc_source/security_iam_service-with-iam-policy-best-practices.md |
9f5e9430b0ba-1 | + **Enable MFA for Sensitive Operations** – For extra security, require IAM users to use multi\-factor authentication \(MFA\) to access sensitive resources or API operations\. For more information, see [Using Multi\-Factor Authentication \(MFA\) in AWS](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_mfa.html) in the *IAM User Guide*\.
+ **Use Policy Conditions for Extra Security** – To the extent that it's practical, define the conditions under which your identity\-based policies allow access to a resource\. For example, you can write conditions to specify a range of allowable IP addresses that a request must come from\. You can also write conditions to allow requests only within a specified date or time range, or to require the use of SSL or MFA\. For more information, see [IAM JSON Policy Elements: Condition](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_elements_condition.html) in the *IAM User Guide*\. | https://github.com/siagholami/aws-documentation/tree/main/documents/aws-codepipeline-user-guide/doc_source/security_iam_service-with-iam-policy-best-practices.md |
1c4cd328493b-0 | Call the put\-rule command, specifying:
+ A name that uniquely identifies the rule you are creating\. This name must be unique across all of the pipelines you create with CodePipeline associated with your AWS account\.
+ The event pattern for the source and detail fields used by the rule\. For more information, see [Amazon CloudWatch Events and Event Patterns](http://docs.aws.amazon.com/AmazonCloudWatch/latest/events/CloudWatchEventsandEventPatterns.html)\.
**To create a CloudWatch Events rule with Amazon ECR as the event source and CodePipeline as the target**
1. Add permissions for Amazon CloudWatch Events to use CodePipeline to invoke the rule\. For more information, see [Using Resource\-Based Policies for Amazon CloudWatch Events](http://docs.aws.amazon.com/AmazonCloudWatch/latest/events/resource-based-policies-cwe.html)\.
1. Use the following sample to create the trust policy that allows CloudWatch Events to assume the service role\. Name the trust policy `trustpolicyforCWE.json`\.
```
{
"Version": "2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Principal": {
"Service": "events.amazonaws.com"
},
"Action": "sts:AssumeRole"
}
] | https://github.com/siagholami/aws-documentation/tree/main/documents/aws-codepipeline-user-guide/doc_source/create-cwe-ecr-source-cli.md |
1c4cd328493b-1 | },
"Action": "sts:AssumeRole"
}
]
}
```
1. Use the following command to create the `Role-for-MyRule` role and attach the trust policy\.
```
aws iam create-role --role-name Role-for-MyRule --assume-role-policy-document file://trustpolicyforCWE.json
```
1. Create the permissions policy JSON, as shown in this sample, for the pipeline named `MyFirstPipeline`\. Name the permissions policy `permissionspolicyforCWE.json`\.
```
{
"Version": "2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Action": [
"codepipeline:StartPipelineExecution"
],
"Resource": [
"arn:aws:codepipeline:us-west-2:80398EXAMPLE:MyFirstPipeline"
]
}
]
}
```
1. Use the following command to attach the `CodePipeline-Permissions-Policy-for-CWE` permissions policy to the `Role-for-MyRule` role\. | https://github.com/siagholami/aws-documentation/tree/main/documents/aws-codepipeline-user-guide/doc_source/create-cwe-ecr-source-cli.md |
1c4cd328493b-2 | **Why am I making this change?** Adding this policy to the role creates permissions for CloudWatch Events\.
```
aws iam put-role-policy --role-name Role-for-MyRule --policy-name CodePipeline-Permissions-Policy-For-CWE --policy-document file://permissionspolicyforCWE.json
```
1. Call the put\-rule command and include the `--name`, `--event-pattern`, and `--role-arn` parameters\.
**Why am I making this change?** We must create an event with a rule that specifies how an image push must be made, and a target that names the pipeline to be triggered by the event\.
The following sample command creates a rule called `MyECRRepoRule`\.
```
aws events put-rule --name "MyECRRepoRule" --event-pattern "{\"detail-type\":[\"ECR Image Action\"],\"source\":[\"aws.ecr\"],\"detail\":{\"action-type\":[\"PUSH\"],\"image-tag\":[\"latest\"],\"repository-name\":[\"cwe-test\"],\"result\":[\"SUCCESS\"]}}}" --role-arn "arn:aws:iam::ACCOUNT_ID:role/Role-for-MyRule"
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/aws-codepipeline-user-guide/doc_source/create-cwe-ecr-source-cli.md |
1c4cd328493b-3 | ```
**Note**
To view the full event pattern supported for Amazon ECR events, see [Amazon ECR Events and EventBridge](https://docs.aws.amazon.com/AmazonECR/latest/userguide/ecr-eventbridge.html) or [Amazon Elastic Container Registry Events](https://docs.aws.amazon.com/eventbridge/latest/userguide/event-types.html#ecr-event-types)\.
1. To add CodePipeline as a target, call the put\-targets command and include the following parameters:
+ The `--rule` parameter is used with the `rule_name` you created by using put\-rule\.
+ The `--targets` parameter is used with the list `Id` of the target in the list of targets and the `ARN` of the target pipeline\.
The following sample command specifies that for the rule called `MyECRRepoRule`, the target `Id` is composed of the number one, indicating that in a list of targets for the rule, this is target 1\. The sample command also specifies an example `Arn` for the pipeline and the example `RoleArn` for the rule\. The pipeline starts when something changes in the repository\.
```
aws events put-targets --rule MyECRRepoRule --targets Id=1,Arn=arn:aws:codepipeline:us-west-2:80398EXAMPLE:TestPipeline,RoleArn=arn:aws:iam::80398EXAMPLE:role/Role-for-MyRule | https://github.com/siagholami/aws-documentation/tree/main/documents/aws-codepipeline-user-guide/doc_source/create-cwe-ecr-source-cli.md |
1c4cd328493b-4 | ``` | https://github.com/siagholami/aws-documentation/tree/main/documents/aws-codepipeline-user-guide/doc_source/create-cwe-ecr-source-cli.md |
f5769c597fd5-0 | The following table describes the important changes in each release of the CodePipeline User Guide\. For notification about updates to this documentation, you can subscribe to an RSS feed\.
+ **API version:** 2015\-07\-09
+ **Latest documentation update:** August 25, 2020
| Change | Description | Date |
| --- |--- |--- |
| [The CodeBuild action supports enabling batch builds in AWS CodePipeline](#history) | For CodeBuild actions in your pipeline, you can enable batch builds to run multiple builds in a single execution\. For more information, see [CodeBuild action structure reference](https://docs.aws.amazon.com/codepipeline/latest/userguide/action-reference-CodeBuild.html) and [Create a pipeline \(console\)](https://docs.aws.amazon.com/codepipeline/latest/userguide/pipelines-create.html#pipelines-create-console)\. | July 30, 2020 | | https://github.com/siagholami/aws-documentation/tree/main/documents/aws-codepipeline-user-guide/doc_source/history.md |
f5769c597fd5-1 | | [AWS CodePipeline now supports AWS AppConfig deployment actions](#history) | A new tutorial, [Tutorial: Create a pipeline that uses AWS AppConfig as a deployment provider](https://docs.aws.amazon.com/codepipeline/latest/userguide/tutorials-AppConfig.html), provides steps to use AWS AppConfig to deploy configuration files with your pipeline\. The [AWS AppConfig action structure reference](https://docs.aws.amazon.com/codepipeline/latest/userguide/action-reference-AppConfig.html) topic has also been added\. | June 25, 2020 |
| [AWS CodePipeline now supports Amazon VPC in AWS GovCloud \(US\-West\)](#history) | You can now connect directly to AWS CodePipeline through a private Amazon VPC endpoint in AWS GovCloud \(US\-West\)\. For more information, see [Use CodePipeline with Amazon Virtual Private Cloud](https://docs.aws.amazon.com/codepipeline/latest/userguide/vpc-support.html)\. | June 2, 2020 | | https://github.com/siagholami/aws-documentation/tree/main/documents/aws-codepipeline-user-guide/doc_source/history.md |
f5769c597fd5-2 | | [AWS CodePipeline now supports AWS Step Functions invoke actions](#history) | You can now create a pipeline in CodePipeline that uses AWS Step Functions as the invoke action provider\. A new tutorial, [Tutorial: Use an AWS Step Functions invoke action in a pipeline](https://docs.aws.amazon.com/codepipeline/latest/userguide/tutorials-step-functions.html), provides steps for starting a state machine execution from your pipeline\. The [AWS Step Functions Action Structure Reference](https://docs.aws.amazon.com/codepipeline/latest/userguide/action-reference-StepFunctions.html) topic has also been added\. | May 28, 2020 |
| [View, list, and update connections](#history) | You can list, delete, and update connections in the console\. See [List connections in CodePipeline](https://docs.aws.amazon.com/codepipeline/latest/userguide/connections-list.html)\. | May 21, 2020 |
| [Connections support tagging connections resources in the CLI](#history) | The connections resources now support tagging in the AWS CLI\. Connections now integrate with AWS CodeGuru\. See [IAM Permissions Reference for Connections](https://docs.aws.amazon.com/codepipeline/latest/userguide/connections-permissions.html)\. | May 6, 2020 | | https://github.com/siagholami/aws-documentation/tree/main/documents/aws-codepipeline-user-guide/doc_source/history.md |
f5769c597fd5-3 | | [CodePipeline is now available in AWS GovCloud \(US\-West\)](#history) | You can now use CodePipeline in AWS GovCloud \(US\-West\)\. For more information, see [Quotas](https://docs.aws.amazon.com/codepipeline/latest/userguide/limits.html)\. | April 8, 2020 |
| [The quotas topic shows which CodePipeline service quotas are configurable](#history) | The CodePipeline quotas topic has been reformatted\. The documentation shows which service quotas are configurable and which quotas are non\-configurable\. See [Quotas in AWS CodePipeline](https://docs.aws.amazon.com/codepipeline/latest/userguide/limits.html)\. | March 12, 2020 |
| [The Amazon ECS deployment action timeout is configurable](#history) | The Amazon ECS deployment action timeout is configurable up to one hour \(the default timeout\)\. See [Quotas in AWS CodePipeline](https://docs.aws.amazon.com/codepipeline/latest/userguide/limits.html)\. | February 5, 2020 | | https://github.com/siagholami/aws-documentation/tree/main/documents/aws-codepipeline-user-guide/doc_source/history.md |
f5769c597fd5-4 | | [New topics describe how you can stop a pipeline execution](#history) | You can stop a pipeline execution in CodePipeline\. You can either specify that the execution stops after in\-progress actions are allowed to complete, or you can specify to stop the execution immediately and abandon in\-progress actions\. See [How pipeline executions are stopped](https://docs.aws.amazon.com/codepipeline/latest/userguide/welcome.html#concepts-how-it-works-stopping) and [Stop a pipeline execution in CodePipeline](https://docs.aws.amazon.com/codepipeline/latest/userguide/pipelines-stop.html)\. | January 21, 2020 |
| [CodePipeline supports connections](#history) | You can use connections to configure AWS resources to interact with external code repositories\. Each connection is a resource that can be used by services such as CodePipeline to connect to a third\-party repository, such as Bitbucket\. For more information, see [Working with connections in CodePipeline](https://docs.aws.amazon.com/codepipeline/latest/userguide/connections.html)\. | December 18, 2019 |
| [Updated security, authentication, and access control topics](#history) | The security, authentication, and access control information for CodePipeline has been organized into a new Security chapter\. For more information, see [Security](https://docs.aws.amazon.com/codepipeline/latest/userguide/security.html)\. | December 17, 2019 | | https://github.com/siagholami/aws-documentation/tree/main/documents/aws-codepipeline-user-guide/doc_source/history.md |
f5769c597fd5-5 | | [New topics describe how you can use variables in your pipelines](#history) | You can now configure namespaces for actions and generate variables each time the action execution is complete\. You can set up downstream actions to reference these namespaces and variables\. See [Working with variables](https://docs.aws.amazon.com/codepipeline/latest/userguide/actions-variables.html) and [Variables](https://docs.aws.amazon.com/codepipeline/latest/userguide/reference-variables.html)\. | November 14, 2019 |
| [New topics describe how pipeline executions work, why stages are locked during an execution, and when pipeline executions are superseded](#history) | A number of topics have been added to the Welcome section to describe how pipeline executions work, including why stages are locked during an execution and what happens when pipeline executions are superseded\. These topics include a list of concepts, a DevOps workflow example, and recommendations for how a pipeline should be structured\. The following topics have been added: [Pipeline terms](https://docs.aws.amazon.com/codepipeline/latest/userguide/concepts.html#concepts-pipeline-terms), [DevOps pipeline example](https://docs.aws.amazon.com/codepipeline/latest/userguide/concepts-devops-example.html), and [How pipeline executions work](https://docs.aws.amazon.com/codepipeline/latest/userguide/concepts-how-it-works.html)\. | November 11, 2019 | | https://github.com/siagholami/aws-documentation/tree/main/documents/aws-codepipeline-user-guide/doc_source/history.md |
f5769c597fd5-6 | | [CodePipeline supports notification rules](#history) | You can now use notification rules to notify users of important changes in pipelines\. For more information, see [Create a notification rule](https://docs.aws.amazon.com/codepipeline/latest/userguide/notification-rule-create.html)\. | November 5, 2019 |
| [CodeBuild environment variables available in CodePipeline](#history) | You can set CodeBuild environment variables in the CodeBuild build action for your pipeline\. You can use the console or CLI to add the `EnvironmentVariables` parameter to the pipeline structure\. The [Create a pipeline \(console\)](https://docs.aws.amazon.com/codepipeline/latest/userguide/pipelines-create-console.html) topic has been updated\. The action configuration examples in the action reference for [CodeBuild](https://docs.aws.amazon.com/codepipeline/latest/userguide/action-reference-codebuild.html) have also been updated\. | October 14, 2019 |
| [New Region](#history) | CodePipeline is now available in Europe \(Stockholm\)\. The [Limits](https://docs.aws.amazon.com/codepipeline/latest/userguide/limits.html) topic and [AWS service endpoints](https://docs.aws.amazon.com/general/latest/gr/rande.html#codepipeline_region) topic have been updated\. | September 5, 2019 | | https://github.com/siagholami/aws-documentation/tree/main/documents/aws-codepipeline-user-guide/doc_source/history.md |
f5769c597fd5-7 | | [Specify canned ACLs and cache control for Amazon S3 deployment actions](#history) | You can now specify canned ACL and cache control options when you create an Amazon S3 deployment action in CodePipeline\. The following topics have been updated: [Create a pipeline \(console\)](https://docs.aws.amazon.com/codepipeline/latest/userguide/pipelines-create-console.html), [CodePipeline Pipeline structure reference](https://docs.aws.amazon.com/codepipeline/latest/userguide/reference-pipeline-structure.html), and [Tutorial: Create a pipeline that uses Amazon S3 as a deployment provider](https://docs.aws.amazon.com/codepipeline/latest/userguide/tutorials-s3deploy.html)\. | June 27, 2019 | | https://github.com/siagholami/aws-documentation/tree/main/documents/aws-codepipeline-user-guide/doc_source/history.md |
f5769c597fd5-8 | | [You can now add tags to resources in AWS CodePipeline](#history) | You can now use tagging to track and manage AWS CodePipeline resources such as pipelines, custom actions, and webhooks\. The following new topics have been added: [Tagging resources](https://docs.aws.amazon.com/codepipeline/latest/userguide/tag-resources.html), [Using tags to control access to CodePipeline resources](https://docs.aws.amazon.com/codepipeline/latest/userguide/security-iam.html#tag-based-access-control), [Tag a pipeline in CodePipeline](https://docs.aws.amazon.com/codepipeline/latest/userguide/pipelines-tag.html), | https://github.com/siagholami/aws-documentation/tree/main/documents/aws-codepipeline-user-guide/doc_source/history.md |
f5769c597fd5-9 | CodePipeline](https://docs.aws.amazon.com/codepipeline/latest/userguide/pipelines-tag.html), [Tag a custom action in CodePipeline](https://docs.aws.amazon.com/codepipeline/latest/userguide/customactions-tag.html), and [Tag a webhook in CodePipeline](https://docs.aws.amazon.com/codepipeline/latest/userguide/tag-webhooks.html)\. The following topics have been updated to show how to use the CLI to tag resources: [Create a pipeline \(CLI\)](https://docs.aws.amazon.com/codepipeline/latest/userguide/pipelines-create.html#pipelines-create-cli), [Create a custom action | https://github.com/siagholami/aws-documentation/tree/main/documents/aws-codepipeline-user-guide/doc_source/history.md |
f5769c597fd5-10 | [Create a custom action \(CLI\)](https://docs.aws.amazon.com/codepipeline/latest/userguide/actions-create-custom-action.html#actions-create-custom-action-cli), and [Create a webhook for a GitHub source](https://docs.aws.amazon.com/codepipeline/latest/userguide/pipelines-webhooks-create.html)\. | May 15, 2019 | | https://github.com/siagholami/aws-documentation/tree/main/documents/aws-codepipeline-user-guide/doc_source/history.md |
f5769c597fd5-11 | | [You can now view action execution history in AWS CodePipeline](#history) | You can now view details about past executions of all actions in a pipeline\. These details include start and end times, duration, action execution ID, status, input and output artifact location details, and external resource details\. The [View pipeline details and history](https://docs.aws.amazon.com/codepipeline/latest/userguide/pipelines-view.html) topic has been updated to reflect this support\. | March 20, 2019 |
| [AWS CodePipeline now supports publishing applications to the AWS Serverless Application Repository](#history) | You can now create a pipeline in CodePipeline that publishes your serverless application to the AWS Serverless Application Repository\. A new tutorial, [Tutorial: Publish applications to the AWS Serverless Application Repository](https://docs.aws.amazon.com/codepipeline/latest/userguide/tutorials-serverlessrepo-auto-publish.html), provides steps for creating and configuring a pipeline to continuously deliver your serverless application to the AWS Serverless Application Repository\. | March 8, 2019 | | https://github.com/siagholami/aws-documentation/tree/main/documents/aws-codepipeline-user-guide/doc_source/history.md |
f5769c597fd5-12 | | [AWS CodePipeline now supports cross\-region actions in the console](#history) | You can now manage cross\-region actions in the AWS CodePipeline console\. [Add a cross\-Region action](https://docs.aws.amazon.com/codepipeline/latest/userguide/actions-create-cross-region.html) has been updated with the steps to add, edit, or delete an action that is in a different AWS Region from your pipeline\. The [Create a pipeline](https://docs.aws.amazon.com/codepipeline/latest/userguide/pipelines-create.html), [Edit a pipeline](https://docs.aws.amazon.com/codepipeline/latest/userguide/pipelines-edit.html), and [CodePipeline pipeline structure reference](https://docs.aws.amazon.com/codepipeline/latest/userguide/reference-pipeline-structure.html) topics have been updated\. | February 14, 2019 | | https://github.com/siagholami/aws-documentation/tree/main/documents/aws-codepipeline-user-guide/doc_source/history.md |
f5769c597fd5-13 | | [AWS CodePipeline now supports Amazon S3 deployments](#history) | You can now create a pipeline in CodePipeline that uses Amazon S3 as the deployment action provider\. A new tutorial, [Tutorial: Create a pipeline that uses Amazon S3 as a deployment provider](https://docs.aws.amazon.com/codepipeline/latest/userguide/tutorials-s3deploy.html), provides steps for deploying sample files to your Amazon S3 bucket with CodePipeline\. The [CodePipeline pipeline structure reference](https://docs.aws.amazon.com/codepipeline/latest/userguide/reference-pipeline-structure.html) topic has also been updated\. | January 16, 2019 |
| [AWS CodePipeline now supports Alexa Skills Kit deployments](#history) | You can now use CodePipeline and Alexa Skills Kit for continuous deployment of Alexa skills\. A new tutorial, [Tutorial: Create a pipeline that deploys an Amazon Alexa skill](https://docs.aws.amazon.com/codepipeline/latest/userguide/tutorials-alexa-skills-kit.html), contains steps for creating credentials that allow AWS CodePipeline to connect to your Alexa Skills Kit developer account and then creating a pipeline that deploys a sample skill\. The [CodePipeline pipeline structure reference](https://docs.aws.amazon.com/codepipeline/latest/userguide/reference-pipeline-structure.html) topic has been updated\. | December 19, 2018 | | https://github.com/siagholami/aws-documentation/tree/main/documents/aws-codepipeline-user-guide/doc_source/history.md |
f5769c597fd5-14 | | [AWS CodePipeline now supports Amazon VPC endpoints powered by AWS PrivateLink](#history) | You can now connect directly to AWS CodePipeline through a private endpoint in your VPC, keeping all traffic inside your VPC and the AWS network\. For more information, see [Use CodePipeline with Amazon Virtual Private Cloud](https://docs.aws.amazon.com/codepipeline/latest/userguide/vpc-support.html)\. | December 6, 2018 |
| [AWS CodePipeline now supports Amazon ECR source actions and ECS\-to\-CodeDeploy deployment actions](#history) | You can now use CodePipeline and CodeDeploy with Amazon ECR and Amazon ECS for continuous deployment of container\-based applications\. A new tutorial, [Create a pipeline with an Amazon ECR source and ECS\-to\-CodeDeploy deployment](https://docs.aws.amazon.com/codepipeline/latest/userguide/tutorials-ecs-ecr-codedeploy.html), contains steps for using the console to create a pipeline that deploys container applications stored in an image repository to an Amazon ECS cluster with CodeDeploy traffic routing\. The [Create a pipeline](https://docs.aws.amazon.com/codepipeline/latest/userguide/pipelines-create.html) and [CodePipeline pipeline structure reference](https://docs.aws.amazon.com/codepipeline/latest/userguide/reference-pipeline-structure.html) topics have been updated\. | November 27, 2018 | | https://github.com/siagholami/aws-documentation/tree/main/documents/aws-codepipeline-user-guide/doc_source/history.md |
f5769c597fd5-15 | | [AWS CodePipeline now supports cross\-region actions in a pipeline](#history) | A new topic, [Add a Cross\-region Action](https://docs.aws.amazon.com/codepipeline/latest/userguide/actions-create-cross-region.html), contains steps for using the AWS CLI or AWS CloudFormation to add an action that is in a different region from your pipeline\. The [Create a pipeline](https://docs.aws.amazon.com/codepipeline/latest/userguide/pipelines-create.html), [Edit a pipeline](https://docs.aws.amazon.com/codepipeline/latest/userguide/pipelines-edit.html), and [CodePipeline pipeline structure reference](https://docs.aws.amazon.com/codepipeline/latest/userguide/reference-pipeline-structure.html) topics have been updated\. | November 12, 2018 | | https://github.com/siagholami/aws-documentation/tree/main/documents/aws-codepipeline-user-guide/doc_source/history.md |
f5769c597fd5-16 | | [AWS CodePipeline now integrates with AWS Service Catalog](#history) | You can now add AWS Service Catalog as a deployment action to your pipeline\. This allows you to set up a pipeline to publish product updates to AWS Service Catalog when you make a change in your source repository\. The [Integrations](https://docs.aws.amazon.com/codepipeline/latest/userguide/integrations.html) topic has been updated to reflect this support for AWS Service Catalog\. Two AWS Service Catalog tutorials have been added to the [AWS CodePipeline tutorials](https://docs.aws.amazon.com/codepipeline/latest/userguide/tutorials.html) section\. | October 16, 2018 |
| [AWS CodePipeline now integrates with AWS Device Farm](#history) | You can now add AWS Device Farm as a test action to your pipeline\. This allows you to set up a pipeline to test mobile applications\. The [Integrations](https://docs.aws.amazon.com/codepipeline/latest/userguide/integrations.html) topic has been updated to reflect this support for AWS Device Farm\. Two AWS Device Farm tutorials have been added to the [AWS CodePipeline tutorials](https://docs.aws.amazon.com/codepipeline/latest/userguide/tutorials.html) section\. | July 19, 2018 | | https://github.com/siagholami/aws-documentation/tree/main/documents/aws-codepipeline-user-guide/doc_source/history.md |
f5769c597fd5-17 | | [AWS CodePipeline User Guide update notifications now available through RSS](#history) | The HTML version of the CodePipeline User Guide now supports an RSS feed of updates that are documented in the Documentation Update History page\. The RSS feed includes updates made after June 30, 2018 and later\. Previously announced updates are still available in the Documentation Update History page\. Use the RSS button in the top menu panel to subscribe to the feed\. | June 30, 2018 | | https://github.com/siagholami/aws-documentation/tree/main/documents/aws-codepipeline-user-guide/doc_source/history.md |
f924b2f48a23-0 | The following table describes important changes in each release of the CodePipeline User Guide on June 30, 2018 and earlier\.
| Change | Description | Date changed |
| --- | --- | --- |
| Use webhooks to detect source changes in GitHub pipelines | When you create or edit a pipeline in the console, CodePipeline now creates a webhook that detects changes to your GitHub source repository and then starts your pipeline\. For information about migrating your pipeline, see [Configure Your GitHub Pipelines to Use Webhooks for Change Detection](https://docs.aws.amazon.com/codepipeline/latest/userguide/pipelines-webhooks-migration.html)\. For more information, see [Start a Pipeline Execution in CodePipeline](https://docs.aws.amazon.com/codepipeline/latest/userguide/pipelines-about-starting.html)\. | May 1, 2018 | | https://github.com/siagholami/aws-documentation/tree/main/documents/aws-codepipeline-user-guide/doc_source/history.md |
f924b2f48a23-1 | | Updated topics | When you create or edit a pipeline in the console, CodePipeline now creates an Amazon CloudWatch Events rule and an AWS CloudTrail trail that detects changes to your Amazon S3 source bucket and then starts your pipeline\. For information about migrating your pipeline, see [ Change detection methods to start pipelines](pipelines-about-starting.md#change-detection-methods)\. The [Tutorial: Create a simple pipeline \(S3 bucket\)](tutorials-simple-s3.md) has been updated to show how the Amazon CloudWatch Events rule and trail are created when you select an Amazon S3 source\. [Create a pipeline in CodePipeline](pipelines-create.md) and [Edit a pipeline in CodePipeline](pipelines-edit.md) have also been updated\. For more information, see [Start a pipeline execution in CodePipeline](pipelines-about-starting.md)\. | March 22, 2018 |
| Updated topic | CodePipeline is now available in Europe \(Paris\)\. The [Quotas in AWS CodePipeline](limits.md) topic has been updated\. | February 21, 2018 | | https://github.com/siagholami/aws-documentation/tree/main/documents/aws-codepipeline-user-guide/doc_source/history.md |
f924b2f48a23-2 | | Updated topics | You can now use CodePipeline and Amazon ECS for continuous deployment of container\-based applications\. When you create a pipeline, you can select Amazon ECS as a deployment provider\. A change to code in your source control repository triggers your pipeline to build a new Docker image, push it to your container registry, and then deploy the updated image to an Amazon ECS service\. The topics [Product and service integrations with CodePipeline](integrations.md), [Create a pipeline in CodePipeline](pipelines-create.md), and [CodePipeline pipeline structure reference](reference-pipeline-structure.md) have been updated to reflect this support for Amazon ECS\. | December 12, 2017 |
| Updated topics | When you create or edit a pipeline in the console, CodePipeline now creates an Amazon CloudWatch Events rule that detects changes to your CodeCommit repository and then automatically starts your pipeline\. For information about migrating your existing pipeline, see [ Change detection methods to start pipelines](pipelines-about-starting.md#change-detection-methods)\. The [Tutorial: Create a simple pipeline \(CodeCommit repository\)](tutorials-simple-codecommit.md) has been updated to show how the Amazon CloudWatch Events rule and role are created when you select a CodeCommit repository and branch\. [Create a pipeline in CodePipeline](pipelines-create.md) and [Edit a pipeline in CodePipeline](pipelines-edit.md) have also been updated\. For more information, see [Start a pipeline execution in CodePipeline](pipelines-about-starting.md)\. | October 11, 2017 | | https://github.com/siagholami/aws-documentation/tree/main/documents/aws-codepipeline-user-guide/doc_source/history.md |
f924b2f48a23-3 | | New and updated topics | CodePipeline now provides built\-in support for pipeline state change notifications through Amazon CloudWatch Events and Amazon Simple Notification Service \(Amazon SNS\)\. A new tutorial [Tutorial: Set up a CloudWatch Events rule to receive email notifications for pipeline state changes](tutorials-cloudwatch-sns-notifications.md) has been added\. For more information, see [Detect and react to changes in pipeline state with Amazon CloudWatch Events](detect-state-changes-cloudwatch-events.md)\. | September 8, 2017 |
| New and updated topics | You can now add CodePipeline as a target for Amazon CloudWatch Events actions\. Amazon CloudWatch Events rules can be set up to detect source changes so that the pipeline starts as soon as those changes occur, or they can be set up to run scheduled pipeline executions\. Information has been added for the PollForSourceChanges source action configuration option\. For more information, see [Start a pipeline execution in CodePipeline](pipelines-about-starting.md)\. | September 5, 2017 |
| New Regions | CodePipeline is now available in Asia Pacific \(Seoul\) and Asia Pacific \(Mumbai\)\. The [Quotas in AWS CodePipeline](limits.md) topic and [Regions and Endpoints](https://docs.aws.amazon.com/general/latest/gr/rande.html#codepipeline_region) topic have been updated\. | July 27, 2017 | | https://github.com/siagholami/aws-documentation/tree/main/documents/aws-codepipeline-user-guide/doc_source/history.md |
f924b2f48a23-4 | | New Regions | CodePipeline is now available in US West \(N\. California\), Canada \(Central\), and Europe \(London\)\. The [Quotas in AWS CodePipeline](limits.md) topic and [Regions and Endpoints](https://docs.aws.amazon.com/general/latest/gr/rande.html#codepipeline_region) topic have been updated\. | June 29, 2017 |
| Updated topics | You can now view details about past executions of a pipeline, not just the most recent execution\. These details include start and end times, duration, and execution ID\. Details are available for a maximum of 100 pipeline executions during the most recent 12\-month period\. The topics [View pipeline details and history in CodePipeline](pipelines-view.md), [CodePipeline permissions reference](permissions-reference.md), and [Quotas in AWS CodePipeline](limits.md) have been updated to reflect this support\. | June 22, 2017 |
| Updated topic | [Nouvola](http://www.nouvola.com/aws-codepipeline-plugin/) has been added to the list of available actions in [Test action integrations](integrations-action-type.md#integrations-test)\. | May 18, 2017 |
| Updated topics | In the AWS CodePipeline wizard, the page Step 4: Beta has been renamed Step 4: Deploy\. The default name of the stage created by this step has been changed from "Beta" to "Staging"\. Numerous topics and screenshots have been updated to reflect these changes\. | April 7, 2017 | | https://github.com/siagholami/aws-documentation/tree/main/documents/aws-codepipeline-user-guide/doc_source/history.md |
f924b2f48a23-5 | | Updated topics | You can now add AWS CodeBuild as a test action to any stage of a pipeline\. This allows you to more easily use AWS CodeBuild to run unit tests against your code\. Prior to this release, you could use AWS CodeBuild to run unit tests only as part of a build action\. A build action requires a build output artifact, which unit tests typically do not produce\. The topics [Product and service integrations with CodePipeline](integrations.md), [Edit a pipeline in CodePipeline](pipelines-edit.md), and [CodePipeline pipeline structure reference](reference-pipeline-structure.md) have been updated to reflect this support for AWS CodeBuild\. | March 8, 2017 |
| New and updated topics | The table of contents has been reorganized to include sections for pipelines, actions, and stage transitions\. A new section has been added for CodePipeline tutorials\. For better usability, [Product and service integrations with CodePipeline](integrations.md) has been divided into shorter topics\. A new section, Authorization and Access Control, provides comprehensive information about using [AWS Identity and Access Management \(IAM\)](https://docs.aws.amazon.com/IAM/latest/UserGuide/introduction.html) and CodePipeline to help secure access to your resources through the use of credentials\. These credentials provide the permissions required to access AWS resources, such as putting and retrieving artifacts from Amazon S3 buckets and integrating AWS OpsWorks stacks into your pipelines\. | February 8, 2017 | | https://github.com/siagholami/aws-documentation/tree/main/documents/aws-codepipeline-user-guide/doc_source/history.md |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.