The blue-green deployment partially shifts traffic, but the rollback condition never triggers because the health alarm watches only the stable target group.
CodeDeploy rollback alarm never fires because canary target group is missing
The blue-green deployment partially shifts traffic, but the rollback condition never triggers because the health alarm watches only the stable target group.
Scenario
What to check first
- Identify the primary failure signal in the Deployment Safety scenario.
- Separate visible symptoms from the underlying technical dependency.
- Describe the safest recovery path and the follow-up prevention work.
Checking checklist
- Summarize the current impact and the last known change.
- Collect direct evidence from logs, runtime state, and configuration before changing anything.
- Separate immediate recovery from permanent prevention work.
Recovery and prevention
Choose the smallest safe recovery action first, then record the prevention work that reduces repeat incidents.
Questions worth viewing together
Prove that the alarm is watching the exact traffic segment and target group touched by the current rollout.
Similar cases seen in the field