Integrations with CodePipeline action types

The integrations information in this topic is organized by CodePipeline action type.

Source action integrations

The following information is organized by CodePipeline action type and can help you configure CodePipeline to integrate with the products and services you use.

Amazon Simple Storage Service (Amazon S3)	Amazon S3 is storage for the internet. You can use Amazon S3 to store and retrieve any amount of data at any time, from anywhere on the web. You can configure CodePipeline to use a versioned Amazon S3 bucket as the source stage for your code. Create the bucket and enable versioning on it. Then you can create a pipeline that uses the bucket as part of a source action in a stage. Note Amazon S3 can also be included in a pipeline as a deploy action. Learn more: For action parameters and definitions, see the action structure reference page for Amazon S3. Step 1: Create an S3 bucket for your application Create a pipeline (CLI) CodePipeline uses Amazon CloudWatch Events to detect changes in your Amazon S3 source bucket. Each source action has a corresponding event rule. This event rule starts your pipeline when a change occurs in the source. See General integrations with CodePipeline.
AWS CodeCommit	CodeCommit is a version control service that you can use to privately store and manage assets (such as documents, source code, and binary files) in the cloud. You can configure CodePipeline to use a branch in a CodeCommit repository as the source stage for your code. Create the repository and associate it with a working directory on your local machine. Then you can create a pipeline that uses the branch as part of a source action in a stage. You can connect to the CodeCommit repository by either creating a pipeline or editing an existing one. Learn more: For action parameters and definitions, see the action structure reference page for CodeCommit. Tutorial: Create a simple pipeline (CodeCommit repository) CodePipeline uses Amazon CloudWatch Events to detect changes in CodeCommit repositories used as a source for a pipeline. Each source action has a corresponding event rule. This event rule starts your pipeline when a change occurs in the repository. See General integrations with CodePipeline.
GitHub	You can configure CodePipeline to use a GitHub repository as the source stage for your code. You must have previously created a GitHub account and at least one GitHub repository. You can connect to the GitHub repository by either creating a pipeline or editing an existing one. Note CodePipeline integration with GitHub Enterprise is not supported. For action parameters and definitions, see the action structure reference page for GitHub. The first time you add a GitHub repository to a pipeline, you are prompted to authorize CodePipeline access to your repositories. To integrate with GitHub, CodePipeline creates an OAuth application for your pipeline. If you create or edit your pipeline in the console, CodePipeline creates a GitHub webhook that starts your pipeline when a change occurs in the repository. The token and webhook require the following GitHub scopes: The repo scope, which is used for full control to read and pull artifacts from public and private repositories into a pipeline. The admin:repo_hook scope, which is used for full control of repository hooks. For more information about GitHub scopes, see the GitHub Developer API Reference. Access for CodePipeline is configured for all repositories to which that GitHub account has access. It cannot currently be configured for individual repositories. To revoke this access from GitHub, choose Settings, and then choose Applications. Under Authorized applications, find CodePipeline in the list of authorized applications, and then choose Revoke. Revoking access immediately prevents CodePipeline from accessing any GitHub repositories previously configured for access with that GitHub account. If you want to limit the access CodePipeline has to repositories, create a GitHub account, grant that account access only to those repositories you want to integrate with CodePipeline, and then use that account when you configure CodePipeline to use GitHub repositories for source stages in pipelines. Learn more: For action parameters and definitions, see the action structure reference page for GitHub. Tutorial: Create a four-stage pipeline Use webhooks to start a pipeline (GitHub source)
Amazon ECR	Amazon ECR is an AWS Docker image repository service. You use Docker push and pull commands to upload Docker images to your repository. An Amazon ECR repository URI and image are used in Amazon ECS task definitions to reference source image information. Learn more: For action parameters and definitions, see the action structure reference page for Amazon ECR. Create a pipeline in CodePipeline Tutorial: Create a pipeline with an Amazon ECR source and ECS-to-CodeDeploy deployment
AWS CodeStar Connections (Connections to Bitbucket)	You can set up resources called connections to allow your pipelines to access third-party code repositories like Bitbucket. When you create a connection, you install the AWS CodeStar app with your third-party code repository, and then associate it with your connection. Learn more: For action parameters and definitions, see the action structure reference page for CodeStarSourceConnection. Create a Connection Create a connection to Bitbucket

