AWS waf documentation change
Summary
Updated terminology from 'protection pack or web ACL' to 'protection pack (web ACL)' in cost optimization guidance
Security assessment
The change clarifies terminology but doesn't alter security recommendations or address vulnerabilities. The security strategy described remains unchanged.
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 892166d68..d4aae0c69 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 @@ -11 +11 @@ You can now use the updated experience to access AWS WAF functionality anywhere -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. +As a cost optimization, you can use two AWS WAF Bot Control managed rule group statements in your protection pack (web ACL), with separate inspection levels and scoping. For instance, you could scope the targeted inspection level statement only to more sensitive application endpoints.