AWS waf documentation change
Summary
Removed redundant statement about inability to perform tasks via AWS interfaces in default IAM permissions explanation
Security assessment
The change simplifies the description of default IAM permissions by removing a redundant explanation about console/CLI/API access. This is a documentation clarity improvement rather than addressing a security vulnerability or adding security features. The core security context (default deny for Shield resource modifications) remains unchanged.
Diff
diff --git a/waf/latest/developerguide/shd-security_iam_id-based-policy-examples.md b/waf/latest/developerguide/shd-security_iam_id-based-policy-examples.md index 0090216d5..4f97df0c1 100644 --- a//waf/latest/developerguide/shd-security_iam_id-based-policy-examples.md +++ b//waf/latest/developerguide/shd-security_iam_id-based-policy-examples.md @@ -13 +13 @@ You can now use the updated experience to access AWS WAF functionality anywhere -By default, users and roles don't have permission to create or modify Shield 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 Shield resources. To grant users permission to perform actions on the resources that they need, an IAM administrator can create IAM policies.