How to avoid storing sensitive data in AWS cloud

[Matthias Moll]

Customer specific sensitive data will be stored in Jira AWS cloud if stored as an attachment or discussed within Jira issues.

However, customers may prohibit sensitive data from being stored in data centers that are subject to the U.S. Cloud Act, which is the case with AWS.

Is there a way to prevent this by at least storing the attachments locally in an automated way so that they are no longer embedded in the issue but linked?

Is there a solution planned in Jira Software to deal with this issue in principle?

[Nic Brough -Adaptavist- · Accepted solution]

Welcome to the Atlassian Community!

Generally, the answer is a simple "no" - attachments uploaded to Atlassian software are stored in the location that the Cloud system is running.

See https://support.atlassian.com/security-and-access-policies/docs/understand-data-residency/ and see how you can "pin" most of your data (including attachments) to a specific AWS region 

But there are some apps in the marketplace that let you move the attachment storage to other systems, which you could have more control over.

[Matthias Moll]

Thanks for clarification!