AWS lexv2 documentation change
Summary
Modified policy document explanation by removing explicit reference to Amazon Lex V2 assuming the role
Security assessment
The change simplifies wording about role assumption but doesn't address any specific security vulnerability. It maintains the same security posture by describing IAM role usage for logs delivery without introducing new security considerations.
Diff
diff --git a/lexv2/latest/dg/conversation-logs-policies.md b/lexv2/latest/dg/conversation-logs-policies.md index c16f8bd6d..2ec8a1ca3 100644 --- a//lexv2/latest/dg/conversation-logs-policies.md +++ b//lexv2/latest/dg/conversation-logs-policies.md @@ -23 +23 @@ The following code is formatted for Linux and MacOS. For Windows, replace the Li - 1. Create a document in the current directory called `LexConversationLogsAssumeRolePolicyDocument.json`, add the following code to it, and save it. This policy document adds Amazon Lex V2 as a trusted entity to the role. This allows Amazon Lex V2 to assume the role to deliver logs to the resources configured for conversation logs. + 1. Create a document in the current directory called `LexConversationLogsAssumeRolePolicyDocument.json`, add the following code to it, and save it. This policy document adds Amazon Lex V2 as a trusted entity to the role. This allows to assume the role to deliver logs to the resources configured for conversation logs.