This is last part of a three part series.
In this part we will go through the concepts of ECS Rolling Update Deployment.
First off, why I prefer to use Rolling Update Deployment over Blue Green Deployment:
Over the past few months AWS has been adding a lots of improvements in Rolling Update Deployment.
1) Capacity Providers: This would be the most important feature of Rolling Update Deployments. With this I can leave the scaling and instance termination worries with ECS and focus on my actual deployments.
ECS Cluster Auto Scaling (CAS) uses something called Capacity…
This is the second part of a three part series.
In ECS we mainly get two types of deployment options:
— Blue/Green Deployments
— Rolling update Deployments
Differences between these deployments and which one to choose specially with ECS:
— Blue/Green requires double of the running resources in deployment phase, while in rolling update this behaviour can be adjusted.
— ECS Blue/Green Deployment integrated with AWS CodeDeploy to run the deployment which makes it easier to visualise during the deployment, Rolling Update doesn’t integrate with CodeDeploy. …
A well oiled strategy on handling autoscaling, deployments and deployment failures is must for a successful Continuous Deployment phase of a CICD setup.
This is a three part series which explains how one should go about autoscaling and deployments in AWS ECS.
Note: Throughout the entire series, we will be discussing ECS(EC2) and not ECS Fargate, so when I say ECS please read it ECS(EC2).
The series is divided in below three parts:
I. Autoscaling in AWS ECS.
II. ECS Blue/Green Deployment.
III. ECS Rolling Update deployment.
This blog is first part of this…
Cloud & DevOps Enthusiast