We are happy to announce that you can now start your journey to supporting data residency on Connect. Apps can now install into a preferred region when supported, the first step of supporting data residency. Documentation can be found here.
With Atlassian data residency, Atlassian organization administrators can specify that subsets of their primary data at rest are hosted in our EU or US realms. We use the term ‘realm’ to indicate that their in-scope data is hosted within a geographical boundary.
Our current available realms are:
- Global: In-scope data is hosted within regions determined by Atlassian. We may move data between regions as needed.
- EU: In-scope data is hosted within the Frankfurt and Dublin AWS regions.
- US: In-scope data is hosted within the US East and US West AWS regions.
You can find out more about Atlassian’s data residency policy here.
Customers now have the option to have their in-scope data stored in specific realms and apps can declare which regions they support by setting region-specific base URLs in their app descriptors. Atlassian will use these details when the app is installed, to route the installation request to the specified regions. Partners are free to structure their European or US realm as they need, but they will need to communicate that structure to end users.
In the future, Atlassian will be adding more guidance on requirements for partners to support data residency such as mandatory data residency policy documents, and the ability to support realm to realm migrations. The work being done for the Connect framework is happening alongside work to help Forge support data residency by utilising hosted storage. Much of the complexity from an architectural standpoint will be managed by Atlassian for Forge apps. The introduction of a new region, for example, would not require additional engineering on Forge.
For some apps remaining on the Connect platform, we are currently designing this migration process and have set out a possible plan below here. Please check it out and provide your input to shape how this will be implemented.