Skip to content

Commit e34be36

Browse files
Apply suggestion from @gemini-code-assist[bot]
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
1 parent 72c7f8e commit e34be36

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

tidb-cloud/premium/tidb-cloud-encrypt-cmek-premium.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -23,7 +23,7 @@ To provide the highest level of data security, {{{ .premium }}} TiDB adopts a tw
2323
- Unlike default storage encryption, this feature can be managed by users, allowing you to choose either a Customer-Managed Encryption Key (CMEK) or a Service-Managed Encryption Key based on your security compliance and operational requirements.
2424

2525

26-
#### Backup & Restore Description
26+
#### Backup and restore description
2727
When Dual-layer Data Encryption is enabled, the backup data for your {{{ .premium }}} TiDB instance is also encrypted. Any new instance restored from this backup will natively inherit the encryption attributes and KMS master key of the original instance.
2828

2929
Since accessing the backup data relies on the originally configured KMS master key, please ensure the following:

0 commit comments

Comments
 (0)