AWS entityresolution documentation change
Summary
Removed mention of specific interfaces (AWS Console/CLI/API) in default permissions explanation
Security assessment
The change simplifies the description of default permissions by removing redundant interface examples (Console/CLI/API). This is a documentation clarification rather than addressing a security vulnerability or adding new security controls. The core security principle of least privilege remains unchanged.
Diff
diff --git a/entityresolution/latest/userguide/security_iam_id-based-policy-examples.md b/entityresolution/latest/userguide/security_iam_id-based-policy-examples.md index e1d3c2a19..cb1b78ef3 100644 --- a//entityresolution/latest/userguide/security_iam_id-based-policy-examples.md +++ b//entityresolution/latest/userguide/security_iam_id-based-policy-examples.md @@ -9 +9 @@ Policy best practicesUsing the consoleAllow users to view their own permissions -By default, users and roles don't have permission to create or modify AWS Entity Resolution 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 AWS Entity Resolution resources. To grant users permission to perform actions on the resources that they need, an IAM administrator can create IAM policies.