AWS waf documentation change
Summary
Added new console experience notice and updated protection configuration link
Security assessment
Minor terminology update ('configuring protection' vs 'using web ACLs') and UI notification, no security vulnerability addressed
Diff
diff --git a/waf/latest/developerguide/ddos-request-service-credit.md b/waf/latest/developerguide/ddos-request-service-credit.md index 66a22f158..af04a3e42 100644 --- a//waf/latest/developerguide/ddos-request-service-credit.md +++ b//waf/latest/developerguide/ddos-request-service-credit.md @@ -4,0 +5,4 @@ +**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). + @@ -44 +48 @@ For more information about how to protect AWS resources using Shield Advanced, s - * For applicable CloudFront and Application Load Balancer protected resources, you must have associated an AWS WAF web ACL and implemented a rate-based rule in the web ACL in Block mode. For information about AWS WAF rate-based rules, see [Using rate-based rule statements in AWS WAF](./waf-rule-statement-type-rate-based.html). For information about how to associate web ACLs with AWS resources, see [Using web ACLs in AWS WAF](./web-acl.html). + * For applicable CloudFront and Application Load Balancer protected resources, you must have associated an AWS WAF web ACL and implemented a rate-based rule in the web ACL in Block mode. For information about AWS WAF rate-based rules, see [Using rate-based rule statements in AWS WAF](./waf-rule-statement-type-rate-based.html). For information about how to associate web ACLs with AWS resources, see [Configuring protection in AWS WAF](./web-acl.html).