Provisioning allows scaling decisions to be performed automatically. For provisioning to work, you must have a provisoning-enabled integration set up. Note that some integrations may be able to be reused across Metric Data and Provisioning. For example, AWS has a service to store your metrics (CloudWatch) and several services to provision virtual machines (EC2, ECS, EKS, etc).
Below are a list of provisioners that Compute Software supports. Note that currently only AWS services are supported. Have a provisioner in mind that we currently don’t support? Send us an email at firstname.lastname@example.org to put in a feature request.
Within a workload, you can set up, activate, and deactivate provisioning on the right side dropdown in the header.
AWS Auto Scaling
After creating an Auto Scaling Group in AWS, input the following:
- Auto Scaling Group Region: The region in which your Auto Scaling Group is deployed
- Auto Scaling Group Name: The name you created for your Auto Scaling Group
VM Scaler will validate that the group exists before enabling provisioning.
Once enabled, VM Scaler will control the number of instances in your Auto Scaling Group by adjusting the Desired Capacity field via the SetDesiredCapacity API. The min and max number of instances set for the Auto Scaling Group will be respected by this operation. If we continually hit the min or max number of instances set on your Auto Scaling Group, we will send you an Alert.
AWS ECS Service or Fargate Scaling
- AWS Region: The region in which your ECS cluster is deployed
- Cluster Name: The ECS cluster name
- Service Name: The name of the ECS service running within your ECS cluster. This can be a service with launch type EC2 or Fargate.
VM Scaler will validate that the cluster and service exist before enabling provisioning.
Once enabled, VM Scaler will control the number of services in your cluster by adjusting the desired count field via the UpdateService API.