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 process takes place to replace the ASG instances with instances managed by Elastigroup:
- Elastigroup launches additional instances (same amount as the original Elastic Beanstalk ASG).
- The new instances are registered to the Elastic Beanstalk environment.
- The new instances are registered to the Load Balancer.
All capacity changes must 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 are deployed automatically. When updating an application version or deploying a new application, no additional actions are required on the Elastigroup.
Infrastructure configuration changes
For non-capacity changes only. In the following steps the Beanstalk environment is updated, then the new configuration is imported and a blue/green deployment is initiated to gracefully replace the existing Elastigroup’s instances with new, updated instances.
- Open the Beanstalk environment in AWS and perform the changes there.
- Open the Elastigroup Management View. Under the Actions Menu select Beanstalk.
- Click Re-Import Config to re-import the updated Beanstalk configuration into your Elastigroup.
- Optional: Configure the Blue/Green Deployment. For more on configuring Blue/Green Deployments in Elastigroup see the documentation here.
- Click Save & Deploy.