Scroll environment configuration update
When the configuration changes require replacement instance when, Elastic Beanstalk can perform batch updates to avoid downtime when propagate changes. During the rollover, according to the capacity of only a single batch size reduction, and you can configure the size. Elastic Beanstalk stop a number of instances, terminate these instances, and then start a number of examples of the new configuration. After the new batch begins processing the request, Elastic Beanstalk moves to the next batch.
Scroll batch configuration update process may be based on periodic time (delay between each batch) or by processing in accordance with operating conditions. For time-based rollover, you can configure Elastic Beanstalk time waiting in the start and finish a number of instances after a batch before the next move. This allows you to pause time of the application guide and begin processing the request.
Immutable environment update
Immutable environment update is rolling update alternative. Immutable environment updated to ensure safe and efficient application configuration changes need to be replaced instance. If you can not change the environment update fails, the rollback process only needs to terminate Auto Scaling group. On the other hand, a failure of rolling updates need to perform additional rollover to roll back the changes.
To perform the update immutable environment, Elastic Beanstalk to create a second temporary Auto Scaling group behind a load balancer in your environment to include the new instance. First, Elastic Beanstalk single instance start using the new configuration in the new group. This instance and all instances of the original Auto Scaling group run before configuration together to provide services for the traffic.
After the first instance by the health check, Elastic Beanstalk using the new configuration starting additional instances that the number of instances running in the original Auto Scaling group match. When all the new instances are checked by health, Elastic Beanstalk will be transferred to these instances the original Auto Scaling group, and termination of provisional Auto Scaling group and the old instance.