From ee5e93a3d57328ca88e400a0a1204856cea719f1 Mon Sep 17 00:00:00 2001 From: milldr Date: Thu, 22 Jan 2026 12:50:02 -0500 Subject: [PATCH 1/2] docs: Add RunsOn regional availability guidance to primary region decision Expand the primary AWS region design decision with specific guidance about reference architecture component availability. Document that RunsOn depends on AWS App Runner (only available in 11 regions) and provide clear cost implications ($80/month) and alternatives for unsupported regions like us-west-1. Co-Authored-By: Claude Haiku 4.5 --- .../decide-on-primary-aws-region.mdx | 31 +++++++++++++++++++ 1 file changed, 31 insertions(+) diff --git a/docs/layers/network/design-decisions/decide-on-primary-aws-region.mdx b/docs/layers/network/design-decisions/decide-on-primary-aws-region.mdx index d2b3ddbb6..c0300c1ff 100644 --- a/docs/layers/network/design-decisions/decide-on-primary-aws-region.mdx +++ b/docs/layers/network/design-decisions/decide-on-primary-aws-region.mdx @@ -49,6 +49,37 @@ certain regions receive platform infrastructure updates slower than others. Also [Local Zones](https://aws.amazon.com/about-aws/global-infrastructure/regions_az/#AWS_Local_Zones) (e.g. `us-west-2-lax-1a`) which operate a subset of AWS services. +See [AWS Regional Services List](https://aws.amazon.com/about-aws/global-infrastructure/regional-product-services/) for +a complete breakdown of service availability by region. + +### Reference Architecture Component Availability + +Beyond standard AWS services, certain components in the reference architecture have their own regional constraints that +should factor into your primary region decision. + +#### RunsOn (Self-Hosted GitHub Runners) + +[RunsOn](/layers/github-actions/runs-on/) is our recommended solution for self-hosted GitHub runners. It relies on +[AWS App Runner](https://aws.amazon.com/apprunner/), which is only available in a subset of AWS regions: + +- `us-east-1`, `us-east-2`, `us-west-2` +- `eu-central-1`, `eu-west-1`, `eu-west-2`, `eu-west-3` +- `ap-south-1`, `ap-southeast-1`, `ap-southeast-2`, `ap-northeast-1` + +Notably, **`us-west-1` does not support App Runner**, and therefore RunsOn cannot be deployed there directly. + +If your primary region doesn't support App Runner, you have two options: + +1. **Deploy RunsOn in a supported region** and connect it to your primary region via Transit Gateway with a cross-region + peering connection. This adds approximately **$80/month** in Transit Gateway cross-region data transfer costs. + +2. **Use an alternative self-hosted runner solution** such as + [Actions Runner Controller (ARC)](/layers/github-actions/tutorials/eks-github-actions-controller/) which runs on EKS + and doesn't have the same regional constraints. + +For most deployments, we recommend choosing a primary region that supports App Runner to avoid the additional +complexity and cost of cross-region connectivity. + ### Instance Types Not all instance types are available in all regions From d2351abba49b75374337dfbdddd20ae95b966cb5 Mon Sep 17 00:00:00 2001 From: milldr Date: Thu, 22 Jan 2026 12:58:42 -0500 Subject: [PATCH 2/2] docs: Simplify RunsOn guidance to focus on Transit Gateway connectivity Remove suggestion to use alternative runner solution. Instead, clarify that if using an unsupported region, you'll need to connect RunsOn via Transit Gateway (recommended) or other connectivity options. Co-Authored-By: Claude Haiku 4.5 --- .../decide-on-primary-aws-region.mdx | 16 ++++++---------- 1 file changed, 6 insertions(+), 10 deletions(-) diff --git a/docs/layers/network/design-decisions/decide-on-primary-aws-region.mdx b/docs/layers/network/design-decisions/decide-on-primary-aws-region.mdx index c0300c1ff..f04eb97cd 100644 --- a/docs/layers/network/design-decisions/decide-on-primary-aws-region.mdx +++ b/docs/layers/network/design-decisions/decide-on-primary-aws-region.mdx @@ -68,17 +68,13 @@ should factor into your primary region decision. Notably, **`us-west-1` does not support App Runner**, and therefore RunsOn cannot be deployed there directly. -If your primary region doesn't support App Runner, you have two options: +If your primary region doesn't support App Runner but you still want to use that region, you'll need to deploy RunsOn +in a supported region and connect it to your primary region. We recommend using Transit Gateway with a cross-region +peering connection for this, though other connectivity options exist. This adds approximately **$80/month** in Transit +Gateway cross-region data transfer costs. -1. **Deploy RunsOn in a supported region** and connect it to your primary region via Transit Gateway with a cross-region - peering connection. This adds approximately **$80/month** in Transit Gateway cross-region data transfer costs. - -2. **Use an alternative self-hosted runner solution** such as - [Actions Runner Controller (ARC)](/layers/github-actions/tutorials/eks-github-actions-controller/) which runs on EKS - and doesn't have the same regional constraints. - -For most deployments, we recommend choosing a primary region that supports App Runner to avoid the additional -complexity and cost of cross-region connectivity. +For most deployments, we recommend choosing a primary region that supports App Runner to avoid this additional +complexity and cost. ### Instance Types