Use Customer-managed keys in cross tenancy clones and cross tenancy Autonomous Data Guard
- Services: Autonomous Database Serverless
- Release Date: December 02, 2025
When a source database uses customer-managed encryption keys, you have several options for specifying the encryption key type and location for a cross tenancy clone.
See Cross Tenancy Cloning Encryption Key Options.
When you add an Autonomous Data Guard cross tenancy standby, if the Primary database uses a customer-managed encryption key, you can use the same key in the standby.
See Cross Tenancy Autonomous Data Guard with Customer-Managed Encryption Keys.
Currently, this feature is available in all OC1 regions excluding:
- US East: Ashburn (IAD)
- US Midwest: Chicago (ORD)
- US West: Phoenix (PHX)
- Australia East: Sydney (SYD)
- Australia Southeast: Melbourne (MEL)
- Japan East: Tokyo (NRT)
- Japan Central: Osaka (KIX)
- Brazil East: Sao Paulo (GRU)
- Brazil Southeast: Vinhedo (VCP)
- Saudi Arabia West: Jeddah (JED)
- Saudi Arabia Central: Riyadh (RUH)
- UK South: London (LHR)
- Germany Central: Frankfurt (FRA)