How does data residency work in the Atlassian Cloud?
As we explained in our article on data residency, data residency is a concept of Cloud computing where the geographic location of the data is determined. If you work in highly regulated industries, such as the financial sector, data residency may be necessary to run a Cloud application in the first place.
Thanks to Atlassian’s concept, it is possible for Jira Software, Jira Service Management and Confluence to choose the location where your in-scope product data is stored.
These locations are available for selection
Global – all Atlassian Clouds in the AWS region
Australia – Sydney AWS region
EU – Frankfurt and Dublin AWS regions
USA – USA East and USA West
Germany – Frankfurt AWS Region
In-Scope Product Data
Atlassian provides an overview of in-scope product data, which can be pinned and which cannot be pinned.
|Product||✅ Can be pinned||❌ Can’t be pinned|
|Jira Service Management||
Note: All analytics data is hosted in Atlassian’s US location!
Also, Atlassian Marketplace apps are not covered by Atlassian data residency.
Read more information in Atlassian’s guide here: Understand data residency.
Why can’t user account data be pinned?
Atlassian stores user account information in a central identity service and a controlled small group of replica services. Account information data is hosted globally to meet Atlassian customers’ agile performance requirements. By limiting the digital footprint in the system, information is not stored directly in the product. Instead, Atlassian uses representative IDs that can be used to retrieve the data from identity services.