Visual workflow to orchestrate CD pipelines. Pipeline can be edited when needed to add or remove stages.
Each stage in the pipeline creates an artifact which is stored in S3 (Artifact Store). The next stage uses this artifact as input.
When a developer commit a code change to source repo -> CodePipeline will auto detect the changes -> Auto build -> Deploy to staging for Testing -> (Manually approval) -> Deploy to production.
Easy to integrate with your pre-built plugins (Github, Jenkins) or custom plugins.
Features
Access control using IAM.
Receive notifications using SNS.
Concepts
Stage: is a logical unit. Each stage contains actions that are performed on the application artifacts.
Action: is a set of operations. Valid CodePipeline action types are source, build, test, deploy, approval, and invoke. The action can be run parallel or sequential.
Execution: is a set of changes released by a pipeline. Each pipeline execution is unique and has its own ID.