From 3e035e353ed95fbe1bc9b369cbeeaf5b20e6ffb0 Mon Sep 17 00:00:00 2001
From: awstools
The default limit is 8 KB (8,192 kilobytes) for regional resources and 16 KB (16,384 kilobytes) for CloudFront distributions. For CloudFront distributions, + *
The default limit is 8 KB (8,192 bytes) for regional resources and 16 KB (16,384 bytes) for CloudFront distributions. For CloudFront distributions,
* you can increase the limit in the web ACL AssociationConfig
, for additional processing fees.
The options for oversize handling are the following:
*The default limit is 8 KB (8,192 kilobytes) for regional resources and 16 KB (16,384 kilobytes) for CloudFront distributions. For CloudFront distributions, + *
The default limit is 8 KB (8,192 bytes) for regional resources and 16 KB (16,384 bytes) for CloudFront distributions. For CloudFront distributions,
* you can increase the limit in the web ACL AssociationConfig
, for additional processing fees.
The options for oversize handling are the following:
*A limited amount of the request body is forwarded to WAF for
- * inspection by the underlying host service. For regional resources, the limit is 8 KB (8,192 kilobytes) and for CloudFront distributions, the limit is 16 KB (16,384 kilobytes). For CloudFront distributions,
+ * inspection by the underlying host service. For regional resources, the limit is 8 KB (8,192 bytes) and for CloudFront distributions, the limit is 16 KB (16,384 bytes). For CloudFront distributions,
* you can increase the limit in the web ACL's AssociationConfig
, for additional processing fees.
For information about how to handle oversized
* request bodies, see the Body
object configuration.
A limited amount of the request body is forwarded to WAF for
- * inspection by the underlying host service. For regional resources, the limit is 8 KB (8,192 kilobytes) and for CloudFront distributions, the limit is 16 KB (16,384 kilobytes). For CloudFront distributions,
+ * inspection by the underlying host service. For regional resources, the limit is 8 KB (8,192 bytes) and for CloudFront distributions, the limit is 16 KB (16,384 bytes). For CloudFront distributions,
* you can increase the limit in the web ACL's AssociationConfig
, for additional processing fees.
For information about how to handle oversized
* request bodies, see the JsonBody
object configuration.
Applies only to the targeted inspection level.
+ *Determines whether to use machine learning (ML) to
+ * analyze your web traffic for bot-related activity. Machine learning is required for the Bot Control rules TGT_ML_CoordinatedActivityLow
and TGT_ML_CoordinatedActivityMedium
, which
+ * inspect for anomalous behavior that might indicate distributed, coordinated bot activity.
For more information about this choice, see the listing for these rules in the table at Bot Control rules listing in the + * WAF Developer Guide.
+ *Default: TRUE
+ *
A rule statement that compares a number of bytes against the size of a request component, using a comparison operator, such as greater than (>) or less than (<). For example, you can use a size constraint statement to look for query strings that are longer than 100 bytes.
- *If you configure WAF to inspect the request body, WAF inspects only the number of bytes of the body up to the limit for the web ACL. By default, for regional web ACLs, this limit is 8 KB (8,192 kilobytes) and for CloudFront web ACLs, this limit is 16 KB (16,384 kilobytes). For CloudFront web ACLs, you can increase the limit in the web ACL AssociationConfig
, for additional fees. If you know that the request body for your web requests should never exceed the inspection limit, you could use a size constraint statement to block requests that have a larger request body size.
If you configure WAF to inspect the request body, WAF inspects only the number of bytes of the body up to the limit for the web ACL. By default, for regional web ACLs, this limit is 8 KB (8,192 bytes) and for CloudFront web ACLs, this limit is 16 KB (16,384 bytes). For CloudFront web ACLs, you can increase the limit in the web ACL AssociationConfig
, for additional fees. If you know that the request body for your web requests should never exceed the inspection limit, you could use a size constraint statement to block requests that have a larger request body size.
If you choose URI for the value of Part of the request to filter on, the slash (/) in the URI counts as one character. For example, the URI /logo.jpg
is nine characters long.
Customizes the maximum size of the request body that your protected CloudFront distributions forward to WAF for inspection. The default size is 16 KB (16,384 kilobytes).
+ *Customizes the maximum size of the request body that your protected CloudFront distributions forward to WAF for inspection. The default size is 16 KB (16,384 bytes).
*You are charged additional fees when your protected resources forward body sizes that are larger than the default. For more information, see WAF Pricing.
*Specifies the maximum size of the web request body component that an associated CloudFront distribution should send to WAF for inspection. This applies to statements in the web ACL that inspect the body or JSON body.
- *Default: 16 KB (16,384 kilobytes)
+ *
Default: 16 KB (16,384 bytes)
*
Specifies custom configurations for the associations between the web ACL and protected resources.
- *Use this to customize the maximum size of the request body that your protected CloudFront distributions forward to WAF for inspection. The default is 16 KB (16,384 kilobytes).
+ *Use this to customize the maximum size of the request body that your protected CloudFront distributions forward to WAF for inspection. The default is 16 KB (16,384 bytes).
*You are charged additional fees when your protected resources forward body sizes that are larger than the default. For more information, see WAF Pricing.
*Customizes the maximum size of the request body that your protected CloudFront distributions forward to WAF for inspection. The default size is 16 KB (16,384 kilobytes).
+ *Customizes the maximum size of the request body that your protected CloudFront distributions forward to WAF for inspection. The default size is 16 KB (16,384 bytes).
*You are charged additional fees when your protected resources forward body sizes that are larger than the default. For more information, see WAF Pricing.
*A rule statement that compares a number of bytes against the size of a request component, using a comparison operator, such as greater than (>) or less than (<). For example, you can use a size constraint statement to look for query strings that are longer than 100 bytes.
- *If you configure WAF to inspect the request body, WAF inspects only the number of bytes of the body up to the limit for the web ACL. By default, for regional web ACLs, this limit is 8 KB (8,192 kilobytes) and for CloudFront web ACLs, this limit is 16 KB (16,384 kilobytes). For CloudFront web ACLs, you can increase the limit in the web ACL AssociationConfig
, for additional fees. If you know that the request body for your web requests should never exceed the inspection limit, you could use a size constraint statement to block requests that have a larger request body size.
If you configure WAF to inspect the request body, WAF inspects only the number of bytes of the body up to the limit for the web ACL. By default, for regional web ACLs, this limit is 8 KB (8,192 bytes) and for CloudFront web ACLs, this limit is 16 KB (16,384 bytes). For CloudFront web ACLs, you can increase the limit in the web ACL AssociationConfig
, for additional fees. If you know that the request body for your web requests should never exceed the inspection limit, you could use a size constraint statement to block requests that have a larger request body size.
If you choose URI for the value of Part of the request to filter on, the slash (/) in the URI counts as one character. For example, the URI /logo.jpg
is nine characters long.
The name of the rule. You can't change the name of a Rule
after you create
- * it.
The name of the rule.
+ *If you change the name of a Rule
after you create
+ * it and you want the rule's metric name to reflect the change, update the metric name in the rule's VisibilityConfig
settings. WAF
+ * doesn't automatically update the metric name when you update the rule name.
Defines and enables Amazon CloudWatch metrics and web request sample collection.
+ *If you change the name of a Rule
after you create
+ * it and you want the rule's metric name to reflect the change, update the metric name as well. WAF
+ * doesn't automatically update the metric name.
Specifies custom configurations for the associations between the web ACL and protected resources.
- *Use this to customize the maximum size of the request body that your protected CloudFront distributions forward to WAF for inspection. The default is 16 KB (16,384 kilobytes).
+ *Use this to customize the maximum size of the request body that your protected CloudFront distributions forward to WAF for inspection. The default is 16 KB (16,384 bytes).
*You are charged additional fees when your protected resources forward body sizes that are larger than the default. For more information, see WAF Pricing.
*Specifies custom configurations for the associations between the web ACL and protected resources.
- *Use this to customize the maximum size of the request body that your protected CloudFront distributions forward to WAF for inspection. The default is 16 KB (16,384 kilobytes).
+ *Use this to customize the maximum size of the request body that your protected CloudFront distributions forward to WAF for inspection. The default is 16 KB (16,384 bytes).
*You are charged additional fees when your protected resources forward body sizes that are larger than the default. For more information, see WAF Pricing.
*Specifies custom configurations for the associations between the web ACL and protected resources.
- *Use this to customize the maximum size of the request body that your protected CloudFront distributions forward to WAF for inspection. The default is 16 KB (16,384 kilobytes).
+ *Use this to customize the maximum size of the request body that your protected CloudFront distributions forward to WAF for inspection. The default is 16 KB (16,384 bytes).
*You are charged additional fees when your protected resources forward body sizes that are larger than the default. For more information, see WAF Pricing.
*The inspection level to use for the Bot Control rule group. The common level is the least expensive. The \n targeted level includes all common level rules and adds rules with more advanced inspection criteria. For \n details, see WAF Bot Control rule group\n in the WAF Developer Guide.
", "smithy.api#required": {} } + }, + "EnableMachineLearning": { + "target": "com.amazonaws.wafv2#Boolean", + "traits": { + "smithy.api#default": false, + "smithy.api#documentation": "Applies only to the targeted inspection level.
\nDetermines whether to use machine learning (ML) to\n analyze your web traffic for bot-related activity. Machine learning is required for the Bot Control rules TGT_ML_CoordinatedActivityLow
and TGT_ML_CoordinatedActivityMedium
, which\ninspect for anomalous behavior that might indicate distributed, coordinated bot activity.
For more information about this choice, see the listing for these rules in the table at Bot Control rules listing in the\n WAF Developer Guide.
\nDefault: TRUE
\n
Customizes the maximum size of the request body that your protected CloudFront distributions forward to WAF for inspection. The default size is 16 KB (16,384 kilobytes).
\nYou are charged additional fees when your protected resources forward body sizes that are larger than the default. For more information, see WAF Pricing.
\nCustomizes the maximum size of the request body that your protected CloudFront distributions forward to WAF for inspection. The default size is 16 KB (16,384 bytes).
\nYou are charged additional fees when your protected resources forward body sizes that are larger than the default. For more information, see WAF Pricing.
\nSpecifies custom configurations for the associations between the web ACL and protected resources.
\nUse this to customize the maximum size of the request body that your protected CloudFront distributions forward to WAF for inspection. The default is 16 KB (16,384 kilobytes).
\nYou are charged additional fees when your protected resources forward body sizes that are larger than the default. For more information, see WAF Pricing.
\nSpecifies custom configurations for the associations between the web ACL and protected resources.
\nUse this to customize the maximum size of the request body that your protected CloudFront distributions forward to WAF for inspection. The default is 16 KB (16,384 bytes).
\nYou are charged additional fees when your protected resources forward body sizes that are larger than the default. For more information, see WAF Pricing.
\nWhat WAF should do if the body is larger than WAF can inspect. \n WAF does not support inspecting the entire contents of the web request body if the body \n exceeds the limit for the resource type. If the body is larger than the limit, the underlying host service \n only forwards the contents that are below the limit to WAF for inspection.
\nThe default limit is 8 KB (8,192 kilobytes) for regional resources and 16 KB (16,384 kilobytes) for CloudFront distributions. For CloudFront distributions, \n you can increase the limit in the web ACL AssociationConfig
, for additional processing fees.
The options for oversize handling are the following:
\n\n CONTINUE
- Inspect the available body contents normally, according to the rule inspection criteria.
\n MATCH
- Treat the web request as matching the rule statement. WAF\n applies the rule action to the request.
\n NO_MATCH
- Treat the web request as not matching the rule\n statement.
You can combine the MATCH
or NO_MATCH
\n settings for oversize handling with your rule and web ACL action settings, so that you block any request whose body is over the limit.
Default: CONTINUE
\n
What WAF should do if the body is larger than WAF can inspect. \n WAF does not support inspecting the entire contents of the web request body if the body \n exceeds the limit for the resource type. If the body is larger than the limit, the underlying host service \n only forwards the contents that are below the limit to WAF for inspection.
\nThe default limit is 8 KB (8,192 bytes) for regional resources and 16 KB (16,384 bytes) for CloudFront distributions. For CloudFront distributions, \n you can increase the limit in the web ACL AssociationConfig
, for additional processing fees.
The options for oversize handling are the following:
\n\n CONTINUE
- Inspect the available body contents normally, according to the rule inspection criteria.
\n MATCH
- Treat the web request as matching the rule statement. WAF\n applies the rule action to the request.
\n NO_MATCH
- Treat the web request as not matching the rule\n statement.
You can combine the MATCH
or NO_MATCH
\n settings for oversize handling with your rule and web ACL action settings, so that you block any request whose body is over the limit.
Default: CONTINUE
\n
Specifies custom configurations for the associations between the web ACL and protected resources.
\nUse this to customize the maximum size of the request body that your protected CloudFront distributions forward to WAF for inspection. The default is 16 KB (16,384 kilobytes).
\nYou are charged additional fees when your protected resources forward body sizes that are larger than the default. For more information, see WAF Pricing.
\nSpecifies custom configurations for the associations between the web ACL and protected resources.
\nUse this to customize the maximum size of the request body that your protected CloudFront distributions forward to WAF for inspection. The default is 16 KB (16,384 bytes).
\nYou are charged additional fees when your protected resources forward body sizes that are larger than the default. For more information, see WAF Pricing.
\nInspect the request body as plain text. The request body immediately follows the request\n headers. This is the part of a request that contains any additional data that you want to\n send to your web server as the HTTP request body, such as data from a form.
\nA limited amount of the request body is forwarded to WAF for\n inspection by the underlying host service. For regional resources, the limit is 8 KB (8,192 kilobytes) and for CloudFront distributions, the limit is 16 KB (16,384 kilobytes). For CloudFront distributions,\n you can increase the limit in the web ACL's AssociationConfig
, for additional processing fees.
For information about how to handle oversized\n request bodies, see the Body
object configuration.
Inspect the request body as plain text. The request body immediately follows the request\n headers. This is the part of a request that contains any additional data that you want to\n send to your web server as the HTTP request body, such as data from a form.
\nA limited amount of the request body is forwarded to WAF for\n inspection by the underlying host service. For regional resources, the limit is 8 KB (8,192 bytes) and for CloudFront distributions, the limit is 16 KB (16,384 bytes). For CloudFront distributions,\n you can increase the limit in the web ACL's AssociationConfig
, for additional processing fees.
For information about how to handle oversized\n request bodies, see the Body
object configuration.
Inspect the request body as JSON. The request body immediately follows the request\n headers. This is the part of a request that contains any additional data that you want to\n send to your web server as the HTTP request body, such as data from a form.
\nA limited amount of the request body is forwarded to WAF for\n inspection by the underlying host service. For regional resources, the limit is 8 KB (8,192 kilobytes) and for CloudFront distributions, the limit is 16 KB (16,384 kilobytes). For CloudFront distributions,\n you can increase the limit in the web ACL's AssociationConfig
, for additional processing fees.
For information about how to handle oversized\n request bodies, see the JsonBody
object configuration.
Inspect the request body as JSON. The request body immediately follows the request\n headers. This is the part of a request that contains any additional data that you want to\n send to your web server as the HTTP request body, such as data from a form.
\nA limited amount of the request body is forwarded to WAF for\n inspection by the underlying host service. For regional resources, the limit is 8 KB (8,192 bytes) and for CloudFront distributions, the limit is 16 KB (16,384 bytes). For CloudFront distributions,\n you can increase the limit in the web ACL's AssociationConfig
, for additional processing fees.
For information about how to handle oversized\n request bodies, see the JsonBody
object configuration.
What WAF should do if the body is larger than WAF can inspect. \n WAF does not support inspecting the entire contents of the web request body if the body \n exceeds the limit for the resource type. If the body is larger than the limit, the underlying host service \n only forwards the contents that are below the limit to WAF for inspection.
\nThe default limit is 8 KB (8,192 kilobytes) for regional resources and 16 KB (16,384 kilobytes) for CloudFront distributions. For CloudFront distributions, \n you can increase the limit in the web ACL AssociationConfig
, for additional processing fees.
The options for oversize handling are the following:
\n\n CONTINUE
- Inspect the available body contents normally, according to the rule inspection criteria.
\n MATCH
- Treat the web request as matching the rule statement. WAF\n applies the rule action to the request.
\n NO_MATCH
- Treat the web request as not matching the rule\n statement.
You can combine the MATCH
or NO_MATCH
\n settings for oversize handling with your rule and web ACL action settings, so that you block any request whose body is over the limit.
Default: CONTINUE
\n
What WAF should do if the body is larger than WAF can inspect. \n WAF does not support inspecting the entire contents of the web request body if the body \n exceeds the limit for the resource type. If the body is larger than the limit, the underlying host service \n only forwards the contents that are below the limit to WAF for inspection.
\nThe default limit is 8 KB (8,192 bytes) for regional resources and 16 KB (16,384 bytes) for CloudFront distributions. For CloudFront distributions, \n you can increase the limit in the web ACL AssociationConfig
, for additional processing fees.
The options for oversize handling are the following:
\n\n CONTINUE
- Inspect the available body contents normally, according to the rule inspection criteria.
\n MATCH
- Treat the web request as matching the rule statement. WAF\n applies the rule action to the request.
\n NO_MATCH
- Treat the web request as not matching the rule\n statement.
You can combine the MATCH
or NO_MATCH
\n settings for oversize handling with your rule and web ACL action settings, so that you block any request whose body is over the limit.
Default: CONTINUE
\n
Specifies the maximum size of the web request body component that an associated CloudFront distribution should send to WAF for inspection. This applies to statements in the web ACL that inspect the body or JSON body.
\nDefault: 16 KB (16,384 kilobytes)
\n
Specifies the maximum size of the web request body component that an associated CloudFront distribution should send to WAF for inspection. This applies to statements in the web ACL that inspect the body or JSON body.
\nDefault: 16 KB (16,384 bytes)
\n
Customizes the maximum size of the request body that your protected CloudFront distributions forward to WAF for inspection. The default size is 16 KB (16,384 kilobytes).
\nYou are charged additional fees when your protected resources forward body sizes that are larger than the default. For more information, see WAF Pricing.
\nThis is used in the AssociationConfig
of the web ACL.
Customizes the maximum size of the request body that your protected CloudFront distributions forward to WAF for inspection. The default size is 16 KB (16,384 bytes).
\nYou are charged additional fees when your protected resources forward body sizes that are larger than the default. For more information, see WAF Pricing.
\nThis is used in the AssociationConfig
of the web ACL.
The name of the rule. You can't change the name of a Rule
after you create\n it.
The name of the rule.
\nIf you change the name of a Rule
after you create\n it and you want the rule's metric name to reflect the change, update the metric name in the rule's VisibilityConfig
settings. WAF \n doesn't automatically update the metric name when you update the rule name.
Defines and enables Amazon CloudWatch metrics and web request sample collection.
", + "smithy.api#documentation": "Defines and enables Amazon CloudWatch metrics and web request sample collection.
\nIf you change the name of a Rule
after you create\n it and you want the rule's metric name to reflect the change, update the metric name as well. WAF \n doesn't automatically update the metric name.
A rule statement that compares a number of bytes against the size of a request component, using a comparison operator, such as greater than (>) or less than (<). For example, you can use a size constraint statement to look for query strings that are longer than 100 bytes.
\nIf you configure WAF to inspect the request body, WAF inspects only the number of bytes of the body up to the limit for the web ACL. By default, for regional web ACLs, this limit is 8 KB (8,192 kilobytes) and for CloudFront web ACLs, this limit is 16 KB (16,384 kilobytes). For CloudFront web ACLs, you can increase the limit in the web ACL AssociationConfig
, for additional fees. If you know that the request body for your web requests should never exceed the inspection limit, you could use a size constraint statement to block requests that have a larger request body size.
If you choose URI for the value of Part of the request to filter on, the slash (/) in the URI counts as one character. For example, the URI /logo.jpg
is nine characters long.
A rule statement that compares a number of bytes against the size of a request component, using a comparison operator, such as greater than (>) or less than (<). For example, you can use a size constraint statement to look for query strings that are longer than 100 bytes.
\nIf you configure WAF to inspect the request body, WAF inspects only the number of bytes of the body up to the limit for the web ACL. By default, for regional web ACLs, this limit is 8 KB (8,192 bytes) and for CloudFront web ACLs, this limit is 16 KB (16,384 bytes). For CloudFront web ACLs, you can increase the limit in the web ACL AssociationConfig
, for additional fees. If you know that the request body for your web requests should never exceed the inspection limit, you could use a size constraint statement to block requests that have a larger request body size.
If you choose URI for the value of Part of the request to filter on, the slash (/) in the URI counts as one character. For example, the URI /logo.jpg
is nine characters long.
A rule statement that compares a number of bytes against the size of a request component, using a comparison operator, such as greater than (>) or less than (<). For example, you can use a size constraint statement to look for query strings that are longer than 100 bytes.
\nIf you configure WAF to inspect the request body, WAF inspects only the number of bytes of the body up to the limit for the web ACL. By default, for regional web ACLs, this limit is 8 KB (8,192 kilobytes) and for CloudFront web ACLs, this limit is 16 KB (16,384 kilobytes). For CloudFront web ACLs, you can increase the limit in the web ACL AssociationConfig
, for additional fees. If you know that the request body for your web requests should never exceed the inspection limit, you could use a size constraint statement to block requests that have a larger request body size.
If you choose URI for the value of Part of the request to filter on, the slash (/) in the URI counts as one character. For example, the URI /logo.jpg
is nine characters long.
A rule statement that compares a number of bytes against the size of a request component, using a comparison operator, such as greater than (>) or less than (<). For example, you can use a size constraint statement to look for query strings that are longer than 100 bytes.
\nIf you configure WAF to inspect the request body, WAF inspects only the number of bytes of the body up to the limit for the web ACL. By default, for regional web ACLs, this limit is 8 KB (8,192 bytes) and for CloudFront web ACLs, this limit is 16 KB (16,384 bytes). For CloudFront web ACLs, you can increase the limit in the web ACL AssociationConfig
, for additional fees. If you know that the request body for your web requests should never exceed the inspection limit, you could use a size constraint statement to block requests that have a larger request body size.
If you choose URI for the value of Part of the request to filter on, the slash (/) in the URI counts as one character. For example, the URI /logo.jpg
is nine characters long.
Specifies custom configurations for the associations between the web ACL and protected resources.
\nUse this to customize the maximum size of the request body that your protected CloudFront distributions forward to WAF for inspection. The default is 16 KB (16,384 kilobytes).
\nYou are charged additional fees when your protected resources forward body sizes that are larger than the default. For more information, see WAF Pricing.
\nSpecifies custom configurations for the associations between the web ACL and protected resources.
\nUse this to customize the maximum size of the request body that your protected CloudFront distributions forward to WAF for inspection. The default is 16 KB (16,384 bytes).
\nYou are charged additional fees when your protected resources forward body sizes that are larger than the default. For more information, see WAF Pricing.
\nSpecifies custom configurations for the associations between the web ACL and protected resources.
\nUse this to customize the maximum size of the request body that your protected CloudFront distributions forward to WAF for inspection. The default is 16 KB (16,384 kilobytes).
\nYou are charged additional fees when your protected resources forward body sizes that are larger than the default. For more information, see WAF Pricing.
\nSpecifies custom configurations for the associations between the web ACL and protected resources.
\nUse this to customize the maximum size of the request body that your protected CloudFront distributions forward to WAF for inspection. The default is 16 KB (16,384 bytes).
\nYou are charged additional fees when your protected resources forward body sizes that are larger than the default. For more information, see WAF Pricing.
\n