Runners

Fargate

Runner group kind backend_type=fargate — ECS Fargate tasks in your AWS account, the default AWS CI and agent path

backend_type: fargate. Connection: AWS. Status: production (GA).

Each execution is an ECS Fargate task in a cluster you name. No EC2 instances to patch. This is the default AWS kind in the Runners create wizard and a production-shaped backend for agent pools.

When to choose it

AWS-resident CI where you want tasks, not VMs.
Agent sessions that should scale to zero when idle.
You already have (or will accept) an ECS cluster for the group.

Choose EC2 VM when you need a dedicated instance, local disk, or the warm-pool controller's disk-pressure drain. Choose EC2 Auto Scaling when you want a persistent ASG behind ECS rather than Fargate.

Connection

An AWS connection on the organization. A broken connection means a broken group — there is no Orkestia compute fallback.

Required config

Key	Type	Meaning
`ecs_cluster_name`	string	ECS cluster this group must use. Set it explicitly — derived names have landed tasks on the wrong cluster.

Read the live field list with data.runner.get-provider-config-spec (backend_type=fargate) or data.runner.list-provider-config-specs.

ecs_cluster_arn, task_family, cpu, memory, container_image, subnet_ids, security_group_ids, assign_public_ip, capacity_type (ON_DEMAND / SPOT), launch_type (FARGATE / FARGATE_SPOT).

Execution control

Fargate owns the unsuffixed runner.execution-* names (stop, restart, sync, logs-sync). Pool reconcile: runner.pool-reconcile-fargate. Confirm names in reference.orkestia.dev.

Purposes

CI (github_actions / gitlab_runner / generic) and agent all run on Fargate. Agent groups still need purpose=agent at create time. See Purposes.

Purposes & integrations

purpose and integration_type are independent enums — github_actions, gitlab_runner, agent, generic, and the job-source grant each one needs

EC2 Auto Scaling