Package-level declarations
Types
Type of addresses in the IPSet, use IPV4 for IPV4 IP addresses, IPV6 for IPV6 address.
Use CLOUDFRONT for CloudFront IPSet, use REGIONAL for Application Load Balancer and API Gateway.
Logic to apply to the filtering conditions. You can specify that, in order to satisfy the filter, a log must match all conditions or must match at least one condition.
How to handle logs that satisfy the filter's conditions and requirement.
Logic to apply to the filtering conditions. You can specify that, in order to satisfy the filter, a log must match all conditions or must match at least one condition.
Default handling for logs that don't match any of the specified filtering conditions.
Use CLOUDFRONT for CloudFront RegexPatternSet, use REGIONAL for Application Load Balancer and API Gateway.
The inspection behavior to fall back to if the JSON in the request body is invalid.
The match status to assign to the web request if the request doesn't have a valid IP address in the specified position.
The match status to assign to the web request if the request doesn't have a valid IP address in the specified position.
The position in the header to search for the IP address. The header can contain IP addresses of the original client and also of proxies. For example, the header value could be 10.1.1.1, 127.0.0.0, 10.10.10.10 where the first IP address identifies the original client and the rest identify proxies that the request went through. The options for this setting are the following:
The match status to assign to the web request if the request doesn't have a JA3 fingerprint. You can specify the following fallback behaviors:
The match status to assign to the web request if the request doesn't have a JA4 fingerprint. You can specify the following fallback behaviors:
The parts of the JSON to match against using the MatchPattern.
The parts of the request to match against using the MatchPattern.
Handling of requests containing oversize fields
Position of the evaluation in the FieldToMatch of request.
Setting that indicates how to aggregate the request counts.
The match status to assign to the web request if there is insufficient TSL Client Hello information to compute the JA3 fingerprint. You can specify the following fallback behaviors:
The match status to assign to the web request if there is insufficient TSL Client Hello information to compute the JA4 fingerprint. You can specify the following fallback behaviors:
Valid values are TEXT_PLAIN, TEXT_HTML, and APPLICATION_JSON.
Use CLOUDFRONT for CloudFront RuleGroup, use REGIONAL for Application Load Balancer and API Gateway.
Sensitivity Level current only used for sqli match statements.
The operator to use to compare the request part to the size setting.
Type of text transformation.
What AWS WAF should do if it fails to completely parse the JSON body. The options are the following:
The inspection level to use for the Bot Control rule group. The common level is the least expensive. The targeted level includes all common level rules and adds rules with more advanced inspection criteria. For details, see AWS WAF Bot Control rule group in the AWS WAF Developer Guide .
The inspection behavior to fall back to if the JSON in the request body is invalid.
Field type to protect
The match status to assign to the web request if the request doesn't have a valid IP address in the specified position.
The match status to assign to the web request if the request doesn't have a valid IP address in the specified position.
The position in the header to search for the IP address. The header can contain IP addresses of the original client and also of proxies. For example, the header value could be 10.1.1.1, 127.0.0.0, 10.10.10.10 where the first IP address identifies the original client and the rest identify proxies that the request went through. The options for this setting are the following:
The match status to assign to the web request if the request doesn't have a JA3 fingerprint. You can specify the following fallback behaviors:
The match status to assign to the web request if the request doesn't have a JA4 fingerprint. You can specify the following fallback behaviors:
The parts of the JSON to match against using the MatchPattern.
The parts of the request to match against using the MatchPattern.
Handling of requests containing oversize fields
Position of the evaluation in the FieldToMatch of request.
Setting that indicates how to aggregate the request counts.
The match status to assign to the web request if there is insufficient TSL Client Hello information to compute the JA3 fingerprint. You can specify the following fallback behaviors:
The match status to assign to the web request if there is insufficient TSL Client Hello information to compute the JA4 fingerprint. You can specify the following fallback behaviors:
The payload type for your account creation endpoint, either JSON or form encoded.
The payload type for your login endpoint, either JSON or form encoded.
Valid values are TEXT_PLAIN, TEXT_HTML, and APPLICATION_JSON.
Use CLOUDFRONT for CloudFront WebACL, use REGIONAL for Application Load Balancer and API Gateway.
Sensitivity Level current only used for sqli match statements.
The operator to use to compare the request part to the size setting.
Type of text transformation.
What AWS WAF should do if it fails to completely parse the JSON body. The options are the following: