cloud —

How Amazon ECS handles blue/green, canary, and linear deployments

Deploying containers safely at scale can mean assembling your own system: traffic-splitting logic, alarm evaluation, rollback automation, approval gates.

How Amazon ECS handles blue/green, canary, and linear deployments

It’s infrastructure that exists solely to protect the deployment itself. AWS has built all of those capabilities directly into Amazon Elastic Container Service (ECS), so you don’t have to.

“Deploying containers safely at scale can mean assembling your own system: traffic-splitting logic, alarm evaluation, rollback automation, approval gates. It’s infrastructure that exists solely to protect the deployment itself.”

You can access all these tools through a single API endpoint. AWS built them to work out of the box when you use Amazon ECS as your container orchestration platform with the Amazon ECS deployment controller.

As a result, you don’t have to build your own abstractions or learn a new framework to get the deployment behavior you want. Instead, you pick and choose the features you want through a service deployment configuration and update it as your needs change. How the building blocks map to ECS If you’ve run progressive delivery on Kubernetes with Argo Rollouts or Flagger, you know the shape of the stack: a controller you install and keep current, analysis wired to your metrics backend, and a traffic provider for weighted canaries.

Earlier coverage

Reported by thenewstack.io.

cloud

Related coverage

Elsewhere in this edition