Data Residency
All new Jira and Confluence Cloud customers can choose the location where their instance is hosted, including all stored data related to that instance. These locations are known as the realms, or localities, that customers can choose to pin their data to, provided they are compliant with any legislation in their chosen region (ex, GDPR in the European Union). You can find more information on locations and associated AWS regions that Atlassian offers here.
ScriptRunner for Jira and Confluence Cloud offers hosting in:
- Germany (Frankfurt)
- the European Union (Frankfurt)
- the USA (Oregon)
The location of ScriptRunner data residency will match that of your Jira or Confluence instance if you chose one of these regions.
What is data residency?
Data residency refers to the physical location where an organization's data is hosted. To understand the term Data Residency and how it relates to your instance of ScriptRunner for Jira and Confluence Cloud, we can outline the benefits it provides and break it down into its component parts.
Refer to Atlassian's data residency documentation for more details.
Benefits of data residency
Data residency gives organizations more control over their data by ensuring their user-generated content is stored within the US (Oregon), Germany (Frankfurt), or European Union (Frankfurt). Companies that work in regulated industries like finance, government, or healthcare may need data residency to operate in a cloud environment.
Data
All script data, including Behaviour scripts, is stored within ScriptRunner for Jira Cloud and Jira.
The data that is stored includes:
- All scripts, script variables, and ScriptRunner-related configurations (script fragments, scripted fields)
- The logs generated by any scripts. These are stored in whole in the specific region/realm where their Jira or Confluence instance is pinned. Note: Metadata about scripts that have run (ex. duration, errors, how long the REST api request took) is stored globally.
When migrating from Jira Data Center to Jira Cloud using the Jira Cloud Migration Assistant (JCMA), ScriptRunner configuration data migrates as part of your Jira data.
According to Atlassian, migration data is temporarily stored in transit in US-WEST or US-EAST for up to 14 days during the migration process. Because ScriptRunner data is embedded within Jira configuration data (for example, Workflow Rules are embedded directly into your workflows), it follows the same migration path.
ScriptRunner does not control where Atlassian stores or routes JCMA migration data during transfer.
Our migration processing services operate in the US (Oregon), Germany (Frankfurt), or European Union (Frankfurt) regions. If your ScriptRunner Cloud data residency is set to US (Oregon), Germany (Frankfurt), or European Union (Frankfurt) then ScriptRunner migration processing will occur in the corresponding region. However, any data handled directly by JCMA during migration remains under Atlassian's control.
Residency
So where does your data reside?
ScriptRunner for Jira and Confluence Cloud installed before June 30th 2021
Your data is stored in the US regardless of where you are geographically located; however, you can change the data residency.
ScriptRunner or Jira and Confluence Cloud installed after 30th June 2021
Your data will be stored in Frankfurt, if your Jira or Confluence instance is pinned to Germany or the European Union; otherwise, it will be stored in the US (Oregon).
If you require data residency hosting in a region that we do not currently provide, please let us know via our suggestion board.
Set locality
Instances of ScriptRunner for Jira and Confluence Cloud installed before 30th June 2021
These instances are automatically stored in the US (Oregon) unless you have pinned your Jira instance to one of the supported regions which are Germany (Frankfurt), the European Union (Frankfurt), or the US (Oregon).
New instances of ScriptRunner for Jira and Confluence Cloud
When ScriptRunner is installed, its data is stored in the European Union (Frankfurt), or Germany (Frankfurt), if your Jira instance is pinned to the European Union or Germany; otherwise, it will be stored in the US (Oregon). For details on how to pin the region, see:
If you are located outside of the US (Oregon), Germany (Frankfurt), or European Union (Frankfurt), for example, in Australia, and select this as your instance location, ScriptRunner for Jira and Confluence Cloud data residency will default to the US (Oregon).
Change locality
You can change the data residency location of your Jira instance and ScriptRunner for Jira/Confluence at any time. For more information on how to perform a data residency move, please refer to Atlassian's documentation.