CI Runnerscirunners.org
Head-to-head

AWS CodeBuild-hosted runners vs Elastic CI Stack for AWS

Answer in brief

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. Elastic CI Stack for AWS suits Buildkite customers on AWS that want an autoscaling agent fleet in their own VPC with a vendor-maintained template. 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; Elastic CI Stack for AWS is an open-source project you run yourself for Buildkite.

By the CI Runners editors · Updated

Key differences between AWS CodeBuild-hosted runners and Elastic CI Stack for AWS

  • Type: AWS CodeBuild-hosted runners is a cloud provider service that runs in your cloud account; Elastic CI Stack for AWS is an open-source project you run yourself.
  • CI systems: Only AWS CodeBuild-hosted runners documents GitHub Actions and GitLab CI.
  • Isolation: AWS CodeBuild-hosted runners: Fresh build environment. Elastic CI Stack for AWS: EC2 instance.
  • Open source: Elastic CI Stack for AWS is open source (MIT); AWS CodeBuild-hosted runners is not.
  • Self-hosting: Elastic CI Stack for AWS documents a self-hosted option; AWS CodeBuild-hosted runners does not.
  • Company headquarters: Amazon Web Services, Inc. is based in Seattle, United States; Buildkite Pty Ltd is based in Melbourne, Australia.

What they have in common

  • Both run Buildkite jobs.
  • Both document Linux and Windows runners.
  • Both document arm64 runners.

AWS CodeBuild-hosted runners vs Elastic CI Stack for AWS at a glance

AttributeAWS CodeBuild-hosted runnersElastic CI Stack for AWS
What it isAWS CodeBuild projects that start a single-use runner in your AWS account for each GitHub Actions, GitLab or Buildkite job.CloudFormation template (with a Terraform option) that runs an autoscaling group of Buildkite agents on EC2 in your own AWS account.
TypeCloud provider serviceOpen-source project
CI systemsGitHub Actions, GitLab CI, BuildkiteBuildkite
Operating systemsLinux, WindowsLinux, Windows
Architecturesx64, arm64x64, arm64
IsolationEach 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 computeAgents run on EC2 instances in an Auto Scaling group inside your VPC; instances are reused between jobs by default, and a template parameter can terminate the instance after each job
Fresh environment per jobYesNot documented
HardwareOn-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 instancesEC2 instance types set with the InstanceTypes parameter (default t3.large); local NVMe instance storage can be enabled on Linux
Performance (vendor claim)Not documentedNot documented
Runner sizesOn-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 memoryNot documented
CachingCodeBuild 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.Git mirrors can be enabled as an agent experiment, and on Linux the builds directory can be placed on local NVMe instance storage.
Docker layer cachingYesNot documented
GPULinux 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.Not documented
ConcurrencyConcurrently running builds are capped by per-Region service quotas for each environment type, which AWS lists as adjustableTemplate defaults are MinSize 0 and MaxSize 10 instances with one agent per instance; all three are configurable
Static IPsNot documentedNot documented
SSH into running jobsNot documentedYes
PricingStandard 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. Buildkite notes that the AWS services are pay-as-you-go and that Buildkite services are billed according to your plan.
Free tier100 build minutes per month on general1.small or arm1.small on-demand EC2, or 6,000 build seconds per month on 1 GB Lambda computeNot documented
Open sourceNoYes (MIT)
Self-host / your cloudNo / YesYes / Yes
ComplianceNot documentedNot documented
RegionsAll AWS Regions where CodeBuild is availableAll AWS Regions except China and US GovCloud
Company headquartersSeattle, Washington, United StatesMelbourne, Victoria, Australia
Good fit forTeams on AWS that want GitHub Actions, GitLab or Buildkite jobs to run inside their own account with IAM and VPC accessBuildkite customers on AWS that want an autoscaling agent fleet in their own VPC with a vendor-maintained template

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 Elastic CI Stack for AWS

  • You use Buildkite and want agents inside your own AWS account and VPC
  • You want a template maintained by Buildkite, with prebuilt Linux and Windows AMIs
  • You want the fleet to scale with build activity and down to a minimum of zero instances
  • You need Linux on x86 and Arm as well as Windows Server agents

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
  • Elastic CI Stack for AWS: The README states that the repository has not been reviewed by security researchers
  • Elastic CI Stack for AWS: Builds can reach the EC2 metadata server and act with the IAM permissions of the instance

