A developer is planning to update a non-critical internal application deployed on AWS Elastic Beanstalk. The update will be performed during off-peak hours over the weekend. To stay within budget, the deployment must not provision any additional EC2 instances. The company accepts that the application will be temporarily offline during the deployment process.
Which deployment strategy meets these requirements?
- ARolling with additional batch
- BImmutable
- All at onceAnswer
- DTraffic splitting
Answer
All at once
The 'All at once' strategy is the only Elastic Beanstalk deployment policy that does not provision any additional EC2 instances during the update. It applies the deployment package to all existing instances at the same time. While this causes a short period of downtime (unavailability) during which the application is offline, this aligns with the company's acceptance of weekend downtime and satisfies the strict budget constraint of zero additional instances.
Step-by-Step Solution
Key Concept
AWS Elastic Beanstalk deployment strategy tradeoffs regarding cost and capacity.
Estimated Time:45s