The article explains the addition of a manual approval stage to a CI/CD pipeline for Lambda and API Gateway using AWS SAM and GitHub.
The manual approval stage allows code to be built but not deployed until manual approval is given, providing governance and review.
Benefits of a manual approval stage include code reviews, risk reduction, compliance adherence, team collaboration, and support for change management processes.
Setting up an SNS topic and email subscription is necessary for notifications related to the manual approval stage.
The article details the steps to add a manual approval stage and action in the pipeline using AWS CodePipeline.
After pushing code changes to the Git repo, the pipeline triggers automatically but stops at the manual approval stage.
Approvers are notified via email and can either approve or reject the deployment directly from the email or on the approval screen.
Upon approval, the pipeline progresses through the build and deployment stages, ultimately deploying the updated function and API.
The article also mentions validating the deployed function and API using Postman and checking related resources like S3 buckets and CloudWatch logs.
Lastly, it emphasizes cleaning up resources post-exercise to avoid unnecessary charges and provides a comprehensive conclusion on enhancing CI/CD pipelines with manual approval.
Overall, the addition of a manual approval stage enhances security, governance, and controlled deployments in Lambda CI/CD pipelines.