AWS waf documentation change
Summary
Added console experience notice and updated web ACL association terminology
Security assessment
Terminology update from 'web ACL' to 'protection' appears to be branding/naming convention change without security implications
Diff
diff --git a/waf/latest/developerguide/manage-protection.md b/waf/latest/developerguide/manage-protection.md index 827b17ac0..9c79ffc1b 100644 --- a//waf/latest/developerguide/manage-protection.md +++ b//waf/latest/developerguide/manage-protection.md @@ -6,0 +7,4 @@ Configure application layer DDoS protections +**Introducing a new console experience for AWS WAF** + +You can now use the updated experience to access AWS WAF functionality anywhere in the console. For more details, see [Working with the updated console experience](./working-with-console.html). + @@ -54 +58 @@ To create a web ACL, follow these steps: -If a resource is already associated with a web ACL, you can't change to a different web ACL. If you want to change the web ACL, you must first remove the associated web ACLs from the resource. For more information, see [Associating or disassociating a web ACL with an AWS resource](./web-acl-associating-aws-resource.html). +If a resource is already associated with a web ACL, you can't change to a different web ACL. If you want to change the web ACL, you must first remove the associated web ACLs from the resource. For more information, see [Associating or disassociating protection with an AWS resource](./web-acl-associating-aws-resource.html).