AWS filegateway documentation change
Summary
Removed redundant explanation about default lack of access to AWS interfaces (Console/CLI/API) while retaining core statement about SGW resource permissions.
Security assessment
The change simplifies documentation phrasing without altering security guidance. The removed text about console/CLI/API access was redundant since resource permissions inherently control interface access. No evidence of addressing a vulnerability or security incident.
Diff
diff --git a/filegateway/latest/files3/security_iam_id-based-policy-examples.md b/filegateway/latest/files3/security_iam_id-based-policy-examples.md index 477d6187f..9ebbd934b 100644 --- a//filegateway/latest/files3/security_iam_id-based-policy-examples.md +++ b//filegateway/latest/files3/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.