AWS kicks off April with new deployment policies for AWS Elastic Beanstalk and updates to Linux AMI.
New Deployment Policies
You can now select between two additional deployment policies: rolling with additional batch and immutable. Along with rolling and all at once, this brings up your policies to four.
- Immutable – you may now use this policy when updating either your application or your Elastic Beanstalk environment settings. This policy works by creating one AWS EC2 instance first and applying the update there. This ensures that should a deployment fail, its impact is limited to one instance and you can handle maximum traffic even during the update. This is best for production environments where downtime must be kept to a minimum.
- Rolling with Additional Batch – Much like immutable, this reduces the impact of failed deployments. In this case, it applies to a single batch of instances. In the meantime, you can still serve traffic at maximum capacity.
As before, Elastic Beanstalk will deploy updates to a batch of new EC2 instances. Then once they pass the health checks, updates will roll out to your other production instances in equal batches.
Note that you can only use policies at platform version 2.1.0 or newer.
Linux AMI Updates
Update 2016.03 Amazon Linux AMI has been applied to all Linux platforms on Elastic Beanstalk. In addition, the environment name now has a max of 40 characters, instead of just 23.
If you wish to know how to apply Elastic Beanstalk to your organization, feel free to contact our cloud specialists today at PolarSeven.