AWS fsx documentation change
Summary
Removed mention of specific AWS interfaces (Console/CLI/API) from default permissions statement and simplified phrasing about IAM policy creation
Security assessment
The change simplifies existing security documentation about default permissions but does not address any specific vulnerability or weakness. The removal of explicit references to AWS interfaces appears to be editorial rather than security-related.
Diff
diff --git a/fsx/latest/LustreGuide/security_iam_id-based-policy-examples.md b/fsx/latest/LustreGuide/security_iam_id-based-policy-examples.md index 5653befe3..6066dcfe5 100644 --- a//fsx/latest/LustreGuide/security_iam_id-based-policy-examples.md +++ b//fsx/latest/LustreGuide/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 Amazon FSx 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 Amazon FSx resources. To grant users permission to perform actions on the resources that they need, an IAM administrator can create IAM policies.