AWS workspaces-web documentation change
Summary
Removed mention of default inability to use AWS Management Console/CLI/API and streamlined explanation of IAM policy creation.
Security assessment
The change simplifies introductory IAM policy documentation but does not address a specific security vulnerability or weakness. It maintains general security documentation about granting permissions.
Diff
diff --git a/workspaces-web/latest/adminguide/security_iam_id-based-policy-examples.md b/workspaces-web/latest/adminguide/security_iam_id-based-policy-examples.md index a5fa4e465..6e7fbe151 100644 --- a//workspaces-web/latest/adminguide/security_iam_id-based-policy-examples.md +++ b//workspaces-web/latest/adminguide/security_iam_id-based-policy-examples.md @@ -7 +7 @@ -By default, users and roles don't have permission to create or modify WorkSpaces Secure Browser 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 WorkSpaces Secure Browser resources. To grant users permission to perform actions on the resources that they need, an IAM administrator can create IAM policies.