AWS lexv2 documentation change
Summary
Removed redundant statement about default permissions not allowing console/CLI/API access, focusing on core IAM policy creation requirement
Security assessment
The change removes a redundant explanation about default permissions not allowing interface access, but maintains the core security guidance about requiring explicit IAM policies. No specific vulnerability or security incident is addressed, just documentation clarity improvement.
Diff
diff --git a/lexv2/latest/dg/security_iam_id-based-policy-examples.md b/lexv2/latest/dg/security_iam_id-based-policy-examples.md index 94af07b43..b4bf13b0e 100644 --- a//lexv2/latest/dg/security_iam_id-based-policy-examples.md +++ b//lexv2/latest/dg/security_iam_id-based-policy-examples.md @@ -9 +9 @@ Policy best practicesUsing the consoleAllow users to add functions to a botAllow -By default, users and roles don't have permission to create or modify Amazon Lex V2 resources. They also can't perform tasks by using the AWS Management Console, AWS Command Line Interface (AWS CLI), or AWS API. To grant users permission to perform actions on the resources that they need, an IAM administrator can create IAM policies. The administrator can then add the IAM policies to roles, and users can assume the roles. +By default, users and roles don't have permission to create or modify Amazon Lex V2 resources. To grant users permission to perform actions on the resources that they need, an IAM administrator can create IAM policies.