identify the part of a web request that you want AWS WAF to inspect, such as the values of the User-Agent header or the query string. For example, you can create a ByteMatchSet that matches any requests with User-Agent headers that contain the string BadBot. You can then configure AWS WAF to reject those requests.

To create and configure a ByteMatchSet, perform the following steps:

1. Use `GetChangeToken` to get the change token that you provide in the `ChangeToken` parameter of a `CreateByteMatchSet` request.
2. Submit a `CreateByteMatchSet` request.
3. Use `GetChangeToken` to get the change token that you provide in the `ChangeToken` parameter of an `UpdateByteMatchSet` request.
4. Submit an `UpdateByteMatchSet` request to specify the part of the request that you want AWS WAF to inspect (for example, the header or the URI) and the value that you want AWS WAF to watch for.

requests you want to allow or block based on the country that the requests originate from. For example, if you're receiving a lot of requests from one or more countries and you want to block the requests, you can create an GeoMatchSet that contains those countries and then configure AWS WAF to block the requests.

To create and configure a GeoMatchSet, perform the following steps:

1. Use `GetChangeToken` to get the change token that you provide in the `ChangeToken` parameter of a `CreateGeoMatchSet` request.
2. Submit a `CreateGeoMatchSet` request.
3. Use `GetChangeToken` to get the change token that you provide in the `ChangeToken` parameter of an `UpdateGeoMatchSet` request.
4. Submit an `UpdateGeoMatchSetSet` request to specify the countries that you want AWS WAF to watch for.

that you want to allow or block based on the IP addresses that the requests originate from. For example, if you're receiving a lot of requests from one or more individual IP addresses or one or more ranges of IP addresses and you want to block the requests, you can create an IPSet that contains those IP addresses and then configure AWS WAF to block the requests.

To create and configure an IPSet, perform the following steps:

1. Use `GetChangeToken` to get the change token that you provide in the `ChangeToken` parameter of a `CreateIPSet` request.
2. Submit a `CreateIPSet` request.
3. Use `GetChangeToken` to get the change token that you provide in the `ChangeToken` parameter of an `UpdateIPSet` request.
4. Submit an `UpdateIPSet` request to specify the IP addresses that you want AWS WAF to watch for.

RateLimit, which specifies the maximum number of requests that AWS WAF allows from a specified IP address in a five-minute period. The RateBasedRule also contains the IPSet objects, ByteMatchSet objects, and other predicates that identify the requests that you want to count or block if these requests exceed the RateLimit.

If you add more than one predicate to a RateBasedRule, a request not only must exceed the RateLimit, but it also must match all the conditions to be counted or blocked. For example, suppose you add the following to a RateBasedRule:

• An `IPSet` that matches the IP address `192.0.2.44/32`
• A `ByteMatchSet` that matches `BadBot` in the `User-Agent` header

