Run a Controlled Deploy With AWS Elastic Beanstalk

• (4.0)

• | 1331 Ratings

Amazon Web Service (AWS) Beanstalk is an easy-to-use service for scaling and deploying web-based services and applications developed with.NET, Java, PHP, Python, Node.js, Ruby, Docker and Go on familiar servers such as Apache, Nginx, IIS, and Passenger. With AWS cloud without much worry, you can deploy and manage applications quickly and easily without complex running infrastructure.

AWS Elastic Beanstalk reduces the complexity of management without restricting control or choice. Usually, you can upload application, and AWS Elastic Beanstalk handles the details of capacity provisioning, scaling, load balancing, and for monitoring application health.
 

A unique deployment ID allocated to each deployment. IDs start at 1 and with each implementation, it increases by 1, and there exists an instant configuration change. Beanstalk from AWS displays the deployment ID in both EB CLI and the health console and reports instance health status in case you enable enhanced reporting. The deployment ID helps you to determine your environment state when a rolling update fails.

Related Page: AWS Elastic Beanstalk Available in AWS GovCloud (US)

In case you have to ensure that the application source deploys to new instances instead of updating existing cases, just configure your environment to immutable deployment updates for. In this immutable update, an additional autoscaling group that sets in this situation and this new version serves traffic alongside the traditional version until the new instances pass health checks.

AWS Beanstalk Supported Deployment Policies

Deployment Configuration

• The procedure starts with Opening the Elastic Beanstalk console
• Navigate to the management page for your environment
• Next Choose Configuration
• Choose Modify On “the Rolling updates and deployments configuration card.”
• Choose a Deployment policy and batch settings in the section “Application Deployments.”
• Choose Save, and then choose to Apply

In case of deployments that depends on configuration changes of resource, a new version that can’t run alongside the older one, you can launch a new environment using this new version and can perform a CNAME swap for a blue/green deployment.

About The Author

Prasanthi is an expert writer in MongoDB, and has written for various reputable online and print publications. At present, she is working for Mindmajix, and writes content not only on MongoDB, but also on Sharepoint, Uipath, and AWS.