Hi Everyone!
As we work to roll out Data Residency for Standard and Premium, we're taking a second look at two terms that we've been using:
- Regions: most closely related to an AWS Region
- Realms: A geographical boundary that may consist of one or more regions
We've discovered using these two has lead to some confusion, we've had to define them, and we haven't been entirely consistent with our usage of them either. We've proposed a few ideas internally, and wanted to get your feedback on one that we've landed on.
- Location: The geographical boundary you choose for Data Residency (dropdown)
- AWS Region: The actual AWS regions that support your chosen location
So for example, you might choose the location of EU, which would be supported by the AWS Regions: Frankfurt, Germany & Dublin, Ireland. If we offer Data Residency in Germany alone, you may choose the location "Germany" which would be supported by the AWS Region, Germany.
This would be reflected in our UI and documentation. And would look like the following example in the Admin section for Data Residency.
The goal for this is to be far more intuitive and transparent, but also get around some of the odd things where you may have 1 country with multiple regions (Like the US, which has US-East & US-West), you may have a continent with multiple countries, each with their own region, or you may have a single country with a single region in it now, that may have multiple regions in the future (such as Australia, with Sydney now and Melbourne eventually).
Additionally, the word "location" feels relatively intuitive, and by stating the AWS Region, you know exactly what that means from an AWS architecture standpoint.
Thanks for any feedback!
