A containerized 311 intake service on ECS must cut over safely and keep the prior task set for a fast revert. Which blue/green approach fits?
Select an answer to reveal the explanation.
Short Explanation
Blue/green on ECS is two teams on the field: CodeDeploy moves the crowd to the new task set after health checks, but keeps the old roster warmed up. Instant revert beats "stop everything and hope."
Full Explanation
ECS blue/green deployments with CodeDeploy create a new task set, validate health, then shift traffic while retaining the original task set for rapid rollback. In-place replacement without a second set, unguarded full stops, or local-only Docker workflows do not provide that safer cutover pattern.