AWS personalize documentation change
Summary
Simplified explanation of default permissions by removing redundant details about console/CLI/API access restrictions
Security assessment
The change removes explicit mentions of access methods (console/CLI/API) from the default permissions explanation, but does not indicate any security vulnerability fix or weakness. This appears to be a documentation clarification rather than a security-related update.
Diff
diff --git a/personalize/latest/dg/security_iam_id-based-policy-examples.md b/personalize/latest/dg/security_iam_id-based-policy-examples.md index e947defdc..590628ebe 100644 --- a//personalize/latest/dg/security_iam_id-based-policy-examples.md +++ b//personalize/latest/dg/security_iam_id-based-policy-examples.md @@ -9 +9 @@ Policy best practicesAWS managed policiesUsing the consoleAllow users to view th -By default, users and roles don't have permission to create or modify Amazon Personalize 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 Personalize resources. To grant users permission to perform actions on the resources that they need, an IAM administrator can create IAM policies.