• A `ByteMatchSet` with `FieldToMatch` of [`URI`](https://hexdocs.pm/elixir/URI.html)
• A `PositionalConstraint` of `STARTS_WITH`
• A `TargetString` of `login`

1. Create and update the predicates that you want to include in the rule. For more information, see `CreateByteMatchSet`, `CreateIPSet`, and `CreateSqlInjectionMatchSet`.
2. Use `GetChangeToken` to get the change token that you provide in the `ChangeToken` parameter of a `CreateRule` request.
3. Submit a `CreateRateBasedRule` request.
4. Use `GetChangeToken` to get the change token that you provide in the `ChangeToken` parameter of an `UpdateRule` request.
5. Submit an `UpdateRateBasedRule` request to specify the predicates that you want to include in the rule.
6. Create and update a `WebACL` that contains the `RateBasedRule`. For more information, see `CreateWebACL`.

identify the part of a web request that you want AWS WAF to inspect, such as the values of the User-Agent header or the query string. For example, you can create a RegexMatchSet that contains a RegexMatchTuple that looks for any requests with User-Agent headers that match a RegexPatternSet with pattern B[a@]dB[o0]t. You can then configure AWS WAF to reject those requests.

To create and configure a RegexMatchSet, perform the following steps:

1. Use `GetChangeToken` to get the change token that you provide in the `ChangeToken` parameter of a `CreateRegexMatchSet` request.
2. Submit a `CreateRegexMatchSet` request.
3. Use `GetChangeToken` to get the change token that you provide in the `ChangeToken` parameter of an `UpdateRegexMatchSet` request.
4. Submit an `UpdateRegexMatchSet` request to specify the part of the request that you want AWS WAF to inspect (for example, the header or the URI) and the value, using a `RegexPatternSet`, that you want AWS WAF to watch for.

to specify the regular expression (regex) pattern that you want AWS WAF to search for, such as B[a@]dB[o0]t. You can then configure AWS WAF to reject those requests.

To create and configure a RegexPatternSet, perform the following steps:

1. Use `GetChangeToken` to get the change token that you provide in the `ChangeToken` parameter of a `CreateRegexPatternSet` request.
2. Submit a `CreateRegexPatternSet` request.
3. Use `GetChangeToken` to get the change token that you provide in the `ChangeToken` parameter of an `UpdateRegexPatternSet` request.
4. Submit an `UpdateRegexPatternSet` request to specify the string that you want AWS WAF to watch for.

ByteMatchSet objects, and other predicates that identify the requests that you want to block. If you add more than one predicate to a Rule, a request must match all of the specifications to be allowed or blocked. For example, suppose that you add the following to a Rule:

• An `IPSet` that matches the IP address `192.0.2.44/32`
• A `ByteMatchSet` that matches `BadBot` in the `User-Agent` header

1. Create and update the predicates that you want to include in the `Rule`. For more information, see `CreateByteMatchSet`, `CreateIPSet`, and `CreateSqlInjectionMatchSet`.
2. Use `GetChangeToken` to get the change token that you provide in the `ChangeToken` parameter of a `CreateRule` request.
3. Submit a `CreateRule` request.
4. Use `GetChangeToken` to get the change token that you provide in the `ChangeToken` parameter of an `UpdateRule` request.
5. Submit an `UpdateRule` request to specify the predicates that you want to include in the `Rule`.
6. Create and update a `WebACL` that contains the `Rule`. For more information, see `CreateWebACL`.

rules that you add to a web ACL. You use UpdateRuleGroup to add rules to the rule group.

Rule groups are subject to the following limits:

• Three rule groups per account. You can request an increase to this limit by contacting customer support.
• One rule group per web ACL.
• Ten rules per rule group.

UpdateSizeConstraintSet to identify the part of a web request that you want AWS WAF to check for length, such as the length of the User-Agent header or the length of the query string. For example, you can create a SizeConstraintSet that matches any requests that have a query string that is longer than 100 bytes. You can then configure AWS WAF to reject those requests.

To create and configure a SizeConstraintSet, perform the following steps:

1. Use `GetChangeToken` to get the change token that you provide in the `ChangeToken` parameter of a `CreateSizeConstraintSet` request.
2. Submit a `CreateSizeConstraintSet` request.
3. Use `GetChangeToken` to get the change token that you provide in the `ChangeToken` parameter of an `UpdateSizeConstraintSet` request.
4. Submit an `UpdateSizeConstraintSet` request to specify the part of the request that you want AWS WAF to inspect (for example, the header or the URI) and the value that you want AWS WAF to watch for.

count requests that contain snippets of SQL code in a specified part of web requests. AWS WAF searches for character sequences that are likely to be malicious strings.

To create and configure a SqlInjectionMatchSet, perform the following steps:

1. Use `GetChangeToken` to get the change token that you provide in the `ChangeToken` parameter of a `CreateSqlInjectionMatchSet` request.
2. Submit a `CreateSqlInjectionMatchSet` request.
3. Use `GetChangeToken` to get the change token that you provide in the `ChangeToken` parameter of an `UpdateSqlInjectionMatchSet` request.
4. Submit an `UpdateSqlInjectionMatchSet` request to specify the parts of web requests in which you want to allow, block, or count malicious SQL code.

CloudFront web requests that you want to allow, block, or count. AWS WAF evaluates Rules in order based on the value of Priority for each Rule.

You also specify a default action, either ALLOW or BLOCK. If a web request doesn't match any of the Rules in a WebACL, AWS WAF responds to the request with the default action.

To create and configure a WebACL, perform the following steps:

1. Create and update the `ByteMatchSet` objects and other predicates that you want to include in `Rules`. For more information, see `CreateByteMatchSet`, `UpdateByteMatchSet`, `CreateIPSet`, `UpdateIPSet`, `CreateSqlInjectionMatchSet`, and `UpdateSqlInjectionMatchSet`.
2. Create and update the `Rules` that you want to include in the `WebACL`. For more information, see `CreateRule` and `UpdateRule`.
3. Use `GetChangeToken` to get the change token that you provide in the `ChangeToken` parameter of a `CreateWebACL` request.
4. Submit a `CreateWebACL` request.
5. Use `GetChangeToken` to get the change token that you provide in the `ChangeToken` parameter of an `UpdateWebACL` request.
6. Submit an `UpdateWebACL` request to specify the `Rules` that you want to include in the `WebACL`, to specify the default action, and to associate the `WebACL` with a CloudFront distribution.

Creates an AWS CloudFormation WAFV2 template for the specified web ACL in the specified Amazon S3 bucket. Then, in CloudFormation, you create a stack from the template, to create the web ACL and its resources in AWS WAFV2. Use this to migrate your AWS WAF Classic web ACL to the latest version of AWS WAF.

This is part of a larger migration procedure for web ACLs from AWS WAF Classic to the latest version of AWS WAF. For the full procedure, including caveats and manual steps to complete the migration and switch over to the new web ACL, see Migrating your AWS WAF Classic resources to AWS WAF in the AWS WAF Developer Guide.

requests that contain cross-site scripting attacks in the specified part of web requests. AWS WAF searches for character sequences that are likely to be malicious strings.

To create and configure an XssMatchSet, perform the following steps:

1. Use `GetChangeToken` to get the change token that you provide in the `ChangeToken` parameter of a `CreateXssMatchSet` request.
2. Submit a `CreateXssMatchSet` request.
3. Use `GetChangeToken` to get the change token that you provide in the `ChangeToken` parameter of an `UpdateXssMatchSet` request.
4. Submit an `UpdateXssMatchSet` request to specify the parts of web requests in which you want to allow, block, or count cross-site scripting attacks.

ByteMatchSet if it's still used in any Rules or if it still includes any ByteMatchTuple objects (any filters).

If you just want to remove a ByteMatchSet from a Rule, use UpdateRule.

To permanently delete a ByteMatchSet, perform the following steps:

1. Update the `ByteMatchSet` to remove filters, if any. For more information, see `UpdateByteMatchSet`.
2. Use `GetChangeToken` to get the change token that you provide in the `ChangeToken` parameter of a `DeleteByteMatchSet` request.
3. Submit a `DeleteByteMatchSet` request.

GeoMatchSet if it's still used in any Rules or if it still includes any countries.

If you just want to remove a GeoMatchSet from a Rule, use UpdateRule.

To permanently delete a GeoMatchSet from AWS WAF, perform the following steps:

1. Update the `GeoMatchSet` to remove any countries. For more information, see `UpdateGeoMatchSet`.
2. Use `GetChangeToken` to get the change token that you provide in the `ChangeToken` parameter of a `DeleteGeoMatchSet` request.
3. Submit a `DeleteGeoMatchSet` request.

still used in any Rules or if it still includes any IP addresses.

If you just want to remove an IPSet from a Rule, use UpdateRule.

To permanently delete an IPSet from AWS WAF, perform the following steps:

1. Update the `IPSet` to remove IP address ranges, if any. For more information, see `UpdateIPSet`.
2. Use `GetChangeToken` to get the change token that you provide in the `ChangeToken` parameter of a `DeleteIPSet` request.
3. Submit a `DeleteIPSet` request.

web ACL.

The user making the request must be the owner of the RuleGroup.

it's still used in any WebACL objects or if it still includes any predicates, such as ByteMatchSet objects.

If you just want to remove a rule from a WebACL, use UpdateWebACL.

To permanently delete a RateBasedRule from AWS WAF, perform the following steps:

1. Update the `RateBasedRule` to remove predicates, if any. For more information, see `UpdateRateBasedRule`.
2. Use `GetChangeToken` to get the change token that you provide in the `ChangeToken` parameter of a `DeleteRateBasedRule` request.
3. Submit a `DeleteRateBasedRule` request.

RegexMatchSet if it's still used in any Rules or if it still includes any RegexMatchTuples objects (any filters).

If you just want to remove a RegexMatchSet from a Rule, use UpdateRule.

To permanently delete a RegexMatchSet, perform the following steps:

1. Update the `RegexMatchSet` to remove filters, if any. For more information, see `UpdateRegexMatchSet`.
2. Use `GetChangeToken` to get the change token that you provide in the `ChangeToken` parameter of a `DeleteRegexMatchSet` request.
3. Submit a `DeleteRegexMatchSet` request.

RegexPatternSet if it's still used in any RegexMatchSet or if the RegexPatternSet is not empty.

still used in any WebACL objects or if it still includes any predicates, such as ByteMatchSet objects.

If you just want to remove a Rule from a WebACL, use UpdateWebACL.

To permanently delete a Rule from AWS WAF, perform the following steps:

1. Update the `Rule` to remove predicates, if any. For more information, see `UpdateRule`.
2. Use `GetChangeToken` to get the change token that you provide in the `ChangeToken` parameter of a `DeleteRule` request.
3. Submit a `DeleteRule` request.

if it's still used in any WebACL objects or if it still includes any rules.

If you just want to remove a RuleGroup from a WebACL, use UpdateWebACL.

To permanently delete a RuleGroup from AWS WAF, perform the following steps:

1. Update the `RuleGroup` to remove rules, if any. For more information, see `UpdateRuleGroup`.
2. Use `GetChangeToken` to get the change token that you provide in the `ChangeToken` parameter of a `DeleteRuleGroup` request.
3. Submit a `DeleteRuleGroup` request.

SizeConstraintSet if it's still used in any Rules or if it still includes any SizeConstraint objects (any filters).

If you just want to remove a SizeConstraintSet from a Rule, use UpdateRule.

To permanently delete a SizeConstraintSet, perform the following steps:

1. Update the `SizeConstraintSet` to remove filters, if any. For more information, see `UpdateSizeConstraintSet`.
2. Use `GetChangeToken` to get the change token that you provide in the `ChangeToken` parameter of a `DeleteSizeConstraintSet` request.
3. Submit a `DeleteSizeConstraintSet` request.

SqlInjectionMatchSet if it's still used in any Rules or if it still contains any SqlInjectionMatchTuple objects.

If you just want to remove a SqlInjectionMatchSet from a Rule, use UpdateRule.

To permanently delete a SqlInjectionMatchSet from AWS WAF, perform the following steps:

1. Update the `SqlInjectionMatchSet` to remove filters, if any. For more information, see `UpdateSqlInjectionMatchSet`.
2. Use `GetChangeToken` to get the change token that you provide in the `ChangeToken` parameter of a `DeleteSqlInjectionMatchSet` request.
3. Submit a `DeleteSqlInjectionMatchSet` request.

still contains any Rules.

To delete a WebACL, perform the following steps:

1. Update the `WebACL` to remove `Rules`, if any. For more information, see `UpdateWebACL`.
2. Use `GetChangeToken` to get the change token that you provide in the `ChangeToken` parameter of a `DeleteWebACL` request.
3. Submit a `DeleteWebACL` request.

XssMatchSet if it's still used in any Rules or if it still contains any XssMatchTuple objects.

If you just want to remove an XssMatchSet from a Rule, use UpdateRule.

To permanently delete an XssMatchSet from AWS WAF, perform the following steps:

1. Update the `XssMatchSet` to remove filters, if any. For more information, see `UpdateXssMatchSet`.
2. Use `GetChangeToken` to get the change token that you provide in the `ChangeToken` parameter of a `DeleteXssMatchSet` request.
3. Submit a `DeleteXssMatchSet` request.

change token and include the change token in the create, update, or delete request. Change tokens ensure that your application doesn't submit conflicting requests to AWS WAF.

Each create, update, or delete request must use a unique change token. If your application submits a GetChangeToken request and then submits a second GetChangeToken request before submitting a create, update, or delete request, the second GetChangeToken request returns the same value as the first GetChangeToken request.

When you use a change token in a create, update, or delete request, the status of the change token changes to PENDING, which indicates that AWS WAF is propagating the change to all AWS WAF servers. Use GetChangeTokenStatus to determine the status of your change token.

GetChangeToken. ChangeTokenStatus is one of the following values:

• `PROVISIONED`: You requested the change token by calling `GetChangeToken`, but you haven't used it yet in a call to create, update, or delete an AWS WAF object.
• `PENDING`: AWS WAF is propagating the create, update, or delete request to all AWS WAF servers.
• `INSYNC`: Propagation is complete.

you included in the GetRateBasedRule request.

RateBasedRule that is specified by the RuleId. The maximum number of managed keys that will be blocked is 10,000. If more than 10,000 addresses exceed the rate limit, the 10,000 addresses with the highest rates will be blocked.

included in the GetRule request.

you included in the GetRuleGroup request.

To view the rules in a rule group, use ListActivatedRulesInRuleGroup.

sample--that AWS WAF randomly selects from among the first 5,000 requests that your AWS resource received during a time range that you choose. You can specify a sample size of up to 500 requests, and you can specify any time range in the previous three hours.

GetSampledRequests returns a time range, which is usually the time range that you specified. However, if your resource (such as a CloudFront distribution) received 5,000 requests before the specified time range elapsed, GetSampledRequests returns an updated time range. This new time range indicates the actual period during which AWS WAF selected the requests in the sample.

SqlInjectionMatchSetId.

are key:value pairs that you can use to categorize and manage your resources, for purposes like billing. For example, you might set the tag key to "customer" and the value to the customer name or ID. You can specify one or more tags to add to each AWS resource, up to 50 tags for a resource.

Tagging is only available through the API, SDKs, and CLI. You can't manage or view tags through the AWS WAF Classic console. You can tag the AWS resources that you manage through AWS WAF Classic: web ACLs, rule groups, and rules.

You can access information about all traffic that AWS WAF inspects using the following steps:

1. Create an Amazon Kinesis Data Firehose. Create the data firehose with a PUT source and in the region that you are operating. However, if you are capturing logs for Amazon CloudFront, always create the firehose in US East (N. Virginia). Do not create the data firehose using a `Kinesis stream` as your source.
2. Associate that firehose to your web ACL using a `PutLoggingConfiguration` request.

supported use for this action is to share a RuleGroup across accounts.

The PutPermissionPolicy is subject to the following restrictions:

• You can attach only one policy with each `PutPermissionPolicy` request.
• The policy must include an `Effect`, `Action` and `Principal`.
• `Effect` must specify `Allow`.
• The `Action` in the policy must be `waf:UpdateWebACL`, `waf-regional:UpdateWebACL`, `waf:GetRuleGroup` and `waf-regional:GetRuleGroup` . Any extra or wildcard actions in the policy will be rejected.
• The policy cannot include a `Resource` parameter.
• The ARN in the request must be a valid WAF RuleGroup ARN and the RuleGroup must exist in the same region.
• The user making the request must be the owner of the RuleGroup.
• Your policy must be composed using IAM Policy version 2012-10-17.

pairs that you can use to categorize and manage your resources, for purposes like billing. For example, you might set the tag key to "customer" and the value to the customer name or ID. You can specify one or more tags to add to each AWS resource, up to 50 tags for a resource.

Tagging is only available through the API, SDKs, and CLI. You can't manage or view tags through the AWS WAF Classic console. You can use this action to tag the AWS resources that you manage through AWS WAF Classic: web ACLs, rule groups, and rules.

ByteMatchSet. For each ByteMatchTuple object, you specify the following values:

• Whether to insert or delete the object from the array. If you want to change a `ByteMatchSetUpdate` object, you delete the existing object and add a new one.
• The part of a web request that you want AWS WAF to inspect, such as a query string or the value of the `User-Agent` header.
• The bytes (typically a string that corresponds with ASCII characters) that you want AWS WAF to look for. For more information, including how you specify the values for the AWS WAF API and the AWS CLI or SDKs, see `TargetString` in the `ByteMatchTuple` data type.
• Where to look, such as at the beginning or the end of a query string.
• Whether to perform any conversions on the request, such as converting it to lowercase, before inspecting it for the specified string.

1. Create a `ByteMatchSet.` For more information, see `CreateByteMatchSet`.
2. Use `GetChangeToken` to get the change token that you provide in the `ChangeToken` parameter of an `UpdateByteMatchSet` request.
3. Submit an `UpdateByteMatchSet` request to specify the part of the request that you want AWS WAF to inspect (for example, the header or the URI) and the value that you want AWS WAF to watch for.

GeoMatchSet. For each GeoMatchConstraint object, you specify the following values:

• Whether to insert or delete the object from the array. If you want to change an `GeoMatchConstraint` object, you delete the existing object and add a new one.
• The `Type`. The only valid value for `Type` is `Country`.
• The `Value`, which is a two character code for the country to add to the `GeoMatchConstraint` object. Valid codes are listed in `GeoMatchConstraint$Value`.

1. Submit a `CreateGeoMatchSet` request.
2. Use `GetChangeToken` to get the change token that you provide in the `ChangeToken` parameter of an `UpdateGeoMatchSet` request.
3. Submit an `UpdateGeoMatchSet` request to specify the country that you want AWS WAF to watch for.

each IPSetDescriptor object, you specify the following values:

• Whether to insert or delete the object from the array. If you want to change an `IPSetDescriptor` object, you delete the existing object and add a new one.
• The IP address version, `IPv4` or `IPv6`.
• The IP address in CIDR notation, for example, `192.0.2.0/24` (for the range of IP addresses from `192.0.2.0` to `192.0.2.255`) or `192.0.2.44/32` (for the individual IP address `192.0.2.44`).

• 1111:0000:0000:0000:0000:0000:0000:0111/128
• 1111:0:0:0:0:0:0:0111/128
• 1111::0111/128
• 1111::111/128

1. Submit a `CreateIPSet` request.
2. Use `GetChangeToken` to get the change token that you provide in the `ChangeToken` parameter of an `UpdateIPSet` request.
3. Submit an `UpdateIPSet` request to specify the IP addresses that you want AWS WAF to watch for.

RateLimit in the rule.

Each Predicate object identifies a predicate, such as a ByteMatchSet or an IPSet, that specifies the web requests that you want to block or count. The RateLimit specifies the number of requests every five minutes that triggers the rule.

If you add more than one predicate to a RateBasedRule, a request must match all the predicates and exceed the RateLimit to be counted or blocked. For example, suppose you add the following to a RateBasedRule:

• An `IPSet` that matches the IP address `192.0.2.44/32`
• A `ByteMatchSet` that matches `BadBot` in the `User-Agent` header

• A `ByteMatchSet` with `FieldToMatch` of [`URI`](https://hexdocs.pm/elixir/URI.html)
• A `PositionalConstraint` of `STARTS_WITH`
• A `TargetString` of `login`

RegexMatchSet. For each RegexMatchSetUpdate object, you specify the following values:

• Whether to insert or delete the object from the array. If you want to change a `RegexMatchSetUpdate` object, you delete the existing object and add a new one.
• The part of a web request that you want AWS WAF to inspectupdate, such as a query string or the value of the `User-Agent` header.
• The identifier of the pattern (a regular expression) that you want AWS WAF to look for. For more information, see `RegexPatternSet`.
• Whether to perform any conversions on the request, such as converting it to lowercase, before inspecting it for the specified string.

1. Create a `RegexMatchSet.` For more information, see `CreateRegexMatchSet`.
2. Use `GetChangeToken` to get the change token that you provide in the `ChangeToken` parameter of an `UpdateRegexMatchSet` request.
3. Submit an `UpdateRegexMatchSet` request to specify the part of the request that you want AWS WAF to inspect (for example, the header or the URI) and the identifier of the `RegexPatternSet` that contain the regular expression patters you want AWS WAF to watch for.

RegexPatternSet. For each RegexPatternString object, you specify the following values:

• Whether to insert or delete the `RegexPatternString`.
• The regular expression pattern that you want to insert or delete. For more information, see `RegexPatternSet`.

• BadBot
• BadB0t
• B@dBot
• B@dB0t

1. Create a `RegexPatternSet.` For more information, see `CreateRegexPatternSet`.
2. Use `GetChangeToken` to get the change token that you provide in the `ChangeToken` parameter of an `UpdateRegexPatternSet` request.
3. Submit an `UpdateRegexPatternSet` request to specify the regular expression pattern that you want AWS WAF to watch for.

Predicate object identifies a predicate, such as a ByteMatchSet or an IPSet, that specifies the web requests that you want to allow, block, or count. If you add more than one predicate to a Rule, a request must match all of the specifications to be allowed, blocked, or counted. For example, suppose that you add the following to a Rule:

• A `ByteMatchSet` that matches the value `BadBot` in the `User-Agent` header
• An `IPSet` that matches the IP address `192.0.2.44`

1. Create and update the predicates that you want to include in the `Rule`.
2. Create the `Rule`. See `CreateRule`.
3. Use `GetChangeToken` to get the change token that you provide in the `ChangeToken` parameter of an `UpdateRule` request.
4. Submit an `UpdateRule` request to add predicates to the `Rule`.
5. Create and update a `WebACL` that contains the `Rule`. See `CreateWebACL`.

You can only insert REGULAR rules into a rule group.

You can have a maximum of ten rules per rule group.

To create and configure a RuleGroup, perform the following steps:

1. Create and update the `Rules` that you want to include in the `RuleGroup`. See `CreateRule`.
2. Use `GetChangeToken` to get the change token that you provide in the `ChangeToken` parameter of an `UpdateRuleGroup` request.
3. Submit an `UpdateRuleGroup` request to add `Rules` to the `RuleGroup`.
4. Create and update a `WebACL` that contains the `RuleGroup`. See `CreateWebACL`.

SizeConstraintSet. For each SizeConstraint object, you specify the following values:

• Whether to insert or delete the object from the array. If you want to change a `SizeConstraintSetUpdate` object, you delete the existing object and add a new one.
• The part of a web request that you want AWS WAF to evaluate, such as the length of a query string or the length of the `User-Agent` header.
• Whether to perform any transformations on the request, such as converting it to lowercase, before checking its length. Note that transformations of the request body are not supported because the AWS resource forwards only the first `8192` bytes of your request to AWS WAF. You can only specify a single type of TextTransformation.
• A `ComparisonOperator` used for evaluating the selected part of the request against the specified `Size`, such as equals, greater than, less than, and so on.
• The length, in bytes, that you want AWS WAF to watch for in selected part of the request. The length is computed after applying the transformation.

1. Create a `SizeConstraintSet.` For more information, see `CreateSizeConstraintSet`.
2. Use `GetChangeToken` to get the change token that you provide in the `ChangeToken` parameter of an `UpdateSizeConstraintSet` request.
3. Submit an `UpdateSizeConstraintSet` request to specify the part of the request that you want AWS WAF to inspect (for example, the header or the URI) and the value that you want AWS WAF to watch for.

SqlInjectionMatchSet. For each SqlInjectionMatchTuple object, you specify the following values:

• `Action`: Whether to insert the object into or delete the object from the array. To change a `SqlInjectionMatchTuple`, you delete the existing object and add a new one.
• `FieldToMatch`: The part of web requests that you want AWS WAF to inspect and, if you want AWS WAF to inspect a header or custom query parameter, the name of the header or parameter.
• `TextTransformation`: Which text transformation, if any, to perform on the web request before inspecting the request for snippets of malicious SQL code. You can only specify a single type of TextTransformation.

1. Submit a `CreateSqlInjectionMatchSet` request.
2. Use `GetChangeToken` to get the change token that you provide in the `ChangeToken` parameter of an `UpdateIPSet` request.
3. Submit an `UpdateSqlInjectionMatchSet` request to specify the parts of web requests that you want AWS WAF to inspect for snippets of SQL code.

Rule identifies web requests that you want to allow, block, or count. When you update a WebACL, you specify the following values:

• A default action for the `WebACL`, either `ALLOW` or `BLOCK`. AWS WAF performs the default action if a request doesn't match the criteria in any of the `Rules` in a `WebACL`.
• The `Rules` that you want to add or delete. If you want to replace one `Rule` with another, you delete the existing `Rule` and add the new one.
• For each `Rule`, whether you want AWS WAF to allow requests, block requests, or count requests that match the conditions in the `Rule`.
• The order in which you want AWS WAF to evaluate the `Rules` in a `WebACL`. If you add more than one `Rule` to a `WebACL`, AWS WAF evaluates each request against the `Rules` in order based on the value of `Priority`. (The `Rule` that has the lowest value for `Priority` is evaluated first.) When a web request matches all the predicates (such as `ByteMatchSets` and `IPSets`) in a `Rule`, AWS WAF immediately takes the corresponding action, allow or block, and doesn't evaluate the request against the remaining `Rules` in the `WebACL`, if any.

1. Create and update the predicates that you want to include in `Rules`. For more information, see `CreateByteMatchSet`, `UpdateByteMatchSet`, `CreateIPSet`, `UpdateIPSet`, `CreateSqlInjectionMatchSet`, and `UpdateSqlInjectionMatchSet`.
2. Create and update the `Rules` that you want to include in the `WebACL`. For more information, see `CreateRule` and `UpdateRule`.
3. Create a `WebACL`. See `CreateWebACL`.
4. Use `GetChangeToken` to get the change token that you provide in the `ChangeToken` parameter of an `UpdateWebACL` request.
5. Submit an `UpdateWebACL` request to specify the `Rules` that you want to include in the `WebACL`, to specify the default action, and to associate the `WebACL` with a CloudFront distribution. The `ActivatedRule` can be a rule group. If you specify a rule group as your `ActivatedRule` , you can exclude specific rules from that rule group. If you already have a rule group associated with a web ACL and want to submit an `UpdateWebACL` request to exclude certain rules from that rule group, you must first remove the rule group from the web ACL, the re-insert it again, specifying the excluded rules. For details, see `ActivatedRule$ExcludedRules` .

XssMatchSet. For each XssMatchTuple object, you specify the following values:

• `Action`: Whether to insert the object into or delete the object from the array. To change an `XssMatchTuple`, you delete the existing object and add a new one.
• `FieldToMatch`: The part of web requests that you want AWS WAF to inspect and, if you want AWS WAF to inspect a header or custom query parameter, the name of the header or parameter.
• `TextTransformation`: Which text transformation, if any, to perform on the web request before inspecting the request for cross-site scripting attacks. You can only specify a single type of TextTransformation.

1. Submit a `CreateXssMatchSet` request.
2. Use `GetChangeToken` to get the change token that you provide in the `ChangeToken` parameter of an `UpdateIPSet` request.
3. Submit an `UpdateXssMatchSet` request to specify the parts of web requests that you want AWS WAF to inspect for cross-site scripting attacks.