AWS clean-rooms documentation change
Summary
Removed statement about default inability to use console/CLI/API and simplified default permission explanation
Security assessment
The change removes a redundant clarification about access methods but does not alter security policy recommendations or address vulnerabilities. This edit simplifies permissions documentation without introducing security implications.
Diff
diff --git a/clean-rooms/latest/userguide/security_iam_id-based-policy-examples.md b/clean-rooms/latest/userguide/security_iam_id-based-policy-examples.md index 2f60f5ef6..cd15dcd05 100644 --- a//clean-rooms/latest/userguide/security_iam_id-based-policy-examples.md +++ b//clean-rooms/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 Clean Rooms 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 Clean Rooms resources. To grant users permission to perform actions on the resources that they need, an IAM administrator can create IAM policies.