Skip to content

Commit 7d9309d

Browse files
Update tidb-cloud/premium/tidb-cloud-encrypt-cmek-aws-premium.md
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
1 parent 3c20daa commit 7d9309d

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -137,7 +137,7 @@ If the backup is encrypted using a CMEK, you must verify that the new instance c
137137

138138
1. The key ARN will remain unchanged. Click **Check** to proceed with the trust policy verification.
139139
2. The system will check if the authorized TiDB Cloud account in the key policy matches the one associated with the original backup.
140-
3. If the TiDB Cloud account in the key policy is the same as the TiDB Cloud account associated with the original backup TiDB instance, no further authorization is required
140+
3. If the TiDB Cloud account in the key policy is the same as the TiDB Cloud account associated with the original backup TiDB instance, no further authorization is required.
141141
4. If the TiDB Cloud account in the key policy is different from the TiDB Cloud account associated with the original backup TiDB instance, you must copy the provided key policy and update it in your AWS KMS. This re-authorizes the key and ensures the new instance can access it.
142142

143143
#### Service-Managed Encryption Key

0 commit comments

Comments
 (0)