@layerborn/cdk-github-runners

GitHub Self-Hosted Runners CDK Constructs

Use this CDK construct to create ephemeral self-hosted GitHub runners on-demand inside your AWS account.

• Easy to configure GitHub integration with a web-based interface
• Customizable runners with decent defaults
• Multiple runner configurations controlled by labels
• Everything fully hosted in your account
• Automatically updated build environment with latest runner version

Self-hosted runners in AWS are useful when:

• You need easy access to internal resources in your actions
• You want to pre-install some software for your actions
• You want to provide some basic AWS API access (but aws-actions/configure-aws-credentials has more security controls)

Ephemeral (or on-demand) runners are the recommended way by GitHub for auto-scaling, and they make sure all jobs run with a clean image. Runners are started on-demand. You don't pay unless a job is running.

API

The best way to browse API documentation is on Constructs Hub. It is available in all supported programming languages.

Providers

A runner provider creates compute resources on-demand and uses actions/runner to start a runner.

	EC2	CodeBuild	Fargate	Lambda
Time limit	Unlimited	8 hours	Unlimited	15 minutes
vCPUs	Unlimited	2, 4, 8, or 72	0.25 to 4	1 to 6
RAM	Unlimited	3gb, 7gb, 15gb, or 145gb	512mb to 30gb	128mb to 10gb
Storage	Unlimited	50gb to 824gb	20gb to 200gb	Up to 10gb
Architecture	x86_64, ARM64	x86_64, ARM64	x86_64, ARM64	x86_64, ARM64
sudo	✔	✔	✔	❌
Docker	✔	✔ (Linux only)	❌	❌
Spot pricing	✔	❌	✔	❌
OS	Linux, Windows	Linux, Windows	Linux, Windows	Linux

The best provider to use mostly depends on your current infrastructure. When in doubt, CodeBuild is always a good choice. Execution history and logs are easy to view, and it has no restrictive limits unless you need to run for more than 8 hours.

You can also create your own provider by implementing IRunnerProvider.

Installation

• Confirm you're using CDK v2
• Install the appropriate package
  • Python

    pip install layerborn.cdk-github-runners
    

  • TypeScript or JavaScript

    npm i @layerborn/cdk-github-runners
    

  • Java

    <dependency>
    <groupId>com.layerborn</groupId>
    <artifactId>cdk.github.runners</artifactId>
    </dependency>
    

  • Go

    go get github.com/layerborn/cdk-github-runners-go/layerborncdkgithubrunners
    

  • .NET

    dotnet add package layerborn.Cdk.Github.Runners
    

• Use GitHubRunners construct in your code (starting with default arguments is fine)
• Deploy your stack
• Look for the status command output similar to aws --region us-east-1 lambda invoke --function-name status-XYZ123 status.json
• Execute the status command (you may need to specify --profile too) and open the resulting status.json file
• Open the URL in github.setup.url from status.json or manually setup GitHub integration as an app or with personal access token
• Run status command again to confirm github.auth.status and github.webhook.status are OK
• Trigger a GitHub action that has a self-hosted label with runs-on: [self-hosted, linux, codebuild] or similar
• If the action is not successful, see troubleshooting

Customizing

The default providers configured by GitHubRunners are useful for testing but probably not too much for actual production work. They run in the default VPC or no VPC and have no added IAM permissions. You would usually want to configure the providers yourself.

For example:

let vpc: ec2.Vpc;
let runnerSg: ec2.SecurityGroup;
let dbSg: ec2.SecurityGroup;
let bucket: s3.Bucket;

// create a custom CodeBuild provider
const myProvider = new CodeBuildRunner(this, 'codebuild runner', { 
  label: 'my-codebuild',
  vpc: vpc,
  securityGroup: runnerSg,
});
// grant some permissions to the provider
bucket.grantReadWrite(myProvider);
dbSg.connections.allowFrom(runnerSg, ec2.Port.tcp(3306), 'allow runners to connect to MySQL database');

// create the runner infrastructure
new GitHubRunners(this, 'runners', {
   providers: [myProvider],
});

Another way to customize runners is by modifying the image used to spin them up. The image contains the runner, any required dependencies, and integration code with the provider. You may choose to customize this image by adding more packages, for example.

const myBuilder = new CodeBuildImageBuilder(this, 'image builder', {
  dockerfilePath: FargateRunner.LINUX_X64_DOCKERFILE_PATH,
  runnerVersion: RunnerVersion.specific('2.291.0'),
  rebuildInterval: Duration.days(14),    
});
myBuilder.setBuildArg('EXTRA_PACKAGES', 'nginx xz-utils');

const myProvider = new FargateRunnerProvider(this, 'fargate runner', {
  label: 'customized-fargate',
  vpc: vpc,
  securityGroup: runnerSg,
  imageBuilder: myBuilder,
});

// create the runner infrastructure
new GitHubRunners(stack, 'runners', {
  providers: [myProvider],
});

Your workflow will then look like:

name: self-hosted example
on: push
jobs:
  self-hosted:
    runs-on: [self-hosted, customized-fargate]
    steps:
      - run: echo hello world

Windows images must be built with AWS Image Builder.

const myWindowsBuilder = new ContainerImageBuilder(this, 'Windows image builder', {
  architecture: Architecture.X86_64,
  os: Os.WINDOWS,
  runnerVersion: RunnerVersion.specific('2.291.0'),
  rebuildInterval: Duration.days(14),    
});
myWindowsBuilder.addComponent(new ImageBuilderComponent(this, 'Ninja Component',
  {
    displayName: 'Ninja',
    description: 'Download and install Ninja build system',
    platform: 'Windows',
    commands: [
      'Invoke-WebRequest -UseBasicParsing -Uri "https://github.com/ninja-build/ninja/releases/download/v1.11.1/ninja-win.zip" -OutFile ninja.zip',
      'Expand-Archive ninja.zip -DestinationPath C:\\actions',
      'del ninja.zip',
    ],
  }
));

const myProvider = new FargateRunnerProvider(this, 'fargate runner', {
  label: 'customized-windows-fargate',
  vpc: vpc,
  securityGroup: runnerSg,
  imageBuiler: myWindowsBuilder,
});

// create the runner infrastructure
new GitHubRunners(stack, 'runners', {
  providers: [myProvider],
});

Architecture

Troubleshooting

• Always start with the status function, make sure no errors are reported, and confirm all status codes are OK
• If jobs are stuck on pending:
  • Make sure runs-on in the workflow matches the expected labels set in the runner provider
  • If it happens every time, cancel the job and start it again
• Confirm the webhook Lambda was called by visiting the URL in troubleshooting.webhookHandlerUrl from status.json
  • If it's not called or logs errors, confirm the webhook settings on the GitHub side
  • If you see too many errors, make sure you're only sending workflow_job events
• When using GitHub app, make sure there are active installation in github.auth.app.installations
• Check execution details of the orchestrator step function by visiting the URL in troubleshooting.stepFunctionUrl from status.json
  • Use the details tab to find the specific execution of the provider (Lambda, CodeBuild, Fargate, etc.)
  • Every step function execution should be successful, even if the runner action inside it failed

Other Options

• philips-labs/terraform-aws-github-runner if you're using Terraform
• actions/actions-runner-controller if you're using Kubernetes