Amazon ECS enables built-in blue/green deployments

Amazon Elastic Container Service (Amazon ECS) announces new features that make software updates for your containerized applications safer, allowing you to ship software faster and with high confidence, without needing to build custom deployment tooling. Amazon ECS now supports a built-in blue/green deployment strategy and deployment lifecycle hooks that allow you to test new application versions in production environments and quickly rollback failed deployments.

You can now deploy software updates to Amazon ECS services which serve traffic from an Application Load Balancer (ALB), Network Load Balancer (NLB), or ECS Service Connect with a blue/green deployment strategy. When you use a blue/green deployment strategy, Amazon ECS provisions the new application version alongside the old, and allows you to validate the new application version before routing production traffic to it. You can use deployment lifecycle hooks to perform custom validation steps, and block the deployment until validation succeeds. Furthermore, once production traffic has been shifted, you can let the new application bake for a pre-specified period, and rollback to the old version without incurring downtime if you detect a regression. To detect failures automatically, you can configure Amazon CloudWatch Alarms and ECS deployment circuit breaker to monitor your deployments. Together, these capabilities help make your software updates safer, allowing you to ship new capabilities faster.

You can use blue/green deployments and deployment lifecycle hooks for new and existing Amazon ECS services in all commercial AWS Regions using the AWS Management Console, SDK, CLI, CloudFormation, CDK, and Terraform by following the steps on the blog. For more details, see our documentation.

Categories:

Source: Amazon Web Services

Latest Posts