AWS quicksight documentation change
Summary
Updated key rotation documentation and added reference to encryption guide
Security assessment
Improves clarity around encryption key management best practices but doesn't indicate vulnerability remediation.
Diff
diff --git a/quicksight/latest/user/customer-managed-keys-change-default-key.md b/quicksight/latest/user/customer-managed-keys-change-default-key.md index 63ed77366..a078989fe 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,3 @@ -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. +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 QuickSight data is encrypted on the new key. The new default key changes how new QuickSight data is encrypted. However, existing QuickSight data will continue to use the previous default key. + +To learn more about which data can be managed with the key, see [Encrypting your QuickSight data with AWS Key Management Service customer-managed keys](./customer-managed-keys.html).