Confluence Cloud Developer

Confluence Cloud Developer

Last updatedNov 9, 2020

Rate this page:

Data residency

For more details on data residency and a glossary of terms see Manage data residency.

Atlassian data residency enables Atlassian organization administrators to specify where subsets of their product data at rest are hosted. Known as realms, administrators can choose between:

  • Global: In-scope data is hosted within regions determined by Atlassian: data may be moved 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.

Data residency and Atlassian Marketplace apps

To support data residency apps declare region-specific base URLs in their app descriptors. Atlassian uses these details when the app is installed, to route the installation request to the specified regions.

The change to the descriptor is not compulsory, you can choose to maintain your app as-is. However, if you choose not to support regional data storage customers with stringent region requirements may not be able to install your app.

Enable data residency

To enable an app to use data residency:

  • Add a regionBaseUrls field to the app descriptor.
  • Add a key-value pair for the region the app is hosted in and it's corresponding baseUrl.

The regionBaseUrls field follows the same standards as the app’s main baseUrl field. The supported region keys are “EU” and “US”.

The URLs listed in the following example are the address of the app within the given region, and the app will store all data at rest within that region.

1
2
3
4
5
6
7
{
  ...
  "regionBaseUrls": {
    "US": "https://us.your.sample.app.com",
    "EU": "https://eu.your.sample.app.com"
  }
}

Customers who chose a single realm require an app to list that realm in its list of supported regions. For example, a customer who chooses US data residency requires a URL that specifies the US:

1
2
3
"regionBaseUrls": { 
  "US": "https://us.your.sample.app.com"
}

or a list of URLs that include the US:

1
2
3
4
"regionBaseUrls": { 
  "US": "https://us.your.sample.app.com",
  "EU": "https://eu.your.sample.app.com" 
}

Customers who don’t have a data residency requirement, but are provisioned in the EU or US for performance reasons install into the nearest supported region. This may provide performance improvements for end users.

To support data resident customers, you may need to spin up stacks outside of your current infrastructure then create databases for EU and US regions, depending on how your app is structured. If you choose to support data residency, you’ll need to support the ability to migrate between realms.

Also, you must also provide a data residency policy, similar to the Atlassian Data Residency policy, and update any of your other customer policies affected.

at

Rate this page: