How can the Development team add a manual approver to the CI/CD pipeline?
Use AWS SES to send an email to approvers when their action is required. Develop a simple application that allows approvers to accept or reject a build. Invoke an AWS Lambda function to advance the pipeline when a build is accepted.
If approved, add an approved tag when pushing changes to the CodeCommit repository. CodePipeline will proceed to build and deploy approved commits without interruption.
Add an approval step to CodeCommit. Commits will not be saved until approved.
Add an approval action to the pipeline. Configure the approval action to publish to an Amazon SNS topic when approval is required. The pipeline execution will stop and wait for an approval.
Explanations:
AWS SES is not directly integrated with CodePipeline for approval workflows. Developing a custom application and using Lambda functions adds unnecessary complexity and is not a native solution for manual approval in CodePipeline.
Adding an approved tag to commits in CodeCommit will not trigger a manual approval process in CodePipeline. CodePipeline does not support conditional deployment based on commit tags without custom configurations.
CodeCommit does not support an approval step for commits. Commits can be pushed directly, and there is no built-in approval mechanism in CodeCommit itself.
CodePipeline supports adding a manual approval action directly within the pipeline. The pipeline execution stops and waits for manual approval, and can be configured to send notifications (e.g., using Amazon SNS) when approval is needed. This is the correct and native approach for adding a manual approval step.
From what I’ve heard, the answer is:
Add an approval action to the pipeline. Configure the approval action to publish to an Amazon SNS topic when approval is required. The pipeline execution will stop and wait for an approval.