Runner capabilities
Optional capabilities you can layer on top of any RunsOn runner - static egress IPs, nested virtualization, remote access, and Amazon Bedrock for AI workloads.
Capabilities are optional features you can layer on top of any runner type. They work the same way across runner families: in Flex a workflow opts in with a job label, in Fleet the platform team enables them on a Terraform-owned runner fleet.
Static IPs Static egress IPs for RunsOn Flex and Fleet runners through private subnets, NAT gateways, and Elastic IPs. Nested virtualization When to use Linux KVM or Windows Hyper-V inside RunsOn runners, and the EC2 constraints that matter. Remote access Use SSM and optional SSH access to troubleshoot RunsOn Flex and Fleet runner instances. AI agents Run AI-assisted CI on RunsOn runners — IAM access to invoke Amazon Bedrock models, and self-hosted execution for GitHub's Copilot coding agent. YOLO mode (tmpfs) How to use the tmpfs feature with RunsOn, for faster builds Shared volumes (EFS) How to use the EFS file system with RunsOn, for storing files across GitHub Actions workflow jobs Sticky disks (EBS) Save and restore entire folders with block-level snapshots. Helps to speed-up docker builds in your GitHub Actions workflows. Docker Hub pull-through Mirror Docker Hub (and other public registries) through ECR in your own account so runners pull images over the VPC instead of the public internet — no more 429 rate limits.