Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions modules/ROOT/pages/security/encryption.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -85,6 +85,11 @@ When using a Customer Managed Key within Aura to encrypt one or more Aura databa
If you no longer need to use this Customer Managed Key to encrypt Aura databases, first delete the Aura database instances that are encrypted with the key, then you can remove the key from Aura.
Keep in mind that this process only breaks the link between the key and Aura - it does not delete the actual key from the Cloud KMS.

== Region requirements

The Customer Managed Key must be created in the same region as your Aura instance. This applies to AWS, Azure, and GCP.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
The Customer Managed Key must be created in the same region as your Aura instance. This applies to AWS, Azure, and GCP.
The Customer Managed Key must be created in the same region as your Aura instance.
This applies to AWS, Azure, and GCP.

For Azure, both the key vault and the Customer Managed Key must be in the same region as the Aura instance.

== AWS keys

=== Create an AWS key
Expand Down