AWS CodeBuild-hosted runners vs terraform-aws-github-runner
AWS CodeBuild-hosted runners suits teams on AWS that want GitHub Actions, GitLab or Buildkite jobs to run inside their own account with IAM and VPC access. terraform-aws-github-runner suits teams on AWS that manage infrastructure with Terraform and want GitHub Actions runners on EC2 that scale to zero. AWS CodeBuild-hosted runners is a cloud provider service that runs in your cloud account for GitHub Actions, GitLab CI and Buildkite, priced at $0.005/min; terraform-aws-github-runner is an open-source project you run yourself for GitHub Actions.
Key differences between AWS CodeBuild-hosted runners and terraform-aws-github-runner
- Type: AWS CodeBuild-hosted runners is a cloud provider service that runs in your cloud account; terraform-aws-github-runner is an open-source project you run yourself.
- CI systems: Only AWS CodeBuild-hosted runners documents GitLab CI and Buildkite.
- Operating systems: Only terraform-aws-github-runner documents macOS.
- Isolation: AWS CodeBuild-hosted runners: Fresh build environment. terraform-aws-github-runner: EC2 instance.
- Open source: terraform-aws-github-runner is open source (MIT); AWS CodeBuild-hosted runners is not.
- Self-hosting: terraform-aws-github-runner documents a self-hosted option; AWS CodeBuild-hosted runners does not.
What they have in common
- Both run GitHub Actions jobs.
- Both document Linux and Windows runners.
- Both document arm64 runners.
- Both document GPU runners.
AWS CodeBuild-hosted runners vs terraform-aws-github-runner at a glance
| Attribute | AWS CodeBuild-hosted runners | terraform-aws-github-runner |
|---|---|---|
| What it is | AWS CodeBuild projects that start a single-use runner in your AWS account for each GitHub Actions, GitLab or Buildkite job. | Terraform module that runs GitHub Actions runners on EC2 spot or on-demand instances, scaled by Lambda functions. |
| Type | Cloud provider service | Open-source project |
| CI systems | GitHub Actions, GitLab CI, Buildkite | GitHub Actions |
| Operating systems | Linux, Windows | Linux, Windows, macOS |
| Architectures | x64, arm64 | x64, arm64 |
| Isolation | Each job starts a CodeBuild build in a fresh environment that is discarded when it finishes; runner builds use CodeBuild containers or instances on Amazon EC2, or AWS Lambda compute | Each runner is an EC2 instance in your AWS account; by default runners are reused until they are idle, and in ephemeral mode each instance takes one job with a just-in-time configuration and is then terminated |
| Fresh environment per job | Yes | Not documented |
| Hardware | On-demand Amazon EC2 or AWS Lambda compute, or reserved capacity fleets, on x86-64 and Arm; AWS says runners can use its latest instance types, including ARM-based instances | EC2 instance types that you list, spot or on-demand, launched through the EC2 CreateFleet API; Graviton types for arm64 and EC2 Mac dedicated hosts for the experimental macOS support |
| Performance (vendor claim) | Not documented | Not documented |
| Runner sizes | On-demand EC2: 2 vCPU / 4 GiB to 72 vCPU / 144 GiB on Linux x86-64, 2 vCPU / 4 GiB to 48 vCPU / 96 GiB on Arm, 4 vCPU / 8 GiB to 72 vCPU / 144 GiB on Windows. Lambda: 1 to 10 GiB of memory | Not documented |
| Caching | CodeBuild projects can cache to Amazon S3 or use a local cache with source, Docker layer and custom modes. A Docker image server with a shared layer cache is billed separately per second. | Not documented |
| Docker layer caching | Yes | Not documented |
| GPU | Linux GPU compute types gpu_small (4 vCPU, 16 GiB) at $0.05 and gpu_large (32 vCPU, 255 GiB) at $0.30 per build minute in US East (N. Virginia); GPU models are not stated on the pages checked. | With dynamic labels enabled, ghr-ec2 override labels can request EC2 instance requirements that include GPU accelerator types. |
| Concurrency | Concurrently running builds are capped by per-Region service quotas for each environment type, which AWS lists as adjustable | The scale-up Lambda stops creating instances once the configured maximum number of runners is reached; an optional pool keeps a scheduled minimum of ephemeral org-level runners |
| Static IPs | Not documented | Not documented |
| SSH into running jobs | Not documented | Yes |
| Pricing | Standard CodeBuild rates per build minute in US East (N. Virginia): Linux x86-64 small (2 vCPU) $0.005, medium $0.01, large $0.02; Arm small $0.0034, medium $0.007, large $0.015; Windows medium $0.018, large $0.036. EC2 builds are rounded up to the minute; Lambda compute is billed per second. Rates vary by Region. | Free and open source; you pay for the infrastructure it runs on. |
| Free tier | 100 build minutes per month on general1.small or arm1.small on-demand EC2, or 6,000 build seconds per month on 1 GB Lambda compute | Not documented |
| Open source | No | Yes (MIT) |
| Self-host / your cloud | No / Yes | Yes / Yes |
| Compliance | Not documented | Not documented |
| Regions | All AWS Regions where CodeBuild is available | Not documented |
| Company headquarters | Seattle, Washington, United States | Not documented |
| Good fit for | Teams on AWS that want GitHub Actions, GitLab or Buildkite jobs to run inside their own account with IAM and VPC access | Teams on AWS that manage infrastructure with Terraform and want GitHub Actions runners on EC2 that scale to zero |
Verified November 22, 2026 from each provider’s documentation. Performance figures are vendor claims, not our measurements.
Which should you choose?
Reasons to choose AWS CodeBuild-hosted runners
- You want CI jobs to run inside your own AWS account with IAM roles and VPC access
- You use GitHub Actions, GitLab or Buildkite and want one runner service for all of them
- You want single-use runners without operating an autoscaler
- You need Arm, GPU or Windows compute billed at standard CodeBuild rates
Reasons to choose terraform-aws-github-runner
- You want runners on EC2 spot instances that scale down to zero when no workflows are active
- You manage AWS with Terraform and want the whole runner stack defined as a module
- You need Linux x64, Linux arm64 and Windows runners from one deployment through the multi-runner module
- You want to bring your own AMI, instance types and subnets
Trade-offs to check first
- AWS CodeBuild-hosted runners: macOS is not listed among the supported runner platforms, and on-demand fleets do not support macOS
- AWS CodeBuild-hosted runners: Build duration on EC2 compute is rounded up to the nearest minute
- terraform-aws-github-runner: Enterprise-level runners are not supported; runners are registered at organization or repository level
- terraform-aws-github-runner: The maintainers describe the project as maintained on a best-effort basis
Run your slowest workflow on both before deciding. See the full AWS CodeBuild-hosted runners profile and terraform-aws-github-runner profile, or the complete comparison.
More comparisons
- Actions Runner Controller (ARC) vs AWS CodeBuild-hosted runners
- AWS CodeBuild-hosted runners vs Elastic CI Stack for AWS
- AWS CodeBuild-hosted runners vs GitLab-hosted runners
- AWS CodeBuild-hosted runners vs Managed DevOps Pools
- AWS CodeBuild-hosted runners vs RunsOn
- Actions Runner Controller (ARC) vs terraform-aws-github-runner
- Cirun vs terraform-aws-github-runner
- GARM (GitHub Actions Runner Manager) vs terraform-aws-github-runner
- HyperEnv for GitHub Actions Runner vs terraform-aws-github-runner
- RunsOn vs terraform-aws-github-runner
- terraform-aws-github-runner vs TestFlows GitHub Hetzner Runners
- ec2-github-runner vs terraform-aws-github-runner
Frequently asked questions
Is AWS CodeBuild-hosted runners or terraform-aws-github-runner better?
What is the difference between AWS CodeBuild-hosted runners and terraform-aws-github-runner?
Which is open source, AWS CodeBuild-hosted runners or terraform-aws-github-runner?
How do AWS CodeBuild-hosted runners and terraform-aws-github-runner isolate jobs?
How does AWS CodeBuild-hosted runners pricing compare with terraform-aws-github-runner?
Do AWS CodeBuild-hosted runners and terraform-aws-github-runner cache Docker layers?
Do AWS CodeBuild-hosted runners and terraform-aws-github-runner offer GPU runners?
Where do AWS CodeBuild-hosted runners and terraform-aws-github-runner runners run?
Sources
- docs.aws.amazon.com/codebuild/latest/userguide/runners.html
- docs.aws.amazon.com/codebuild/latest/userguide/action-runner-overview.html
- docs.aws.amazon.com/codebuild/latest/userguide/action-runner-questions.html
- docs.aws.amazon.com/codebuild/latest/userguide/sample-github-action-runners-update-labels.html
- github.com/github-aws-runners/terraform-aws-github-runner
- github.com/github-aws-runners/terraform-aws-github-runner/releases
- github.com/github-aws-runners/terraform-aws-github-runner/blob/main/CHANGELOG.md
- github.com/github-aws-runners/terraform-aws-github-runner/blob/main/LICENSE.md
Check before you rely on it. Products change quickly, and this page reflects public documentation as of November 22, 2026. Confirm anything that matters in the provider’s own documentation.
Cite this page
CI Runners. (2026). AWS CodeBuild-hosted runners vs terraform-aws-github-runner. cirunners.org. Last reviewed November 22, 2026. https://cirunners.org/compare/aws-codebuild-runners-vs-terraform-aws-github-runner/