AWS athena documentation change
Summary
Removed KMS policy example for encrypted Data Catalog access
Security assessment
Encryption policy example removal doesn't indicate security remediation. Appears to be documentation simplification rather than security-related change.
Diff
diff --git a/athena/latest/ug/access-encrypted-data-glue-data-catalog.md b/athena/latest/ug/access-encrypted-data-glue-data-catalog.md index 28f88563f..d1fd069ff 100644 --- a//athena/latest/ug/access-encrypted-data-glue-data-catalog.md +++ b//athena/latest/ug/access-encrypted-data-glue-data-catalog.md @@ -11,22 +10,0 @@ If the AWS Glue Data Catalog is encrypted, you must add the following actions to -JSON - - -**** - - - - { - "Version": "2012-10-17", - "Statement": { - "Effect": "Allow", - "Action": [ - "kms:GenerateDataKey", - "kms:Decrypt", - "kms:Encrypt" - ], - "Resource": "(arn of the key used to encrypt the catalog)" - } - } - - -