Using Your Own Encryption Key in OCI Database with PostgreSQL
Maintain control over your encryption keys by using your own key when running OCI Database with PostgreSQL.
To use this use your own encryption key with a database system, you must define a policy in the root compartment of your tenancy using the following examples:
ALLOW any-user TO use keys IN tenancy WHERE ANY {request.principal.type='postgresqldbsystem', request.principal.type='postgresqlbackup'}
ALLOW any-user TO use key-delegates in tenancy WHERE ANY {request.principal.type='postgresqldbsystem', request.principal.type='postgresqlbackup'}
Using Your Own Encryption when Creating a Database System
Changing the Encryption Key for an Existing Database System
Disabling and Reenabling a Database System's Encryption Key
To reenable a disabled encryption key, following same steps and select Enable from the Actions menu.
You must restart the database system using the CLI after reenabling its encryption key. You can restart the database system immediately after reenabling the encryption key.
Using Your Own Encryption Key with Database System Backups
Backups automatically retain the encryption key from the database system from which they were created. The encryption key used is displayed in the backup's details page for Encryption key. You can't change the encryption key of a backup.
When you restore a database system from a backup, the restored database system retains the same encryption key used in the backup. After the restoration is complete, you can change the encryption key of the restored database system.
If you're creating a new database system from a backup, you can add or update an encryption key. For more information, see Creating a Database System from a Backup.