Data Residency

What is Data Residency?

Data Residency allows app customers to have greater control over where their data is stored. This is beneficial for organizations that need to meet regulatory compliance requirements.

What data is in-scope?

All application data related to your JEMH Cloud installation is in-scope for Data Residency. See https://thepluginpeople.atlassian.net/wiki/spaces/JEMHC/pages/3510763521 for more details on what this data consists of and how it’s stored.

Where is my app data located?

Existing installations

App data is located in the US. The ability to relocate your JEMH Cloud app data when you change your Jira product location is coming soon!

New installations

Where app data for new installations will be located depends on if the host Jira product is pinned to a location. For more information on product pinning, see Atlassian’s documentation: https://support.atlassian.com/security-and-access-policies/docs/understand-data-residency/ .

Atlassian product location	JEMH Cloud app data location

Atlassian product location	JEMH Cloud app data location
Not pinned to a product location	US (Virginia) AWS region
EU or DE	EU (Frankfurt) AWS region
US	US (Virginia) AWS region
All other product locations	US (Virginia) AWS region

What about other regions?

Currently we support EU (Frankfurt) and US (Virginia) AWS regions. If you require data residency in a region that we don’t currently support, please let us know via our support channel: https://thepluginpeople.atlassian.net/wiki/spaces/PP/pages/34439179.

How do I select where app data is pinned?

Currently, Atlassian does not support the ability to customise where App configuration data is stored. In order for your data to be stored in a given region, your Jira site must already be pinned to one of the above regions.

If your site is not pinned to a given region, the default (US) will be used. The current list of available regions for pinning are displayed in https://support.atlassian.com/security-and-access-policies/docs/understand-data-residency/#What-are-locations-and-AWS-regions. Please refer to the above table to ensure your app data is installed as expected.

Example 1: No region pinning

The installation will point to default, and app data will be stored in the US region

Example 2: DE region pinning

The installation will point to DE and app data will be stored in the DE region.

Example 1: IN region pinning

The installation will point to default, due to the app not currently supporting IN region, so app data will be stored in the US region.

If you do not wish to use the default US region, you must be pinned to an eligible region based on the above table (EU or DE).

Migrating an existing JEMHC instance data

As yet we do not have a region migration tool, the only way to export anything is through app feature specific exports (Profiles, Test Cases, Templates):

Export what config you can (profiles / test cases / template sets) for later use, take screenshots of notification config screens, mailbox handler config etc.
JEMHC must be uninstalled prior to migration, otherwise the migrated Jira will still point to the original (typically USA) app location. Uninstalling JEMHC also prevents mail retrieval ahead of the migration. We retain that data for 30days so you could reinstall JEMHC if the migration failed and a rollback is needed - no JEMHC data loss will occur if this is done within 30days!
After migration, reinstall JEMHC to get a fresh install in the target region.
Import saved profiles / test cases / template sets if required
Reconfigure all inbound/outbound connections, handlers and notification mappings
When changing regions ensure you update any firewall rules you have in place, as we have different outbound IP addresses (2 for multi-AZ) for each geographical region, see https://thepluginpeople.atlassian.net/wiki/spaces/JEMHC/blog/2024/03/13/4123918353 .