AWS lex documentation change
Summary
Removed mention of users not being able to perform tasks via AWS Management Console, CLI, or API by default. Simplified the explanation of default permissions.
Security assessment
The change removes a redundant clarification about access methods (Console/CLI/API) but does not alter the core security policy information. This is an editorial simplification rather than a security-related update. No evidence of addressing a vulnerability or security incident.
Diff
diff --git a/lex/latest/dg/security_iam_id-based-policy-examples.md b/lex/latest/dg/security_iam_id-based-policy-examples.md index 992c0def5..6a0ee1fdf 100644 --- a//lex/latest/dg/security_iam_id-based-policy-examples.md +++ b//lex/latest/dg/security_iam_id-based-policy-examples.md @@ -11 +11 @@ End of support notice: On September 15, 2025, AWS will discontinue support for A -By default, users and roles don't have permission to create or modify Amazon Lex 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 resources. To grant users permission to perform actions on the resources that they need, an IAM administrator can create IAM policies.