Skip to content

runs-on/runner-images-for-aws

Repository files navigation

GitHub Actions runner images for AWS

GitHub Actions Runner images for AWS, to be used with RunsOn, or for your own usage.

Official images are replicated and published every 15 days.

Supported images

Linux

Those images are very close to 1-1 compatible with official GitHub Actions runner images. Some legacy or easily available through actions software has been removed to ensure faster boot times and lower disk usage.

  • ubuntu22-full-x64
  • ubuntu22-full-arm64
  • ubuntu24-full-x64
  • ubuntu24-full-arm64

Windows

These images are being aligned with upstream "full" Windows tooling (including Visual Studio/C++ and Hyper-V-related components where supported). Some legacy or easily available through actions software may still be removed to ensure faster boot times and lower disk usage. Availability of virtualization-dependent components can vary based on EC2 instance capabilities and build tooling support.

  • windows22-full-x64
  • windows25-full-x64
  • windows25-gpu-x64

GPU

Those use the corresponding base images. Linux GPU images include NVIDIA GPU drivers, CUDA toolkit, and container toolkit. Windows GPU images include the AWS GRID driver plus the CUDA toolkit.

  • ubuntu22-gpu-x64
  • ubuntu24-gpu-x64
  • ubuntu24-gpu-arm64
  • windows25-gpu-x64

Supported regions

  • North Virginia (us-east-1)
  • Ohio (us-east-2)
  • Oregon (us-west-2)
  • Ireland (eu-west-1)
  • London (eu-west-2)
  • Paris (eu-west-3)
  • Frankfurt (eu-central-1)
  • Mumbai (ap-south-1)
  • Tokyo (ap-northeast-1)
  • Singapore (ap-southeast-1)
  • Sydney (ap-southeast-2)

Find the AMI

For the x86_64 image, search for:

  • name: runs-on-v2.2-<IMAGE_ID>-*
  • owner: 135269210855

For instance, for the ubuntu22-full-x64 image, search for:

  • name: runs-on-v2.2-ubuntu22-full-x64-*
  • owner: 135269210855

Notes

  • SSH daemon is disabled by default, so be sure to enable it in a user-data script if needed.

Inspector AMI scanning

Deploy the AWS-native Inspector scanner stack from this repo:

AWS_PROFILE=<profile> make inspector-stack-deploy

The target defaults to us-east-1, stack name runs-on-inspector-ami-scanner, and notification email security@runs-on.com. Optional overrides:

AWS_REGION=us-east-1 \
INSPECTOR_STACK_NAME=runs-on-inspector-ami-scanner \
INSPECTOR_NOTIFICATION_EMAIL=security@runs-on.com \
make inspector-stack-deploy

The stack creates the scanner VPC, outbound-only temporary scan instances, IAM roles, encrypted S3 report bucket, SNS topic, EventBridge schedule, Lambda orchestration, and Step Functions workflow. Confirm the SNS email subscription before expecting notifications.

Amazon Inspector EC2 scanning must be enabled in us-east-1 for the account. Reports are exported under s3://<stack-report-bucket>/inspector/<image-id>/<channel>/<ami-id>/.

AMI scanning is opt-in from config.yml. Add inspect: true to an image entry to scan the latest dev and prod AMIs matching runs-on-dev-<image_id>-* and runs-on-v2.2-<image_id>-*. Missing inspect defaults to false. The inspector_scan AMI tag is scanner-owned state; do not manage it from Packer templates or bin/copy-ami.

See docs/inspector-ami-scanner.md for operational details.