In a past series of articles, I outlined an approach for implementing containerized, self-hosted ephemeral runners on AWS ECS/EC2, with Amazon cluster auto scaling enabled. Maintenance of the final infrastructure …
An ECS cluster, with support for capacity provider FARGATE, is essential in order to run tasks with“Launchtype=AWS Fargate“. The ECS task definition for our Fargate JIT runner will be covered …
Our EventBridge rule includes two (2) targets, i.e.: The runner container extracts the event payload from the queue, and uses the relevant source field values to generate and initialize the …
Our image will be derived from an ubuntu:jammy base, for target architecture type, linux/amd64. After building the image, we’ll push it to an ECR repository. Image Artifacts Create a location …
The ECS Fargate task includes the container definition for our JIT runner, along with the URI of the associated ECR image. A walkthrough for creating a sample task is covered …
Our GitHub webhook is configured to send queued workflow_job events to the following event bus. An EventBridge rule with two (2) targets, will be required for provisioning a JIT runner. …