AWS waf documentation change
Summary
Added identical cost optimization guidance as in waf-anti-ddos-alb.md for general DDoS protection
Security assessment
Replicates observability configuration instructions across documentation sections, enhancing security monitoring documentation without fixing vulnerabilities
Diff
diff --git a/waf/latest/developerguide/waf-anti-ddos.md b/waf/latest/developerguide/waf-anti-ddos.md index e5ed96311..d6febca6f 100644 --- a//waf/latest/developerguide/waf-anti-ddos.md +++ b//waf/latest/developerguide/waf-anti-ddos.md @@ -30,0 +31,17 @@ Resource-level DDoS protection: +###### To optimize web ACL request costs for your Application Load Balancer + +You must associate a web ACL with your Application Load Balancer to enable resource-level protection. If your Application Load Balancer is associated with a web ACL that has no configuration, you will not incur charges from AWS WAF requests, however, AWS WAF will not provide sampled requests or report on the Application Load Balancer in CloudWatch metrics. You can take the following actions to enable observability features for the Application Load Balancer: + + * Use the `Block` action or `Allow` action with custom request headers in the `DefaultAction`. For information, see [Inserting custom request headers for non-blocking actions](./customizing-the-incoming-request.html). + + * Add any rules to the web ACL. For information, see [AWS WAF rules](./waf-rules.html). + + * Enable a logging destination. For information, see [Configuring logging for a protection pack (web ACL)](./logging-management-configure.html). + + * Associate the web ACL with an AWS Firewall Manager policy. For information, see [Creating an AWS Firewall Manager policy for AWS WAF](./create-policy.html#creating-firewall-manager-policy-for-waf). + + + + +AWS WAF will not provide sampled requests or publish CloudWatch metrics without these configurations. +