GitHub Actions runners on AWS
backmesh runs each GitHub Actions job on its own EC2 VM in your AWS account, spot unless the label says on demand or the job reruns after a spot reclaim. The VM is deleted when the job ends, and AWS bills you for it.
VM types
Section titled “VM types”A job’s VM is the first type in its label’s list that has capacity:
| Label | vCPU | Memory | Types, in order |
|---|---|---|---|
backmesh-2 |
2 | 8 GiB | m8i.large, m7a.large, m7i.large, m6a.large |
backmesh-4 |
4 | 16 GiB | m8i.xlarge, m7a.xlarge, m7i.xlarge, m6a.xlarge |
backmesh-8 |
8 | 32 GiB | m8i.2xlarge, m7a.2xlarge, m7i.2xlarge, m6a.2xlarge |
backmesh-16 |
16 | 64 GiB | m8i.4xlarge, m7a.4xlarge, m7i.4xlarge, m6a.4xlarge |
The KVM labels use m8i, then m7i (m7a and m6a don’t
nest). The GPU labels use g4dn.xlarge (one T4, 4 vCPUs and
16 GiB), then g4dn.2xlarge (the same T4, 8 vCPUs and 32 GiB). When AWS is the control plane’s cloud, its labels are plain, as above;
otherwise they name it, such as backmesh-aws-4.
Regions
Section titled “Regions”Runners use a fixed list of US regions, not discovered through your cloud CLI
or chosen on the command line: every one whose catalog offers every type
above, which leaves out us-west-1 (no m7a), narrowed to the ones your
account allows. Each job tries the cheapest region first, then another when
AWS refuses for capacity or quota. More.
What install creates
Section titled “What install creates”Install works through your signed-in aws CLI, and creates:
- A role connection: a CloudFormation stack with an IAM role and an OIDC
provider, in the control plane’s region, or
us-east-1when the control plane is on another cloud, unlessAWS_REGIONis set. The role trusts only your control plane, so no AWS keys are stored. - Cache buckets, through that connection: one per runner region,
bm-cache-<id>-<region>, for the cache. - The control plane, when AWS is its cloud: a
t3.largeVM and at3.smallVM for the listener, with their disks and public addresses, and a checkpoint bucket for its backups.
Uninstall deletes the VMs and buckets. It asks before deleting the checkpoint bucket, and leaves the role connection’s setup for you to delete in the console.
Quotas
Section titled “Quotas”Spot labels count against EC2’s “All Standard (A, C, D, H, I, M, R, T, Z) Spot
Instance Requests” quota (L-34B43A08), and on-demand labels against “Running
On-Demand Standard (A, C, D, H, I, M, R, T, Z) instances” (L-1216C47A), in
vCPUs per region. Install reads both through aws service-quotas and prints
them as how many backmesh-4 jobs fit at once. A region whose quota is at AWS’s
default 5 vCPUs gets no backmesh-8 or backmesh-16 runners until you raise
it; install and backmesh status name the quota. The GPU labels
count against “All G and VT Spot Instance Requests” (L-3819A6DF) and
“Running On-Demand G and VT instances” (L-DB2E81BA) instead, 0 on most new
accounts: request at least 4 vCPUs per region in the
Service Quotas console.
More.
These are catalog prices in us-east-2, spot in the lowest zone, for a
backmesh-4 VM while its job runs:
| Type | Spot $/h | On demand $/h |
|---|---|---|
m8i.xlarge |
0.0583 | 0.2117 |
m7a.xlarge |
0.07 | 0.2318 |
m7i.xlarge |
0.0497 | 0.2016 |
m6a.xlarge |
0.0547 | 0.1728 |
Other sizes scale with their vCPUs. Each job also pays for its VM’s boot and its
100 GB gp3 disk at 4,000 IOPS and 500 MiB/s, about $0.038 an hour. The
control plane costs about $86 a month. At
those prices, 150,000 minutes a month of backmesh-4 jobs cost at least
$210–$261 with the control plane, before disks, boots and runners started ahead
of jobs; see the costs. Spot prices change by the hour.