When Beanstalk deployment policy is set as:
Rolling with additional batch Elastigroup will use the
Independent integration method to manage the cluster instances.
Once an Elastigroup is created with Beanstalk
Independent integration, the following procedure takes place:
- Elastigroup will launch additional instances (same amount as the original Elastic Beanstalk ASG)
- Registering new instances to Elastic Beanstalk environment
- Registering new instances to Load Balancer
It’s crucial that all capacity changes be done via Elastigroup. Failing to do so may result in unexpected behavior. This includes detaching instances, Elastigroup/Beanstalk environment termination, scaling policies, and manual capacity changes.
Application Updates / Deployment
Versions will be deployed automatically. When updating application version or deploying a new application, no additional actions are required on the Elastigroup.
Infrastructure configuration changes
It’s crucial that all capacity changes will be done via Elastigroup. Failing to do so may result in unexpected behavior and changes may not propagate to the Elastigroup. this includes but not restricted to VPC, Subnets, AMI, Instance Type, Key pairs and load balancer configuration