Skip to content

Conversation

@milldr
Copy link
Member

@milldr milldr commented Jan 22, 2026

what

  • Added new "Reference Architecture Component Availability" section to the primary AWS region design decision
  • Document that RunsOn depends on AWS App Runner, which is only available in 11 regions
  • Call out us-west-1 specifically as unsupported
  • Explain cost implications ($80/month) and alternatives for unsupported regions

why

Teams choosing their primary AWS region need to understand that reference architecture components like RunsOn have their own regional constraints. This guidance helps prevent costly mistakes like deploying to us-west-1 and discovering App Runner isn't available, which would require expensive cross-region Transit Gateway connections.

references

…ision

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 <noreply@anthropic.com>
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 <noreply@anthropic.com>
@milldr milldr merged commit d154ff6 into master Jan 22, 2026
3 checks passed
@milldr milldr deleted the milldr/runson-region-availability branch January 22, 2026 21:34
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.

3 participants