Build action integrations

AWS CodeBuild	CodeBuild is a fully managed build service that compiles your source code, runs unit tests, and produces artifacts that are ready to deploy. You can add CodeBuild as a build action to the build stage of a pipeline. Note CodeBuild can also be included in a pipeline as a test action, with or without a build output. Learn more: For action parameters and definitions, see the action structure reference page for AWS CodeBuild. What Is CodeBuild? CodeBuild – Fully Managed Build Service
CloudBees	You can configure CodePipeline to use CloudBees to build or test your code in one or more actions in a pipeline. Learn more: Cloud First with AWS
Jenkins	You can configure CodePipeline to use Jenkins CI to build or test your code in one or more actions in a pipeline. You must have previously created a Jenkins project and installed and configured the CodePipeline Plugin for Jenkins for that project. You can connect to the Jenkins project by either creating a new pipeline or editing an existing one. Access for Jenkins is configured on a per-project basis. You must install the CodePipeline Plugin for Jenkins on every Jenkins instance you want to use with CodePipeline. You must also configure CodePipeline access to the Jenkins project. Secure your Jenkins project by configuring it to accept HTTPS/SSL connections only. If your Jenkins project is installed on an Amazon EC2 instance, consider providing your AWS credentials by installing the AWS CLI on each instance. Then configure an AWS profile on those instances with the IAM user profile and AWS credentials you want to use for connections. This is an alternative to adding and storing them through the Jenkins web interface. Learn more: Accessing Jenkins Tutorial: Create a four-stage pipeline
TeamCity	You can configure CodePipeline to use TeamCity to build and test your code in one or more actions in a pipeline. Learn more: TeamCity Plugin for CodePipeline Building End-to-End Continuous Delivery and Deployment Pipelines in AWS and TeamCity

Test action integrations

AWS CodeBuild	CodeBuild is a fully managed build service in the cloud. CodeBuild compiles your source code, runs unit tests, and produces artifacts that are ready to deploy. You can add CodeBuild to a pipeline as a test action. For more information, see the CodePipeline Action Configuration Reference for AWS CodeBuild. Note CodeBuild can also be included in a pipeline as a build action, with a mandatory build output artifact. Learn more: For action parameters and definitions, see the action structure reference page for AWS CodeBuild. What Is CodeBuild?
AWS Device Farm	AWS Device Farm is an app testing service that you can use to test and interact with your Android, iOS, and web applications on real, physical phones and tablets. You can configure CodePipeline to use AWS Device Farm to test your code in one or more actions in a pipeline. AWS Device Farm allows you to upload your own tests or use built-in, script-free compatibility tests. Because testing is performed in parallel, tests on multiple devices begin in minutes. A test report that contains high-level results, low-level logs, pixel-to-pixel screenshots, and performance data is updated as tests are completed. AWS Device Farm supports testing of native and hybrid Android, iOS, and Fire OS apps, including those created with PhoneGap, Titanium, Xamarin, Unity, and other frameworks. It supports remote access of Android apps, which allows you to interact directly with test devices. Learn more: For action parameters and definitions, see the action structure reference page for AWS Device Farm. What Is AWS Device Farm? Using AWS Device Farm in a CodePipeline Test Stage
BlazeMeter	You can configure CodePipeline to use BlazeMeter to test your code in one or more actions in a pipeline. Learn more: BlazeMeter documentation for testing with CodePipeline
Ghost Inspector	You can configure CodePipeline to use Ghost Inspector to test your code in one or more actions in a pipeline. Learn more: Ghost Inspector documentation for service integration with CodePipeline
Micro Focus StormRunner Load	You can configure CodePipeline to use Micro Focus StormRunner Load in one or more actions in a pipeline. Learn more: Micro Focus StormRunner Load documentation for integrating with CodePipeline
Nouvola	You can configure CodePipeline to use Nouvola to test your code in one or more actions in a pipeline. Learn more: Nouvola Plugin for CodePipeline
Runscope	You can configure CodePipeline to use Runscope to test your code in one or more actions in a pipeline. Learn more: Runscope documentation for integrating with CodePipeline

