AWS storagegateway documentation change
Summary
Simplified explanation about default permissions for AWS SGW resources by removing explicit mention of console/CLI/API access limitations
Security assessment
The change removes specific examples of access methods (console/CLI/API) from a general statement about default permissions, but does not address any specific vulnerability or security incident. This appears to be a documentation clarification rather than a security-related update.
Diff
diff --git a/storagegateway/latest/vgw/security_iam_id-based-policy-examples.md b/storagegateway/latest/vgw/security_iam_id-based-policy-examples.md index ec5fd872f..c72160af4 100644 --- a//storagegateway/latest/vgw/security_iam_id-based-policy-examples.md +++ b//storagegateway/latest/vgw/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 SGW 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 SGW resources. To grant users permission to perform actions on the resources that they need, an IAM administrator can create IAM policies.