AWS AmazonRDS documentation change
Summary
Updated terminology from 'KMS permissions' to 'AWS KMS permissions' for clarity
Security assessment
Minor terminology clarification without any security policy changes or vulnerability references.
Diff
diff --git a/AmazonRDS/latest/AuroraUserGuide/USER_PerfInsights.access-control.cmk-policy.md b/AmazonRDS/latest/AuroraUserGuide/USER_PerfInsights.access-control.cmk-policy.md index 69f73b12e..05c43bc87 100644 --- a//AmazonRDS/latest/AuroraUserGuide/USER_PerfInsights.access-control.cmk-policy.md +++ b//AmazonRDS/latest/AuroraUserGuide/USER_PerfInsights.access-control.cmk-policy.md @@ -65 +65 @@ JSON -Performance Insights uses customer managed keys to encrypt sensitive data. When you turn on Performance Insights, you can provide an AWS KMS key through the API. Performance Insights creates KMS permissions on this key. It uses the key and performs the necessary operations to process sensitive data. Sensitive data includes fields such as user, database, application, and SQL query text. Performance Insights ensures that the data remains encrypted both at rest and in-flight. +Performance Insights uses customer managed keys to encrypt sensitive data. When you turn on Performance Insights, you can provide an AWS KMS key through the API. Performance Insights creates AWS KMS permissions on this key. It uses the key and performs the necessary operations to process sensitive data. Sensitive data includes fields such as user, database, application, and SQL query text. Performance Insights ensures that the data remains encrypted both at rest and in-flight.