You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am using custom AMI based on ubuntu24 OS, but the runner is not registering on my github organisation. Below is the script I executed on my instance before creating the AMI.
provider "aws" {
region = "us-east-1"
}
module "github-runner" {
# Terraform downloads this automatically during 'terraform init'
source = "github-aws-runners/github-runner/aws"
version = "7.6.0" # Use the version matching your downloaded zips
aws_region = "us-east-1"
vpc_id = ""
subnet_ids = []
prefix = "gh-ci"
github_app = {
key_base64 = ""
id = ""
webhook_secret = ""
}
# --- AMI Configuration ---
ami = {
owners = ["ACCID"]
filter = { name = ["CUSTOMAMI], state = ["available"] }
}
# --- Pre-baked Settings ---
# 1. Disable the syncer lambda
enable_runner_binaries_syncer = false
# 2. Disable the default userdata scripts that try to install Docker/Git
# In 7.x, setting enable_userdata = false stops the module's default install scripts
enable_userdata = false
runner_as_root = false
# --- Operational Mode ---
instance_types = ["t3.xlarge"]
enable_organization_runners = true
enable_ephemeral_runners = true
# Runner custom label
runner_extra_labels = ["aws-ephemeral"]
# Pointing to the files you manually placed in the folder
webhook_lambda_zip = abspath("${path.root}/lambdas-download/webhook.zip")
runner_binaries_syncer_lambda_zip = abspath("${path.root}/lambdas-download/runner-binaries-syncer.zip")
runners_lambda_zip = abspath("${path.root}/lambdas-download/runners.zip")
}
Is there anything that I am missing here in the configuration.
Even if I don't use custom AMI the runner gets created intermittently.
There is no issue on lambda side lambda is doing its job and launching the instance based on webhook, but post that whatever script suppose to execute, its not happening.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
I am using custom AMI based on ubuntu24 OS, but the runner is not registering on my github organisation. Below is the script I executed on my instance before creating the AMI.
`# 1. Update and install basic tools
sudo apt-get update && sudo apt-get upgrade -y
sudo apt-get install -y git jq unzip curl libicu-dev
2. Install AWS CLI v2
curl "https://awscli.amazonaws.com/awscli-exe-linux-x86_64.zip" -o "awscliv2.zip"
unzip awscliv2.zip
sudo ./aws/install
3. Install Docker
sudo apt-get install -y docker.io
sudo systemctl enable docker
sudo usermod -aG docker ubuntu # Allow the runner to use docker without sudo
4. (Optional but Recommended) Pre-download the Runner Agent
This avoids the "Syncer" step at boot
mkdir actions-runner && cd actions-runner
curl -o actions-runner-linux-x64-2.333.1.tar.gz -L https://github.com/actions/runner/releases/download/v2.333.1/actions-runner-linux-x64-2.333.1.tar.gz
tar xzf ./actions-runner-linux-x64-2.333.1.tar.gz`
And here is my terraform code
Is there anything that I am missing here in the configuration.
Even if I don't use custom AMI the runner gets created intermittently.
There is no issue on lambda side lambda is doing its job and launching the instance based on webhook, but post that whatever script suppose to execute, its not happening.
Beta Was this translation helpful? Give feedback.
All reactions