"Blue/green deployments on Amazon Elastic Container Service (Amazon ECS) have long been a go-to pattern for shipping zero-downtime deployments. Historically, the recommended approach in the AWS Cloud Development Kit (AWS CDK) was to wire ECS to AWS CodeDeploy for traffic shifting, lifecycle hooks, and tight integration with AWS CodePipeline. In July 2025, Amazon ECS launched built-in blue/green deployments. This allows you to operate directly within the ECS service, without requiring the use of Amazon CodeDeploy."
"The ECS service team saw an opportunity to simplify the deployment process by creating lifecycle hooks, bake time, and managed rollback directly within ECS. With this shift, the complexity of coordinating blue/green deployments through CodeDeploy is consolidated into a single service. This consolidation not only simplifies the deployment pipeline but also reduces the number of moving parts, making it easier to maintain and troubleshoot over time."
Amazon ECS launched built-in blue/green deployments in July 2025, enabling traffic shifting, lifecycle hooks, bake time, and managed rollback within ECS. The ECS-native model provisions a replacement task set registered to a separate target group behind the Elastic Load Balancing listener. When cutover is approved, ECS performs an all-at-once traffic shift to the new revision, then holds both revisions during a configurable bake period before retiring the old revision or rolling back if alarms or hooks fail. The native approach consolidates deployment complexity into a single service, reducing moving parts compared to using CodeDeploy. The change simplifies pipelines and eases maintenance and troubleshooting.
Read at Amazon Web Services
Unable to calculate read time
Collection
[
|
...
]