AWS storagegateway documentation change
Summary
Simplified explanation of default permissions by removing references to specific interfaces (Console/CLI/API) where tasks cannot be performed without permissions
Security assessment
The change removes redundant details about access methods (Console/CLI/API) but does not address any specific security vulnerability or weakness. It maintains the same security posture by clarifying that default permissions deny SGW resource modifications without explicit policies.
Diff
diff --git a/storagegateway/latest/tgw/security_iam_id-based-policy-examples.md b/storagegateway/latest/tgw/security_iam_id-based-policy-examples.md index 6ffa17d07..043899667 100644 --- a//storagegateway/latest/tgw/security_iam_id-based-policy-examples.md +++ b//storagegateway/latest/tgw/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.