AWS waf documentation change
Summary
Added section about new console experience and updated 'web ACL' references to 'protection pack or web ACL'
Security assessment
Documents expanded security configuration options with protection packs for bot control strategies, but doesn't address specific security issues
Diff
diff --git a/waf/latest/developerguide/waf-bot-control-example-common-and-targeted-inspection-level.md b/waf/latest/developerguide/waf-bot-control-example-common-and-targeted-inspection-level.md index 7622512ae..892166d68 100644 --- a//waf/latest/developerguide/waf-bot-control-example-common-and-targeted-inspection-level.md +++ b//waf/latest/developerguide/waf-bot-control-example-common-and-targeted-inspection-level.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). + @@ -7 +11 @@ -As a cost optimization, you can use two AWS WAF Bot Control managed rule group statements in your web ACL, with separate inspection levels and scoping. For instance, you could scope the targeted inspection level statement only to more sensitive application endpoints. +As a cost optimization, you can use two AWS WAF Bot Control managed rule group statements in your protection pack or web ACL, with separate inspection levels and scoping. For instance, you could scope the targeted inspection level statement only to more sensitive application endpoints.