- Newest
- Most votes
- Most comments
Based on the AWS CodeBuild documentation, to use Amazon Linux 2023 for your CodeBuild-hosted GitHub Actions runner, you need to make specific configuration choices in your runner setup.
For EC2 compute with Amazon Linux 2023, you should use one of these configurations:
- For x86_64 architecture:
- Environment type:
linux - Image identifier:
5.0 - Platform: Amazon Linux 2023
- Resolved image:
aws/codebuild/amazonlinux-x86_64-standard:5.0
- Alternatively, for EC2 instances:
- Environment type:
linux-ec2 - Image identifier:
latest - Platform: Amazon Linux 2023
- Resolved image:
aws/codebuild/ami/amazonlinux-x86_64-base:latest
- For ARM architecture:
- Environment type:
arm - Image identifier:
3.0 - Platform: Amazon Linux 2023
- Resolved image:
aws/codebuild/amazonlinux-aarch64-standard:3.0
The issue you're experiencing might be because you're using the image identifier aws/codebuild/ami/amazonlinux-x86_64-base:latest directly, rather than using the environment type and image identifier combination that maps to AL2023.
When configuring your runner, make sure you're using the proper label overrides in your configuration file. For GitHub Actions runners, you would specify these values in the runner configuration where you set up the CodeBuild-hosted runner.
If you're still experiencing issues after making these changes, it could be related to regional availability or a specific limitation with the runner implementation.
Sources
Compute images supported with the CodeBuild-hosted GitHub Actions runner - AWS CodeBuild
EC2 compute images - AWS CodeBuild
Compute images supported with the CodeBuild-hosted GitLab runner - AWS CodeBuild
Relevant content
- asked 5 months ago

Unfortunately, this still doesn’t solve my problem. Here’s what I’ve observed:
aws/codebuild/ami/amazonlinux-x86_64-base:latestamzn2, not AL2023.What I’ve tried already:
image:linux-5.0) directly in theruns-onsection of my GitHub Actions workflow file, per AWS docs and advice here.What I’m looking for: