AWS lex medium security documentation change
Summary
Removed KMS GenerateDataKey policy example from documentation
Security assessment
Removal of explicit kms:GenerateDataKey permission could indicate recognition of over-permissive policies, preventing potential key misuse if followed correctly.
Diff
diff --git a/lex/latest/dg/conversation-logs-encrypting.md b/lex/latest/dg/conversation-logs-encrypting.md index bfce12ef0..928979725 100644 --- a//lex/latest/dg/conversation-logs-encrypting.md +++ b//lex/latest/dg/conversation-logs-encrypting.md @@ -27,13 +26,0 @@ If you have not created a role for conversation logs, see [IAM Policies for Conv - { - "Version": "2012-10-17", - "Statement": [ - { - "Effect": "Allow", - "Action": [ - "kms:GenerateDataKey" - ], - "Resource": "kms-key-arn" - } - ] - } -