Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add multi-region support for cases that don't rely only on a primary and secondary region #631

Open
diego-ojeda-binbash opened this issue Sep 25, 2024 · 0 comments

Comments

@diego-ojeda-binbash
Copy link
Contributor

Describe the Feature

Currently the reference architecture supports a primary and secondary region which works for most cases. However, as clients scale up their businesses, they might face scenarios where they need to deploy their workloads to other regions, in order to address latency issues or to adhere to compliance requirements.
Such scenarios require a redesign of the reference architecture in order to support, at least, the following cases:

  • Multi-region resource stacks
  • Terraform state buckets in the same region as the resources they reference
  • Automatic injection of the current region in order to remove hardcoded region definitions in the layers
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

No branches or pull requests

1 participant