A developer is updating a critical production web application deployed on AWS Elastic Beanstalk. The deployment process must ensure zero downtime and support an immediate rollback to the previous version if the new version fails health checks. Which two Elastic Beanstalk deployment strategies or options meet these requirements?
- Blue/Green deployment using a CNAME swapAnswer
- Immutable deploymentAnswer
- CAll-at-once deployment
- DRolling deployment
- ERolling with additional batch deployment
Answer
The correct options are Blue/Green deployment using a CNAME swap and Immutable deployment.
Blue/Green deployment using a CNAME swap and Immutable deployment both satisfy the requirements. A Blue/Green deployment routes traffic to a completely separate environment, allowing an immediate rollback by swapping CNAME records back if the new version fails. An Immutable deployment deploys the new version to a temporary Auto Scaling group alongside the original one. If health checks fail, the temporary group is deleted immediately, leaving the original instances unaffected.
Step-by-Step Solution
Key Concept
AWS Elastic Beanstalk deployment strategies and their trade-offs regarding downtime, capacity, and rollback speed.