AWS lex medium security documentation change
Summary
Removed explicit CloudWatch Logs and S3 logging policies while adding JSON formatting markers
Security assessment
Removal of required logging permissions could lead to misconfigured audit trails if users don't implement equivalent policies elsewhere.
Diff
diff --git a/lex/latest/dg/conversation-logs-policies.md b/lex/latest/dg/conversation-logs-policies.md index ae072b6de..2425271f2 100644 --- a//lex/latest/dg/conversation-logs-policies.md +++ b//lex/latest/dg/conversation-logs-policies.md @@ -26,0 +27,6 @@ The following code is formatted for Linux and MacOS. For Windows, replace the Li +JSON + + +**** + + @@ -57,15 +63,0 @@ Next, create and attach a policy to the role that enables Amazon Lex to write to - { - "Version": "2012-10-17", - "Statement": [ - { - "Effect": "Allow", - "Action": [ - "logs:CreateLogStream", - "logs:PutLogEvents" - ], - "Resource": "arn:aws:logs:region:account-id:log-group:log-group-name:*" - } - ] - } - - @@ -94,0 +87,6 @@ If you are logging audio to an S3 bucket, create a policy that enables Amazon Le +JSON + + +**** + + @@ -128,0 +128,6 @@ The following policy defines the permission to grant to the user, role, or group +JSON + + +**** + + @@ -136 +141 @@ The following policy defines the permission to grant to the user, role, or group - "Resource": "arn:aws:iam::account-id:role/role-name", + "Resource": "arn:aws:iam::111122223333:role/role-name",