AWS quicksight documentation change
Summary
Updated terminology from 'KMS keys' to 'AWS KMS keys' in one instance
Security assessment
The change is a minor terminology update and does not address any specific security issues or add new security documentation
Diff
diff --git a/quicksight/latest/user/customer-managed-keys-change-default-key.md index 9711f1189..63ed77366 100644 --- a/quicksight/latest/user/customer-managed-keys-change-default-key.md +++ b/quicksight/latest/user/customer-managed-keys-change-default-key.md @@ -7 +7 @@ -You can change the default key to another key that already exists in the **KMS keys** dashboard. When you change the default key, all new datasets created in SPICE are encrypted on the new key. The new default key changes how new SPICE datasets are encrypted. However, existing datasets continue to use the previous default key until the dataset is fully refreshed. To encrypt the dataset with a new default key, perform a full refresh on the dataset. +You can change the default key to another key that already exists in the **KMS keys** dashboard. When you change the default key, all new SPICE datasets are encrypted on the new key. The new default key changes how new SPICE datasets are encrypted. However, existing datasets continue to use the previous default key until the dataset is fully refreshed. To encrypt the dataset with a new default key, perform a full refresh on the dataset. @@ -13 +13 @@ You can change the default key to another key that already exists in the **KMS k - 2. On the **KMS keys** page, choose **MANAGE** to open the **KMS keys** dashboard. + 2. On the **AWS KMS keys** page, choose **MANAGE** to open the **KMS keys** dashboard.