Manual Approval Actions
What you'll learn: How to add manual approval steps in AWS CodePipeline to pause deployments for human review before proceeding.
Understanding Manual Approval Gates
Manual approval actions are checkpoints in your AWS CodePipeline that pause execution until a human approves or rejects the next step. Think of them as a "pause button" that requires someone to review and confirm before continuing—like a quality inspector signing off before a product moves to the next assembly line stage.
This is crucial when you want human oversight before critical operations like production deployments, infrastructure changes, or releasing new features to customers.
When to Use Manual Approvals
You typically insert manual approval actions between stages where risk increases:
- Before Production Deployment: Review test results and staging performance before releasing to live users
- After Build, Before Deploy: Verify build artifacts meet quality standards
- Between Environments: Control promotion from staging to production
- Before Infrastructure Changes: Review planned changes to critical resources
How Manual Approvals Work
When CodePipeline reaches a manual approval action, it:
- Pauses execution at that point in the pipeline
- Sends notifications (via SNS topic) to designated reviewers
- Waits indefinitely or until an optional timeout expires
- Proceeds or stops based on the reviewer's decision (approve/reject)
Reviewers can add comments when approving or rejecting, creating an audit trail of why certain decisions were made.
Key Configuration Elements
Manual approval actions require:
- SNS topic for notifications to reviewers
- IAM permissions allowing designated users to approve/reject
- Optional custom data to provide context to reviewers
- Optional timeout to automatically reject after a period
Key Takeaway: Manual approval actions provide human control gates in automated pipelines, enabling review and sign-off before proceeding to high-risk stages like production deployment.