Skip to content

fix: support runner subnets in the same availability zone - #5304

Open
Quindrix wants to merge 1 commit into
github-aws-runners:mainfrom
Quindrix:support-multiple-subnets-in-az
Open

fix: support runner subnets in the same availability zone#5304
Quindrix wants to merge 1 commit into
github-aws-runners:mainfrom
Quindrix:support-multiple-subnets-in-az

Conversation

@Quindrix

@Quindrix Quindrix commented Aug 27, 2026

Copy link
Copy Markdown
Contributor

Description

This PR allows runner subnets to exist in the same AZ. It groups the configured subnets into safe combinations and distributes runner capacity across separate fleet requests. If a request encounters a retryable capacity failure, the remaining capacity is carried forward to the next available subnet combination.

It also adds the required ec2:DescribeSubnets permissions and updates the documentation to remove the previous requirement that every subnet must be in a different AZ. Dedicated-host and explicit subnet override behaviour remains unchanged.

Test Plan

  • Unit tests were added for subnet grouping, capacity distribution, and retryable failures. All 71 EC2 runner tests pass, along with the ESLint and Prettier checks.
  • Used these changes in our environment and were able to provide two subnets in the same AZ without issue.

Related Issues

Fixes #5297, and follows on from #2904

Group subnets into AZ-safe fleet requests and distribute capacity across them.
Carry retryable failures forward to alternative subnets and add the required
DescribeSubnets permissions.
@Quindrix
Quindrix requested review from a team as code owners August 27, 2026 10:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Support multiple subnets in the same AZ

1 participant