Elastic Beanstalk

Question 1

How is Elastic Beanstalk All at once deployment option?

Answer 1

All at once
- The quickest deployment method.
- Suitable if you can accept a short loss of service, and if quick deployments are important to you.
- Elastic Beanstalk deploys the new application version to each instance. Then, the web proxy or application server might need to restart.
- Your application might be unavailable to users (or have low availability) for a short time.

Question 1

How is Elastic Beanstalk Rolling deployment option?

Answer 1

Rolling
- Avoids downtime and minimizes reduced availability, at a cost of a longer deployment time.
- Suitable if you can’t accept any period of completely lost service.
- Your application is deployed to your environment one batch of instances at a time.
- Most bandwidth is retained throughout the deployment.

Question 2

How is Elastic Beanstalk Rolling with additional batch deployment option?

Answer 2

Rolling with additional batch
- Avoids any reduced availability, at a cost of an even longer deployment time compared to the Rolling method.
- Suitable if you must maintain the same bandwidth throughout the deployment.
- Elastic Beanstalk launches an extra batch of instances, then performs a rolling deployment.
- Launching the extra batch takes time, and ensures that the same bandwidth is retained throughout the deployment.

Question 3

How is Elastic Beanstalk Immutable deployment option?

Answer 3

Immutable
- A slower deployment method
- Ensures your new application version is always deployed to new instances, instead of updating existing instances.
- It also has the additional advantage of a quick and safe rollback in case the deployment fails.
- In an immutable update, a second Auto Scaling group is launched in your environment and the new version serves traffic alongside the old version until the new instances pass health checks.

Question 4

How is Elastic Beanstalk Traffic splitting deployment option?

Answer 4

Traffic splitting
- A canary testing deployment method.
- Suitable if you want to test the health of your new application version using a portion of incoming traffic, while keeping the rest of the traffic served by the old application version.

Question 5

How is Elastic Beanstalk Blue Green deployment option?

Answer 5

Blue Green
- Required if you want to update an environment to an incompatible platform version.
- Deploy the new version to a separate environment, and then swap the CNAMEs of the two environments to redirect traffic to the new version instantly.
- Elastic Beanstalk swaps the CNAME records of the old and new environments, redirecting traffic from the old version to the new version.