GitHub’s hosted runner fleet has been expanded to include AWS, letting developers execute workflows across Azure and AWS and cut down queue times.
GitHub Actions now runs jobs on both Azure and AWS, expanding the hosted runner fleet to a true multi‑cloud environment and promising faster, more reliable CI/CD pipelines.
Why a multi‑cloud runner fleet matters
Developers have long relied on GitHub’s Azure‑based runners for on‑demand builds, but growing demand often led to queue spikes and occasional latency. By adding AWS to the mix, GitHub can balance load across two of the world’s largest cloud providers, reducing wait times and providing redundancy if one region experiences issues.
How the new AWS runners work
The AWS runners are built on the same managed infrastructure as the Azure fleet, offering identical OS images, toolchains, and security hardening. When a workflow is triggered, GitHub’s scheduler evaluates capacity across both clouds and dispatches the job to the most available runner, transparently to the user.
- Automatic load‑balancing between Azure and AWS
- Identical runner environments for consistent builds
- Improved fault tolerance with cross‑cloud failover
- Potentially lower queue times during peak usage
Impact on developers and teams
Teams can now expect shorter start‑up latency for large pipelines, especially when one cloud region is saturated. The change also simplifies disaster‑recovery planning, as jobs can continue on the alternate provider without manual intervention.
For organizations already using both Azure and AWS for production workloads, the unified runner fleet aligns CI/CD with existing cloud strategies, making it easier to keep credentials and network policies consistent.
Related coverage: about the rollout in the GitHub Blog changelog: GitHub Actions adds multi‑cloud compute to improve reliability.
Explore related stories in the Infrastructure section on uxc.news.
Track coverage on Momentum · More in Infrastructure.