Run your slowest workflow on both before deciding. See the full AWS CodeBuild-hosted runners profile and Elastic CI Stack for AWS profile, or the complete comparison.

More comparisons

Frequently asked questions

Is AWS CodeBuild-hosted runners or Elastic CI Stack for AWS better?
Neither is better for every pipeline. 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. Elastic CI Stack for AWS suits Buildkite customers on AWS that want an autoscaling agent fleet in their own VPC with a vendor-maintained template.
What is the difference between AWS CodeBuild-hosted runners and Elastic CI Stack for AWS?
AWS CodeBuild-hosted runners is a cloud provider service that runs in your cloud account; Elastic CI Stack for AWS is an open-source project you run yourself. Only AWS CodeBuild-hosted runners documents GitHub Actions and GitLab CI. Isolation is Fresh build environment on AWS CodeBuild-hosted runners and EC2 instance on Elastic CI Stack for AWS. Elastic CI Stack for AWS is open source (MIT); AWS CodeBuild-hosted runners is not. Elastic CI Stack for AWS documents a self-hosted option; AWS CodeBuild-hosted runners does not.
Which is open source, AWS CodeBuild-hosted runners or Elastic CI Stack for AWS?
AWS CodeBuild-hosted runners is not open source; Elastic CI Stack for AWS is open source (MIT).
How do AWS CodeBuild-hosted runners and Elastic CI Stack for AWS isolate jobs?
AWS CodeBuild-hosted runners: 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. Elastic CI Stack for AWS: Agents run on EC2 instances in an Auto Scaling group inside your VPC; instances are reused between jobs by default, and a template parameter can terminate the instance after each job.
How does AWS CodeBuild-hosted runners pricing compare with Elastic CI Stack for AWS?
AWS CodeBuild-hosted runners: 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. Elastic CI Stack for AWS: Free and open source; you pay for the infrastructure it runs on. Buildkite notes that the AWS services are pay-as-you-go and that Buildkite services are billed according to your plan. Rates change, so check the AWS CodeBuild-hosted runners and Elastic CI Stack for AWS pricing pages before deciding.
Do AWS CodeBuild-hosted runners and Elastic CI Stack for AWS cache Docker layers?
AWS CodeBuild-hosted runners: 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. Elastic CI Stack for AWS: Docker layer caching is not documented.
Do AWS CodeBuild-hosted runners and Elastic CI Stack for AWS offer GPU runners?
AWS CodeBuild-hosted runners: 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. Elastic CI Stack for AWS: Not documented.
Where do AWS CodeBuild-hosted runners and Elastic CI Stack for AWS runners run?
AWS CodeBuild-hosted runners is a cloud provider service that runs in your cloud account (AWS). Elastic CI Stack for AWS is an open-source project you run yourself (AWS).

Sources

  1. docs.aws.amazon.com/codebuild/latest/userguide/runners.html
  2. docs.aws.amazon.com/codebuild/latest/userguide/action-runner-overview.html
  3. docs.aws.amazon.com/codebuild/latest/userguide/action-runner-questions.html
  4. docs.aws.amazon.com/codebuild/latest/userguide/sample-github-action-runners-update-labels.html
  5. github.com/buildkite/elastic-ci-stack-for-aws
  6. github.com/buildkite/elastic-ci-stack-for-aws/releases
  7. github.com/buildkite/elastic-ci-stack-for-aws/blob/main/Licence.md
  8. github.com/buildkite/elastic-ci-stack-for-aws/blob/main/templates/aws-stack.yml

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 Elastic CI Stack for AWS. cirunners.org. Last reviewed November 22, 2026. https://cirunners.org/compare/aws-codebuild-runners-vs-buildkite-elastic-ci-stack/