You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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:
The text was updated successfully, but these errors were encountered: