Spotinst Elastigroup integrates with Multai Load Balancing to enable you to attach one or more load balancers to an existing Elastigroup. After you attach the load balancer, it automatically registers the instances in the group and distributes incoming traffic across the instances.

When you attach a load balancer, it registers instances into Adding state. After at least one health checks test passes, it enters the instance into Healthy state.


Prerequisite; Install MLB on AWS or any other cloud of your choice  and have an existing Spotinst Elastigroup ready


Attach an Elastigroup

Follow the steps below to attach an Elastigroup with MLB:

  1. Go to the Spotinst Console -> Elastigroup
  2. Navigate to your Elastigroup
  3. From the top right “Actions” menu select “Edit Configuration
  4. Click on the “Compute” tab and scroll down to Load Balancers section
  5. From the drop-down select the “Target Set” for the desired balancer.
  6. Configure the MLB Health Check as the primary Health Check in the Elastigroup. Instances that do not pass the MLB health check within a specified time frame will automatically be terminated and new instances will be launched to replace them.
  7. When finished, update your Elastigroup. The instances will register immediately to your MLB TargetSet.
  8. Verify that the new Elastigroup instances were added to your MLB Load Balancer. The instance that has been added via the Elastigroup integration will have the name field set as the EC2 instance ID.

Advanced Configuration

The option “AZ Awareness” will ensure that instances within the same AZ are using the corresponding MLB runtime instance in the same AZ. This feature reduces multi-zone data transfer fees.
The option “Auto Weight” will automatically provide a higher weight for instances that are larger as appropriate. For example, if you have configured your Elastigroup with m4.large and m4.xlarge instances the m4.large will have half the weight of an m4.xlarge. This ensures that larger instances receive a higher number of MLB requests as appropriate and further optimizes your Elastigroup instances.


Things to note:

  • MLB Runtime nodes will need to be in a public subnet (Internet Gateway Attached) and belong to the same VPC as your Elastigroup. These nodes will require private routes from to your Elastigroup instances.
  • A good test prior to configuring the Elastigroup integration is to SSH into one of your MLB Runtime nodes and perform a curl to the health check address for your application. If this functions properly then you are ready to configure the integration