AWS cloudshell documentation change
Summary
Removed statement about users/roles being unable to perform tasks via AWS Management Console, CLI, or API by default. Simplified explanation of default permissions.
Security assessment
The change removes a redundant or potentially misleading statement about default access restrictions but does not address a specific security vulnerability or weakness. It clarifies IAM policy documentation without introducing new security controls or acknowledging a security incident.
Diff
diff --git a/cloudshell/latest/userguide/security_iam_id-based-policy-examples.md b/cloudshell/latest/userguide/security_iam_id-based-policy-examples.md index c03f6a254..14c8fd60d 100644 --- a//cloudshell/latest/userguide/security_iam_id-based-policy-examples.md +++ b//cloudshell/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 CloudShell 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 CloudShell resources. To grant users permission to perform actions on the resources that they need, an IAM administrator can create IAM policies.