AWS fis documentation change
Summary
Removed mention of users being unable to perform tasks via AWS Management Console, CLI, or API by default. Simplified default permissions explanation.
Security assessment
The change removes redundant details about access methods (console/CLI/API) but does not alter the core security principle of least privilege or address a specific vulnerability. The documentation still emphasizes that permissions must be explicitly granted via IAM policies.
Diff
diff --git a/fis/latest/userguide/security_iam_id-based-policy-examples.md b/fis/latest/userguide/security_iam_id-based-policy-examples.md index 0e48b4f28..29c8656ce 100644 --- a//fis/latest/userguide/security_iam_id-based-policy-examples.md +++ b//fis/latest/userguide/security_iam_id-based-policy-examples.md @@ -9 +9 @@ Policy best practicesExample: Use the AWS FIS consoleExample: List available AWS -By default, users and roles don't have permission to create or modify AWS FIS 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 FIS resources. To grant users permission to perform actions on the resources that they need, an IAM administrator can create IAM policies.