-
You didn’t factor in the existing EB environment. Say we have an EB environment with instances EC2a, EC2b, and EC2c. If you choose to use All-at-once or Rolling w/ batch, the new version will be deployed to those instances (EC2a, EC2b, and EC2c). No new instances are created. Also just to clarify, the developer is tasked to configure the EB’s deployment policy and not to manually add instances to the existing EB environment.
Let me know if this helps.
