Valid action providers in CodePipeline - AWS CodePipeline

Valid action providers in CodePipeline

The pipeline structure format is used to build actions and stages in a pipeline. An action type consists of an action category and provider type.

Each action category has a valid list of action providers. To reference the valid action providers for each action category, see the Action structure reference.

Each action category has a designated set of providers. Each action provider, such as Amazon S3, has a provider name, such as S3, that must be used in the Provider field in the action category in your pipeline structure.

There are three valid values for the Owner field in the action category section in your pipeline structure: AWS, ThirdParty, and Custom.

To find the provider name and owner information for your action provider, see the Action structure reference or Valid input and output artifacts for each action type.

This table lists valid providers by action type.

Note

For Bitbucket, GitHub, or GitHub Enterprise Server actions, refer to the CodeStarSourceConnection for Bitbucket Cloud, GitHub, GitHub Enterprise Server, GitLab.com, and GitLab self-managed actions action reference topic.

Valid action providers by action type
Action category Valid action providers Action reference
Source Amazon S3 Amazon S3 source action reference
Amazon ECR Amazon ECR source action reference
CodeCommit CodeCommit source action reference
CodeStarSourceConnection (for Bitbucket, GitHub, GitHub Enterprise Server actions) CodeStarSourceConnection for Bitbucket Cloud, GitHub, GitHub Enterprise Server, GitLab.com, and GitLab self-managed actions
Build CodeBuild AWS CodeBuild build and test action reference
Custom CloudBees Valid input and output artifacts for each action type
Custom Jenkins Valid input and output artifacts for each action type
Custom TeamCity Valid input and output artifacts for each action type
ECRBuildAndPublish ECRBuildAndPublish build action reference
Test CodeBuild AWS CodeBuild build and test action reference
AWS Device Farm Valid input and output artifacts for each action type
Custom BlazeMeter Valid input and output artifacts for each action type
ThirdParty GhostInspector Valid input and output artifacts for each action type
Custom Jenkins Valid input and output artifacts for each action type
ThirdParty Micro Focus StormRunner Load Valid input and output artifacts for each action type
ThirdParty Nouvola Valid input and output artifacts for each action type
ThirdParty Runscope Valid input and output artifacts for each action type
Deploy Amazon S3 Amazon S3 deploy action reference
AWS CloudFormation AWS CloudFormation deploy action reference
CodeDeploy Valid input and output artifacts for each action type
Amazon ECS Valid input and output artifacts for each action type
Amazon ECS (Blue/Green) (this is the CodeDeployToECS action) Valid input and output artifacts for each action type
Elastic Beanstalk Valid input and output artifacts for each action type
AWS AppConfig AWS AppConfig deploy action reference
AWS OpsWorks Valid input and output artifacts for each action type
Service Catalog Valid input and output artifacts for each action type
Amazon Alexa Valid input and output artifacts for each action type
Custom XebiaLabs Valid input and output artifacts for each action type
Approval Manual Valid input and output artifacts for each action type
Invoke AWS Lambda AWS Lambda invoke action reference
AWS Step Functions AWS Step Functions invoke action reference
InspectorScan Amazon Inspector InspectorScan invoke action reference
Compute Commands action Commands action reference

Some action types in CodePipeline are available in select AWS Regions only. It is possible that an action type is available in an AWS Region, but an AWS provider for that action type is not available.

For more information about each action provider, see Integrations with CodePipeline action types.