When first selecting "Deployment policy" in the Beanstalk console, five options appear equivalent: All at once, Rolling, Rolling with additional batch, Immutable, Blue-Green. The names sound similar, yet they determine whether you experience five minutes of downtime, whether your 30-minute deployment costs twice as much, and whether a single alarm instantly triggers rollback.
This article begins with why Beanstalk as a PaaS intentionally creates EC2/ALB/ASG inside customer accounts, then examines the five policies across four trade-off axes: speed, cost, downtime, and rollback