EC2 Auto Scaling
backend_type: ec2_auto_scaling. Connection: AWS. Status: production.
The group is an EC2 Auto Scaling group that feeds an ECS capacity provider. Executions land as ECS tasks on those instances, not as one-shot Fargate tasks and not as a dedicated VM per job.
When to choose it
- You want always-on (or min-sized) EC2 capacity that ECS can place tasks onto.
- Instance type, VPC, and Spot price need to be first-class group config.
- Fargate's per-task billing or networking model is a poor fit, but you still want ECS as the scheduler.
Choose Fargate for serverless tasks. Choose EC2 VM for one instance per execution with the warm-pool VM controller.
Connection
An AWS connection. Placement uses the group's region plus optional vpc_id / subnet_ids.
Required config
| Key | Type | Meaning |
|---|---|---|
instance_type | string | EC2 instance type for ASG members (e.g. t3.medium). |
Optional knobs
vpc_id, subnet_ids, security_group_ids, cluster_name (ECS cluster backing the capacity provider), capacity_type (ON_DEMAND / SPOT), spot_max_price.
Provisioning
Environment DAG orientation: runner.environment-provision-ec2 / runner.environment-deletion-ec2. Confirm current names before calling them from MCP.
Purposes
Same as every AWS kind — CI or agent. Do not reuse an Actions ASG as an agent pool; create purpose=agent from the start.