- Newest
- Most votes
- Most comments
There could be a few reasons why the rollback option is not working for your blue-green deployment with CodeDeploy:
The deployment configuration may not be set up correctly for rollback. Ensure the deployment configuration specifies a rollback trigger and rollback mechanism.
There could be issues with the validation test for the deployment. If the validation test fails or times out, CodeDeploy will not trigger the rollback. Check the validation test is properly configured and completes successfully within the timeout period.
Permissions or IAM roles used by CodeDeploy may be missing the required permissions for rollback actions. Confirm the CodeDeploy service role has permissions for the rollback operations.
Logs from the CodeDeploy agent on the EC2 instances ( /var/log/aws/codedeploy-agent/codedeploy-agent.log ) can provide more clues on where the deployment is failing during the validation or rollback stages. Check these logs for errors.
If using Auto Scaling groups, the deployment configuration may need adjusting to ensure instances are properly deregistered and registered during rollback.
Relevant content
- asked a year ago
- Accepted Answerasked 4 months ago
- asked 9 months ago
- Accepted Answerasked a year ago
- AWS OFFICIALUpdated 10 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago