CI Runnerscirunners.org
Runner profile · Open-source project

Elastic CI Stack for AWS

Answer in brief

CloudFormation template (with a Terraform option) that runs an autoscaling group of Buildkite agents on EC2 in your own AWS account. Buildkite’s own open-source template for autoscaling agents on EC2; it suits Buildkite customers that keep builds inside their AWS account.

By the CI Runners editors · Updated

Overview

The Elastic CI Stack for AWS is Buildkite’s template for a private, autoscaling cluster of Buildkite agents. Each deployment contains an EC2 Auto Scaling group and a launch template, and a Lambda function adjusts the group according to build activity. It is deployed with CloudFormation, and Buildkite also publishes a Terraform module. Docker and Docker Compose are preinstalled, and secrets can be delivered per pipeline from an S3 bucket.

Buildkite builds AMIs for Amazon Linux 2023 and Ubuntu 24.04 on x86 and Arm, and for Windows Server 2022 and 2025 on x86. The minimum size defaults to zero and instances are reused until idle unless you set them to terminate after each job. Spot instances, scheduled scaling and several agents per instance are configurable. Instances can be reached over SSH on Linux or through AWS Systems Manager. A separate CloudFormation setup covers EC2 Mac.

Notable

  • v7.13.0 was released on 19 November 2026
  • The README states that new features are developed only for v7 and that security fixes continue to be backported to v6
  • Buildkite says it aims to publish a tagged release at the end of each month when the main branch has changed

Elastic CI Stack for AWS specifications

AttributeDetails
CI systemsBuildkite
Operating systemsLinux, Windows
Architecturesx64, arm64
DeploymentOpen-source project
Where it can runAWS
IsolationAgents 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 jobNot documented
HardwareEC2 instance types set with the InstanceTypes parameter (default t3.large); local NVMe instance storage can be enabled on Linux
Performance (vendor claim)Not documented
Runner sizesNot documented
CachingGit mirrors can be enabled as an agent experiment, and on Linux the builds directory can be placed on local NVMe instance storage.
Docker layer cachingNot documented
GPUNot documented
ConcurrencyTemplate defaults are MinSize 0 and MaxSize 10 instances with one agent per instance; all three are configurable
Job limitsNot documented
Static IPsNot documented
SSH into running jobsYes
ObservabilityCloudWatch Logs for system and Buildkite agent events, and CloudWatch metrics from the Buildkite API
SetupLaunch the CloudFormation template (or the Terraform module) with a Buildkite agent token, then set parameters such as instance types and the minimum and maximum number of instances.
Example labelNot documented
PricingFree 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 tierNot documented
ComplianceNot documented
RegionsAll AWS Regions except China and US GovCloud
Open sourceYes (MIT)
Company headquartersMelbourne, Victoria, Australia · More from Australia

Facts from Elastic CI Stack for AWS’s public documentation, verified November 22, 2026. Performance figures are vendor claims.

Strengths and trade-offs

Reasons to choose it

  • 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
  • You want to use spot instances and scheduled scaling to manage EC2 cost

Trade-offs

  • The README states that the repository has not been reviewed by security researchers
  • Builds can reach the EC2 metadata server and act with the IAM permissions of the instance
  • China and US GovCloud regions are not supported
  • SSH access, instance NVMe storage and Git LFS are listed as Linux-only features

Good fit for: Buildkite customers on AWS that want an autoscaling agent fleet in their own VPC with a vendor-maintained template.

Use cases Elastic CI Stack for AWS fits

  • ARM64 builds: Amazon Linux 2023 and Ubuntu 24.04 AMIs are published for 64-bit Arm.
  • Windows builds: Buildkite publishes Windows Server 2022 and 2025 AMIs for the stack.
  • Your own cloud: The stack creates the agents, Auto Scaling group and VPC in your own AWS account.
  • Open source and self-hosted: The template and AMI build scripts are MIT licensed.

How Elastic CI Stack for AWS compares

RunnerCI systemsRuns onDeploymentIsolationPriceLargest runnerDocker layer cacheGPUOpen sourceCompany HQ
Elastic CI Stack for AWSBuildkiteLinux, Windows, x64, arm64Self-hostedEC2 instanceFree software + your infrastructureSet by your infrastructureNot documentedNot documentedYesAustralia
Buildkite hosted agentsBuildkiteLinux, macOS, Windows, x64, arm64Platform-hostedEphemeral virtualized environment$0.008/min64 vCPU / 256 GBYesNot documentedNoNot documented
GitLab RunnerGitLab CILinux, macOS, Windows, x64, arm64Self-hostedDepends on executorFree software + your infrastructureSet by your infrastructureNot documentedYesYesNot documented
terraform-aws-github-runnerGitHub ActionsLinux, Windows, macOS, x64, arm64Self-hostedEC2 instanceFree software + your infrastructureSet by your infrastructureNot documentedYesYesNot documented
Actions Runner Controller (ARC)GitHub ActionsLinux, WindowsSelf-hostedKubernetes podFree software + your infrastructureSet by your infrastructureNot documentedNot documentedYesUnited States
RunsOnGitHub ActionsLinux, Windows, x64, arm64Your cloud or hardwareEC2 instance€300/yr licence + AWS cost896 vCPUYesYesNoFrance
AWS CodeBuild-hosted runnersGitHub Actions, GitLab CI, BuildkiteLinux, Windows, x64, arm64Your cloud accountFresh build environment$0.005/min72 vCPU / 144 GBYesYesNoUnited States

Head-to-head: AWS CodeBuild-hosted runners vs Elastic CI Stack for AWS · Buildkite hosted agents vs Elastic CI Stack for AWS · Elastic CI Stack for AWS vs GitLab Runner · Aspect Workflows vs Elastic CI Stack for AWS

See all Elastic CI Stack for AWS alternatives →

Frequently asked questions

What is Elastic CI Stack for AWS?
CloudFormation template (with a Terraform option) that runs an autoscaling group of Buildkite agents on EC2 in your own AWS account. Buildkite’s own open-source template for autoscaling agents on EC2; it suits Buildkite customers that keep builds inside their AWS account.
Which CI systems does Elastic CI Stack for AWS work with?
Elastic CI Stack for AWS runs jobs for Buildkite, on Linux, Windows, x64 and arm64.
How does Elastic CI Stack for AWS isolate jobs?
Elastic CI Stack for AWS documents its isolation as: 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.
Is Elastic CI Stack for AWS open source?
Yes (MIT). It can be self-hosted.
How much does Elastic CI Stack for AWS cost?
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. Check the official pricing page for current rates.
How do you set up Elastic CI Stack for AWS?
Launch the CloudFormation template (or the Terraform module) with a Buildkite agent token, then set parameters such as instance types and the minimum and maximum number of instances.
Does Elastic CI Stack for AWS support ARM64 runners?
Yes, Elastic CI Stack for AWS documents arm64 runners (Linux and Windows).
How many jobs can run at once on Elastic CI Stack for AWS?
Template defaults are MinSize 0 and MaxSize 10 instances with one agent per instance; all three are configurable.
Where do Elastic CI Stack for AWS runners run?
All AWS Regions except China and US GovCloud.
Where is Buildkite Pty Ltd based?
Buildkite Pty Ltd, the organisation behind Elastic CI Stack for AWS, is headquartered in Melbourne, Victoria, Australia. That is where the company is based, not where jobs run; for that, see the regions listed for Elastic CI Stack for AWS.
What are the alternatives to Elastic CI Stack for AWS?

Sources

  1. github.com/buildkite/elastic-ci-stack-for-aws
  2. github.com/buildkite/elastic-ci-stack-for-aws/releases
  3. github.com/buildkite/elastic-ci-stack-for-aws/blob/main/Licence.md
  4. github.com/buildkite/elastic-ci-stack-for-aws/blob/main/templates/aws-stack.yml
  5. buildkite.com/docs/agent/self-hosted/aws/elastic-ci-stack
  6. buildkite.com/docs/agent/self-hosted/aws/elastic-ci-stack/ec2-linux-and-windows
  7. buildkite.com/about/legal/privacy-policy/

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