| I don't believe this is accurate. When making radical changes to your application it might be required to run two copies in EB and do a CNAME swap. But for day-to-day deploys of new versions, EB can use rolling batches within one application, as you say ECS does, you configure it to. Specifically, you can have EB update only a fixed number or percentage of instances in your application with new versions at a time. It does this by removing, in batches, only some of the instances from the load balancers, waiting for existing connections to complete, updating those instances, and then re-adding them to the load-balancer. See http://docs.aws.amazon.com/elasticbeanstalk/latest/dg/using-... (I agree that the existence of this page along with "Deploying Versions with Zero Downtime" is confusing, but rolling deploys are specifically mentioned as an alternative to CNAME swap: "Batched application version deployments are also an alternative to application version deployments that involve a CNAME swap") Also, regarding terminology, note that under the hood EB, when used for multi-container Docker applications, is just an abstraction layer over ECS. It sets up ECS tasks for you you. |