Restore access to your CMK encryption keys
CMK gives greater control over encryption keys to protect your Atlassian Cloud data. Currently you can create only one CMK encryption (policy) per organization for all data in scope. Customers not using BYOK can enroll in CMK. BYOK customers will eventually be migrated to CMK.
After the revocation of KMS key access and the suspension of sites, Atlassian is able to help reinstate the suspended sites within 10 days with potential data loss up to one hour. However, if the revocation period extends beyond 20 days, we may be unable to fully recover your data. Understand how to revoke access to your KMS keys.
To restore Atlassian access to your KMS key(s):
Log in to your AWS console. If you need help with your AWS account, contact AWS support.
Choose a region that you have chosen for Atlassian CMK.
Go to the Key Management Service console.
Select Customer Managed Keys from the left navigation bar, and you will see a list of available KMS keys.
Select the key for enabling, that takes you to the details page to expose more options.
Select the Key actions from the drop-down list at the top right corner.
Select Enable.
If you have previously chosen a dual-region realm for hosting your CMK-enabled app instances, i.e. United States or Europe, repeat the above steps for both regions.
8. Inform Atlassian to initiate the restoration process. Do this via the same support ticket we created for your organization when your KMS key access was revoked.
Post-revocation, if you submit a restoration request through a support ticket, the process is generally completed within two business days after the ticket is addressed. However, this timeframe may vary based on the volume of data and the specific patterns associated with the case.
Was this helpful?