TechPrufer
Get started
Atlassian
Atlassian logoAtlassian · Feature trail

App Data Residency

2 posts · Dec 2023 – Nov 2024

What this trail covers

Atlassian Marketplace partners are implementing data residency for their apps, enabling customers to keep their data in a region they trust. This involves supporting realm pinning and realm migration, with partners sharing their motivations, supported regions, and technical approaches to infrastructure setup, region-specific base URLs, and handling Connect lifecycle requests. Challenges include managing region-specific base URLs, handling Connect lifecycle requests for region identification, and the introduction of a new 'Runs on Atlassian' badge for Forge apps that do not transmit data outside the Atlassian environment and provide data residency.

All Atlassian trails
  1. Runs on Atlassian Gives Partners a New Way to Showcase Strict Data ProtectionsIntroduces the 'Runs on Atlassian' badge for Forge apps that meet specific criteria: no data egress (no external resource domains, remotes, or Connect modules declared in the manifest) and data residency-enabled storage (Forge storage or entity properties). Details how Forge blocks data egress by default and provides customer controls for logs. Explains that the badge will be automatically detected and applied. Provides guidance for partners on checking their manifest files for egress permissions and removing unnecessary declarations. Highlights recent updates to the CDN and Forge Node.js runtime that reduce the need for egress declarations for media links and API redirects. Mentions the distinction between 'Runs on Atlassian' and 'Cloud Fortified' badges.
  2. Implementing app data residency: perspectives from JXL, ScriptRunner and Codefortynine - Inside AtlassianThis post details how three Atlassian Marketplace Partners (JXL, ScriptRunner, and codefortynine) implemented data residency for their apps. It covers their motivations for supporting data residency (customer experience, data protection, compliance with Atlassian's roadmap), the regions they support (US, EU, Germany, Global), and their technical approaches to realm pinning (infrastructure setup in different AWS regions, managing region-specific base URLs, handling Connect lifecycle requests) and realm migration (internal APIs for sending/retrieving data between realms, asynchronous process with permutations and edge cases, unit and integration testing, handling EU/Germany region overlap).