AWS waf documentation change
Summary
Updated references from 'protection pack or web ACL' to 'protection pack (web ACL)' in rate limiting documentation
Security assessment
Documentation consistency update. Existing security mechanisms (CAPTCHA/Challenge actions) remain unchanged in their operation and documentation.
Diff
diff --git a/waf/latest/developerguide/waf-rule-statement-type-rate-based-request-limiting.md b/waf/latest/developerguide/waf-rule-statement-type-rate-based-request-limiting.md index 802d1bb80..2ce3a6226 100644 --- a//waf/latest/developerguide/waf-rule-statement-type-rate-based-request-limiting.md +++ b//waf/latest/developerguide/waf-rule-statement-type-rate-based-request-limiting.md @@ -34 +34 @@ The following list describes how rate limiting works for each of the actions. - * **Count** – AWS WAF counts the request, applies any custom headers or labels that you've defined, and continues the protection pack or web ACL evaluation of the request. + * **Count** – AWS WAF counts the request, applies any custom headers or labels that you've defined, and continues the protection pack (web ACL) evaluation of the request. @@ -46 +46 @@ If the end user or client browser responds successfully, the client receives a v - * If the request has a valid, unexpired token, the CAPTCHA or Challenge action verifies the token and takes no action on the request, similar to the Count action. The rate-based rule returns the request evaluation back to the protection pack or web ACL without taking any terminating action, and the protection pack or web ACL continues its evaluation of the request. + * If the request has a valid, unexpired token, the CAPTCHA or Challenge action verifies the token and takes no action on the request, similar to the Count action. The rate-based rule returns the request evaluation back to the protection pack (web ACL) without taking any terminating action, and the protection pack (web ACL) continues its evaluation of the request.