AWS lightsail-for-research documentation change
Summary
Removed mention of users being unable to perform tasks via AWS console/CLI/API by default, simplified default permissions statement.
Security assessment
The change clarifies default permissions but does not address a specific security vulnerability or weakness. It removes redundant information about access methods (console/CLI/API) being blocked by default, which is already implied by the lack of permissions. No evidence of patching a security issue or introducing new security controls.
Diff
diff --git a/lightsail-for-research/latest/ug/security_iam_id-based-policy-examples.md b/lightsail-for-research/latest/ug/security_iam_id-based-policy-examples.md index c6826cedb..743129f53 100644 --- a//lightsail-for-research/latest/ug/security_iam_id-based-policy-examples.md +++ b//lightsail-for-research/latest/ug/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 Lightsail for Research 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 Lightsail for Research resources. To grant users permission to perform actions on the resources that they need, an IAM administrator can create IAM policies.