AWS fsx documentation change
Summary
Removed explicit mention of AWS Management Console, CLI, and API access restrictions in default IAM policy explanation
Security assessment
The change simplifies the description of default permissions but doesn't address a specific security vulnerability or weakness. It maintains the core security concept that IAM policies are required for resource access, without evidence of patching a security issue or introducing new security controls.
Diff
diff --git a/fsx/latest/FileCacheGuide/security_iam_id-based-policy-examples.md b/fsx/latest/FileCacheGuide/security_iam_id-based-policy-examples.md index 9ef38105f..8021d63fc 100644 --- a//fsx/latest/FileCacheGuide/security_iam_id-based-policy-examples.md +++ b//fsx/latest/FileCacheGuide/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 File Cache 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 File Cache resources. To grant users permission to perform actions on the resources that they need, an IAM administrator can create IAM policies.