Deploy action integrations

Amazon Simple Storage Service (Amazon S3)	Amazon S3 is storage for the internet. You can use Amazon S3 to store and retrieve any amount of data at any time, from anywhere on the web. You can add an action to a pipeline that uses Amazon S3 as a deployment provider. Note Amazon S3 can also be included in a pipeline as a source action. Learn more: Create a pipeline in CodePipeline Tutorial: Create a pipeline that uses Amazon S3 as a deployment provider
AWS AppConfig	AWS AppConfig is a capability of AWS Systems Manager to create, manage, and quickly deploy application configurations. You can use AppConfig with applications hosted on EC2 instances, AWS Lambda, containers, mobile applications, or IoT devices. Learn more: CodePipeline Action Configuration Reference for AWS AppConfig Tutorial: Create a pipeline that uses AWS AppConfig as a deployment provider
AWS CloudFormation	AWS CloudFormation gives developers and systems administrators an easy way to create and manage a collection of related AWS resources, using templates to provision and update those resources. You can use the service’s sample templates or create your own. Templates describe the AWS resources and any dependencies or runtime parameters required to run your application. The AWS Serverless Application Model (AWS SAM) extends AWS CloudFormation to provide a simplified way to define and deploy serverless applications. AWS SAM supports Amazon API Gateway APIs, AWS Lambda functions, and Amazon DynamoDB tables. You can use CodePipeline with AWS CloudFormation and the AWS SAM to continuously deliver your serverless applications. You can add an action to a pipeline that uses AWS CloudFormation as a deployment provider. When you use AWS CloudFormation as a deployment provider, you can take action on AWS CloudFormation stacks and change sets as part of a pipeline execution. AWS CloudFormation can create, update, replace, and delete stacks and change sets when a pipeline runs. As a result, AWS and custom resources can be created, provisioned, updated, or terminated during a pipeline execution according to the specifications you provide in AWS CloudFormation templates and parameter definitions. Learn more: CodePipeline Action Configuration Reference for AWS CloudFormation Continuous Delivery with CodePipeline — Learn how to use CodePipeline to build a continuous delivery workflow for AWS CloudFormation. Automating Deployment of Lambda-based Applications — Learn how to use the AWS Serverless Application Model and AWS CloudFormation to build a continuous delivery workflow for your Lambda-based application.
AWS CodeDeploy	CodeDeploy coordinates application deployments to Amazon EC2 instances, on-premises instances, or both. You can configure CodePipeline to use CodeDeploy to deploy your code. You can create the CodeDeploy application, deployment, and deployment group to use in a deploy action in a stage either before you create the pipeline or when you use the Create Pipeline wizard. Learn more: For action parameters and definitions, see the action structure reference page for AWS CodeDeploy. Step 3: Create an application in CodeDeploy Tutorial: Create a simple pipeline (CodeCommit repository)
Amazon Elastic Container Service	Amazon ECS is a highly scalable, high performance container management service that allows you to run container-based applications in the AWS Cloud. 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 Amazon ECS. You can also use the ECS (Blue/Green) provider action in CodePipeline to route and deploy blue/green deployments to Amazon ECS with CodeDeploy. Learn more: For action parameters and definitions for Amazon ECS standard deployments, see the action structure reference page for Amazon Elastic Container Service. For action parameters and definitions for Amazon ECS and CodeDeploy blue/green deployments, see the action structure reference page for Amazon Elastic Container Service and CodeDeploy Blue-Green. What Is Amazon ECS? Tutorial: Continuous Deployment with CodePipeline Create a pipeline in CodePipeline Tutorial: Create a pipeline with an Amazon ECR source and ECS-to-CodeDeploy deployment
AWS Elastic Beanstalk	Elastic Beanstalk is a service for deploying and scaling web applications and services developed with Java, .NET, PHP, Node.js, Python, Ruby, Go, and Docker on familiar servers such as Apache, Nginx, Passenger, and IIS. You can configure CodePipeline to use Elastic Beanstalk to deploy your code. You can create the Elastic Beanstalk application and environment to use in a deploy action in a stage either before you create the pipeline or when you use the Create Pipeline wizard. Learn more: Getting started using Elastic Beanstalk Create a pipeline in CodePipeline
AWS OpsWorks Stacks	AWS OpsWorks is a configuration management service that helps you configure and operate applications of all shapes and sizes using Chef. Using AWS OpsWorks Stacks, you can define the application’s architecture and the specification of each component including package installation, software configuration and resources such as storage. You can configure CodePipeline to use AWS OpsWorks Stacks to deploy your code in conjunction with custom Chef cookbooks and applications in AWS OpsWorks. Custom Chef Cookbooks – AWS OpsWorks uses Chef Cookbooks to handle tasks such as installing and configuring packages and deploying applications. Applications – An AWS OpsWorks applications consists of code that you want to run on an application server. The application code is stored in a repository, such as an Amazon S3 bucket. Before you create the pipeline, you create the AWS OpsWorks stack and layer. You can create the AWS OpsWorks application to use in a deploy action in a stage either before you create the pipeline or when you use the Create Pipeline wizard. CodePipeline support for AWS OpsWorks is currently available in the US East (N. Virginia) Region (us-east-1) only. Learn more: Using CodePipeline with AWS OpsWorks Stacks Cookbooks and Recipes AWS OpsWorks Apps
AWS Service Catalog	AWS Service Catalog enables organizations to create and manage catalogs of products that are approved for use on AWS. You can configure CodePipeline to deploy updates and versions of your product templates to AWS Service Catalog. You can create the AWS Service Catalog product to use in a deployment action and then use the Create Pipeline wizard to create the pipeline. Learn more: Tutorial: Create a pipeline that deploys to AWS Service Catalog Create a pipeline in CodePipeline
Alexa Skills Kit	Amazon Alexa Skills Kit lets you build and distribute cloud-based skills to users of Alexa-enabled devices. You can add an action to a pipeline that uses Alexa Skills Kit as a deployment provider. Source changes are detected by your pipeline, and then your pipeline deploys updates to your Alexa skill in the Alexa service. Learn more: Tutorial: Create a pipeline that deploys an Amazon Alexa skill
XebiaLabs	You can configure CodePipeline to use XebiaLabs to deploy your code in one or more actions in a pipeline. Learn more: XebiaLabs documentation for using XL Deploy with CodePipeline

Approval action integrations

Amazon Simple Notification Service

Amazon SNS is a fast, flexible, fully managed push notification service that lets you send individual messages or to fan out messages to large numbers of recipients. Amazon SNS makes it simple and cost effective to send push notifications to mobile device users, email recipients or even send messages to other distributed services. When you create a manual approval request in CodePipeline, you can optionally publish to a topic in Amazon SNS so that all IAM users subscribed to it are notified that the approval action is ready to be reviewed. Learn more: What Is Amazon SNS? Grant Amazon SNS permissions to a CodePipeline service role

Invoke action integrations

AWS Lambda

Lambda lets you run code without provisioning or managing servers. You can configure CodePipeline to use Lambda functions to add flexibility and functionality to your pipelines. You can create the Lambda function to add as an action in a stage either before you create the pipeline or when you use the Create Pipeline wizard. Learn more: CodePipeline Action Configuration Reference for AWS Lambda Invoke an AWS Lambda function in a pipeline in CodePipeline

AWS Step Functions

Step Functions lets you create and configure state machines. You can configure CodePipeline to use Step Functions invoke actions to trigger state machine executions. Learn more: CodePipeline Action Configuration Reference for AWS Step Functions Tutorial: Use an AWS Step Functions invoke action in a pipeline