Skip to content

Commit dcebd0b

Browse files
Clarify TDE cannot be disabled once enabled
Updated the TDE section in the CMEK doc to make it explicit that: - Once TDE is enabled, it cannot be disabled. - If a customer wants to disable it, they must create a new instance and migrate data. This change is intended to avoid confusion for users asking if TDE can be turned off.
1 parent fb83919 commit dcebd0b

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

docs/cloud/security/cmek.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,7 @@ Enhanced encryption is currently available in AWS and GCP services. Azure is com
1919

2020
## Transparent Data Encryption (TDE) {#transparent-data-encryption-tde}
2121

22-
TDE must be enabled on service creation. Existing services cannot be encrypted after creation.
22+
TDE must be enabled on service creation. Existing services cannot be encrypted after creation. Once TDE is enabled, it cannot be disabled. All data in the service will remain encrypted. If you want to disable TDE after it has been enabled, you must create a new service and migrate your data there.
2323

2424
1. Select `Create new service`
2525
2. Name the service

0 commit comments

Comments
 (0)