- New instances are not starting, what should I do?
Check your email - We send out alerts once such a thing happens. There could be various reasons for it:
Resources that are mandatory for instance launch (Such as AMI or security group) that are specified in your Elastigroup configuration was deleted from AWS
If you are using private IP, verify that the private IP is not in use by other instances
You reached the volume limit or other limits in AWS - And therefore new instances cannot be launched - Check your AWS console and open a support ticket to AWS to resolve it.
- How do I disable the Elastigroup?
In order to disable the Elastigroup, simply change the target, minimum and maximum capacity to ‘0’. No instances will be launched in the group, but you will still have the configuration ready.
- My group has more instances than its max size
During deployments or instance replacements we allow for some time were the instance count surpasses the max value. This should be sorted as soon as the deployment finishes.
- How can I detach an instance from a group?
Each Elastigroup has a capacity setting to determine the instance count for the group. These values can change dynamically based on scheduling rules or AutoScaling rules. The Max and Min capacity number signify the limits of what is allowed. If you are getting an error it probably means you are trying to set a target (number of instances) lower than the set min capacity OR you are trying to detach an instance manually. To fix this you can select the Elastigroup, click on Actions, select “Manage Capacity” and alter the values to reflect your needs.
Alternatively, you can select a specific instance from the Instances tab and perform a detaching action on it