AWS workmail documentation change
Summary
Removed IAM policy JSON examples for WorkMail message access
Security assessment
Removal of policy examples related to message content access does not explicitly address security vulnerabilities. Likely documentation simplification rather than security-related change.
Diff
diff --git a/workmail/latest/adminguide/lambda-content-access.md b/workmail/latest/adminguide/lambda-content-access.md index 89294dcf1..c86a84b64 100644 --- a//workmail/latest/adminguide/lambda-content-access.md +++ b//workmail/latest/adminguide/lambda-content-access.md @@ -44,21 +43,0 @@ The following example policy grants an IAM entity full read access to all inboun -JSON - - -**** - - - - { - "Version": "2012-10-17", - "Statement": [ - { - "Action": [ - "workmailmessageflow:GetRawMessageContent" - ], - "Resource": "arn:aws:workmailmessageflow:aws-region:111122223333:message/*", - "Effect": "Allow" - } - ] - } - - @@ -115,22 +93,0 @@ The following example policy grants an IAM entity full read and update access to -JSON - - -**** - - - - { - "Version": "2012-10-17", - "Statement": [ - { - "Action": [ - "workmailmessageflow:GetRawMessageContent", - "workmailmessageflow:PutRawMessageContent" - ], - "Resource": "arn:aws:workmailmessageflow:us-east-1:account:message/*", - "Effect": "Allow" - } - ] - } - -