Course contentsShow
← Cloud and Infrastructure
Lesson 1841 of 2,98938. AWS Native CI/CDFree lesson

Pipeline Actions and Action Types

Understanding action types, action providers, and how actions execute within pipeline stages.

Pipeline Actions and Action Types

What you'll learn: How CodePipeline executes work through actions, what action types exist, and how they fit into your pipeline stages.

What Are Pipeline Actions?

Think of a pipeline stage as a workstation on an assembly line. Actions are the actual tasks performed at that workstation—the specific operations that transform or move your code. Each stage contains one or more actions, and these actions are the "verbs" of your pipeline: pulling code, building artifacts, deploying applications, or testing functionality.

Action Types and Providers

AWS CodePipeline supports several action types, each representing a category of work:

  • Source: Retrieve code from repositories (CodeCommit, GitHub, S3)
  • Build: Compile and package code (CodeBuild, Jenkins)
  • Test: Run automated tests (CodeBuild, third-party tools)
  • Deploy: Release to environments (CodeDeploy, ECS, S3, CloudFormation)
  • Approval: Manual gate requiring human confirmation
  • Invoke: Trigger Lambda functions for custom logic

Each action type has multiple action providers—the specific service or tool performing the work. For example, the "Deploy" action type might use CodeDeploy as its provider, while another deploy action uses ECS.

How Actions Execute

Actions within a single stage can run serially (one after another) or in parallel (simultaneously). When multiple actions exist in a stage without dependencies, CodePipeline runs them concurrently to speed up your pipeline. Each action receives input artifacts (from previous stages) and produces output artifacts (for downstream stages).

Actions are atomic units: they either succeed completely or fail, triggering pipeline halt and optional notifications.

Key Takeaway: Pipeline actions are the executable tasks within stages, categorized by action types (Source, Build, Deploy, etc.) and powered by specific action providers—understanding this structure lets you orchestrate complex workflows efficiently.