AWS lookout-for-vision documentation change
Summary
Simplified explanation of default permissions by removing explicit mention of AWS Management Console, CLI, and API restrictions
Security assessment
The change removes redundant details about access methods but doesn't alter security controls or address vulnerabilities. It maintains the core security principle of least privilege by default.
Diff
diff --git a/lookout-for-vision/latest/developer-guide/security_iam_id-based-policy-examples.md b/lookout-for-vision/latest/developer-guide/security_iam_id-based-policy-examples.md index a08797ddd..f4b00c5b3 100644 --- a//lookout-for-vision/latest/developer-guide/security_iam_id-based-policy-examples.md +++ b//lookout-for-vision/latest/developer-guide/security_iam_id-based-policy-examples.md @@ -11 +11 @@ End of support notice: On October 31, 2025, AWS will discontinue support for Ama -By default, users and roles don't have permission to create or modify Lookout for Vision 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 Lookout for Vision resources. To grant users permission to perform actions on the resources that they need, an IAM administrator can create IAM policies.