You are viewing the documentation for an older major version of the AWS SDK for JavaScript.
The modular AWS SDK for JavaScript (v3), the latest major version of AWS SDK for JavaScript, is now stable and recommended for general use. For more information, see the Migration Guide and API Reference.

Class: AWS.WAFV2

Inherits:
AWS.Service show all
Identifier:
wafv2
API Version:
2019-07-29
Defined in:
(unknown)

Overview

Constructs a service interface object. Each API operation is exposed as a function on service.

Service Description

Note: This is the latest version of the WAF API, released in November, 2019. The names of the entities that you use to access this API, like endpoints and namespaces, all have the versioning information added, like "V2" or "v2", to distinguish from the prior version. We recommend migrating your resources to this version, because it has a number of significant improvements. If you used WAF prior to this release, you can't use this WAFV2 API to access any WAF resources that you created before. You can access your old rules, web ACLs, and other WAF resources only through the WAF Classic APIs. The WAF Classic APIs have retained the prior names, endpoints, and namespaces. For information, including how to migrate your WAF resources to this version, see the WAF Developer Guide.

WAF is a web application firewall that lets you monitor the HTTP and HTTPS requests that are forwarded to Amazon CloudFront, an Amazon API Gateway REST API, an Application Load Balancer, or an AppSync GraphQL API. WAF also lets you control access to your content. Based on conditions that you specify, such as the IP addresses that requests originate from or the values of query strings, the Amazon API Gateway REST API, CloudFront distribution, the Application Load Balancer, or the AppSync GraphQL API responds to requests either with the requested content or with an HTTP 403 status code (Forbidden). You also can configure CloudFront to return a custom error page when a request is blocked.

This API guide is for developers who need detailed information about WAF API actions, data types, and errors. For detailed information about WAF features and an overview of how to use WAF, see the WAF Developer Guide.

You can make calls using the endpoints listed in WAF endpoints and quotas.

  • For regional applications, you can use any of the endpoints in the list. A regional application can be an Application Load Balancer (ALB), an Amazon API Gateway REST API, or an AppSync GraphQL API.

  • For Amazon CloudFront applications, you must use the API endpoint listed for US East (N. Virginia): us-east-1.

Alternatively, you can use one of the Amazon Web Services SDKs to access an API that's tailored to the programming language or platform that you're using. For more information, see Amazon Web Services SDKs.

We currently provide two versions of the WAF API: this API and the prior versions, the classic WAF APIs. This new API provides the same functionality as the older versions, with the following major improvements:

  • You use one API for both global and regional applications. Where you need to distinguish the scope, you specify a Scope parameter and set it to CLOUDFRONT or REGIONAL.

  • You can define a web ACL or rule group with a single call, and update it with a single call. You define all rule specifications in JSON format, and pass them to your rule group or web ACL calls.

  • The limits WAF places on the use of rules more closely reflects the cost of running each type of rule. Rule groups include capacity settings, so you know the maximum cost of a rule group when you use it.

Sending a Request Using WAFV2

var wafv2 = new AWS.WAFV2();
wafv2.associateWebACL(params, function (err, data) {
  if (err) console.log(err, err.stack); // an error occurred
  else     console.log(data);           // successful response
});

Locking the API Version

In order to ensure that the WAFV2 object uses this specific API, you can construct the object by passing the apiVersion option to the constructor:

var wafv2 = new AWS.WAFV2({apiVersion: '2019-07-29'});

You can also set the API version globally in AWS.config.apiVersions using the wafv2 service identifier:

AWS.config.apiVersions = {
  wafv2: '2019-07-29',
  // other service API versions
};

var wafv2 = new AWS.WAFV2();

Version:

  • 2019-07-29

Constructor Summary collapse

Property Summary collapse

Properties inherited from AWS.Service

apiVersions

Method Summary collapse

Methods inherited from AWS.Service

makeRequest, makeUnauthenticatedRequest, waitFor, setupRequestListeners, defineService

Constructor Details

new AWS.WAFV2(options = {}) ⇒ Object

Constructs a service object. This object has one method for each API operation.

Examples:

Constructing a WAFV2 object

var wafv2 = new AWS.WAFV2({apiVersion: '2019-07-29'});

Options Hash (options):

  • params (map) —

    An optional map of parameters to bind to every request sent by this service object. For more information on bound parameters, see "Working with Services" in the Getting Started Guide.

  • endpoint (String|AWS.Endpoint) —

    The endpoint URI to send requests to. The default endpoint is built from the configured region. The endpoint should be a string like 'https://{service}.{region}.amazonaws.com' or an Endpoint object.

  • accessKeyId (String) —

    your AWS access key ID.

  • secretAccessKey (String) —

    your AWS secret access key.

  • sessionToken (AWS.Credentials) —

    the optional AWS session token to sign requests with.

  • credentials (AWS.Credentials) —

    the AWS credentials to sign requests with. You can either specify this object, or specify the accessKeyId and secretAccessKey options directly.

  • credentialProvider (AWS.CredentialProviderChain) —

    the provider chain used to resolve credentials if no static credentials property is set.

  • region (String) —

    the region to send service requests to. See AWS.WAFV2.region for more information.

  • maxRetries (Integer) —

    the maximum amount of retries to attempt with a request. See AWS.WAFV2.maxRetries for more information.

  • maxRedirects (Integer) —

    the maximum amount of redirects to follow with a request. See AWS.WAFV2.maxRedirects for more information.

  • sslEnabled (Boolean) —

    whether to enable SSL for requests.

  • paramValidation (Boolean|map) —

    whether input parameters should be validated against the operation description before sending the request. Defaults to true. Pass a map to enable any of the following specific validation features:

    • min [Boolean] — Validates that a value meets the min constraint. This is enabled by default when paramValidation is set to true.
    • max [Boolean] — Validates that a value meets the max constraint.
    • pattern [Boolean] — Validates that a string value matches a regular expression.
    • enum [Boolean] — Validates that a string value matches one of the allowable enum values.
  • computeChecksums (Boolean) —

    whether to compute checksums for payload bodies when the service accepts it (currently supported in S3 only)

  • convertResponseTypes (Boolean) —

    whether types are converted when parsing response data. Currently only supported for JSON based services. Turning this off may improve performance on large response payloads. Defaults to true.

  • correctClockSkew (Boolean) —

    whether to apply a clock skew correction and retry requests that fail because of an skewed client clock. Defaults to false.

  • s3ForcePathStyle (Boolean) —

    whether to force path style URLs for S3 objects.

  • s3BucketEndpoint (Boolean) —

    whether the provided endpoint addresses an individual bucket (false if it addresses the root API endpoint). Note that setting this configuration option requires an endpoint to be provided explicitly to the service constructor.

  • s3DisableBodySigning (Boolean) —

    whether S3 body signing should be disabled when using signature version v4. Body signing can only be disabled when using https. Defaults to true.

  • s3UsEast1RegionalEndpoint ('legacy'|'regional') —

    when region is set to 'us-east-1', whether to send s3 request to global endpoints or 'us-east-1' regional endpoints. This config is only applicable to S3 client. Defaults to legacy

  • s3UseArnRegion (Boolean) —

    whether to override the request region with the region inferred from requested resource's ARN. Only available for S3 buckets Defaults to true

  • retryDelayOptions (map) —

    A set of options to configure the retry delay on retryable errors. Currently supported options are:

    • base [Integer] — The base number of milliseconds to use in the exponential backoff for operation retries. Defaults to 100 ms for all services except DynamoDB, where it defaults to 50ms.
    • customBackoff [function] — A custom function that accepts a retry count and error and returns the amount of time to delay in milliseconds. If the result is a non-zero negative value, no further retry attempts will be made. The base option will be ignored if this option is supplied. The function is only called for retryable errors.
  • httpOptions (map) —

    A set of options to pass to the low-level HTTP request. Currently supported options are:

    • proxy [String] — the URL to proxy requests through
    • agent [http.Agent, https.Agent] — the Agent object to perform HTTP requests with. Used for connection pooling. Defaults to the global agent (http.globalAgent) for non-SSL connections. Note that for SSL connections, a special Agent object is used in order to enable peer certificate verification. This feature is only available in the Node.js environment.
    • connectTimeout [Integer] — Sets the socket to timeout after failing to establish a connection with the server after connectTimeout milliseconds. This timeout has no effect once a socket connection has been established.
    • timeout [Integer] — Sets the socket to timeout after timeout milliseconds of inactivity on the socket. Defaults to two minutes (120000).
    • xhrAsync [Boolean] — Whether the SDK will send asynchronous HTTP requests. Used in the browser environment only. Set to false to send requests synchronously. Defaults to true (async on).
    • xhrWithCredentials [Boolean] — Sets the "withCredentials" property of an XMLHttpRequest object. Used in the browser environment only. Defaults to false.
  • apiVersion (String, Date) —

    a String in YYYY-MM-DD format (or a date) that represents the latest possible API version that can be used in all services (unless overridden by apiVersions). Specify 'latest' to use the latest possible version.

  • apiVersions (map<String, String|Date>) —

    a map of service identifiers (the lowercase service class name) with the API version to use when instantiating a service. Specify 'latest' for each individual that can use the latest available version.

  • logger (#write, #log) —

    an object that responds to .write() (like a stream) or .log() (like the console object) in order to log information about requests

  • systemClockOffset (Number) —

    an offset value in milliseconds to apply to all signing times. Use this to compensate for clock skew when your system may be out of sync with the service time. Note that this configuration option can only be applied to the global AWS.config object and cannot be overridden in service-specific configuration. Defaults to 0 milliseconds.

  • signatureVersion (String) —

    the signature version to sign requests with (overriding the API configuration). Possible values are: 'v2', 'v3', 'v4'.

  • signatureCache (Boolean) —

    whether the signature to sign requests with (overriding the API configuration) is cached. Only applies to the signature version 'v4'. Defaults to true.

  • dynamoDbCrc32 (Boolean) —

    whether to validate the CRC32 checksum of HTTP response bodies returned by DynamoDB. Default: true.

  • useAccelerateEndpoint (Boolean) —

    Whether to use the S3 Transfer Acceleration endpoint with the S3 service. Default: false.

  • clientSideMonitoring (Boolean) —

    whether to collect and publish this client's performance metrics of all its API requests.

  • endpointDiscoveryEnabled (Boolean|undefined) —

    whether to call operations with endpoints given by service dynamically. Setting this

  • endpointCacheSize (Number) —

    the size of the global cache storing endpoints from endpoint discovery operations. Once endpoint cache is created, updating this setting cannot change existing cache size. Defaults to 1000

  • hostPrefixEnabled (Boolean) —

    whether to marshal request parameters to the prefix of hostname. Defaults to true.

  • stsRegionalEndpoints ('legacy'|'regional') —

    whether to send sts request to global endpoints or regional endpoints. Defaults to 'legacy'.

Property Details

endpoint ⇒ AWS.Endpoint (readwrite)

Returns an Endpoint object representing the endpoint URL for service requests.

Returns:

  • (AWS.Endpoint) —

    an Endpoint object representing the endpoint URL for service requests.

Method Details

associateWebACL(params = {}, callback) ⇒ AWS.Request

Associates a web ACL with a regional application resource, to protect the resource. A regional application can be an Application Load Balancer (ALB), an Amazon API Gateway REST API, or an AppSync GraphQL API.

For Amazon CloudFront, don't use this call. Instead, use your CloudFront distribution configuration. To associate a web ACL, in the CloudFront call UpdateDistribution, set the web ACL ID to the Amazon Resource Name (ARN) of the web ACL. For information, see UpdateDistribution.

Service Reference:

Examples:

Calling the associateWebACL operation

var params = {
  ResourceArn: 'STRING_VALUE', /* required */
  WebACLArn: 'STRING_VALUE' /* required */
};
wafv2.associateWebACL(params, function(err, data) {
  if (err) console.log(err, err.stack); // an error occurred
  else     console.log(data);           // successful response
});

Parameters:

  • params (Object) (defaults to: {}) —
    • WebACLArn — (String)

      The Amazon Resource Name (ARN) of the web ACL that you want to associate with the resource.

    • ResourceArn — (String)

      The Amazon Resource Name (ARN) of the resource to associate with the web ACL.

      The ARN must be in one of the following formats:

      • For an Application Load Balancer: arn:aws:elasticloadbalancing:region:account-id:loadbalancer/app/load-balancer-name/load-balancer-id

      • For an Amazon API Gateway REST API: arn:aws:apigateway:region::/restapis/api-id/stages/stage-name

      • For an AppSync GraphQL API: arn:aws:appsync:region:account-id:apis/GraphQLApiId

Callback (callback):

  • function(err, data) { ... }

    Called when a response from the service is returned. If a callback is not supplied, you must call AWS.Request.send() on the returned request object to initiate the request.

    Context (this):

    • (AWS.Response) —

      the response object containing error, data properties, and the original request object.

    Parameters:

    • err (Error) —

      the error object returned from the request. Set to null if the request is successful.

    • data (Object) —

      the de-serialized data returned from the request. Set to null if a request error occurs.

Returns:

  • (AWS.Request) —

    a handle to the operation request for subsequent event callback registration.

checkCapacity(params = {}, callback) ⇒ AWS.Request

Returns the web ACL capacity unit (WCU) requirements for a specified scope and set of rules. You can use this to check the capacity requirements for the rules you want to use in a RuleGroup or WebACL.

WAF uses WCUs to calculate and control the operating resources that are used to run your rules, rule groups, and web ACLs. WAF calculates capacity differently for each rule type, to reflect the relative cost of each rule. Simple rules that cost little to run use fewer WCUs than more complex rules that use more processing power. Rule group capacity is fixed at creation, which helps users plan their web ACL WCU usage when they use a rule group. The WCU limit for web ACLs is 1,500.

Service Reference:

Examples:

Calling the checkCapacity operation

var params = {
  Rules: [ /* required */
    {
      Name: 'STRING_VALUE', /* required */
      Priority: 'NUMBER_VALUE', /* required */
      Statement: { /* Statement */ /* required */
        AndStatement: {
          Statements: [ /* required */
            /* recursive Statement */,
            /* more items */
          ]
        },
        ByteMatchStatement: {
          FieldToMatch: { /* required */
            AllQueryArguments: {
            },
            Body: {
            },
            JsonBody: {
              MatchPattern: { /* required */
                All: {
                },
                IncludedPaths: [
                  'STRING_VALUE',
                  /* more items */
                ]
              },
              MatchScope: ALL | KEY | VALUE, /* required */
              InvalidFallbackBehavior: MATCH | NO_MATCH | EVALUATE_AS_STRING
            },
            Method: {
            },
            QueryString: {
            },
            SingleHeader: {
              Name: 'STRING_VALUE' /* required */
            },
            SingleQueryArgument: {
              Name: 'STRING_VALUE' /* required */
            },
            UriPath: {
            }
          },
          PositionalConstraint: EXACTLY | STARTS_WITH | ENDS_WITH | CONTAINS | CONTAINS_WORD, /* required */
          SearchString: Buffer.from('...') || 'STRING_VALUE' /* Strings will be Base-64 encoded on your behalf */, /* required */
          TextTransformations: [ /* required */
            {
              Priority: 'NUMBER_VALUE', /* required */
              Type: NONE | COMPRESS_WHITE_SPACE | HTML_ENTITY_DECODE | LOWERCASE | CMD_LINE | URL_DECODE | BASE64_DECODE | HEX_DECODE | MD5 | REPLACE_COMMENTS | ESCAPE_SEQ_DECODE | SQL_HEX_DECODE | CSS_DECODE | JS_DECODE | NORMALIZE_PATH | NORMALIZE_PATH_WIN | REMOVE_NULLS | REPLACE_NULLS | BASE64_DECODE_EXT | URL_DECODE_UNI | UTF8_TO_UNICODE /* required */
            },
            /* more items */
          ]
        },
        GeoMatchStatement: {
          CountryCodes: [
            AF | AX | AL | DZ | AS | AD | AO | AI | AQ | AG | AR | AM | AW | AU | AT | AZ | BS | BH | BD | BB | BY | BE | BZ | BJ | BM | BT | BO | BQ | BA | BW | BV | BR | IO | BN | BG | BF | BI | KH | CM | CA | CV | KY | CF | TD | CL | CN | CX | CC | CO | KM | CG | CD | CK | CR | CI | HR | CU | CW | CY | CZ | DK | DJ | DM | DO | EC | EG | SV | GQ | ER | EE | ET | FK | FO | FJ | FI | FR | GF | PF | TF | GA | GM | GE | DE | GH | GI | GR | GL | GD | GP | GU | GT | GG | GN | GW | GY | HT | HM | VA | HN | HK | HU | IS | IN | ID | IR | IQ | IE | IM | IL | IT | JM | JP | JE | JO | KZ | KE | KI | KP | KR | KW | KG | LA | LV | LB | LS | LR | LY | LI | LT | LU | MO | MK | MG | MW | MY | MV | ML | MT | MH | MQ | MR | MU | YT | MX | FM | MD | MC | MN | ME | MS | MA | MZ | MM | NA | NR | NP | NL | NC | NZ | NI | NE | NG | NU | NF | MP | NO | OM | PK | PW | PS | PA | PG | PY | PE | PH | PN | PL | PT | PR | QA | RE | RO | RU | RW | BL | SH | KN | LC | MF | PM | VC | WS | SM | ST | SA | SN | RS | SC | SL | SG | SX | SK | SI | SB | SO | ZA | GS | SS | ES | LK | SD | SR | SJ | SZ | SE | CH | SY | TW | TJ | TZ | TH | TL | TG | TK | TO | TT | TN | TR | TM | TC | TV | UG | UA | AE | GB | US | UM | UY | UZ | VU | VE | VN | VG | VI | WF | EH | YE | ZM | ZW,
            /* more items */
          ],
          ForwardedIPConfig: {
            FallbackBehavior: MATCH | NO_MATCH, /* required */
            HeaderName: 'STRING_VALUE' /* required */
          }
        },
        IPSetReferenceStatement: {
          ARN: 'STRING_VALUE', /* required */
          IPSetForwardedIPConfig: {
            FallbackBehavior: MATCH | NO_MATCH, /* required */
            HeaderName: 'STRING_VALUE', /* required */
            Position: FIRST | LAST | ANY /* required */
          }
        },
        LabelMatchStatement: {
          Key: 'STRING_VALUE', /* required */
          Scope: LABEL | NAMESPACE /* required */
        },
        ManagedRuleGroupStatement: {
          Name: 'STRING_VALUE', /* required */
          VendorName: 'STRING_VALUE', /* required */
          ExcludedRules: [
            {
              Name: 'STRING_VALUE' /* required */
            },
            /* more items */
          ],
          ScopeDownStatement: /* recursive Statement */,
          Version: 'STRING_VALUE'
        },
        NotStatement: {
          Statement: /* recursive Statement */
        },
        OrStatement: {
          Statements: [ /* required */
            /* recursive Statement */,
            /* more items */
          ]
        },
        RateBasedStatement: {
          AggregateKeyType: IP | FORWARDED_IP, /* required */
          Limit: 'NUMBER_VALUE', /* required */
          ForwardedIPConfig: {
            FallbackBehavior: MATCH | NO_MATCH, /* required */
            HeaderName: 'STRING_VALUE' /* required */
          },
          ScopeDownStatement: /* recursive Statement */
        },
        RegexMatchStatement: {
          FieldToMatch: { /* required */
            AllQueryArguments: {
            },
            Body: {
            },
            JsonBody: {
              MatchPattern: { /* required */
                All: {
                },
                IncludedPaths: [
                  'STRING_VALUE',
                  /* more items */
                ]
              },
              MatchScope: ALL | KEY | VALUE, /* required */
              InvalidFallbackBehavior: MATCH | NO_MATCH | EVALUATE_AS_STRING
            },
            Method: {
            },
            QueryString: {
            },
            SingleHeader: {
              Name: 'STRING_VALUE' /* required */
            },
            SingleQueryArgument: {
              Name: 'STRING_VALUE' /* required */
            },
            UriPath: {
            }
          },
          RegexString: 'STRING_VALUE', /* required */
          TextTransformations: [ /* required */
            {
              Priority: 'NUMBER_VALUE', /* required */
              Type: NONE | COMPRESS_WHITE_SPACE | HTML_ENTITY_DECODE | LOWERCASE | CMD_LINE | URL_DECODE | BASE64_DECODE | HEX_DECODE | MD5 | REPLACE_COMMENTS | ESCAPE_SEQ_DECODE | SQL_HEX_DECODE | CSS_DECODE | JS_DECODE | NORMALIZE_PATH | NORMALIZE_PATH_WIN | REMOVE_NULLS | REPLACE_NULLS | BASE64_DECODE_EXT | URL_DECODE_UNI | UTF8_TO_UNICODE /* required */
            },
            /* more items */
          ]
        },
        RegexPatternSetReferenceStatement: {
          ARN: 'STRING_VALUE', /* required */
          FieldToMatch: { /* required */
            AllQueryArguments: {
            },
            Body: {
            },
            JsonBody: {
              MatchPattern: { /* required */
                All: {
                },
                IncludedPaths: [
                  'STRING_VALUE',
                  /* more items */
                ]
              },
              MatchScope: ALL | KEY | VALUE, /* required */
              InvalidFallbackBehavior: MATCH | NO_MATCH | EVALUATE_AS_STRING
            },
            Method: {
            },
            QueryString: {
            },
            SingleHeader: {
              Name: 'STRING_VALUE' /* required */
            },
            SingleQueryArgument: {
              Name: 'STRING_VALUE' /* required */
            },
            UriPath: {
            }
          },
          TextTransformations: [ /* required */
            {
              Priority: 'NUMBER_VALUE', /* required */
              Type: NONE | COMPRESS_WHITE_SPACE | HTML_ENTITY_DECODE | LOWERCASE | CMD_LINE | URL_DECODE | BASE64_DECODE | HEX_DECODE | MD5 | REPLACE_COMMENTS | ESCAPE_SEQ_DECODE | SQL_HEX_DECODE | CSS_DECODE | JS_DECODE | NORMALIZE_PATH | NORMALIZE_PATH_WIN | REMOVE_NULLS | REPLACE_NULLS | BASE64_DECODE_EXT | URL_DECODE_UNI | UTF8_TO_UNICODE /* required */
            },
            /* more items */
          ]
        },
        RuleGroupReferenceStatement: {
          ARN: 'STRING_VALUE', /* required */
          ExcludedRules: [
            {
              Name: 'STRING_VALUE' /* required */
            },
            /* more items */
          ]
        },
        SizeConstraintStatement: {
          ComparisonOperator: EQ | NE | LE | LT | GE | GT, /* required */
          FieldToMatch: { /* required */
            AllQueryArguments: {
            },
            Body: {
            },
            JsonBody: {
              MatchPattern: { /* required */
                All: {
                },
                IncludedPaths: [
                  'STRING_VALUE',
                  /* more items */
                ]
              },
              MatchScope: ALL | KEY | VALUE, /* required */
              InvalidFallbackBehavior: MATCH | NO_MATCH | EVALUATE_AS_STRING
            },
            Method: {
            },
            QueryString: {
            },
            SingleHeader: {
              Name: 'STRING_VALUE' /* required */
            },
            SingleQueryArgument: {
              Name: 'STRING_VALUE' /* required */
            },
            UriPath: {
            }
          },
          Size: 'NUMBER_VALUE', /* required */
          TextTransformations: [ /* required */
            {
              Priority: 'NUMBER_VALUE', /* required */
              Type: NONE | COMPRESS_WHITE_SPACE | HTML_ENTITY_DECODE | LOWERCASE | CMD_LINE | URL_DECODE | BASE64_DECODE | HEX_DECODE | MD5 | REPLACE_COMMENTS | ESCAPE_SEQ_DECODE | SQL_HEX_DECODE | CSS_DECODE | JS_DECODE | NORMALIZE_PATH | NORMALIZE_PATH_WIN | REMOVE_NULLS | REPLACE_NULLS | BASE64_DECODE_EXT | URL_DECODE_UNI | UTF8_TO_UNICODE /* required */
            },
            /* more items */
          ]
        },
        SqliMatchStatement: {
          FieldToMatch: { /* required */
            AllQueryArguments: {
            },
            Body: {
            },
            JsonBody: {
              MatchPattern: { /* required */
                All: {
                },
                IncludedPaths: [
                  'STRING_VALUE',
                  /* more items */
                ]
              },
              MatchScope: ALL | KEY | VALUE, /* required */
              InvalidFallbackBehavior: MATCH | NO_MATCH | EVALUATE_AS_STRING
            },
            Method: {
            },
            QueryString: {
            },
            SingleHeader: {
              Name: 'STRING_VALUE' /* required */
            },
            SingleQueryArgument: {
              Name: 'STRING_VALUE' /* required */
            },
            UriPath: {
            }
          },
          TextTransformations: [ /* required */
            {
              Priority: 'NUMBER_VALUE', /* required */
              Type: NONE | COMPRESS_WHITE_SPACE | HTML_ENTITY_DECODE | LOWERCASE | CMD_LINE | URL_DECODE | BASE64_DECODE | HEX_DECODE | MD5 | REPLACE_COMMENTS | ESCAPE_SEQ_DECODE | SQL_HEX_DECODE | CSS_DECODE | JS_DECODE | NORMALIZE_PATH | NORMALIZE_PATH_WIN | REMOVE_NULLS | REPLACE_NULLS | BASE64_DECODE_EXT | URL_DECODE_UNI | UTF8_TO_UNICODE /* required */
            },
            /* more items */
          ]
        },
        XssMatchStatement: {
          FieldToMatch: { /* required */
            AllQueryArguments: {
            },
            Body: {
            },
            JsonBody: {
              MatchPattern: { /* required */
                All: {
                },
                IncludedPaths: [
                  'STRING_VALUE',
                  /* more items */
                ]
              },
              MatchScope: ALL | KEY | VALUE, /* required */
              InvalidFallbackBehavior: MATCH | NO_MATCH | EVALUATE_AS_STRING
            },
            Method: {
            },
            QueryString: {
            },
            SingleHeader: {
              Name: 'STRING_VALUE' /* required */
            },
            SingleQueryArgument: {
              Name: 'STRING_VALUE' /* required */
            },
            UriPath: {
            }
          },
          TextTransformations: [ /* required */
            {
              Priority: 'NUMBER_VALUE', /* required */
              Type: NONE | COMPRESS_WHITE_SPACE | HTML_ENTITY_DECODE | LOWERCASE | CMD_LINE | URL_DECODE | BASE64_DECODE | HEX_DECODE | MD5 | REPLACE_COMMENTS | ESCAPE_SEQ_DECODE | SQL_HEX_DECODE | CSS_DECODE | JS_DECODE | NORMALIZE_PATH | NORMALIZE_PATH_WIN | REMOVE_NULLS | REPLACE_NULLS | BASE64_DECODE_EXT | URL_DECODE_UNI | UTF8_TO_UNICODE /* required */
            },
            /* more items */
          ]
        }
      },
      VisibilityConfig: { /* required */
        CloudWatchMetricsEnabled: true || false, /* required */
        MetricName: 'STRING_VALUE', /* required */
        SampledRequestsEnabled: true || false /* required */
      },
      Action: {
        Allow: {
          CustomRequestHandling: {
            InsertHeaders: [ /* required */
              {
                Name: 'STRING_VALUE', /* required */
                Value: 'STRING_VALUE' /* required */
              },
              /* more items */
            ]
          }
        },
        Block: {
          CustomResponse: {
            ResponseCode: 'NUMBER_VALUE', /* required */
            CustomResponseBodyKey: 'STRING_VALUE',
            ResponseHeaders: [
              {
                Name: 'STRING_VALUE', /* required */
                Value: 'STRING_VALUE' /* required */
              },
              /* more items */
            ]
          }
        },
        Captcha: {
          CustomRequestHandling: {
            InsertHeaders: [ /* required */
              {
                Name: 'STRING_VALUE', /* required */
                Value: 'STRING_VALUE' /* required */
              },
              /* more items */
            ]
          }
        },
        Count: {
          CustomRequestHandling: {
            InsertHeaders: [ /* required */
              {
                Name: 'STRING_VALUE', /* required */
                Value: 'STRING_VALUE' /* required */
              },
              /* more items */
            ]
          }
        }
      },
      CaptchaConfig: {
        ImmunityTimeProperty: {
          ImmunityTime: 'NUMBER_VALUE' /* required */
        }
      },
      OverrideAction: {
        Count: {
          CustomRequestHandling: {
            InsertHeaders: [ /* required */
              {
                Name: 'STRING_VALUE', /* required */
                Value: 'STRING_VALUE' /* required */
              },
              /* more items */
            ]
          }
        },
        None: {
        }
      },
      RuleLabels: [
        {
          Name: 'STRING_VALUE' /* required */
        },
        /* more items */
      ]
    },
    /* more items */
  ],
  Scope: CLOUDFRONT | REGIONAL /* required */
};
wafv2.checkCapacity(params, function(err, data) {
  if (err) console.log(err, err.stack); // an error occurred
  else     console.log(data);           // successful response
});

Parameters:

  • params (Object) (defaults to: {}) —
    • Scope — (String)

      Specifies whether this is for an Amazon CloudFront distribution or for a regional application. A regional application can be an Application Load Balancer (ALB), an Amazon API Gateway REST API, or an AppSync GraphQL API.

      To work with CloudFront, you must also specify the Region US East (N. Virginia) as follows:

      • CLI - Specify the Region when you use the CloudFront scope: --scope=CLOUDFRONT --region=us-east-1.

      • API and SDKs - For all calls, use the Region endpoint us-east-1.

      Possible values include:
      • "CLOUDFRONT"
      • "REGIONAL"
    • Rules — (Array<map>)

      An array of Rule that you're configuring to use in a rule group or web ACL.

      • Name — required — (String)

        The name of the rule. You can't change the name of a Rule after you create it.

      • Priority — required — (Integer)

        If you define more than one Rule in a WebACL, WAF evaluates each request against the Rules in order based on the value of Priority. WAF processes rules with lower priority first. The priorities don't need to be consecutive, but they must all be different.

      • Statement — required — (map)

        The WAF processing statement for the rule, for example ByteMatchStatement or SizeConstraintStatement.

        • ByteMatchStatement — (map)

          A rule statement that defines a string match search for WAF to apply to web requests. The byte match statement provides the bytes to search for, the location in requests that you want WAF to search, and other settings. The bytes to search for are typically a string that corresponds with ASCII characters. In the WAF console and the developer guide, this is refered to as a string match statement.

          • SearchString — required — (Buffer, Typed Array, Blob, String)

            A string value that you want WAF to search for. WAF searches only in the part of web requests that you designate for inspection in FieldToMatch. The maximum length of the value is 50 bytes.

            Valid values depend on the component that you specify for inspection in FieldToMatch:

            • Method: The HTTP method that you want WAF to search for. This indicates the type of operation specified in the request.

            • UriPath: The value that you want WAF to search for in the URI path, for example, /images/daily-ad.jpg.

            If SearchString includes alphabetic characters A-Z and a-z, note that the value is case sensitive.

            If you're using the WAF API

            Specify a base64-encoded version of the value. The maximum length of the value before you base64-encode it is 50 bytes.

            For example, suppose the value of Type is HEADER and the value of Data is User-Agent. If you want to search the User-Agent header for the value BadBot, you base64-encode BadBot using MIME base64-encoding and include the resulting value, QmFkQm90, in the value of SearchString.

            If you're using the CLI or one of the Amazon Web Services SDKs

            The value that you want WAF to search for. The SDK automatically base64 encodes the value.

          • FieldToMatch — required — (map)

            The part of a web request that you want WAF to inspect. For more information, see FieldToMatch.

            • SingleHeader — (map)

              Inspect a single header. Provide the name of the header to inspect, for example, User-Agent or Referer. This setting isn't case sensitive.

              Example JSON: "SingleHeader": { "Name": "haystack" }

              • Name — required — (String)

                The name of the query header to inspect.

            • SingleQueryArgument — (map)

              Inspect a single query argument. Provide the name of the query argument to inspect, such as UserName or SalesRegion. The name can be up to 30 characters long and isn't case sensitive.

              This is used only to indicate the web request component for WAF to inspect, in the FieldToMatch specification.

              Example JSON: "SingleQueryArgument": { "Name": "myArgument" }

              • Name — required — (String)

                The name of the query argument to inspect.

            • AllQueryArguments — (map)

              Inspect all query arguments.

            • UriPath — (map)

              Inspect the request URI path. This is the part of a web request that identifies a resource, for example, /images/daily-ad.jpg.

            • QueryString — (map)

              Inspect the query string. This is the part of a URL that appears after a ? character, if any.

            • Body — (map)

              Inspect the request body as plain text. The request body immediately follows the request headers. This is the part of a request that contains any additional data that you want to send to your web server as the HTTP request body, such as data from a form.

              Note that only the first 8 KB (8192 bytes) of the request body are forwarded to WAF for inspection by the underlying host service. If you don't need to inspect more than 8 KB, you can guarantee that you don't allow additional bytes in by combining a statement that inspects the body of the web request, such as ByteMatchStatement or RegexPatternSetReferenceStatement, with a SizeConstraintStatement that enforces an 8 KB size limit on the body of the request. WAF doesn't support inspecting the entire contents of web requests whose bodies exceed the 8 KB limit.

            • Method — (map)

              Inspect the HTTP method. The method indicates the type of operation that the request is asking the origin to perform.

            • JsonBody — (map)

              Inspect the request body as JSON. The request body immediately follows the request headers. This is the part of a request that contains any additional data that you want to send to your web server as the HTTP request body, such as data from a form.

              Note that only the first 8 KB (8192 bytes) of the request body are forwarded to WAF for inspection by the underlying host service. If you don't need to inspect more than 8 KB, you can guarantee that you don't allow additional bytes in by combining a statement that inspects the body of the web request, such as ByteMatchStatement or RegexPatternSetReferenceStatement, with a SizeConstraintStatement that enforces an 8 KB size limit on the body of the request. WAF doesn't support inspecting the entire contents of web requests whose bodies exceed the 8 KB limit.

              • MatchPattern — required — (map)

                The patterns to look for in the JSON body. WAF inspects the results of these pattern matches against the rule inspection criteria.

                • All — (map)

                  Match all of the elements. See also MatchScope in JsonBody.

                  You must specify either this setting or the IncludedPaths setting, but not both.

                • IncludedPaths — (Array<String>)

                  Match only the specified include paths. See also MatchScope in JsonBody.

                  Provide the include paths using JSON Pointer syntax. For example, "IncludedPaths": ["/dogs/0/name", "/dogs/1/name"]. For information about this syntax, see the Internet Engineering Task Force (IETF) documentation JavaScript Object Notation (JSON) Pointer.

                  You must specify either this setting or the All setting, but not both.

                  Note: Don't use this option to include all paths. Instead, use the All setting.
              • MatchScope — required — (String)

                The parts of the JSON to match against using the MatchPattern. If you specify All, WAF matches against keys and values.

                Possible values include:
                • "ALL"
                • "KEY"
                • "VALUE"
              • InvalidFallbackBehavior — (String)

                What WAF should do if it fails to completely parse the JSON body. The options are the following:

                • EVALUATE_AS_STRING - Inspect the body as plain text. WAF applies the text transformations and inspection criteria that you defined for the JSON inspection to the body text string.

                • MATCH - Treat the web request as matching the rule statement. WAF applies the rule action to the request.

                • NO_MATCH - Treat the web request as not matching the rule statement.

                If you don't provide this setting, WAF parses and evaluates the content only up to the first parsing failure that it encounters.

                WAF does its best to parse the entire JSON body, but might be forced to stop for reasons such as invalid characters, duplicate keys, truncation, and any content whose root node isn't an object or an array.

                WAF parses the JSON in the following examples as two valid key, value pairs:

                • Missing comma: {"key1":"value1""key2":"value2"}

                • Missing colon: {"key1":"value1","key2""value2"}

                • Extra colons: {"key1"::"value1","key2""value2"}

                Possible values include:
                • "MATCH"
                • "NO_MATCH"
                • "EVALUATE_AS_STRING"
          • TextTransformations — required — (Array<map>)

            Text transformations eliminate some of the unusual formatting that attackers use in web requests in an effort to bypass detection. If you specify one or more transformations in a rule statement, WAF performs all transformations on the content of the request component identified by FieldToMatch, starting from the lowest priority setting, before inspecting the content for a match.

            • Priority — required — (Integer)

              Sets the relative processing order for multiple transformations that are defined for a rule statement. WAF processes all transformations, from lowest priority to highest, before inspecting the transformed content. The priorities don't need to be consecutive, but they must all be different.

            • Type — required — (String)

              You can specify the following transformation types:

              BASE64_DECODE - Decode a Base64-encoded string.

              BASE64_DECODE_EXT - Decode a Base64-encoded string, but use a forgiving implementation that ignores characters that aren't valid.

              CMD_LINE - Command-line transformations. These are helpful in reducing effectiveness of attackers who inject an operating system command-line command and use unusual formatting to disguise some or all of the command.

              • Delete the following characters: \ " ' ^

              • Delete spaces before the following characters: / (

              • Replace the following characters with a space: , ;

              • Replace multiple spaces with one space

              • Convert uppercase letters (A-Z) to lowercase (a-z)

              COMPRESS_WHITE_SPACE - Replace these characters with a space character (decimal 32):

              • \f, formfeed, decimal 12

              • \t, tab, decimal 9

              • \n, newline, decimal 10

              • \r, carriage return, decimal 13

              • \v, vertical tab, decimal 11

              • Non-breaking space, decimal 160

              COMPRESS_WHITE_SPACE also replaces multiple spaces with one space.

              CSS_DECODE - Decode characters that were encoded using CSS 2.x escape rules syndata.html#characters. This function uses up to two bytes in the decoding process, so it can help to uncover ASCII characters that were encoded using CSS encoding that wouldn’t typically be encoded. It's also useful in countering evasion, which is a combination of a backslash and non-hexadecimal characters. For example, ja\vascript for javascript.

              ESCAPE_SEQ_DECODE - Decode the following ANSI C escape sequences: \a, \b, \f, \n, \r, \t, \v, \, \?, \', \", \xHH (hexadecimal), \0OOO (octal). Encodings that aren't valid remain in the output.

              HEX_DECODE - Decode a string of hexadecimal characters into a binary.

              HTML_ENTITY_DECODE - Replace HTML-encoded characters with unencoded characters. HTML_ENTITY_DECODE performs these operations:

              • Replaces (ampersand)quot; with "

              • Replaces (ampersand)nbsp; with a non-breaking space, decimal 160

              • Replaces (ampersand)lt; with a "less than" symbol

              • Replaces (ampersand)gt; with >

              • Replaces characters that are represented in hexadecimal format, (ampersand)#xhhhh;, with the corresponding characters

              • Replaces characters that are represented in decimal format, (ampersand)#nnnn;, with the corresponding characters

              JS_DECODE - Decode JavaScript escape sequences. If a \ u HHHH code is in the full-width ASCII code range of FF01-FF5E, then the higher byte is used to detect and adjust the lower byte. If not, only the lower byte is used and the higher byte is zeroed, causing a possible loss of information.

              LOWERCASE - Convert uppercase letters (A-Z) to lowercase (a-z).

              MD5 - Calculate an MD5 hash from the data in the input. The computed hash is in a raw binary form.

              NONE - Specify NONE if you don't want any text transformations.

              NORMALIZE_PATH - Remove multiple slashes, directory self-references, and directory back-references that are not at the beginning of the input from an input string.

              NORMALIZE_PATH_WIN - This is the same as NORMALIZE_PATH, but first converts backslash characters to forward slashes.

              REMOVE_NULLS - Remove all NULL bytes from the input.

              REPLACE_COMMENTS - Replace each occurrence of a C-style comment (/* ... */) with a single space. Multiple consecutive occurrences are not compressed. Unterminated comments are also replaced with a space (ASCII 0x20). However, a standalone termination of a comment (*/) is not acted upon.

              REPLACE_NULLS - Replace NULL bytes in the input with space characters (ASCII 0x20).

              SQL_HEX_DECODE - Decode SQL hex data. Example (0x414243) will be decoded to (ABC).

              URL_DECODE - Decode a URL-encoded value.

              URL_DECODE_UNI - Like URL_DECODE, but with support for Microsoft-specific %u encoding. If the code is in the full-width ASCII code range of FF01-FF5E, the higher byte is used to detect and adjust the lower byte. Otherwise, only the lower byte is used and the higher byte is zeroed.

              UTF8_TO_UNICODE - Convert all UTF-8 character sequences to Unicode. This helps input normalization, and minimizing false-positives and false-negatives for non-English languages.

              Possible values include:
              • "NONE"
              • "COMPRESS_WHITE_SPACE"
              • "HTML_ENTITY_DECODE"
              • "LOWERCASE"
              • "CMD_LINE"
              • "URL_DECODE"
              • "BASE64_DECODE"
              • "HEX_DECODE"
              • "MD5"
              • "REPLACE_COMMENTS"
              • "ESCAPE_SEQ_DECODE"
              • "SQL_HEX_DECODE"
              • "CSS_DECODE"
              • "JS_DECODE"
              • "NORMALIZE_PATH"
              • "NORMALIZE_PATH_WIN"
              • "REMOVE_NULLS"
              • "REPLACE_NULLS"
              • "BASE64_DECODE_EXT"
              • "URL_DECODE_UNI"
              • "UTF8_TO_UNICODE"
          • PositionalConstraint — required — (String)

            The area within the portion of a web request that you want WAF to search for SearchString. Valid values include the following:

            CONTAINS

            The specified part of the web request must include the value of SearchString, but the location doesn't matter.

            CONTAINS_WORD

            The specified part of the web request must include the value of SearchString, and SearchString must contain only alphanumeric characters or underscore (A-Z, a-z, 0-9, or ). In addition, SearchString must be a word, which means that both of the following are true:

            • SearchString is at the beginning of the specified part of the web request or is preceded by a character other than an alphanumeric character or underscore (). Examples include the value of a header and ;BadBot.

            • SearchString is at the end of the specified part of the web request or is followed by a character other than an alphanumeric character or underscore (_), for example, BadBot; and -BadBot;.

            EXACTLY

            The value of the specified part of the web request must exactly match the value of SearchString.

            STARTS_WITH

            The value of SearchString must appear at the beginning of the specified part of the web request.

            ENDS_WITH

            The value of SearchString must appear at the end of the specified part of the web request.

            Possible values include:
            • "EXACTLY"
            • "STARTS_WITH"
            • "ENDS_WITH"
            • "CONTAINS"
            • "CONTAINS_WORD"
        • SqliMatchStatement — (map)

          Attackers sometimes insert malicious SQL code into web requests in an effort to extract data from your database. To allow or block web requests that appear to contain malicious SQL code, create one or more SQL injection match conditions. An SQL injection match condition identifies the part of web requests, such as the URI or the query string, that you want WAF to inspect. Later in the process, when you create a web ACL, you specify whether to allow or block requests that appear to contain malicious SQL code.

          • FieldToMatch — required — (map)

            The part of a web request that you want WAF to inspect. For more information, see FieldToMatch.

            • SingleHeader — (map)

              Inspect a single header. Provide the name of the header to inspect, for example, User-Agent or Referer. This setting isn't case sensitive.

              Example JSON: "SingleHeader": { "Name": "haystack" }

              • Name — required — (String)

                The name of the query header to inspect.

            • SingleQueryArgument — (map)

              Inspect a single query argument. Provide the name of the query argument to inspect, such as UserName or SalesRegion. The name can be up to 30 characters long and isn't case sensitive.

              This is used only to indicate the web request component for WAF to inspect, in the FieldToMatch specification.

              Example JSON: "SingleQueryArgument": { "Name": "myArgument" }

              • Name — required — (String)

                The name of the query argument to inspect.

            • AllQueryArguments — (map)

              Inspect all query arguments.

            • UriPath — (map)

              Inspect the request URI path. This is the part of a web request that identifies a resource, for example, /images/daily-ad.jpg.

            • QueryString — (map)

              Inspect the query string. This is the part of a URL that appears after a ? character, if any.

            • Body — (map)

              Inspect the request body as plain text. The request body immediately follows the request headers. This is the part of a request that contains any additional data that you want to send to your web server as the HTTP request body, such as data from a form.

              Note that only the first 8 KB (8192 bytes) of the request body are forwarded to WAF for inspection by the underlying host service. If you don't need to inspect more than 8 KB, you can guarantee that you don't allow additional bytes in by combining a statement that inspects the body of the web request, such as ByteMatchStatement or RegexPatternSetReferenceStatement, with a SizeConstraintStatement that enforces an 8 KB size limit on the body of the request. WAF doesn't support inspecting the entire contents of web requests whose bodies exceed the 8 KB limit.

            • Method — (map)

              Inspect the HTTP method. The method indicates the type of operation that the request is asking the origin to perform.

            • JsonBody — (map)

              Inspect the request body as JSON. The request body immediately follows the request headers. This is the part of a request that contains any additional data that you want to send to your web server as the HTTP request body, such as data from a form.

              Note that only the first 8 KB (8192 bytes) of the request body are forwarded to WAF for inspection by the underlying host service. If you don't need to inspect more than 8 KB, you can guarantee that you don't allow additional bytes in by combining a statement that inspects the body of the web request, such as ByteMatchStatement or RegexPatternSetReferenceStatement, with a SizeConstraintStatement that enforces an 8 KB size limit on the body of the request. WAF doesn't support inspecting the entire contents of web requests whose bodies exceed the 8 KB limit.

              • MatchPattern — required — (map)

                The patterns to look for in the JSON body. WAF inspects the results of these pattern matches against the rule inspection criteria.

                • All — (map)

                  Match all of the elements. See also MatchScope in JsonBody.

                  You must specify either this setting or the IncludedPaths setting, but not both.

                • IncludedPaths — (Array<String>)

                  Match only the specified include paths. See also MatchScope in JsonBody.

                  Provide the include paths using JSON Pointer syntax. For example, "IncludedPaths": ["/dogs/0/name", "/dogs/1/name"]. For information about this syntax, see the Internet Engineering Task Force (IETF) documentation JavaScript Object Notation (JSON) Pointer.

                  You must specify either this setting or the All setting, but not both.

                  Note: Don't use this option to include all paths. Instead, use the All setting.
              • MatchScope — required — (String)

                The parts of the JSON to match against using the MatchPattern. If you specify All, WAF matches against keys and values.

                Possible values include:
                • "ALL"
                • "KEY"
                • "VALUE"
              • InvalidFallbackBehavior — (String)

                What WAF should do if it fails to completely parse the JSON body. The options are the following:

                • EVALUATE_AS_STRING - Inspect the body as plain text. WAF applies the text transformations and inspection criteria that you defined for the JSON inspection to the body text string.

                • MATCH - Treat the web request as matching the rule statement. WAF applies the rule action to the request.

                • NO_MATCH - Treat the web request as not matching the rule statement.

                If you don't provide this setting, WAF parses and evaluates the content only up to the first parsing failure that it encounters.

                WAF does its best to parse the entire JSON body, but might be forced to stop for reasons such as invalid characters, duplicate keys, truncation, and any content whose root node isn't an object or an array.

                WAF parses the JSON in the following examples as two valid key, value pairs:

                • Missing comma: {"key1":"value1""key2":"value2"}

                • Missing colon: {"key1":"value1","key2""value2"}

                • Extra colons: {"key1"::"value1","key2""value2"}

                Possible values include:
                • "MATCH"
                • "NO_MATCH"
                • "EVALUATE_AS_STRING"
          • TextTransformations — required — (Array<map>)

            Text transformations eliminate some of the unusual formatting that attackers use in web requests in an effort to bypass detection. If you specify one or more transformations in a rule statement, WAF performs all transformations on the content of the request component identified by FieldToMatch, starting from the lowest priority setting, before inspecting the content for a match.

            • Priority — required — (Integer)

              Sets the relative processing order for multiple transformations that are defined for a rule statement. WAF processes all transformations, from lowest priority to highest, before inspecting the transformed content. The priorities don't need to be consecutive, but they must all be different.

            • Type — required — (String)

              You can specify the following transformation types:

              BASE64_DECODE - Decode a Base64-encoded string.

              BASE64_DECODE_EXT - Decode a Base64-encoded string, but use a forgiving implementation that ignores characters that aren't valid.

              CMD_LINE - Command-line transformations. These are helpful in reducing effectiveness of attackers who inject an operating system command-line command and use unusual formatting to disguise some or all of the command.

              • Delete the following characters: \ " ' ^

              • Delete spaces before the following characters: / (

              • Replace the following characters with a space: , ;

              • Replace multiple spaces with one space

              • Convert uppercase letters (A-Z) to lowercase (a-z)

              COMPRESS_WHITE_SPACE - Replace these characters with a space character (decimal 32):

              • \f, formfeed, decimal 12

              • \t, tab, decimal 9

              • \n, newline, decimal 10

              • \r, carriage return, decimal 13

              • \v, vertical tab, decimal 11

              • Non-breaking space, decimal 160

              COMPRESS_WHITE_SPACE also replaces multiple spaces with one space.

              CSS_DECODE - Decode characters that were encoded using CSS 2.x escape rules syndata.html#characters. This function uses up to two bytes in the decoding process, so it can help to uncover ASCII characters that were encoded using CSS encoding that wouldn’t typically be encoded. It's also useful in countering evasion, which is a combination of a backslash and non-hexadecimal characters. For example, ja\vascript for javascript.

              ESCAPE_SEQ_DECODE - Decode the following ANSI C escape sequences: \a, \b, \f, \n, \r, \t, \v, \, \?, \', \", \xHH (hexadecimal), \0OOO (octal). Encodings that aren't valid remain in the output.

              HEX_DECODE - Decode a string of hexadecimal characters into a binary.

              HTML_ENTITY_DECODE - Replace HTML-encoded characters with unencoded characters. HTML_ENTITY_DECODE performs these operations:

              • Replaces (ampersand)quot; with "

              • Replaces (ampersand)nbsp; with a non-breaking space, decimal 160

              • Replaces (ampersand)lt; with a "less than" symbol

              • Replaces (ampersand)gt; with >

              • Replaces characters that are represented in hexadecimal format, (ampersand)#xhhhh;, with the corresponding characters

              • Replaces characters that are represented in decimal format, (ampersand)#nnnn;, with the corresponding characters

              JS_DECODE - Decode JavaScript escape sequences. If a \ u HHHH code is in the full-width ASCII code range of FF01-FF5E, then the higher byte is used to detect and adjust the lower byte. If not, only the lower byte is used and the higher byte is zeroed, causing a possible loss of information.

              LOWERCASE - Convert uppercase letters (A-Z) to lowercase (a-z).

              MD5 - Calculate an MD5 hash from the data in the input. The computed hash is in a raw binary form.

              NONE - Specify NONE if you don't want any text transformations.

              NORMALIZE_PATH - Remove multiple slashes, directory self-references, and directory back-references that are not at the beginning of the input from an input string.

              NORMALIZE_PATH_WIN - This is the same as NORMALIZE_PATH, but first converts backslash characters to forward slashes.

              REMOVE_NULLS - Remove all NULL bytes from the input.

              REPLACE_COMMENTS - Replace each occurrence of a C-style comment (/* ... */) with a single space. Multiple consecutive occurrences are not compressed. Unterminated comments are also replaced with a space (ASCII 0x20). However, a standalone termination of a comment (*/) is not acted upon.

              REPLACE_NULLS - Replace NULL bytes in the input with space characters (ASCII 0x20).

              SQL_HEX_DECODE - Decode SQL hex data. Example (0x414243) will be decoded to (ABC).

              URL_DECODE - Decode a URL-encoded value.

              URL_DECODE_UNI - Like URL_DECODE, but with support for Microsoft-specific %u encoding. If the code is in the full-width ASCII code range of FF01-FF5E, the higher byte is used to detect and adjust the lower byte. Otherwise, only the lower byte is used and the higher byte is zeroed.

              UTF8_TO_UNICODE - Convert all UTF-8 character sequences to Unicode. This helps input normalization, and minimizing false-positives and false-negatives for non-English languages.

              Possible values include:
              • "NONE"
              • "COMPRESS_WHITE_SPACE"
              • "HTML_ENTITY_DECODE"
              • "LOWERCASE"
              • "CMD_LINE"
              • "URL_DECODE"
              • "BASE64_DECODE"
              • "HEX_DECODE"
              • "MD5"
              • "REPLACE_COMMENTS"
              • "ESCAPE_SEQ_DECODE"
              • "SQL_HEX_DECODE"
              • "CSS_DECODE"
              • "JS_DECODE"
              • "NORMALIZE_PATH"
              • "NORMALIZE_PATH_WIN"
              • "REMOVE_NULLS"
              • "REPLACE_NULLS"
              • "BASE64_DECODE_EXT"
              • "URL_DECODE_UNI"
              • "UTF8_TO_UNICODE"
        • XssMatchStatement — (map)

          A rule statement that defines a cross-site scripting (XSS) match search for WAF to apply to web requests. XSS attacks are those where the attacker uses vulnerabilities in a benign website as a vehicle to inject malicious client-site scripts into other legitimate web browsers. The XSS match statement provides the location in requests that you want WAF to search and text transformations to use on the search area before WAF searches for character sequences that are likely to be malicious strings.

          • FieldToMatch — required — (map)

            The part of a web request that you want WAF to inspect. For more information, see FieldToMatch.

            • SingleHeader — (map)

              Inspect a single header. Provide the name of the header to inspect, for example, User-Agent or Referer. This setting isn't case sensitive.

              Example JSON: "SingleHeader": { "Name": "haystack" }

              • Name — required — (String)

                The name of the query header to inspect.

            • SingleQueryArgument — (map)

              Inspect a single query argument. Provide the name of the query argument to inspect, such as UserName or SalesRegion. The name can be up to 30 characters long and isn't case sensitive.

              This is used only to indicate the web request component for WAF to inspect, in the FieldToMatch specification.

              Example JSON: "SingleQueryArgument": { "Name": "myArgument" }

              • Name — required — (String)

                The name of the query argument to inspect.

            • AllQueryArguments — (map)

              Inspect all query arguments.

            • UriPath — (map)

              Inspect the request URI path. This is the part of a web request that identifies a resource, for example, /images/daily-ad.jpg.

            • QueryString — (map)

              Inspect the query string. This is the part of a URL that appears after a ? character, if any.

            • Body — (map)

              Inspect the request body as plain text. The request body immediately follows the request headers. This is the part of a request that contains any additional data that you want to send to your web server as the HTTP request body, such as data from a form.

              Note that only the first 8 KB (8192 bytes) of the request body are forwarded to WAF for inspection by the underlying host service. If you don't need to inspect more than 8 KB, you can guarantee that you don't allow additional bytes in by combining a statement that inspects the body of the web request, such as ByteMatchStatement or RegexPatternSetReferenceStatement, with a SizeConstraintStatement that enforces an 8 KB size limit on the body of the request. WAF doesn't support inspecting the entire contents of web requests whose bodies exceed the 8 KB limit.

            • Method — (map)

              Inspect the HTTP method. The method indicates the type of operation that the request is asking the origin to perform.

            • JsonBody — (map)

              Inspect the request body as JSON. The request body immediately follows the request headers. This is the part of a request that contains any additional data that you want to send to your web server as the HTTP request body, such as data from a form.

              Note that only the first 8 KB (8192 bytes) of the request body are forwarded to WAF for inspection by the underlying host service. If you don't need to inspect more than 8 KB, you can guarantee that you don't allow additional bytes in by combining a statement that inspects the body of the web request, such as ByteMatchStatement or RegexPatternSetReferenceStatement, with a SizeConstraintStatement that enforces an 8 KB size limit on the body of the request. WAF doesn't support inspecting the entire contents of web requests whose bodies exceed the 8 KB limit.

              • MatchPattern — required — (map)

                The patterns to look for in the JSON body. WAF inspects the results of these pattern matches against the rule inspection criteria.

                • All — (map)

                  Match all of the elements. See also MatchScope in JsonBody.

                  You must specify either this setting or the IncludedPaths setting, but not both.

                • IncludedPaths — (Array<String>)

                  Match only the specified include paths. See also MatchScope in JsonBody.

                  Provide the include paths using JSON Pointer syntax. For example, "IncludedPaths": ["/dogs/0/name", "/dogs/1/name"]. For information about this syntax, see the Internet Engineering Task Force (IETF) documentation JavaScript Object Notation (JSON) Pointer.

                  You must specify either this setting or the All setting, but not both.

                  Note: Don't use this option to include all paths. Instead, use the All setting.
              • MatchScope — required — (String)

                The parts of the JSON to match against using the MatchPattern. If you specify All, WAF matches against keys and values.

                Possible values include:
                • "ALL"
                • "KEY"
                • "VALUE"
              • InvalidFallbackBehavior — (String)

                What WAF should do if it fails to completely parse the JSON body. The options are the following:

                • EVALUATE_AS_STRING - Inspect the body as plain text. WAF applies the text transformations and inspection criteria that you defined for the JSON inspection to the body text string.

                • MATCH - Treat the web request as matching the rule statement. WAF applies the rule action to the request.

                • NO_MATCH - Treat the web request as not matching the rule statement.

                If you don't provide this setting, WAF parses and evaluates the content only up to the first parsing failure that it encounters.

                WAF does its best to parse the entire JSON body, but might be forced to stop for reasons such as invalid characters, duplicate keys, truncation, and any content whose root node isn't an object or an array.

                WAF parses the JSON in the following examples as two valid key, value pairs:

                • Missing comma: {"key1":"value1""key2":"value2"}

                • Missing colon: {"key1":"value1","key2""value2"}

                • Extra colons: {"key1"::"value1","key2""value2"}

                Possible values include:
                • "MATCH"
                • "NO_MATCH"
                • "EVALUATE_AS_STRING"
          • TextTransformations — required — (Array<map>)

            Text transformations eliminate some of the unusual formatting that attackers use in web requests in an effort to bypass detection. If you specify one or more transformations in a rule statement, WAF performs all transformations on the content of the request component identified by FieldToMatch, starting from the lowest priority setting, before inspecting the content for a match.

            • Priority — required — (Integer)

              Sets the relative processing order for multiple transformations that are defined for a rule statement. WAF processes all transformations, from lowest priority to highest, before inspecting the transformed content. The priorities don't need to be consecutive, but they must all be different.

            • Type — required — (String)

              You can specify the following transformation types:

              BASE64_DECODE - Decode a Base64-encoded string.

              BASE64_DECODE_EXT - Decode a Base64-encoded string, but use a forgiving implementation that ignores characters that aren't valid.

              CMD_LINE - Command-line transformations. These are helpful in reducing effectiveness of attackers who inject an operating system command-line command and use unusual formatting to disguise some or all of the command.

              • Delete the following characters: \ " ' ^

              • Delete spaces before the following characters: / (

              • Replace the following characters with a space: , ;

              • Replace multiple spaces with one space

              • Convert uppercase letters (A-Z) to lowercase (a-z)

              COMPRESS_WHITE_SPACE - Replace these characters with a space character (decimal 32):

              • \f, formfeed, decimal 12

              • \t, tab, decimal 9

              • \n, newline, decimal 10

              • \r, carriage return, decimal 13

              • \v, vertical tab, decimal 11

              • Non-breaking space, decimal 160

              COMPRESS_WHITE_SPACE also replaces multiple spaces with one space.

              CSS_DECODE - Decode characters that were encoded using CSS 2.x escape rules syndata.html#characters. This function uses up to two bytes in the decoding process, so it can help to uncover ASCII characters that were encoded using CSS encoding that wouldn’t typically be encoded. It's also useful in countering evasion, which is a combination of a backslash and non-hexadecimal characters. For example, ja\vascript for javascript.

              ESCAPE_SEQ_DECODE - Decode the following ANSI C escape sequences: \a, \b, \f, \n, \r, \t, \v, \, \?, \', \", \xHH (hexadecimal), \0OOO (octal). Encodings that aren't valid remain in the output.

              HEX_DECODE - Decode a string of hexadecimal characters into a binary.

              HTML_ENTITY_DECODE - Replace HTML-encoded characters with unencoded characters. HTML_ENTITY_DECODE performs these operations:

              • Replaces (ampersand)quot; with "

              • Replaces (ampersand)nbsp; with a non-breaking space, decimal 160

              • Replaces (ampersand)lt; with a "less than" symbol

              • Replaces (ampersand)gt; with >

              • Replaces characters that are represented in hexadecimal format, (ampersand)#xhhhh;, with the corresponding characters

              • Replaces characters that are represented in decimal format, (ampersand)#nnnn;, with the corresponding characters

              JS_DECODE - Decode JavaScript escape sequences. If a \ u HHHH code is in the full-width ASCII code range of FF01-FF5E, then the higher byte is used to detect and adjust the lower byte. If not, only the lower byte is used and the higher byte is zeroed, causing a possible loss of information.

              LOWERCASE - Convert uppercase letters (A-Z) to lowercase (a-z).

              MD5 - Calculate an MD5 hash from the data in the input. The computed hash is in a raw binary form.

              NONE - Specify NONE if you don't want any text transformations.

              NORMALIZE_PATH - Remove multiple slashes, directory self-references, and directory back-references that are not at the beginning of the input from an input string.

              NORMALIZE_PATH_WIN - This is the same as NORMALIZE_PATH, but first converts backslash characters to forward slashes.

              REMOVE_NULLS - Remove all NULL bytes from the input.

              REPLACE_COMMENTS - Replace each occurrence of a C-style comment (/* ... */) with a single space. Multiple consecutive occurrences are not compressed. Unterminated comments are also replaced with a space (ASCII 0x20). However, a standalone termination of a comment (*/) is not acted upon.

              REPLACE_NULLS - Replace NULL bytes in the input with space characters (ASCII 0x20).

              SQL_HEX_DECODE - Decode SQL hex data. Example (0x414243) will be decoded to (ABC).

              URL_DECODE - Decode a URL-encoded value.

              URL_DECODE_UNI - Like URL_DECODE, but with support for Microsoft-specific %u encoding. If the code is in the full-width ASCII code range of FF01-FF5E, the higher byte is used to detect and adjust the lower byte. Otherwise, only the lower byte is used and the higher byte is zeroed.

              UTF8_TO_UNICODE - Convert all UTF-8 character sequences to Unicode. This helps input normalization, and minimizing false-positives and false-negatives for non-English languages.

              Possible values include:
              • "NONE"
              • "COMPRESS_WHITE_SPACE"
              • "HTML_ENTITY_DECODE"
              • "LOWERCASE"
              • "CMD_LINE"
              • "URL_DECODE"
              • "BASE64_DECODE"
              • "HEX_DECODE"
              • "MD5"
              • "REPLACE_COMMENTS"
              • "ESCAPE_SEQ_DECODE"
              • "SQL_HEX_DECODE"
              • "CSS_DECODE"
              • "JS_DECODE"
              • "NORMALIZE_PATH"
              • "NORMALIZE_PATH_WIN"
              • "REMOVE_NULLS"
              • "REPLACE_NULLS"
              • "BASE64_DECODE_EXT"
              • "URL_DECODE_UNI"
              • "UTF8_TO_UNICODE"
        • SizeConstraintStatement — (map)

          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 first 8192 bytes (8 KB). If the request body for your web requests never exceeds 8192 bytes, you can create a size constraint condition and block requests that have a request body greater than 8192 bytes.

          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.

          • FieldToMatch — required — (map)

            The part of a web request that you want WAF to inspect. For more information, see FieldToMatch.

            • SingleHeader — (map)

              Inspect a single header. Provide the name of the header to inspect, for example, User-Agent or Referer. This setting isn't case sensitive.

              Example JSON: "SingleHeader": { "Name": "haystack" }

              • Name — required — (String)

                The name of the query header to inspect.

            • SingleQueryArgument — (map)

              Inspect a single query argument. Provide the name of the query argument to inspect, such as UserName or SalesRegion. The name can be up to 30 characters long and isn't case sensitive.

              This is used only to indicate the web request component for WAF to inspect, in the FieldToMatch specification.

              Example JSON: "SingleQueryArgument": { "Name": "myArgument" }

              • Name — required — (String)

                The name of the query argument to inspect.

            • AllQueryArguments — (map)

              Inspect all query arguments.

            • UriPath — (map)

              Inspect the request URI path. This is the part of a web request that identifies a resource, for example, /images/daily-ad.jpg.

            • QueryString — (map)

              Inspect the query string. This is the part of a URL that appears after a ? character, if any.

            • Body — (map)

              Inspect the request body as plain text. The request body immediately follows the request headers. This is the part of a request that contains any additional data that you want to send to your web server as the HTTP request body, such as data from a form.

              Note that only the first 8 KB (8192 bytes) of the request body are forwarded to WAF for inspection by the underlying host service. If you don't need to inspect more than 8 KB, you can guarantee that you don't allow additional bytes in by combining a statement that inspects the body of the web request, such as ByteMatchStatement or RegexPatternSetReferenceStatement, with a SizeConstraintStatement that enforces an 8 KB size limit on the body of the request. WAF doesn't support inspecting the entire contents of web requests whose bodies exceed the 8 KB limit.

            • Method — (map)

              Inspect the HTTP method. The method indicates the type of operation that the request is asking the origin to perform.

            • JsonBody — (map)

              Inspect the request body as JSON. The request body immediately follows the request headers. This is the part of a request that contains any additional data that you want to send to your web server as the HTTP request body, such as data from a form.

              Note that only the first 8 KB (8192 bytes) of the request body are forwarded to WAF for inspection by the underlying host service. If you don't need to inspect more than 8 KB, you can guarantee that you don't allow additional bytes in by combining a statement that inspects the body of the web request, such as ByteMatchStatement or RegexPatternSetReferenceStatement, with a SizeConstraintStatement that enforces an 8 KB size limit on the body of the request. WAF doesn't support inspecting the entire contents of web requests whose bodies exceed the 8 KB limit.

              • MatchPattern — required — (map)

                The patterns to look for in the JSON body. WAF inspects the results of these pattern matches against the rule inspection criteria.

                • All — (map)

                  Match all of the elements. See also MatchScope in JsonBody.

                  You must specify either this setting or the IncludedPaths setting, but not both.

                • IncludedPaths — (Array<String>)

                  Match only the specified include paths. See also MatchScope in JsonBody.

                  Provide the include paths using JSON Pointer syntax. For example, "IncludedPaths": ["/dogs/0/name", "/dogs/1/name"]. For information about this syntax, see the Internet Engineering Task Force (IETF) documentation JavaScript Object Notation (JSON) Pointer.

                  You must specify either this setting or the All setting, but not both.

                  Note: Don't use this option to include all paths. Instead, use the All setting.
              • MatchScope — required — (String)

                The parts of the JSON to match against using the MatchPattern. If you specify All, WAF matches against keys and values.

                Possible values include:
                • "ALL"
                • "KEY"
                • "VALUE"
              • InvalidFallbackBehavior — (String)

                What WAF should do if it fails to completely parse the JSON body. The options are the following:

                • EVALUATE_AS_STRING - Inspect the body as plain text. WAF applies the text transformations and inspection criteria that you defined for the JSON inspection to the body text string.

                • MATCH - Treat the web request as matching the rule statement. WAF applies the rule action to the request.

                • NO_MATCH - Treat the web request as not matching the rule statement.

                If you don't provide this setting, WAF parses and evaluates the content only up to the first parsing failure that it encounters.

                WAF does its best to parse the entire JSON body, but might be forced to stop for reasons such as invalid characters, duplicate keys, truncation, and any content whose root node isn't an object or an array.

                WAF parses the JSON in the following examples as two valid key, value pairs:

                • Missing comma: {"key1":"value1""key2":"value2"}

                • Missing colon: {"key1":"value1","key2""value2"}

                • Extra colons: {"key1"::"value1","key2""value2"}

                Possible values include:
                • "MATCH"
                • "NO_MATCH"
                • "EVALUATE_AS_STRING"
          • ComparisonOperator — required — (String)

            The operator to use to compare the request part to the size setting.

            Possible values include:
            • "EQ"
            • "NE"
            • "LE"
            • "LT"
            • "GE"
            • "GT"
          • Size — required — (Integer)

            The size, in byte, to compare to the request part, after any transformations.

          • TextTransformations — required — (Array<map>)

            Text transformations eliminate some of the unusual formatting that attackers use in web requests in an effort to bypass detection. If you specify one or more transformations in a rule statement, WAF performs all transformations on the content of the request component identified by FieldToMatch, starting from the lowest priority setting, before inspecting the content for a match.

            • Priority — required — (Integer)

              Sets the relative processing order for multiple transformations that are defined for a rule statement. WAF processes all transformations, from lowest priority to highest, before inspecting the transformed content. The priorities don't need to be consecutive, but they must all be different.

            • Type — required — (String)

              You can specify the following transformation types:

              BASE64_DECODE - Decode a Base64-encoded string.

              BASE64_DECODE_EXT - Decode a Base64-encoded string, but use a forgiving implementation that ignores characters that aren't valid.

              CMD_LINE - Command-line transformations. These are helpful in reducing effectiveness of attackers who inject an operating system command-line command and use unusual formatting to disguise some or all of the command.

              • Delete the following characters: \ " ' ^

              • Delete spaces before the following characters: / (

              • Replace the following characters with a space: , ;

              • Replace multiple spaces with one space

              • Convert uppercase letters (A-Z) to lowercase (a-z)

              COMPRESS_WHITE_SPACE - Replace these characters with a space character (decimal 32):

              • \f, formfeed, decimal 12

              • \t, tab, decimal 9

              • \n, newline, decimal 10

              • \r, carriage return, decimal 13

              • \v, vertical tab, decimal 11

              • Non-breaking space, decimal 160

              COMPRESS_WHITE_SPACE also replaces multiple spaces with one space.

              CSS_DECODE - Decode characters that were encoded using CSS 2.x escape rules syndata.html#characters. This function uses up to two bytes in the decoding process, so it can help to uncover ASCII characters that were encoded using CSS encoding that wouldn’t typically be encoded. It's also useful in countering evasion, which is a combination of a backslash and non-hexadecimal characters. For example, ja\vascript for javascript.

              ESCAPE_SEQ_DECODE - Decode the following ANSI C escape sequences: \a, \b, \f, \n, \r, \t, \v, \, \?, \', \", \xHH (hexadecimal), \0OOO (octal). Encodings that aren't valid remain in the output.

              HEX_DECODE - Decode a string of hexadecimal characters into a binary.

              HTML_ENTITY_DECODE - Replace HTML-encoded characters with unencoded characters. HTML_ENTITY_DECODE performs these operations:

              • Replaces (ampersand)quot; with "

              • Replaces (ampersand)nbsp; with a non-breaking space, decimal 160

              • Replaces (ampersand)lt; with a "less than" symbol

              • Replaces (ampersand)gt; with >

              • Replaces characters that are represented in hexadecimal format, (ampersand)#xhhhh;, with the corresponding characters

              • Replaces characters that are represented in decimal format, (ampersand)#nnnn;, with the corresponding characters

              JS_DECODE - Decode JavaScript escape sequences. If a \ u HHHH code is in the full-width ASCII code range of FF01-FF5E, then the higher byte is used to detect and adjust the lower byte. If not, only the lower byte is used and the higher byte is zeroed, causing a possible loss of information.

              LOWERCASE - Convert uppercase letters (A-Z) to lowercase (a-z).

              MD5 - Calculate an MD5 hash from the data in the input. The computed hash is in a raw binary form.

              NONE - Specify NONE if you don't want any text transformations.

              NORMALIZE_PATH - Remove multiple slashes, directory self-references, and directory back-references that are not at the beginning of the input from an input string.

              NORMALIZE_PATH_WIN - This is the same as NORMALIZE_PATH, but first converts backslash characters to forward slashes.

              REMOVE_NULLS - Remove all NULL bytes from the input.

              REPLACE_COMMENTS - Replace each occurrence of a C-style comment (/* ... */) with a single space. Multiple consecutive occurrences are not compressed. Unterminated comments are also replaced with a space (ASCII 0x20). However, a standalone termination of a comment (*/) is not acted upon.

              REPLACE_NULLS - Replace NULL bytes in the input with space characters (ASCII 0x20).

              SQL_HEX_DECODE - Decode SQL hex data. Example (0x414243) will be decoded to (ABC).

              URL_DECODE - Decode a URL-encoded value.

              URL_DECODE_UNI - Like URL_DECODE, but with support for Microsoft-specific %u encoding. If the code is in the full-width ASCII code range of FF01-FF5E, the higher byte is used to detect and adjust the lower byte. Otherwise, only the lower byte is used and the higher byte is zeroed.

              UTF8_TO_UNICODE - Convert all UTF-8 character sequences to Unicode. This helps input normalization, and minimizing false-positives and false-negatives for non-English languages.

              Possible values include:
              • "NONE"
              • "COMPRESS_WHITE_SPACE"
              • "HTML_ENTITY_DECODE"
              • "LOWERCASE"
              • "CMD_LINE"
              • "URL_DECODE"
              • "BASE64_DECODE"
              • "HEX_DECODE"
              • "MD5"
              • "REPLACE_COMMENTS"
              • "ESCAPE_SEQ_DECODE"
              • "SQL_HEX_DECODE"
              • "CSS_DECODE"
              • "JS_DECODE"
              • "NORMALIZE_PATH"
              • "NORMALIZE_PATH_WIN"
              • "REMOVE_NULLS"
              • "REPLACE_NULLS"
              • "BASE64_DECODE_EXT"
              • "URL_DECODE_UNI"
              • "UTF8_TO_UNICODE"
        • GeoMatchStatement — (map)

          A rule statement used to identify web requests based on country of origin.

          • CountryCodes — (Array<String>)

            An array of two-character country codes, for example, [ "US", "CN" ], from the alpha-2 country ISO codes of the ISO 3166 international standard.

          • ForwardedIPConfig — (map)

            The configuration for inspecting IP addresses in an HTTP header that you specify, instead of using the IP address that's reported by the web request origin. Commonly, this is the X-Forwarded-For (XFF) header, but you can specify any header name.

            Note: If the specified header isn't present in the request, WAF doesn't apply the rule to the web request at all.
            • HeaderName — required — (String)

              The name of the HTTP header to use for the IP address. For example, to use the X-Forwarded-For (XFF) header, set this to X-Forwarded-For.

              Note: If the specified header isn't present in the request, WAF doesn't apply the rule to the web request at all.
            • FallbackBehavior — required — (String)

              The match status to assign to the web request if the request doesn't have a valid IP address in the specified position.

              Note: If the specified header isn't present in the request, WAF doesn't apply the rule to the web request at all.

              You can specify the following fallback behaviors:

              • MATCH - Treat the web request as matching the rule statement. WAF applies the rule action to the request.

              • NO_MATCH - Treat the web request as not matching the rule statement.

              Possible values include:
              • "MATCH"
              • "NO_MATCH"
        • RuleGroupReferenceStatement — (map)

          A rule statement used to run the rules that are defined in a RuleGroup. To use this, create a rule group with your rules, then provide the ARN of the rule group in this statement.

          You cannot nest a RuleGroupReferenceStatement, for example for use inside a NotStatement or OrStatement. You can only use a rule group reference statement at the top level inside a web ACL.

          • ARN — required — (String)

            The Amazon Resource Name (ARN) of the entity.

          • ExcludedRules — (Array<map>)

            The rules in the referenced rule group whose actions are set to Count. When you exclude a rule, WAF evaluates it exactly as it would if the rule action setting were Count. This is a useful option for testing the rules in a rule group without modifying how they handle your web traffic.

            • Name — required — (String)

              The name of the rule whose action you want to override to Count.

        • IPSetReferenceStatement — (map)

          A rule statement used to detect web requests coming from particular IP addresses or address ranges. To use this, create an IPSet that specifies the addresses you want to detect, then use the ARN of that set in this statement. To create an IP set, see CreateIPSet.

          Each IP set rule statement references an IP set. You create and maintain the set independent of your rules. This allows you to use the single set in multiple rules. When you update the referenced set, WAF automatically updates all rules that reference it.

          • ARN — required — (String)

            The Amazon Resource Name (ARN) of the IPSet that this statement references.

          • IPSetForwardedIPConfig — (map)

            The configuration for inspecting IP addresses in an HTTP header that you specify, instead of using the IP address that's reported by the web request origin. Commonly, this is the X-Forwarded-For (XFF) header, but you can specify any header name.

            Note: If the specified header isn't present in the request, WAF doesn't apply the rule to the web request at all.
            • HeaderName — required — (String)

              The name of the HTTP header to use for the IP address. For example, to use the X-Forwarded-For (XFF) header, set this to X-Forwarded-For.

              Note: If the specified header isn't present in the request, WAF doesn't apply the rule to the web request at all.
            • FallbackBehavior — required — (String)

              The match status to assign to the web request if the request doesn't have a valid IP address in the specified position.

              Note: If the specified header isn't present in the request, WAF doesn't apply the rule to the web request at all.

              You can specify the following fallback behaviors:

              • MATCH - Treat the web request as matching the rule statement. WAF applies the rule action to the request.

              • NO_MATCH - Treat the web request as not matching the rule statement.

              Possible values include:
              • "MATCH"
              • "NO_MATCH"
            • Position — required — (String)

              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:

              • FIRST - Inspect the first IP address in the list of IP addresses in the header. This is usually the client's original IP.

              • LAST - Inspect the last IP address in the list of IP addresses in the header.

              • ANY - Inspect all IP addresses in the header for a match. If the header contains more than 10 IP addresses, WAF inspects the last 10.

              Possible values include:
              • "FIRST"
              • "LAST"
              • "ANY"
        • RegexPatternSetReferenceStatement — (map)

          A rule statement used to search web request components for matches with regular expressions. To use this, create a RegexPatternSet that specifies the expressions that you want to detect, then use the ARN of that set in this statement. A web request matches the pattern set rule statement if the request component matches any of the patterns in the set. To create a regex pattern set, see CreateRegexPatternSet.

          Each regex pattern set rule statement references a regex pattern set. You create and maintain the set independent of your rules. This allows you to use the single set in multiple rules. When you update the referenced set, WAF automatically updates all rules that reference it.

          • ARN — required — (String)

            The Amazon Resource Name (ARN) of the RegexPatternSet that this statement references.

          • FieldToMatch — required — (map)

            The part of a web request that you want WAF to inspect. For more information, see FieldToMatch.

            • SingleHeader — (map)

              Inspect a single header. Provide the name of the header to inspect, for example, User-Agent or Referer. This setting isn't case sensitive.

              Example JSON: "SingleHeader": { "Name": "haystack" }

              • Name — required — (String)

                The name of the query header to inspect.

            • SingleQueryArgument — (map)

              Inspect a single query argument. Provide the name of the query argument to inspect, such as UserName or SalesRegion. The name can be up to 30 characters long and isn't case sensitive.

              This is used only to indicate the web request component for WAF to inspect, in the FieldToMatch specification.

              Example JSON: "SingleQueryArgument": { "Name": "myArgument" }

              • Name — required — (String)

                The name of the query argument to inspect.

            • AllQueryArguments — (map)

              Inspect all query arguments.

            • UriPath — (map)

              Inspect the request URI path. This is the part of a web request that identifies a resource, for example, /images/daily-ad.jpg.

            • QueryString — (map)

              Inspect the query string. This is the part of a URL that appears after a ? character, if any.

            • Body — (map)

              Inspect the request body as plain text. The request body immediately follows the request headers. This is the part of a request that contains any additional data that you want to send to your web server as the HTTP request body, such as data from a form.

              Note that only the first 8 KB (8192 bytes) of the request body are forwarded to WAF for inspection by the underlying host service. If you don't need to inspect more than 8 KB, you can guarantee that you don't allow additional bytes in by combining a statement that inspects the body of the web request, such as ByteMatchStatement or RegexPatternSetReferenceStatement, with a SizeConstraintStatement that enforces an 8 KB size limit on the body of the request. WAF doesn't support inspecting the entire contents of web requests whose bodies exceed the 8 KB limit.

            • Method — (map)

              Inspect the HTTP method. The method indicates the type of operation that the request is asking the origin to perform.

            • JsonBody — (map)

              Inspect the request body as JSON. The request body immediately follows the request headers. This is the part of a request that contains any additional data that you want to send to your web server as the HTTP request body, such as data from a form.

              Note that only the first 8 KB (8192 bytes) of the request body are forwarded to WAF for inspection by the underlying host service. If you don't need to inspect more than 8 KB, you can guarantee that you don't allow additional bytes in by combining a statement that inspects the body of the web request, such as ByteMatchStatement or RegexPatternSetReferenceStatement, with a SizeConstraintStatement that enforces an 8 KB size limit on the body of the request. WAF doesn't support inspecting the entire contents of web requests whose bodies exceed the 8 KB limit.

              • MatchPattern — required — (map)

                The patterns to look for in the JSON body. WAF inspects the results of these pattern matches against the rule inspection criteria.

                • All — (map)

                  Match all of the elements. See also MatchScope in JsonBody.

                  You must specify either this setting or the IncludedPaths setting, but not both.

                • IncludedPaths — (Array<String>)

                  Match only the specified include paths. See also MatchScope in JsonBody.

                  Provide the include paths using JSON Pointer syntax. For example, "IncludedPaths": ["/dogs/0/name", "/dogs/1/name"]. For information about this syntax, see the Internet Engineering Task Force (IETF) documentation JavaScript Object Notation (JSON) Pointer.

                  You must specify either this setting or the All setting, but not both.

                  Note: Don't use this option to include all paths. Instead, use the All setting.
              • MatchScope — required — (String)

                The parts of the JSON to match against using the MatchPattern. If you specify All, WAF matches against keys and values.

                Possible values include:
                • "ALL"
                • "KEY"
                • "VALUE"
              • InvalidFallbackBehavior — (String)

                What WAF should do if it fails to completely parse the JSON body. The options are the following:

                • EVALUATE_AS_STRING - Inspect the body as plain text. WAF applies the text transformations and inspection criteria that you defined for the JSON inspection to the body text string.

                • MATCH - Treat the web request as matching the rule statement. WAF applies the rule action to the request.

                • NO_MATCH - Treat the web request as not matching the rule statement.

                If you don't provide this setting, WAF parses and evaluates the content only up to the first parsing failure that it encounters.

                WAF does its best to parse the entire JSON body, but might be forced to stop for reasons such as invalid characters, duplicate keys, truncation, and any content whose root node isn't an object or an array.

                WAF parses the JSON in the following examples as two valid key, value pairs:

                • Missing comma: {"key1":"value1""key2":"value2"}

                • Missing colon: {"key1":"value1","key2""value2"}

                • Extra colons: {"key1"::"value1","key2""value2"}

                Possible values include:
                • "MATCH"
                • "NO_MATCH"
                • "EVALUATE_AS_STRING"
          • TextTransformations — required — (Array<map>)

            Text transformations eliminate some of the unusual formatting that attackers use in web requests in an effort to bypass detection. If you specify one or more transformations in a rule statement, WAF performs all transformations on the content of the request component identified by FieldToMatch, starting from the lowest priority setting, before inspecting the content for a match.

            • Priority — required — (Integer)

              Sets the relative processing order for multiple transformations that are defined for a rule statement. WAF processes all transformations, from lowest priority to highest, before inspecting the transformed content. The priorities don't need to be consecutive, but they must all be different.

            • Type — required — (String)

              You can specify the following transformation types:

              BASE64_DECODE - Decode a Base64-encoded string.

              BASE64_DECODE_EXT - Decode a Base64-encoded string, but use a forgiving implementation that ignores characters that aren't valid.

              CMD_LINE - Command-line transformations. These are helpful in reducing effectiveness of attackers who inject an operating system command-line command and use unusual formatting to disguise some or all of the command.

              • Delete the following characters: \ " ' ^

              • Delete spaces before the following characters: / (

              • Replace the following characters with a space: , ;

              • Replace multiple spaces with one space

              • Convert uppercase letters (A-Z) to lowercase (a-z)

              COMPRESS_WHITE_SPACE - Replace these characters with a space character (decimal 32):

              • \f, formfeed, decimal 12

              • \t, tab, decimal 9

              • \n, newline, decimal 10

              • \r, carriage return, decimal 13

              • \v, vertical tab, decimal 11

              • Non-breaking space, decimal 160

              COMPRESS_WHITE_SPACE also replaces multiple spaces with one space.

              CSS_DECODE - Decode characters that were encoded using CSS 2.x escape rules syndata.html#characters. This function uses up to two bytes in the decoding process, so it can help to uncover ASCII characters that were encoded using CSS encoding that wouldn’t typically be encoded. It's also useful in countering evasion, which is a combination of a backslash and non-hexadecimal characters. For example, ja\vascript for javascript.

              ESCAPE_SEQ_DECODE - Decode the following ANSI C escape sequences: \a, \b, \f, \n, \r, \t, \v, \, \?, \', \", \xHH (hexadecimal), \0OOO (octal). Encodings that aren't valid remain in the output.

              HEX_DECODE - Decode a string of hexadecimal characters into a binary.

              HTML_ENTITY_DECODE - Replace HTML-encoded characters with unencoded characters. HTML_ENTITY_DECODE performs these operations:

              • Replaces (ampersand)quot; with "

              • Replaces (ampersand)nbsp; with a non-breaking space, decimal 160

              • Replaces (ampersand)lt; with a "less than" symbol

              • Replaces (ampersand)gt; with >

              • Replaces characters that are represented in hexadecimal format, (ampersand)#xhhhh;, with the corresponding characters

              • Replaces characters that are represented in decimal format, (ampersand)#nnnn;, with the corresponding characters

              JS_DECODE - Decode JavaScript escape sequences. If a \ u HHHH code is in the full-width ASCII code range of FF01-FF5E, then the higher byte is used to detect and adjust the lower byte. If not, only the lower byte is used and the higher byte is zeroed, causing a possible loss of information.

              LOWERCASE - Convert uppercase letters (A-Z) to lowercase (a-z).

              MD5 - Calculate an MD5 hash from the data in the input. The computed hash is in a raw binary form.

              NONE - Specify NONE if you don't want any text transformations.

              NORMALIZE_PATH - Remove multiple slashes, directory self-references, and directory back-references that are not at the beginning of the input from an input string.

              NORMALIZE_PATH_WIN - This is the same as NORMALIZE_PATH, but first converts backslash characters to forward slashes.

              REMOVE_NULLS - Remove all NULL bytes from the input.

              REPLACE_COMMENTS - Replace each occurrence of a C-style comment (/* ... */) with a single space. Multiple consecutive occurrences are not compressed. Unterminated comments are also replaced with a space (ASCII 0x20). However, a standalone termination of a comment (*/) is not acted upon.

              REPLACE_NULLS - Replace NULL bytes in the input with space characters (ASCII 0x20).

              SQL_HEX_DECODE - Decode SQL hex data. Example (0x414243) will be decoded to (ABC).

              URL_DECODE - Decode a URL-encoded value.

              URL_DECODE_UNI - Like URL_DECODE, but with support for Microsoft-specific %u encoding. If the code is in the full-width ASCII code range of FF01-FF5E, the higher byte is used to detect and adjust the lower byte. Otherwise, only the lower byte is used and the higher byte is zeroed.

              UTF8_TO_UNICODE - Convert all UTF-8 character sequences to Unicode. This helps input normalization, and minimizing false-positives and false-negatives for non-English languages.

              Possible values include:
              • "NONE"
              • "COMPRESS_WHITE_SPACE"
              • "HTML_ENTITY_DECODE"
              • "LOWERCASE"
              • "CMD_LINE"
              • "URL_DECODE"
              • "BASE64_DECODE"
              • "HEX_DECODE"
              • "MD5"
              • "REPLACE_COMMENTS"
              • "ESCAPE_SEQ_DECODE"
              • "SQL_HEX_DECODE"
              • "CSS_DECODE"
              • "JS_DECODE"
              • "NORMALIZE_PATH"
              • "NORMALIZE_PATH_WIN"
              • "REMOVE_NULLS"
              • "REPLACE_NULLS"
              • "BASE64_DECODE_EXT"
              • "URL_DECODE_UNI"
              • "UTF8_TO_UNICODE"
        • RateBasedStatement — (map)

          A rate-based rule tracks the rate of requests for each originating IP address, and triggers the rule action when the rate exceeds a limit that you specify on the number of requests in any 5-minute time span. You can use this to put a temporary block on requests from an IP address that is sending excessive requests.

          WAF tracks and manages web requests separately for each instance of a rate-based rule that you use. For example, if you provide the same rate-based rule settings in two web ACLs, each of the two rule statements represents a separate instance of the rate-based rule and gets its own tracking and management by WAF. If you define a rate-based rule inside a rule group, and then use that rule group in multiple places, each use creates a separate instance of the rate-based rule that gets its own tracking and management by WAF.

          When the rule action triggers, WAF blocks additional requests from the IP address until the request rate falls below the limit.

          You can optionally nest another statement inside the rate-based statement, to narrow the scope of the rule so that it only counts requests that match the nested statement. For example, based on recent requests that you have seen from an attacker, you might create a rate-based rule with a nested AND rule statement that contains the following nested statements:

          • An IP match statement with an IP set that specified the address 192.0.2.44.

          • A string match statement that searches in the User-Agent header for the string BadBot.

          In this rate-based rule, you also define a rate limit. For this example, the rate limit is 1,000. Requests that meet both of the conditions in the statements are counted. If the count exceeds 1,000 requests per five minutes, the rule action triggers. Requests that do not meet both conditions are not counted towards the rate limit and are not affected by this rule.

          You cannot nest a RateBasedStatement inside another statement, for example inside a NotStatement or OrStatement. You can define a RateBasedStatement inside a web ACL and inside a rule group.

          • Limit — required — (Integer)

            The limit on requests per 5-minute period for a single originating IP address. If the statement includes a ScopeDownStatement, this limit is applied only to the requests that match the statement.

          • AggregateKeyType — required — (String)

            Setting that indicates how to aggregate the request counts. The options are the following:

            • IP - Aggregate the request counts on the IP address from the web request origin.

            • FORWARDED_IP - Aggregate the request counts on the first IP address in an HTTP header. If you use this, configure the ForwardedIPConfig, to specify the header to use.

            Possible values include:
            • "IP"
            • "FORWARDED_IP"
          • ForwardedIPConfig — (map)

            The configuration for inspecting IP addresses in an HTTP header that you specify, instead of using the IP address that's reported by the web request origin. Commonly, this is the X-Forwarded-For (XFF) header, but you can specify any header name.

            Note: If the specified header isn't present in the request, WAF doesn't apply the rule to the web request at all.

            This is required if AggregateKeyType is set to FORWARDED_IP.

            • HeaderName — required — (String)

              The name of the HTTP header to use for the IP address. For example, to use the X-Forwarded-For (XFF) header, set this to X-Forwarded-For.

              Note: If the specified header isn't present in the request, WAF doesn't apply the rule to the web request at all.
            • FallbackBehavior — required — (String)

              The match status to assign to the web request if the request doesn't have a valid IP address in the specified position.

              Note: If the specified header isn't present in the request, WAF doesn't apply the rule to the web request at all.

              You can specify the following fallback behaviors:

              • MATCH - Treat the web request as matching the rule statement. WAF applies the rule action to the request.

              • NO_MATCH - Treat the web request as not matching the rule statement.

              Possible values include:
              • "MATCH"
              • "NO_MATCH"
        • AndStatement — (map)

          A logical rule statement used to combine other rule statements with AND logic. You provide more than one Statement within the AndStatement.

          • Statements — required — (Array<map>)

            The statements to combine with AND logic. You can use any statements that can be nested.

        • OrStatement — (map)

          A logical rule statement used to combine other rule statements with OR logic. You provide more than one Statement within the OrStatement.

          • Statements — required — (Array<map>)

            The statements to combine with OR logic. You can use any statements that can be nested.

        • NotStatement — (map)

          A logical rule statement used to negate the results of another rule statement. You provide one Statement within the NotStatement.

        • ManagedRuleGroupStatement — (map)

          A rule statement used to run the rules that are defined in a managed rule group. To use this, provide the vendor name and the name of the rule group in this statement. You can retrieve the required names by calling ListAvailableManagedRuleGroups.

          You cannot nest a ManagedRuleGroupStatement, for example for use inside a NotStatement or OrStatement. It can only be referenced as a top-level statement within a rule.

          • VendorName — required — (String)

            The name of the managed rule group vendor. You use this, along with the rule group name, to identify the rule group.

          • Name — required — (String)

            The name of the managed rule group. You use this, along with the vendor name, to identify the rule group.

          • Version — (String)

            The version of the managed rule group to use. If you specify this, the version setting is fixed until you change it. If you don't specify this, WAF uses the vendor's default version, and then keeps the version at the vendor's default when the vendor updates the managed rule group settings.

          • ExcludedRules — (Array<map>)

            The rules in the referenced rule group whose actions are set to Count. When you exclude a rule, WAF evaluates it exactly as it would if the rule action setting were Count. This is a useful option for testing the rules in a rule group without modifying how they handle your web traffic.

            • Name — required — (String)

              The name of the rule whose action you want to override to Count.

        • LabelMatchStatement — (map)

          A rule statement that defines a string match search against labels that have been added to the web request by rules that have already run in the web ACL.

          The label match statement provides the label or namespace string to search for. The label string can represent a part or all of the fully qualified label name that had been added to the web request. Fully qualified labels have a prefix, optional namespaces, and label name. The prefix identifies the rule group or web ACL context of the rule that added the label. If you do not provide the fully qualified name in your label match string, WAF performs the search for labels that were added in the same context as the label match statement.

          • Scope — required — (String)

            Specify whether you want to match using the label name or just the namespace.

            Possible values include:
            • "LABEL"
            • "NAMESPACE"
          • Key — required — (String)

            The string to match against. The setting you provide for this depends on the match statement's Scope setting:

            • If the Scope indicates LABEL, then this specification must include the name and can include any number of preceding namespace specifications and prefix up to providing the fully qualified label name.

            • If the Scope indicates NAMESPACE, then this specification can include any number of contiguous namespace strings, and can include the entire label namespace prefix from the rule group or web ACL where the label originates.

            Labels are case sensitive and components of a label must be separated by colon, for example NS1:NS2:name.

        • RegexMatchStatement — (map)

          A rule statement used to search web request components for a match against a single regular expression.

          • RegexString — required — (String)

            The string representing the regular expression.

          • FieldToMatch — required — (map)

            The part of a web request that you want WAF to inspect. For more information, see FieldToMatch.

            • SingleHeader — (map)

              Inspect a single header. Provide the name of the header to inspect, for example, User-Agent or Referer. This setting isn't case sensitive.

              Example JSON: "SingleHeader": { "Name": "haystack" }

              • Name — required — (String)

                The name of the query header to inspect.

            • SingleQueryArgument — (map)

              Inspect a single query argument. Provide the name of the query argument to inspect, such as UserName or SalesRegion. The name can be up to 30 characters long and isn't case sensitive.

              This is used only to indicate the web request component for WAF to inspect, in the FieldToMatch specification.

              Example JSON: "SingleQueryArgument": { "Name": "myArgument" }

              • Name — required — (String)

                The name of the query argument to inspect.

            • AllQueryArguments — (map)

              Inspect all query arguments.

            • UriPath — (map)

              Inspect the request URI path. This is the part of a web request that identifies a resource, for example, /images/daily-ad.jpg.

            • QueryString — (map)

              Inspect the query string. This is the part of a URL that appears after a ? character, if any.

            • Body — (map)

              Inspect the request body as plain text. The request body immediately follows the request headers. This is the part of a request that contains any additional data that you want to send to your web server as the HTTP request body, such as data from a form.

              Note that only the first 8 KB (8192 bytes) of the request body are forwarded to WAF for inspection by the underlying host service. If you don't need to inspect more than 8 KB, you can guarantee that you don't allow additional bytes in by combining a statement that inspects the body of the web request, such as ByteMatchStatement or RegexPatternSetReferenceStatement, with a SizeConstraintStatement that enforces an 8 KB size limit on the body of the request. WAF doesn't support inspecting the entire contents of web requests whose bodies exceed the 8 KB limit.

            • Method — (map)

              Inspect the HTTP method. The method indicates the type of operation that the request is asking the origin to perform.

            • JsonBody — (map)

              Inspect the request body as JSON. The request body immediately follows the request headers. This is the part of a request that contains any additional data that you want to send to your web server as the HTTP request body, such as data from a form.

              Note that only the first 8 KB (8192 bytes) of the request body are forwarded to WAF for inspection by the underlying host service. If you don't need to inspect more than 8 KB, you can guarantee that you don't allow additional bytes in by combining a statement that inspects the body of the web request, such as ByteMatchStatement or RegexPatternSetReferenceStatement, with a SizeConstraintStatement that enforces an 8 KB size limit on the body of the request. WAF doesn't support inspecting the entire contents of web requests whose bodies exceed the 8 KB limit.

              • MatchPattern — required — (map)

                The patterns to look for in the JSON body. WAF inspects the results of these pattern matches against the rule inspection criteria.

                • All — (map)

                  Match all of the elements. See also MatchScope in JsonBody.

                  You must specify either this setting or the IncludedPaths setting, but not both.

                • IncludedPaths — (Array<String>)

                  Match only the specified include paths. See also MatchScope in JsonBody.

                  Provide the include paths using JSON Pointer syntax. For example, "IncludedPaths": ["/dogs/0/name", "/dogs/1/name"]. For information about this syntax, see the Internet Engineering Task Force (IETF) documentation JavaScript Object Notation (JSON) Pointer.

                  You must specify either this setting or the All setting, but not both.

                  Note: Don't use this option to include all paths. Instead, use the All setting.
              • MatchScope — required — (String)

                The parts of the JSON to match against using the MatchPattern. If you specify All, WAF matches against keys and values.

                Possible values include:
                • "ALL"
                • "KEY"
                • "VALUE"
              • InvalidFallbackBehavior — (String)

                What WAF should do if it fails to completely parse the JSON body. The options are the following:

                • EVALUATE_AS_STRING - Inspect the body as plain text. WAF applies the text transformations and inspection criteria that you defined for the JSON inspection to the body text string.

                • MATCH - Treat the web request as matching the rule statement. WAF applies the rule action to the request.

                • NO_MATCH - Treat the web request as not matching the rule statement.

                If you don't provide this setting, WAF parses and evaluates the content only up to the first parsing failure that it encounters.

                WAF does its best to parse the entire JSON body, but might be forced to stop for reasons such as invalid characters, duplicate keys, truncation, and any content whose root node isn't an object or an array.

                WAF parses the JSON in the following examples as two valid key, value pairs:

                • Missing comma: {"key1":"value1""key2":"value2"}

                • Missing colon: {"key1":"value1","key2""value2"}

                • Extra colons: {"key1"::"value1","key2""value2"}

                Possible values include:
                • "MATCH"
                • "NO_MATCH"
                • "EVALUATE_AS_STRING"
          • TextTransformations — required — (Array<map>)

            Text transformations eliminate some of the unusual formatting that attackers use in web requests in an effort to bypass detection. If you specify one or more transformations in a rule statement, WAF performs all transformations on the content of the request component identified by FieldToMatch, starting from the lowest priority setting, before inspecting the content for a match.

            • Priority — required — (Integer)

              Sets the relative processing order for multiple transformations that are defined for a rule statement. WAF processes all transformations, from lowest priority to highest, before inspecting the transformed content. The priorities don't need to be consecutive, but they must all be different.

            • Type — required — (String)

              You can specify the following transformation types:

              BASE64_DECODE - Decode a Base64-encoded string.

              BASE64_DECODE_EXT - Decode a Base64-encoded string, but use a forgiving implementation that ignores characters that aren't valid.

              CMD_LINE - Command-line transformations. These are helpful in reducing effectiveness of attackers who inject an operating system command-line command and use unusual formatting to disguise some or all of the command.

              • Delete the following characters: \ " ' ^

              • Delete spaces before the following characters: / (

              • Replace the following characters with a space: , ;

              • Replace multiple spaces with one space

              • Convert uppercase letters (A-Z) to lowercase (a-z)

              COMPRESS_WHITE_SPACE - Replace these characters with a space character (decimal 32):

              • \f, formfeed, decimal 12

              • \t, tab, decimal 9

              • \n, newline, decimal 10

              • \r, carriage return, decimal 13

              • \v, vertical tab, decimal 11

              • Non-breaking space, decimal 160

              COMPRESS_WHITE_SPACE also replaces multiple spaces with one space.

              CSS_DECODE - Decode characters that were encoded using CSS 2.x escape rules syndata.html#characters. This function uses up to two bytes in the decoding process, so it can help to uncover ASCII characters that were encoded using CSS encoding that wouldn’t typically be encoded. It's also useful in countering evasion, which is a combination of a backslash and non-hexadecimal characters. For example, ja\vascript for javascript.

              ESCAPE_SEQ_DECODE - Decode the following ANSI C escape sequences: \a, \b, \f, \n, \r, \t, \v, \, \?, \', \", \xHH (hexadecimal), \0OOO (octal). Encodings that aren't valid remain in the output.

              HEX_DECODE - Decode a string of hexadecimal characters into a binary.

              HTML_ENTITY_DECODE - Replace HTML-encoded characters with unencoded characters. HTML_ENTITY_DECODE performs these operations:

              • Replaces (ampersand)quot; with "

              • Replaces (ampersand)nbsp; with a non-breaking space, decimal 160

              • Replaces (ampersand)lt; with a "less than" symbol

              • Replaces (ampersand)gt; with >

              • Replaces characters that are represented in hexadecimal format, (ampersand)#xhhhh;, with the corresponding characters

              • Replaces characters that are represented in decimal format, (ampersand)#nnnn;, with the corresponding characters

              JS_DECODE - Decode JavaScript escape sequences. If a \ u HHHH code is in the full-width ASCII code range of FF01-FF5E, then the higher byte is used to detect and adjust the lower byte. If not, only the lower byte is used and the higher byte is zeroed, causing a possible loss of information.

              LOWERCASE - Convert uppercase letters (A-Z) to lowercase (a-z).

              MD5 - Calculate an MD5 hash from the data in the input. The computed hash is in a raw binary form.

              NONE - Specify NONE if you don't want any text transformations.

              NORMALIZE_PATH - Remove multiple slashes, directory self-references, and directory back-references that are not at the beginning of the input from an input string.

              NORMALIZE_PATH_WIN - This is the same as NORMALIZE_PATH, but first converts backslash characters to forward slashes.

              REMOVE_NULLS - Remove all NULL bytes from the input.

              REPLACE_COMMENTS - Replace each occurrence of a C-style comment (/* ... */) with a single space. Multiple consecutive occurrences are not compressed. Unterminated comments are also replaced with a space (ASCII 0x20). However, a standalone termination of a comment (*/) is not acted upon.

              REPLACE_NULLS - Replace NULL bytes in the input with space characters (ASCII 0x20).

              SQL_HEX_DECODE - Decode SQL hex data. Example (0x414243) will be decoded to (ABC).

              URL_DECODE - Decode a URL-encoded value.

              URL_DECODE_UNI - Like URL_DECODE, but with support for Microsoft-specific %u encoding. If the code is in the full-width ASCII code range of FF01-FF5E, the higher byte is used to detect and adjust the lower byte. Otherwise, only the lower byte is used and the higher byte is zeroed.

              UTF8_TO_UNICODE - Convert all UTF-8 character sequences to Unicode. This helps input normalization, and minimizing false-positives and false-negatives for non-English languages.

              Possible values include:
              • "NONE"
              • "COMPRESS_WHITE_SPACE"
              • "HTML_ENTITY_DECODE"
              • "LOWERCASE"
              • "CMD_LINE"
              • "URL_DECODE"
              • "BASE64_DECODE"
              • "HEX_DECODE"
              • "MD5"
              • "REPLACE_COMMENTS"
              • "ESCAPE_SEQ_DECODE"
              • "SQL_HEX_DECODE"
              • "CSS_DECODE"
              • "JS_DECODE"
              • "NORMALIZE_PATH"
              • "NORMALIZE_PATH_WIN"
              • "REMOVE_NULLS"
              • "REPLACE_NULLS"
              • "BASE64_DECODE_EXT"
              • "URL_DECODE_UNI"
              • "UTF8_TO_UNICODE"
      • Action — (map)

        The action that WAF should take on a web request when it matches the rule statement. Settings at the web ACL level can override the rule action setting.

        This is used only for rules whose statements do not reference a rule group. Rule statements that reference a rule group include RuleGroupReferenceStatement and ManagedRuleGroupStatement.

        You must specify either this Action setting or the rule OverrideAction setting, but not both:

        • If the rule statement does not reference a rule group, use this rule action setting and not the rule override action setting.

        • If the rule statement references a rule group, use the override action setting and not this action setting.

        • Block — (map)

          Instructs WAF to block the web request.

          • CustomResponse — (map)

            Defines a custom response for the web request.

            For information about customizing web requests and responses, see Customizing web requests and responses in WAF in the WAF Developer Guide.

            • ResponseCode — required — (Integer)

              The HTTP status code to return to the client.

              For a list of status codes that you can use in your custom reqponses, see Supported status codes for custom response in the WAF Developer Guide.

            • CustomResponseBodyKey — (String)

              References the response body that you want WAF to return to the web request client. You can define a custom response for a rule action or a default web ACL action that is set to block. To do this, you first define the response body key and value in the CustomResponseBodies setting for the WebACL or RuleGroup where you want to use it. Then, in the rule action or web ACL default action BlockAction setting, you reference the response body using this key.

            • ResponseHeaders — (Array<map>)

              The HTTP headers to use in the response. Duplicate header names are not allowed.

              For information about the limits on count and size for custom request and response settings, see WAF quotas in the WAF Developer Guide.

              • Name — required — (String)

                The name of the custom header.

                For custom request header insertion, when WAF inserts the header into the request, it prefixes this name x-amzn-waf-, to avoid confusion with the headers that are already in the request. For example, for the header name sample, WAF inserts the header x-amzn-waf-sample.

              • Value — required — (String)

                The value of the custom header.

        • Allow — (map)

          Instructs WAF to allow the web request.

          • CustomRequestHandling — (map)

            Defines custom handling for the web request.

            For information about customizing web requests and responses, see Customizing web requests and responses in WAF in the WAF Developer Guide.

            • InsertHeaders — required — (Array<map>)

              The HTTP headers to insert into the request. Duplicate header names are not allowed.

              For information about the limits on count and size for custom request and response settings, see WAF quotas in the WAF Developer Guide.

              • Name — required — (String)

                The name of the custom header.

                For custom request header insertion, when WAF inserts the header into the request, it prefixes this name x-amzn-waf-, to avoid confusion with the headers that are already in the request. For example, for the header name sample, WAF inserts the header x-amzn-waf-sample.

              • Value — required — (String)

                The value of the custom header.

        • Count — (map)

          Instructs WAF to count the web request and allow it.

          • CustomRequestHandling — (map)

            Defines custom handling for the web request.

            For information about customizing web requests and responses, see Customizing web requests and responses in WAF in the WAF Developer Guide.

            • InsertHeaders — required — (Array<map>)

              The HTTP headers to insert into the request. Duplicate header names are not allowed.

              For information about the limits on count and size for custom request and response settings, see WAF quotas in the WAF Developer Guide.

              • Name — required — (String)

                The name of the custom header.

                For custom request header insertion, when WAF inserts the header into the request, it prefixes this name x-amzn-waf-, to avoid confusion with the headers that are already in the request. For example, for the header name sample, WAF inserts the header x-amzn-waf-sample.

              • Value — required — (String)

                The value of the custom header.

        • Captcha — (map)

          Instructs WAF to run a CAPTCHA check against the web request.

          • CustomRequestHandling — (map)

            Defines custom handling for the web request.

            For information about customizing web requests and responses, see Customizing web requests and responses in WAF in the WAF Developer Guide.

            • InsertHeaders — required — (Array<map>)

              The HTTP headers to insert into the request. Duplicate header names are not allowed.

              For information about the limits on count and size for custom request and response settings, see WAF quotas in the WAF Developer Guide.

              • Name — required — (String)

                The name of the custom header.

                For custom request header insertion, when WAF inserts the header into the request, it prefixes this name x-amzn-waf-, to avoid confusion with the headers that are already in the request. For example, for the header name sample, WAF inserts the header x-amzn-waf-sample.

              • Value — required — (String)

                The value of the custom header.

      • OverrideAction — (map)

        The action to use in the place of the action that results from the rule group evaluation. Set the override action to none to leave the result of the rule group alone. Set it to count to override the result to count only.

        You can only use this for rule statements that reference a rule group, like RuleGroupReferenceStatement and ManagedRuleGroupStatement.

        Note: This option is usually set to none. It does not affect how the rules in the rule group are evaluated. If you want the rules in the rule group to only count matches, do not use this and instead exclude those rules in your rule group reference statement settings.
        • Count — (map)

          Override the rule group evaluation result to count only.

          Note: This option is usually set to none. It does not affect how the rules in the rule group are evaluated. If you want the rules in the rule group to only count matches, do not use this and instead exclude those rules in your rule group reference statement settings.
          • CustomRequestHandling — (map)

            Defines custom handling for the web request.

            For information about customizing web requests and responses, see Customizing web requests and responses in WAF in the WAF Developer Guide.

            • InsertHeaders — required — (Array<map>)

              The HTTP headers to insert into the request. Duplicate header names are not allowed.

              For information about the limits on count and size for custom request and response settings, see WAF quotas in the WAF Developer Guide.

              • Name — required — (String)

                The name of the custom header.

                For custom request header insertion, when WAF inserts the header into the request, it prefixes this name x-amzn-waf-, to avoid confusion with the headers that are already in the request. For example, for the header name sample, WAF inserts the header x-amzn-waf-sample.

              • Value — required — (String)

                The value of the custom header.

        • None — (map)

          Don't override the rule group evaluation result. This is the most common setting.

      • RuleLabels — (Array<map>)

        Labels to apply to web requests that match the rule match statement. WAF applies fully qualified labels to matching web requests. A fully qualified label is the concatenation of a label namespace and a rule label. The rule's rule group or web ACL defines the label namespace.

        Rules that run after this rule in the web ACL can match against these labels using a LabelMatchStatement.

        For each label, provide a case-sensitive string containing optional namespaces and a label name, according to the following guidelines:

        • Separate each component of the label with a colon.

        • Each namespace or name can have up to 128 characters.

        • You can specify up to 5 namespaces in a label.

        • Don't use the following reserved words in your label specification: aws, waf, managed, rulegroup, webacl, regexpatternset, or ipset.

        For example, myLabelName or nameSpace1:nameSpace2:myLabelName.

        • Name — required — (String)

          The label string.

      • VisibilityConfig — required — (map)

        Defines and enables Amazon CloudWatch metrics and web request sample collection.

        • SampledRequestsEnabled — required — (Boolean)

          A boolean indicating whether WAF should store a sampling of the web requests that match the rules. You can view the sampled requests through the WAF console.

        • CloudWatchMetricsEnabled — required — (Boolean)

          A boolean indicating whether the associated resource sends metrics to Amazon CloudWatch. For the list of available metrics, see WAF Metrics.

        • MetricName — required — (String)

          A name of the Amazon CloudWatch metric. The name can contain only the characters: A-Z, a-z, 0-9, - (hyphen), and _ (underscore). The name can be from one to 128 characters long. It can't contain whitespace or metric names reserved for WAF, for example "All" and "Default_Action."

      • CaptchaConfig — (map)

        Specifies how WAF should handle CAPTCHA evaluations. If you don't specify this, WAF uses the CAPTCHA configuration that's defined for the web ACL.

        • ImmunityTimeProperty — (map)

          Determines how long a CAPTCHA token remains valid after the client successfully solves a CAPTCHA puzzle.

          • ImmunityTime — required — (Integer)

            The amount of time, in seconds, that a CAPTCHA token is valid. The default setting is 300.

Callback (callback):

  • function(err, data) { ... }

    Called when a response from the service is returned. If a callback is not supplied, you must call AWS.Request.send() on the returned request object to initiate the request.

    Context (this):

    • (AWS.Response) —

      the response object containing error, data properties, and the original request object.

    Parameters:

    • err (Error) —

      the error object returned from the request. Set to null if the request is successful.

    • data (Object) —

      the de-serialized data returned from the request. Set to null if a request error occurs. The data object has the following properties:

      • Capacity — (Integer)

        The capacity required by the rules and scope.

Returns:

  • (AWS.Request) —

    a handle to the operation request for subsequent event callback registration.

createIPSet(params = {}, callback) ⇒ AWS.Request

Creates an IPSet, which you use to identify web requests that originate from specific IP addresses or ranges of IP addresses. For example, if you're receiving a lot of requests from a ranges of IP addresses, you can configure WAF to block them using an IPSet that lists those IP addresses.

Service Reference:

Examples:

Calling the createIPSet operation

var params = {
  Addresses: [ /* required */
    'STRING_VALUE',
    /* more items */
  ],
  IPAddressVersion: IPV4 | IPV6, /* required */
  Name: 'STRING_VALUE', /* required */
  Scope: CLOUDFRONT | REGIONAL, /* required */
  Description: 'STRING_VALUE',
  Tags: [
    {
      Key: 'STRING_VALUE', /* required */
      Value: 'STRING_VALUE' /* required */
    },
    /* more items */
  ]
};
wafv2.createIPSet(params, function(err, data) {
  if (err) console.log(err, err.stack); // an error occurred
  else     console.log(data);           // successful response
});

Parameters:

  • params (Object) (defaults to: {}) —
    • Name — (String)

      The name of the IP set. You cannot change the name of an IPSet after you create it.

    • Scope — (String)

      Specifies whether this is for an Amazon CloudFront distribution or for a regional application. A regional application can be an Application Load Balancer (ALB), an Amazon API Gateway REST API, or an AppSync GraphQL API.

      To work with CloudFront, you must also specify the Region US East (N. Virginia) as follows:

      • CLI - Specify the Region when you use the CloudFront scope: --scope=CLOUDFRONT --region=us-east-1.

      • API and SDKs - For all calls, use the Region endpoint us-east-1.

      Possible values include:
      • "CLOUDFRONT"
      • "REGIONAL"
    • Description — (String)

      A description of the IP set that helps with identification.

    • IPAddressVersion — (String)

      The version of the IP addresses, either IPV4 or IPV6.

      Possible values include:
      • "IPV4"
      • "IPV6"
    • Addresses — (Array<String>)

      Contains an array of strings that specify one or more IP addresses or blocks of IP addresses in Classless Inter-Domain Routing (CIDR) notation. WAF supports all IPv4 and IPv6 CIDR ranges except for /0.

      Examples:

      • To configure WAF to allow, block, or count requests that originated from the IP address 192.0.2.44, specify 192.0.2.44/32.

      • To configure WAF to allow, block, or count requests that originated from IP addresses from 192.0.2.0 to 192.0.2.255, specify 192.0.2.0/24.

      • To configure WAF to allow, block, or count requests that originated from the IP address 1111:0000:0000:0000:0000:0000:0000:0111, specify 1111:0000:0000:0000:0000:0000:0000:0111/128.

      • To configure WAF to allow, block, or count requests that originated from IP addresses 1111:0000:0000:0000:0000:0000:0000:0000 to 1111:0000:0000:0000:ffff:ffff:ffff:ffff, specify 1111:0000:0000:0000:0000:0000:0000:0000/64.

      For more information about CIDR notation, see the Wikipedia entry Classless Inter-Domain Routing.

    • Tags — (Array<map>)

      An array of key:value pairs to associate with the resource.

      • Key — required — (String)

        Part of the key:value pair that defines a tag. You can use a tag key to describe a category of information, such as "customer." Tag keys are case-sensitive.

      • Value — required — (String)

        Part of the key:value pair that defines a tag. You can use a tag value to describe a specific value within a category, such as "companyA" or "companyB." Tag values are case-sensitive.

Callback (callback):

  • function(err, data) { ... }

    Called when a response from the service is returned. If a callback is not supplied, you must call AWS.Request.send() on the returned request object to initiate the request.

    Context (this):

    • (AWS.Response) —

      the response object containing error, data properties, and the original request object.

    Parameters:

    • err (Error) —

      the error object returned from the request. Set to null if the request is successful.

    • data (Object) —

      the de-serialized data returned from the request. Set to null if a request error occurs. The data object has the following properties:

      • Summary — (map)

        High-level information about an IPSet, returned by operations like create and list. This provides information like the ID, that you can use to retrieve and manage an IPSet, and the ARN, that you provide to the IPSetReferenceStatement to use the address set in a Rule.

        • Name — (String)

          The name of the IP set. You cannot change the name of an IPSet after you create it.

        • Id — (String)

          A unique identifier for the set. This ID is returned in the responses to create and list commands. You provide it to operations like update and delete.

        • Description — (String)

          A description of the IP set that helps with identification.

        • LockToken — (String)

          A token used for optimistic locking. WAF returns a token to your get and list requests, to mark the state of the entity at the time of the request. To make changes to the entity associated with the token, you provide the token to operations like update and delete. WAF uses the token to ensure that no changes have been made to the entity since you last retrieved it. If a change has been made, the update fails with a WAFOptimisticLockException. If this happens, perform another get, and use the new token returned by that operation.

        • ARN — (String)

          The Amazon Resource Name (ARN) of the entity.

Returns:

  • (AWS.Request) —

    a handle to the operation request for subsequent event callback registration.

createRegexPatternSet(params = {}, callback) ⇒ AWS.Request

Creates a RegexPatternSet, which you reference in a RegexPatternSetReferenceStatement, to have WAF inspect a web request component for the specified patterns.

Service Reference:

Examples:

Calling the createRegexPatternSet operation

var params = {
  Name: 'STRING_VALUE', /* required */
  RegularExpressionList: [ /* required */
    {
      RegexString: 'STRING_VALUE'
    },
    /* more items */
  ],
  Scope: CLOUDFRONT | REGIONAL, /* required */
  Description: 'STRING_VALUE',
  Tags: [
    {
      Key: 'STRING_VALUE', /* required */
      Value: 'STRING_VALUE' /* required */
    },
    /* more items */
  ]
};
wafv2.createRegexPatternSet(params, function(err, data) {
  if (err) console.log(err, err.stack); // an error occurred
  else     console.log(data);           // successful response
});

Parameters:

  • params (Object) (defaults to: {}) —
    • Name — (String)

      The name of the set. You cannot change the name after you create the set.

    • Scope — (String)

      Specifies whether this is for an Amazon CloudFront distribution or for a regional application. A regional application can be an Application Load Balancer (ALB), an Amazon API Gateway REST API, or an AppSync GraphQL API.

      To work with CloudFront, you must also specify the Region US East (N. Virginia) as follows:

      • CLI - Specify the Region when you use the CloudFront scope: --scope=CLOUDFRONT --region=us-east-1.

      • API and SDKs - For all calls, use the Region endpoint us-east-1.

      Possible values include:
      • "CLOUDFRONT"
      • "REGIONAL"
    • Description — (String)

      A description of the set that helps with identification.

    • RegularExpressionList — (Array<map>)

      Array of regular expression strings.

      • RegexString — (String)

        The string representing the regular expression.

    • Tags — (Array<map>)

      An array of key:value pairs to associate with the resource.

      • Key — required — (String)

        Part of the key:value pair that defines a tag. You can use a tag key to describe a category of information, such as "customer." Tag keys are case-sensitive.

      • Value — required — (String)

        Part of the key:value pair that defines a tag. You can use a tag value to describe a specific value within a category, such as "companyA" or "companyB." Tag values are case-sensitive.

Callback (callback):

  • function(err, data) { ... }

    Called when a response from the service is returned. If a callback is not supplied, you must call AWS.Request.send() on the returned request object to initiate the request.

    Context (this):

    • (AWS.Response) —

      the response object containing error, data properties, and the original request object.

    Parameters:

    • err (Error) —

      the error object returned from the request. Set to null if the request is successful.

    • data (Object) —

      the de-serialized data returned from the request. Set to null if a request error occurs. The data object has the following properties:

      • Summary — (map)

        High-level information about a RegexPatternSet, returned by operations like create and list. This provides information like the ID, that you can use to retrieve and manage a RegexPatternSet, and the ARN, that you provide to the RegexPatternSetReferenceStatement to use the pattern set in a Rule.

        • Name — (String)

          The name of the data type instance. You cannot change the name after you create the instance.

        • Id — (String)

          A unique identifier for the set. This ID is returned in the responses to create and list commands. You provide it to operations like update and delete.

        • Description — (String)

          A description of the set that helps with identification.

        • LockToken — (String)

          A token used for optimistic locking. WAF returns a token to your get and list requests, to mark the state of the entity at the time of the request. To make changes to the entity associated with the token, you provide the token to operations like update and delete. WAF uses the token to ensure that no changes have been made to the entity since you last retrieved it. If a change has been made, the update fails with a WAFOptimisticLockException. If this happens, perform another get, and use the new token returned by that operation.

        • ARN — (String)

          The Amazon Resource Name (ARN) of the entity.

Returns:

  • (AWS.Request) —

    a handle to the operation request for subsequent event callback registration.

createRuleGroup(params = {}, callback) ⇒ AWS.Request

Creates a RuleGroup per the specifications provided.

A rule group defines a collection of rules to inspect and control web requests that you can use in a WebACL. When you create a rule group, you define an immutable capacity limit. If you update a rule group, you must stay within the capacity. This allows others to reuse the rule group with confidence in its capacity requirements.

Service Reference:

Examples:

Calling the createRuleGroup operation

var params = {
  Capacity: 'NUMBER_VALUE', /* required */
  Name: 'STRING_VALUE', /* required */
  Scope: CLOUDFRONT | REGIONAL, /* required */
  VisibilityConfig: { /* required */
    CloudWatchMetricsEnabled: true || false, /* required */
    MetricName: 'STRING_VALUE', /* required */
    SampledRequestsEnabled: true || false /* required */
  },
  CustomResponseBodies: {
    '<EntityName>': {
      Content: 'STRING_VALUE', /* required */
      ContentType: TEXT_PLAIN | TEXT_HTML | APPLICATION_JSON /* required */
    },
    /* '<EntityName>': ... */
  },
  Description: 'STRING_VALUE',
  Rules: [
    {
      Name: 'STRING_VALUE', /* required */
      Priority: 'NUMBER_VALUE', /* required */
      Statement: { /* Statement */ /* required */
        AndStatement: {
          Statements: [ /* required */
            /* recursive Statement */,
            /* more items */
          ]
        },
        ByteMatchStatement: {
          FieldToMatch: { /* required */
            AllQueryArguments: {
            },
            Body: {
            },
            JsonBody: {
              MatchPattern: { /* required */
                All: {
                },
                IncludedPaths: [
                  'STRING_VALUE',
                  /* more items */
                ]
              },
              MatchScope: ALL | KEY | VALUE, /* required */
              InvalidFallbackBehavior: MATCH | NO_MATCH | EVALUATE_AS_STRING
            },
            Method: {
            },
            QueryString: {
            },
            SingleHeader: {
              Name: 'STRING_VALUE' /* required */
            },
            SingleQueryArgument: {
              Name: 'STRING_VALUE' /* required */
            },
            UriPath: {
            }
          },
          PositionalConstraint: EXACTLY | STARTS_WITH | ENDS_WITH | CONTAINS | CONTAINS_WORD, /* required */
          SearchString: Buffer.from('...') || 'STRING_VALUE' /* Strings will be Base-64 encoded on your behalf */, /* required */
          TextTransformations: [ /* required */
            {
              Priority: 'NUMBER_VALUE', /* required */
              Type: NONE | COMPRESS_WHITE_SPACE | HTML_ENTITY_DECODE | LOWERCASE | CMD_LINE | URL_DECODE | BASE64_DECODE | HEX_DECODE | MD5 | REPLACE_COMMENTS | ESCAPE_SEQ_DECODE | SQL_HEX_DECODE | CSS_DECODE | JS_DECODE | NORMALIZE_PATH | NORMALIZE_PATH_WIN | REMOVE_NULLS | REPLACE_NULLS | BASE64_DECODE_EXT | URL_DECODE_UNI | UTF8_TO_UNICODE /* required */
            },
            /* more items */
          ]
        },
        GeoMatchStatement: {
          CountryCodes: [
            AF | AX | AL | DZ | AS | AD | AO | AI | AQ | AG | AR | AM | AW | AU | AT | AZ | BS | BH | BD | BB | BY | BE | BZ | BJ | BM | BT | BO | BQ | BA | BW | BV | BR | IO | BN | BG | BF | BI | KH | CM | CA | CV | KY | CF | TD | CL | CN | CX | CC | CO | KM | CG | CD | CK | CR | CI | HR | CU | CW | CY | CZ | DK | DJ | DM | DO | EC | EG | SV | GQ | ER | EE | ET | FK | FO | FJ | FI | FR | GF | PF | TF | GA | GM | GE | DE | GH | GI | GR | GL | GD | GP | GU | GT | GG | GN | GW | GY | HT | HM | VA | HN | HK | HU | IS | IN | ID | IR | IQ | IE | IM | IL | IT | JM | JP | JE | JO | KZ | KE | KI | KP | KR | KW | KG | LA | LV | LB | LS | LR | LY | LI | LT | LU | MO | MK | MG | MW | MY | MV | ML | MT | MH | MQ | MR | MU | YT | MX | FM | MD | MC | MN | ME | MS | MA | MZ | MM | NA | NR | NP | NL | NC | NZ | NI | NE | NG | NU | NF | MP | NO | OM | PK | PW | PS | PA | PG | PY | PE | PH | PN | PL | PT | PR | QA | RE | RO | RU | RW | BL | SH | KN | LC | MF | PM | VC | WS | SM | ST | SA | SN | RS | SC | SL | SG | SX | SK | SI | SB | SO | ZA | GS | SS | ES | LK | SD | SR | SJ | SZ | SE | CH | SY | TW | TJ | TZ | TH | TL | TG | TK | TO | TT | TN | TR | TM | TC | TV | UG | UA | AE | GB | US | UM | UY | UZ | VU | VE | VN | VG | VI | WF | EH | YE | ZM | ZW,
            /* more items */
          ],
          ForwardedIPConfig: {
            FallbackBehavior: MATCH | NO_MATCH, /* required */
            HeaderName: 'STRING_VALUE' /* required */
          }
        },
        IPSetReferenceStatement: {
          ARN: 'STRING_VALUE', /* required */
          IPSetForwardedIPConfig: {
            FallbackBehavior: MATCH | NO_MATCH, /* required */
            HeaderName: 'STRING_VALUE', /* required */
            Position: FIRST | LAST | ANY /* required */
          }
        },
        LabelMatchStatement: {
          Key: 'STRING_VALUE', /* required */
          Scope: LABEL | NAMESPACE /* required */
        },
        ManagedRuleGroupStatement: {
          Name: 'STRING_VALUE', /* required */
          VendorName: 'STRING_VALUE', /* required */
          ExcludedRules: [
            {
              Name: 'STRING_VALUE' /* required */
            },
            /* more items */
          ],
          ScopeDownStatement: /* recursive Statement */,
          Version: 'STRING_VALUE'
        },
        NotStatement: {
          Statement: /* recursive Statement */
        },
        OrStatement: {
          Statements: [ /* required */
            /* recursive Statement */,
            /* more items */
          ]
        },
        RateBasedStatement: {
          AggregateKeyType: IP | FORWARDED_IP, /* required */
          Limit: 'NUMBER_VALUE', /* required */
          ForwardedIPConfig: {
            FallbackBehavior: MATCH | NO_MATCH, /* required */
            HeaderName: 'STRING_VALUE' /* required */
          },
          ScopeDownStatement: /* recursive Statement */
        },
        RegexMatchStatement: {
          FieldToMatch: { /* required */
            AllQueryArguments: {
            },
            Body: {
            },
            JsonBody: {
              MatchPattern: { /* required */
                All: {
                },
                IncludedPaths: [
                  'STRING_VALUE',
                  /* more items */
                ]
              },
              MatchScope: ALL | KEY | VALUE, /* required */
              InvalidFallbackBehavior: MATCH | NO_MATCH | EVALUATE_AS_STRING
            },
            Method: {
            },
            QueryString: {
            },
            SingleHeader: {
              Name: 'STRING_VALUE' /* required */
            },
            SingleQueryArgument: {
              Name: 'STRING_VALUE' /* required */
            },
            UriPath: {
            }
          },
          RegexString: 'STRING_VALUE', /* required */
          TextTransformations: [ /* required */
            {
              Priority: 'NUMBER_VALUE', /* required */
              Type: NONE | COMPRESS_WHITE_SPACE | HTML_ENTITY_DECODE | LOWERCASE | CMD_LINE | URL_DECODE | BASE64_DECODE | HEX_DECODE | MD5 | REPLACE_COMMENTS | ESCAPE_SEQ_DECODE | SQL_HEX_DECODE | CSS_DECODE | JS_DECODE | NORMALIZE_PATH | NORMALIZE_PATH_WIN | REMOVE_NULLS | REPLACE_NULLS | BASE64_DECODE_EXT | URL_DECODE_UNI | UTF8_TO_UNICODE /* required */
            },
            /* more items */
          ]
        },
        RegexPatternSetReferenceStatement: {
          ARN: 'STRING_VALUE', /* required */
          FieldToMatch: { /* required */
            AllQueryArguments: {
            },
            Body: {
            },
            JsonBody: {
              MatchPattern: { /* required */
                All: {
                },
                IncludedPaths: [
                  'STRING_VALUE',
                  /* more items */
                ]
              },
              MatchScope: ALL | KEY | VALUE, /* required */
              InvalidFallbackBehavior: MATCH | NO_MATCH | EVALUATE_AS_STRING
            },
            Method: {
            },
            QueryString: {
            },
            SingleHeader: {
              Name: 'STRING_VALUE' /* required */
            },
            SingleQueryArgument: {
              Name: 'STRING_VALUE' /* required */
            },
            UriPath: {
            }
          },
          TextTransformations: [ /* required */
            {
              Priority: 'NUMBER_VALUE', /* required */
              Type: NONE | COMPRESS_WHITE_SPACE | HTML_ENTITY_DECODE | LOWERCASE | CMD_LINE | URL_DECODE | BASE64_DECODE | HEX_DECODE | MD5 | REPLACE_COMMENTS | ESCAPE_SEQ_DECODE | SQL_HEX_DECODE | CSS_DECODE | JS_DECODE | NORMALIZE_PATH | NORMALIZE_PATH_WIN | REMOVE_NULLS | REPLACE_NULLS | BASE64_DECODE_EXT | URL_DECODE_UNI | UTF8_TO_UNICODE /* required */
            },
            /* more items */
          ]
        },
        RuleGroupReferenceStatement: {
          ARN: 'STRING_VALUE', /* required */
          ExcludedRules: [
            {
              Name: 'STRING_VALUE' /* required */
            },
            /* more items */
          ]
        },
        SizeConstraintStatement: {
          ComparisonOperator: EQ | NE | LE | LT | GE | GT, /* required */
          FieldToMatch: { /* required */
            AllQueryArguments: {
            },
            Body: {
            },
            JsonBody: {
              MatchPattern: { /* required */
                All: {
                },
                IncludedPaths: [
                  'STRING_VALUE',
                  /* more items */
                ]
              },
              MatchScope: ALL | KEY | VALUE, /* required */
              InvalidFallbackBehavior: MATCH | NO_MATCH | EVALUATE_AS_STRING
            },
            Method: {
            },
            QueryString: {
            },
            SingleHeader: {
              Name: 'STRING_VALUE' /* required */
            },
            SingleQueryArgument: {
              Name: 'STRING_VALUE' /* required */
            },
            UriPath: {
            }
          },
          Size: 'NUMBER_VALUE', /* required */
          TextTransformations: [ /* required */
            {
              Priority: 'NUMBER_VALUE', /* required */
              Type: NONE | COMPRESS_WHITE_SPACE | HTML_ENTITY_DECODE | LOWERCASE | CMD_LINE | URL_DECODE | BASE64_DECODE | HEX_DECODE | MD5 | REPLACE_COMMENTS | ESCAPE_SEQ_DECODE | SQL_HEX_DECODE | CSS_DECODE | JS_DECODE | NORMALIZE_PATH | NORMALIZE_PATH_WIN | REMOVE_NULLS | REPLACE_NULLS | BASE64_DECODE_EXT | URL_DECODE_UNI | UTF8_TO_UNICODE /* required */
            },
            /* more items */
          ]
        },
        SqliMatchStatement: {
          FieldToMatch: { /* required */
            AllQueryArguments: {
            },
            Body: {
            },
            JsonBody: {
              MatchPattern: { /* required */
                All: {
                },
                IncludedPaths: [
                  'STRING_VALUE',
                  /* more items */
                ]
              },
              MatchScope: ALL | KEY | VALUE, /* required */
              InvalidFallbackBehavior: MATCH | NO_MATCH | EVALUATE_AS_STRING
            },
            Method: {
            },
            QueryString: {
            },
            SingleHeader: {
              Name: 'STRING_VALUE' /* required */
            },
            SingleQueryArgument: {
              Name: 'STRING_VALUE' /* required */
            },
            UriPath: {
            }
          },
          TextTransformations: [ /* required */
            {
              Priority: 'NUMBER_VALUE', /* required */
              Type: NONE | COMPRESS_WHITE_SPACE | HTML_ENTITY_DECODE | LOWERCASE | CMD_LINE | URL_DECODE | BASE64_DECODE | HEX_DECODE | MD5 | REPLACE_COMMENTS | ESCAPE_SEQ_DECODE | SQL_HEX_DECODE | CSS_DECODE | JS_DECODE | NORMALIZE_PATH | NORMALIZE_PATH_WIN | REMOVE_NULLS | REPLACE_NULLS | BASE64_DECODE_EXT | URL_DECODE_UNI | UTF8_TO_UNICODE /* required */
            },
            /* more items */
          ]
        },
        XssMatchStatement: {
          FieldToMatch: { /* required */
            AllQueryArguments: {
            },
            Body: {
            },
            JsonBody: {
              MatchPattern: { /* required */
                All: {
                },
                IncludedPaths: [
                  'STRING_VALUE',
                  /* more items */
                ]
              },
              MatchScope: ALL | KEY | VALUE, /* required */
              InvalidFallbackBehavior: MATCH | NO_MATCH | EVALUATE_AS_STRING
            },
            Method: {
            },
            QueryString: {
            },
            SingleHeader: {
              Name: 'STRING_VALUE' /* required */
            },
            SingleQueryArgument: {
              Name: 'STRING_VALUE' /* required */
            },
            UriPath: {
            }
          },
          TextTransformations: [ /* required */
            {
              Priority: 'NUMBER_VALUE', /* required */
              Type: NONE | COMPRESS_WHITE_SPACE | HTML_ENTITY_DECODE | LOWERCASE | CMD_LINE | URL_DECODE | BASE64_DECODE | HEX_DECODE | MD5 | REPLACE_COMMENTS | ESCAPE_SEQ_DECODE | SQL_HEX_DECODE | CSS_DECODE | JS_DECODE | NORMALIZE_PATH | NORMALIZE_PATH_WIN | REMOVE_NULLS | REPLACE_NULLS | BASE64_DECODE_EXT | URL_DECODE_UNI | UTF8_TO_UNICODE /* required */
            },
            /* more items */
          ]
        }
      },
      VisibilityConfig: { /* required */
        CloudWatchMetricsEnabled: true || false, /* required */
        MetricName: 'STRING_VALUE', /* required */
        SampledRequestsEnabled: true || false /* required */
      },
      Action: {
        Allow: {
          CustomRequestHandling: {
            InsertHeaders: [ /* required */
              {
                Name: 'STRING_VALUE', /* required */
                Value: 'STRING_VALUE' /* required */
              },
              /* more items */
            ]
          }
        },
        Block: {
          CustomResponse: {
            ResponseCode: 'NUMBER_VALUE', /* required */
            CustomResponseBodyKey: 'STRING_VALUE',
            ResponseHeaders: [
              {
                Name: 'STRING_VALUE', /* required */
                Value: 'STRING_VALUE' /* required */
              },
              /* more items */
            ]
          }
        },
        Captcha: {
          CustomRequestHandling: {
            InsertHeaders: [ /* required */
              {
                Name: 'STRING_VALUE', /* required */
                Value: 'STRING_VALUE' /* required */
              },
              /* more items */
            ]
          }
        },
        Count: {
          CustomRequestHandling: {
            InsertHeaders: [ /* required */
              {
                Name: 'STRING_VALUE', /* required */
                Value: 'STRING_VALUE' /* required */
              },
              /* more items */
            ]
          }
        }
      },
      CaptchaConfig: {
        ImmunityTimeProperty: {
          ImmunityTime: 'NUMBER_VALUE' /* required */
        }
      },
      OverrideAction: {
        Count: {
          CustomRequestHandling: {
            InsertHeaders: [ /* required */
              {
                Name: 'STRING_VALUE', /* required */
                Value: 'STRING_VALUE' /* required */
              },
              /* more items */
            ]
          }
        },
        None: {
        }
      },
      RuleLabels: [
        {
          Name: 'STRING_VALUE' /* required */
        },
        /* more items */
      ]
    },
    /* more items */
  ],
  Tags: [
    {
      Key: 'STRING_VALUE', /* required */
      Value: 'STRING_VALUE' /* required */
    },
    /* more items */
  ]
};
wafv2.createRuleGroup(params, function(err, data) {
  if (err) console.log(err, err.stack); // an error occurred
  else     console.log(data);           // successful response
});

Parameters:

  • params (Object) (defaults to: {}) —
    • Name — (String)

      The name of the rule group. You cannot change the name of a rule group after you create it.

    • Scope — (String)

      Specifies whether this is for an Amazon CloudFront distribution or for a regional application. A regional application can be an Application Load Balancer (ALB), an Amazon API Gateway REST API, or an AppSync GraphQL API.

      To work with CloudFront, you must also specify the Region US East (N. Virginia) as follows:

      • CLI - Specify the Region when you use the CloudFront scope: --scope=CLOUDFRONT --region=us-east-1.

      • API and SDKs - For all calls, use the Region endpoint us-east-1.

      Possible values include:
      • "CLOUDFRONT"
      • "REGIONAL"
    • Capacity — (Integer)

      The web ACL capacity units (WCUs) required for this rule group.

      When you create your own rule group, you define this, and you cannot change it after creation. When you add or modify the rules in a rule group, WAF enforces this limit. You can check the capacity for a set of rules using CheckCapacity.

      WAF uses WCUs to calculate and control the operating resources that are used to run your rules, rule groups, and web ACLs. WAF calculates capacity differently for each rule type, to reflect the relative cost of each rule. Simple rules that cost little to run use fewer WCUs than more complex rules that use more processing power. Rule group capacity is fixed at creation, which helps users plan their web ACL WCU usage when they use a rule group. The WCU limit for web ACLs is 1,500.

    • Description — (String)

      A description of the rule group that helps with identification.

    • Rules — (Array<map>)

      The Rule statements used to identify the web requests that you want to allow, block, or count. Each rule includes one top-level statement that WAF uses to identify matching web requests, and parameters that govern how WAF handles them.

      • Name — required — (String)

        The name of the rule. You can't change the name of a Rule after you create it.

      • Priority — required — (Integer)

        If you define more than one Rule in a WebACL, WAF evaluates each request against the Rules in order based on the value of Priority. WAF processes rules with lower priority first. The priorities don't need to be consecutive, but they must all be different.

      • Statement — required — (map)

        The WAF processing statement for the rule, for example ByteMatchStatement or SizeConstraintStatement.

        • ByteMatchStatement — (map)

          A rule statement that defines a string match search for WAF to apply to web requests. The byte match statement provides the bytes to search for, the location in requests that you want WAF to search, and other settings. The bytes to search for are typically a string that corresponds with ASCII characters. In the WAF console and the developer guide, this is refered to as a string match statement.

          • SearchString — required — (Buffer, Typed Array, Blob, String)

            A string value that you want WAF to search for. WAF searches only in the part of web requests that you designate for inspection in FieldToMatch. The maximum length of the value is 50 bytes.

            Valid values depend on the component that you specify for inspection in FieldToMatch:

            • Method: The HTTP method that you want WAF to search for. This indicates the type of operation specified in the request.

            • UriPath: The value that you want WAF to search for in the URI path, for example, /images/daily-ad.jpg.

            If SearchString includes alphabetic characters A-Z and a-z, note that the value is case sensitive.

            If you're using the WAF API

            Specify a base64-encoded version of the value. The maximum length of the value before you base64-encode it is 50 bytes.

            For example, suppose the value of Type is HEADER and the value of Data is User-Agent. If you want to search the User-Agent header for the value BadBot, you base64-encode BadBot using MIME base64-encoding and include the resulting value, QmFkQm90, in the value of SearchString.

            If you're using the CLI or one of the Amazon Web Services SDKs

            The value that you want WAF to search for. The SDK automatically base64 encodes the value.

          • FieldToMatch — required — (map)

            The part of a web request that you want WAF to inspect. For more information, see FieldToMatch.

            • SingleHeader — (map)

              Inspect a single header. Provide the name of the header to inspect, for example, User-Agent or Referer. This setting isn't case sensitive.

              Example JSON: "SingleHeader": { "Name": "haystack" }

              • Name — required — (String)

                The name of the query header to inspect.

            • SingleQueryArgument — (map)

              Inspect a single query argument. Provide the name of the query argument to inspect, such as UserName or SalesRegion. The name can be up to 30 characters long and isn't case sensitive.

              This is used only to indicate the web request component for WAF to inspect, in the FieldToMatch specification.

              Example JSON: "SingleQueryArgument": { "Name": "myArgument" }

              • Name — required — (String)

                The name of the query argument to inspect.

            • AllQueryArguments — (map)

              Inspect all query arguments.

            • UriPath — (map)

              Inspect the request URI path. This is the part of a web request that identifies a resource, for example, /images/daily-ad.jpg.

            • QueryString — (map)

              Inspect the query string. This is the part of a URL that appears after a ? character, if any.

            • Body — (map)

              Inspect the request body as plain text. The request body immediately follows the request headers. This is the part of a request that contains any additional data that you want to send to your web server as the HTTP request body, such as data from a form.

              Note that only the first 8 KB (8192 bytes) of the request body are forwarded to WAF for inspection by the underlying host service. If you don't need to inspect more than 8 KB, you can guarantee that you don't allow additional bytes in by combining a statement that inspects the body of the web request, such as ByteMatchStatement or RegexPatternSetReferenceStatement, with a SizeConstraintStatement that enforces an 8 KB size limit on the body of the request. WAF doesn't support inspecting the entire contents of web requests whose bodies exceed the 8 KB limit.

            • Method — (map)

              Inspect the HTTP method. The method indicates the type of operation that the request is asking the origin to perform.

            • JsonBody — (map)

              Inspect the request body as JSON. The request body immediately follows the request headers. This is the part of a request that contains any additional data that you want to send to your web server as the HTTP request body, such as data from a form.

              Note that only the first 8 KB (8192 bytes) of the request body are forwarded to WAF for inspection by the underlying host service. If you don't need to inspect more than 8 KB, you can guarantee that you don't allow additional bytes in by combining a statement that inspects the body of the web request, such as ByteMatchStatement or RegexPatternSetReferenceStatement, with a SizeConstraintStatement that enforces an 8 KB size limit on the body of the request. WAF doesn't support inspecting the entire contents of web requests whose bodies exceed the 8 KB limit.

              • MatchPattern — required — (map)

                The patterns to look for in the JSON body. WAF inspects the results of these pattern matches against the rule inspection criteria.

                • All — (map)

                  Match all of the elements. See also MatchScope in JsonBody.

                  You must specify either this setting or the IncludedPaths setting, but not both.

                • IncludedPaths — (Array<String>)

                  Match only the specified include paths. See also MatchScope in JsonBody.

                  Provide the include paths using JSON Pointer syntax. For example, "IncludedPaths": ["/dogs/0/name", "/dogs/1/name"]. For information about this syntax, see the Internet Engineering Task Force (IETF) documentation JavaScript Object Notation (JSON) Pointer.

                  You must specify either this setting or the All setting, but not both.

                  Note: Don't use this option to include all paths. Instead, use the All setting.
              • MatchScope — required — (String)

                The parts of the JSON to match against using the MatchPattern. If you specify All, WAF matches against keys and values.

                Possible values include:
                • "ALL"
                • "KEY"
                • "VALUE"
              • InvalidFallbackBehavior — (String)

                What WAF should do if it fails to completely parse the JSON body. The options are the following:

                • EVALUATE_AS_STRING - Inspect the body as plain text. WAF applies the text transformations and inspection criteria that you defined for the JSON inspection to the body text string.

                • MATCH - Treat the web request as matching the rule statement. WAF applies the rule action to the request.

                • NO_MATCH - Treat the web request as not matching the rule statement.

                If you don't provide this setting, WAF parses and evaluates the content only up to the first parsing failure that it encounters.

                WAF does its best to parse the entire JSON body, but might be forced to stop for reasons such as invalid characters, duplicate keys, truncation, and any content whose root node isn't an object or an array.

                WAF parses the JSON in the following examples as two valid key, value pairs:

                • Missing comma: {"key1":"value1""key2":"value2"}

                • Missing colon: {"key1":"value1","key2""value2"}

                • Extra colons: {"key1"::"value1","key2""value2"}

                Possible values include:
                • "MATCH"
                • "NO_MATCH"
                • "EVALUATE_AS_STRING"
          • TextTransformations — required — (Array<map>)

            Text transformations eliminate some of the unusual formatting that attackers use in web requests in an effort to bypass detection. If you specify one or more transformations in a rule statement, WAF performs all transformations on the content of the request component identified by FieldToMatch, starting from the lowest priority setting, before inspecting the content for a match.

            • Priority — required — (Integer)

              Sets the relative processing order for multiple transformations that are defined for a rule statement. WAF processes all transformations, from lowest priority to highest, before inspecting the transformed content. The priorities don't need to be consecutive, but they must all be different.

            • Type — required — (String)

              You can specify the following transformation types:

              BASE64_DECODE - Decode a Base64-encoded string.

              BASE64_DECODE_EXT - Decode a Base64-encoded string, but use a forgiving implementation that ignores characters that aren't valid.

              CMD_LINE - Command-line transformations. These are helpful in reducing effectiveness of attackers who inject an operating system command-line command and use unusual formatting to disguise some or all of the command.

              • Delete the following characters: \ " ' ^

              • Delete spaces before the following characters: / (

              • Replace the following characters with a space: , ;

              • Replace multiple spaces with one space

              • Convert uppercase letters (A-Z) to lowercase (a-z)

              COMPRESS_WHITE_SPACE - Replace these characters with a space character (decimal 32):

              • \f, formfeed, decimal 12

              • \t, tab, decimal 9

              • \n, newline, decimal 10

              • \r, carriage return, decimal 13

              • \v, vertical tab, decimal 11

              • Non-breaking space, decimal 160

              COMPRESS_WHITE_SPACE also replaces multiple spaces with one space.

              CSS_DECODE - Decode characters that were encoded using CSS 2.x escape rules syndata.html#characters. This function uses up to two bytes in the decoding process, so it can help to uncover ASCII characters that were encoded using CSS encoding that wouldn’t typically be encoded. It's also useful in countering evasion, which is a combination of a backslash and non-hexadecimal characters. For example, ja\vascript for javascript.

              ESCAPE_SEQ_DECODE - Decode the following ANSI C escape sequences: \a, \b, \f, \n, \r, \t, \v, \, \?, \', \", \xHH (hexadecimal), \0OOO (octal). Encodings that aren't valid remain in the output.

              HEX_DECODE - Decode a string of hexadecimal characters into a binary.

              HTML_ENTITY_DECODE - Replace HTML-encoded characters with unencoded characters. HTML_ENTITY_DECODE performs these operations:

              • Replaces (ampersand)quot; with "

              • Replaces (ampersand)nbsp; with a non-breaking space, decimal 160

              • Replaces (ampersand)lt; with a "less than" symbol

              • Replaces (ampersand)gt; with >

              • Replaces characters that are represented in hexadecimal format, (ampersand)#xhhhh;, with the corresponding characters

              • Replaces characters that are represented in decimal format, (ampersand)#nnnn;, with the corresponding characters

              JS_DECODE - Decode JavaScript escape sequences. If a \ u HHHH code is in the full-width ASCII code range of FF01-FF5E, then the higher byte is used to detect and adjust the lower byte. If not, only the lower byte is used and the higher byte is zeroed, causing a possible loss of information.

              LOWERCASE - Convert uppercase letters (A-Z) to lowercase (a-z).

              MD5 - Calculate an MD5 hash from the data in the input. The computed hash is in a raw binary form.

              NONE - Specify NONE if you don't want any text transformations.

              NORMALIZE_PATH - Remove multiple slashes, directory self-references, and directory back-references that are not at the beginning of the input from an input string.

              NORMALIZE_PATH_WIN - This is the same as NORMALIZE_PATH, but first converts backslash characters to forward slashes.

              REMOVE_NULLS - Remove all NULL bytes from the input.

              REPLACE_COMMENTS - Replace each occurrence of a C-style comment (/* ... */) with a single space. Multiple consecutive occurrences are not compressed. Unterminated comments are also replaced with a space (ASCII 0x20). However, a standalone termination of a comment (*/) is not acted upon.

              REPLACE_NULLS - Replace NULL bytes in the input with space characters (ASCII 0x20).

              SQL_HEX_DECODE - Decode SQL hex data. Example (0x414243) will be decoded to (ABC).

              URL_DECODE - Decode a URL-encoded value.

              URL_DECODE_UNI - Like URL_DECODE, but with support for Microsoft-specific %u encoding. If the code is in the full-width ASCII code range of FF01-FF5E, the higher byte is used to detect and adjust the lower byte. Otherwise, only the lower byte is used and the higher byte is zeroed.

              UTF8_TO_UNICODE - Convert all UTF-8 character sequences to Unicode. This helps input normalization, and minimizing false-positives and false-negatives for non-English languages.

              Possible values include:
              • "NONE"
              • "COMPRESS_WHITE_SPACE"
              • "HTML_ENTITY_DECODE"
              • "LOWERCASE"
              • "CMD_LINE"
              • "URL_DECODE"
              • "BASE64_DECODE"
              • "HEX_DECODE"
              • "MD5"
              • "REPLACE_COMMENTS"
              • "ESCAPE_SEQ_DECODE"
              • "SQL_HEX_DECODE"
              • "CSS_DECODE"
              • "JS_DECODE"
              • "NORMALIZE_PATH"
              • "NORMALIZE_PATH_WIN"
              • "REMOVE_NULLS"
              • "REPLACE_NULLS"
              • "BASE64_DECODE_EXT"
              • "URL_DECODE_UNI"
              • "UTF8_TO_UNICODE"
          • PositionalConstraint — required — (String)

            The area within the portion of a web request that you want WAF to search for SearchString. Valid values include the following:

            CONTAINS

            The specified part of the web request must include the value of SearchString, but the location doesn't matter.

            CONTAINS_WORD

            The specified part of the web request must include the value of SearchString, and SearchString must contain only alphanumeric characters or underscore (A-Z, a-z, 0-9, or ). In addition, SearchString must be a word, which means that both of the following are true:

            • SearchString is at the beginning of the specified part of the web request or is preceded by a character other than an alphanumeric character or underscore (). Examples include the value of a header and ;BadBot.

            • SearchString is at the end of the specified part of the web request or is followed by a character other than an alphanumeric character or underscore (_), for example, BadBot; and -BadBot;.

            EXACTLY

            The value of the specified part of the web request must exactly match the value of SearchString.

            STARTS_WITH

            The value of SearchString must appear at the beginning of the specified part of the web request.

            ENDS_WITH

            The value of SearchString must appear at the end of the specified part of the web request.

            Possible values include:
            • "EXACTLY"
            • "STARTS_WITH"
            • "ENDS_WITH"
            • "CONTAINS"
            • "CONTAINS_WORD"
        • SqliMatchStatement — (map)

          Attackers sometimes insert malicious SQL code into web requests in an effort to extract data from your database. To allow or block web requests that appear to contain malicious SQL code, create one or more SQL injection match conditions. An SQL injection match condition identifies the part of web requests, such as the URI or the query string, that you want WAF to inspect. Later in the process, when you create a web ACL, you specify whether to allow or block requests that appear to contain malicious SQL code.

          • FieldToMatch — required — (map)

            The part of a web request that you want WAF to inspect. For more information, see FieldToMatch.

            • SingleHeader — (map)

              Inspect a single header. Provide the name of the header to inspect, for example, User-Agent or Referer. This setting isn't case sensitive.

              Example JSON: "SingleHeader": { "Name": "haystack" }

              • Name — required — (String)

                The name of the query header to inspect.

            • SingleQueryArgument — (map)

              Inspect a single query argument. Provide the name of the query argument to inspect, such as UserName or SalesRegion. The name can be up to 30 characters long and isn't case sensitive.

              This is used only to indicate the web request component for WAF to inspect, in the FieldToMatch specification.

              Example JSON: "SingleQueryArgument": { "Name": "myArgument" }

              • Name — required — (String)

                The name of the query argument to inspect.

            • AllQueryArguments — (map)

              Inspect all query arguments.

            • UriPath — (map)

              Inspect the request URI path. This is the part of a web request that identifies a resource, for example, /images/daily-ad.jpg.

            • QueryString — (map)

              Inspect the query string. This is the part of a URL that appears after a ? character, if any.

            • Body — (map)

              Inspect the request body as plain text. The request body immediately follows the request headers. This is the part of a request that contains any additional data that you want to send to your web server as the HTTP request body, such as data from a form.

              Note that only the first 8 KB (8192 bytes) of the request body are forwarded to WAF for inspection by the underlying host service. If you don't need to inspect more than 8 KB, you can guarantee that you don't allow additional bytes in by combining a statement that inspects the body of the web request, such as ByteMatchStatement or RegexPatternSetReferenceStatement, with a SizeConstraintStatement that enforces an 8 KB size limit on the body of the request. WAF doesn't support inspecting the entire contents of web requests whose bodies exceed the 8 KB limit.

            • Method — (map)

              Inspect the HTTP method. The method indicates the type of operation that the request is asking the origin to perform.

            • JsonBody — (map)

              Inspect the request body as JSON. The request body immediately follows the request headers. This is the part of a request that contains any additional data that you want to send to your web server as the HTTP request body, such as data from a form.

              Note that only the first 8 KB (8192 bytes) of the request body are forwarded to WAF for inspection by the underlying host service. If you don't need to inspect more than 8 KB, you can guarantee that you don't allow additional bytes in by combining a statement that inspects the body of the web request, such as ByteMatchStatement or RegexPatternSetReferenceStatement, with a SizeConstraintStatement that enforces an 8 KB size limit on the body of the request. WAF doesn't support inspecting the entire contents of web requests whose bodies exceed the 8 KB limit.

              • MatchPattern — required — (map)

                The patterns to look for in the JSON body. WAF inspects the results of these pattern matches against the rule inspection criteria.

                • All — (map)

                  Match all of the elements. See also MatchScope in JsonBody.

                  You must specify either this setting or the IncludedPaths setting, but not both.

                • IncludedPaths — (Array<String>)

                  Match only the specified include paths. See also MatchScope in JsonBody.

                  Provide the include paths using JSON Pointer syntax. For example, "IncludedPaths": ["/dogs/0/name", "/dogs/1/name"]. For information about this syntax, see the Internet Engineering Task Force (IETF) documentation JavaScript Object Notation (JSON) Pointer.

                  You must specify either this setting or the All setting, but not both.

                  Note: Don't use this option to include all paths. Instead, use the All setting.
              • MatchScope — required — (String)

                The parts of the JSON to match against using the MatchPattern. If you specify All, WAF matches against keys and values.

                Possible values include:
                • "ALL"
                • "KEY"
                • "VALUE"
              • InvalidFallbackBehavior — (String)

                What WAF should do if it fails to completely parse the JSON body. The options are the following:

                • EVALUATE_AS_STRING - Inspect the body as plain text. WAF applies the text transformations and inspection criteria that you defined for the JSON inspection to the body text string.

                • MATCH - Treat the web request as matching the rule statement. WAF applies the rule action to the request.

                • NO_MATCH - Treat the web request as not matching the rule statement.

                If you don't provide this setting, WAF parses and evaluates the content only up to the first parsing failure that it encounters.

                WAF does its best to parse the entire JSON body, but might be forced to stop for reasons such as invalid characters, duplicate keys, truncation, and any content whose root node isn't an object or an array.

                WAF parses the JSON in the following examples as two valid key, value pairs:

                • Missing comma: {"key1":"value1""key2":"value2"}

                • Missing colon: {"key1":"value1","key2""value2"}

                • Extra colons: {"key1"::"value1","key2""value2"}

                Possible values include:
                • "MATCH"
                • "NO_MATCH"
                • "EVALUATE_AS_STRING"
          • TextTransformations — required — (Array<map>)

            Text transformations eliminate some of the unusual formatting that attackers use in web requests in an effort to bypass detection. If you specify one or more transformations in a rule statement, WAF performs all transformations on the content of the request component identified by FieldToMatch, starting from the lowest priority setting, before inspecting the content for a match.

            • Priority — required — (Integer)

              Sets the relative processing order for multiple transformations that are defined for a rule statement. WAF processes all transformations, from lowest priority to highest, before inspecting the transformed content. The priorities don't need to be consecutive, but they must all be different.

            • Type — required — (String)

              You can specify the following transformation types:

              BASE64_DECODE - Decode a Base64-encoded string.

              BASE64_DECODE_EXT - Decode a Base64-encoded string, but use a forgiving implementation that ignores characters that aren't valid.

              CMD_LINE - Command-line transformations. These are helpful in reducing effectiveness of attackers who inject an operating system command-line command and use unusual formatting to disguise some or all of the command.

              • Delete the following characters: \ " ' ^

              • Delete spaces before the following characters: / (

              • Replace the following characters with a space: , ;

              • Replace multiple spaces with one space

              • Convert uppercase letters (A-Z) to lowercase (a-z)

              COMPRESS_WHITE_SPACE - Replace these characters with a space character (decimal 32):

              • \f, formfeed, decimal 12

              • \t, tab, decimal 9

              • \n, newline, decimal 10

              • \r, carriage return, decimal 13

              • \v, vertical tab, decimal 11

              • Non-breaking space, decimal 160

              COMPRESS_WHITE_SPACE also replaces multiple spaces with one space.

              CSS_DECODE - Decode characters that were encoded using CSS 2.x escape rules syndata.html#characters. This function uses up to two bytes in the decoding process, so it can help to uncover ASCII characters that were encoded using CSS encoding that wouldn’t typically be encoded. It's also useful in countering evasion, which is a combination of a backslash and non-hexadecimal characters. For example, ja\vascript for javascript.

              ESCAPE_SEQ_DECODE - Decode the following ANSI C escape sequences: \a, \b, \f, \n, \r, \t, \v, \, \?, \', \", \xHH (hexadecimal), \0OOO (octal). Encodings that aren't valid remain in the output.

              HEX_DECODE - Decode a string of hexadecimal characters into a binary.

              HTML_ENTITY_DECODE - Replace HTML-encoded characters with unencoded characters. HTML_ENTITY_DECODE performs these operations:

              • Replaces (ampersand)quot; with "

              • Replaces (ampersand)nbsp; with a non-breaking space, decimal 160

              • Replaces (ampersand)lt; with a "less than" symbol

              • Replaces (ampersand)gt; with >

              • Replaces characters that are represented in hexadecimal format, (ampersand)#xhhhh;, with the corresponding characters

              • Replaces characters that are represented in decimal format, (ampersand)#nnnn;, with the corresponding characters

              JS_DECODE - Decode JavaScript escape sequences. If a \ u HHHH code is in the full-width ASCII code range of FF01-FF5E, then the higher byte is used to detect and adjust the lower byte. If not, only the lower byte is used and the higher byte is zeroed, causing a possible loss of information.

              LOWERCASE - Convert uppercase letters (A-Z) to lowercase (a-z).

              MD5 - Calculate an MD5 hash from the data in the input. The computed hash is in a raw binary form.

              NONE - Specify NONE if you don't want any text transformations.

              NORMALIZE_PATH - Remove multiple slashes, directory self-references, and directory back-references that are not at the beginning of the input from an input string.

              NORMALIZE_PATH_WIN - This is the same as NORMALIZE_PATH, but first converts backslash characters to forward slashes.

              REMOVE_NULLS - Remove all NULL bytes from the input.

              REPLACE_COMMENTS - Replace each occurrence of a C-style comment (/* ... */) with a single space. Multiple consecutive occurrences are not compressed. Unterminated comments are also replaced with a space (ASCII 0x20). However, a standalone termination of a comment (*/) is not acted upon.

              REPLACE_NULLS - Replace NULL bytes in the input with space characters (ASCII 0x20).

              SQL_HEX_DECODE - Decode SQL hex data. Example (0x414243) will be decoded to (ABC).

              URL_DECODE - Decode a URL-encoded value.

              URL_DECODE_UNI - Like URL_DECODE, but with support for Microsoft-specific %u encoding. If the code is in the full-width ASCII code range of FF01-FF5E, the higher byte is used to detect and adjust the lower byte. Otherwise, only the lower byte is used and the higher byte is zeroed.

              UTF8_TO_UNICODE - Convert all UTF-8 character sequences to Unicode. This helps input normalization, and minimizing false-positives and false-negatives for non-English languages.

              Possible values include:
              • "NONE"
              • "COMPRESS_WHITE_SPACE"
              • "HTML_ENTITY_DECODE"
              • "LOWERCASE"
              • "CMD_LINE"
              • "URL_DECODE"
              • "BASE64_DECODE"
              • "HEX_DECODE"
              • "MD5"
              • "REPLACE_COMMENTS"
              • "ESCAPE_SEQ_DECODE"
              • "SQL_HEX_DECODE"
              • "CSS_DECODE"
              • "JS_DECODE"
              • "NORMALIZE_PATH"
              • "NORMALIZE_PATH_WIN"
              • "REMOVE_NULLS"
              • "REPLACE_NULLS"
              • "BASE64_DECODE_EXT"
              • "URL_DECODE_UNI"
              • "UTF8_TO_UNICODE"
        • XssMatchStatement — (map)

          A rule statement that defines a cross-site scripting (XSS) match search for WAF to apply to web requests. XSS attacks are those where the attacker uses vulnerabilities in a benign website as a vehicle to inject malicious client-site scripts into other legitimate web browsers. The XSS match statement provides the location in requests that you want WAF to search and text transformations to use on the search area before WAF searches for character sequences that are likely to be malicious strings.

          • FieldToMatch — required — (map)

            The part of a web request that you want WAF to inspect. For more information, see FieldToMatch.

            • SingleHeader — (map)

              Inspect a single header. Provide the name of the header to inspect, for example, User-Agent or Referer. This setting isn't case sensitive.

              Example JSON: "SingleHeader": { "Name": "haystack" }

              • Name — required — (String)

                The name of the query header to inspect.

            • SingleQueryArgument — (map)

              Inspect a single query argument. Provide the name of the query argument to inspect, such as UserName or SalesRegion. The name can be up to 30 characters long and isn't case sensitive.

              This is used only to indicate the web request component for WAF to inspect, in the FieldToMatch specification.

              Example JSON: "SingleQueryArgument": { "Name": "myArgument" }

              • Name — required — (String)

                The name of the query argument to inspect.

            • AllQueryArguments — (map)

              Inspect all query arguments.

            • UriPath — (map)

              Inspect the request URI path. This is the part of a web request that identifies a resource, for example, /images/daily-ad.jpg.

            • QueryString — (map)

              Inspect the query string. This is the part of a URL that appears after a ? character, if any.

            • Body — (map)

              Inspect the request body as plain text. The request body immediately follows the request headers. This is the part of a request that contains any additional data that you want to send to your web server as the HTTP request body, such as data from a form.

              Note that only the first 8 KB (8192 bytes) of the request body are forwarded to WAF for inspection by the underlying host service. If you don't need to inspect more than 8 KB, you can guarantee that you don't allow additional bytes in by combining a statement that inspects the body of the web request, such as ByteMatchStatement or RegexPatternSetReferenceStatement, with a SizeConstraintStatement that enforces an 8 KB size limit on the body of the request. WAF doesn't support inspecting the entire contents of web requests whose bodies exceed the 8 KB limit.

            • Method — (map)

              Inspect the HTTP method. The method indicates the type of operation that the request is asking the origin to perform.

            • JsonBody — (map)

              Inspect the request body as JSON. The request body immediately follows the request headers. This is the part of a request that contains any additional data that you want to send to your web server as the HTTP request body, such as data from a form.

              Note that only the first 8 KB (8192 bytes) of the request body are forwarded to WAF for inspection by the underlying host service. If you don't need to inspect more than 8 KB, you can guarantee that you don't allow additional bytes in by combining a statement that inspects the body of the web request, such as ByteMatchStatement or RegexPatternSetReferenceStatement, with a SizeConstraintStatement that enforces an 8 KB size limit on the body of the request. WAF doesn't support inspecting the entire contents of web requests whose bodies exceed the 8 KB limit.

              • MatchPattern — required — (map)

                The patterns to look for in the JSON body. WAF inspects the results of these pattern matches against the rule inspection criteria.

                • All — (map)

                  Match all of the elements. See also MatchScope in JsonBody.

                  You must specify either this setting or the IncludedPaths setting, but not both.

                • IncludedPaths — (Array<String>)

                  Match only the specified include paths. See also MatchScope in JsonBody.

                  Provide the include paths using JSON Pointer syntax. For example, "IncludedPaths": ["/dogs/0/name", "/dogs/1/name"]. For information about this syntax, see the Internet Engineering Task Force (IETF) documentation JavaScript Object Notation (JSON) Pointer.

                  You must specify either this setting or the All setting, but not both.

                  Note: Don't use this option to include all paths. Instead, use the All setting.
              • MatchScope — required — (String)

                The parts of the JSON to match against using the MatchPattern. If you specify All, WAF matches against keys and values.

                Possible values include:
                • "ALL"
                • "KEY"
                • "VALUE"
              • InvalidFallbackBehavior — (String)

                What WAF should do if it fails to completely parse the JSON body. The options are the following:

                • EVALUATE_AS_STRING - Inspect the body as plain text. WAF applies the text transformations and inspection criteria that you defined for the JSON inspection to the body text string.

                • MATCH - Treat the web request as matching the rule statement. WAF applies the rule action to the request.

                • NO_MATCH - Treat the web request as not matching the rule statement.

                If you don't provide this setting, WAF parses and evaluates the content only up to the first parsing failure that it encounters.

                WAF does its best to parse the entire JSON body, but might be forced to stop for reasons such as invalid characters, duplicate keys, truncation, and any content whose root node isn't an object or an array.

                WAF parses the JSON in the following examples as two valid key, value pairs:

                • Missing comma: {"key1":"value1""key2":"value2"}

                • Missing colon: {"key1":"value1","key2""value2"}

                • Extra colons: {"key1"::"value1","key2""value2"}

                Possible values include:
                • "MATCH"
                • "NO_MATCH"
                • "EVALUATE_AS_STRING"
          • TextTransformations — required — (Array<map>)

            Text transformations eliminate some of the unusual formatting that attackers use in web requests in an effort to bypass detection. If you specify one or more transformations in a rule statement, WAF performs all transformations on the content of the request component identified by FieldToMatch, starting from the lowest priority setting, before inspecting the content for a match.

            • Priority — required — (Integer)

              Sets the relative processing order for multiple transformations that are defined for a rule statement. WAF processes all transformations, from lowest priority to highest, before inspecting the transformed content. The priorities don't need to be consecutive, but they must all be different.

            • Type — required — (String)

              You can specify the following transformation types:

              BASE64_DECODE - Decode a Base64-encoded string.

              BASE64_DECODE_EXT - Decode a Base64-encoded string, but use a forgiving implementation that ignores characters that aren't valid.

              CMD_LINE - Command-line transformations. These are helpful in reducing effectiveness of attackers who inject an operating system command-line command and use unusual formatting to disguise some or all of the command.

              • Delete the following characters: \ " ' ^

              • Delete spaces before the following characters: / (

              • Replace the following characters with a space: , ;

              • Replace multiple spaces with one space

              • Convert uppercase letters (A-Z) to lowercase (a-z)

              COMPRESS_WHITE_SPACE - Replace these characters with a space character (decimal 32):

              • \f, formfeed, decimal 12

              • \t, tab, decimal 9

              • \n, newline, decimal 10

              • \r, carriage return, decimal 13

              • \v, vertical tab, decimal 11

              • Non-breaking space, decimal 160

              COMPRESS_WHITE_SPACE also replaces multiple spaces with one space.

              CSS_DECODE - Decode characters that were encoded using CSS 2.x escape rules syndata.html#characters. This function uses up to two bytes in the decoding process, so it can help to uncover ASCII characters that were encoded using CSS encoding that wouldn’t typically be encoded. It's also useful in countering evasion, which is a combination of a backslash and non-hexadecimal characters. For example, ja\vascript for javascript.

              ESCAPE_SEQ_DECODE - Decode the following ANSI C escape sequences: \a, \b, \f, \n, \r, \t, \v, \, \?, \', \", \xHH (hexadecimal), \0OOO (octal). Encodings that aren't valid remain in the output.

              HEX_DECODE - Decode a string of hexadecimal characters into a binary.

              HTML_ENTITY_DECODE - Replace HTML-encoded characters with unencoded characters. HTML_ENTITY_DECODE performs these operations:

              • Replaces (ampersand)quot; with "

              • Replaces (ampersand)nbsp; with a non-breaking space, decimal 160

              • Replaces (ampersand)lt; with a "less than" symbol

              • Replaces (ampersand)gt; with >

              • Replaces characters that are represented in hexadecimal format, (ampersand)#xhhhh;, with the corresponding characters

              • Replaces characters that are represented in decimal format, (ampersand)#nnnn;, with the corresponding characters

              JS_DECODE - Decode JavaScript escape sequences. If a \ u HHHH code is in the full-width ASCII code range of FF01-FF5E, then the higher byte is used to detect and adjust the lower byte. If not, only the lower byte is used and the higher byte is zeroed, causing a possible loss of information.

              LOWERCASE - Convert uppercase letters (A-Z) to lowercase (a-z).

              MD5 - Calculate an MD5 hash from the data in the input. The computed hash is in a raw binary form.

              NONE - Specify NONE if you don't want any text transformations.

              NORMALIZE_PATH - Remove multiple slashes, directory self-references, and directory back-references that are not at the beginning of the input from an input string.

              NORMALIZE_PATH_WIN - This is the same as NORMALIZE_PATH, but first converts backslash characters to forward slashes.

              REMOVE_NULLS - Remove all NULL bytes from the input.

              REPLACE_COMMENTS - Replace each occurrence of a C-style comment (/* ... */) with a single space. Multiple consecutive occurrences are not compressed. Unterminated comments are also replaced with a space (ASCII 0x20). However, a standalone termination of a comment (*/) is not acted upon.

              REPLACE_NULLS - Replace NULL bytes in the input with space characters (ASCII 0x20).

              SQL_HEX_DECODE - Decode SQL hex data. Example (0x414243) will be decoded to (ABC).

              URL_DECODE - Decode a URL-encoded value.

              URL_DECODE_UNI - Like URL_DECODE, but with support for Microsoft-specific %u encoding. If the code is in the full-width ASCII code range of FF01-FF5E, the higher byte is used to detect and adjust the lower byte. Otherwise, only the lower byte is used and the higher byte is zeroed.

              UTF8_TO_UNICODE - Convert all UTF-8 character sequences to Unicode. This helps input normalization, and minimizing false-positives and false-negatives for non-English languages.

              Possible values include:
              • "NONE"
              • "COMPRESS_WHITE_SPACE"
              • "HTML_ENTITY_DECODE"
              • "LOWERCASE"
              • "CMD_LINE"
              • "URL_DECODE"
              • "BASE64_DECODE"
              • "HEX_DECODE"
              • "MD5"
              • "REPLACE_COMMENTS"
              • "ESCAPE_SEQ_DECODE"
              • "SQL_HEX_DECODE"
              • "CSS_DECODE"
              • "JS_DECODE"
              • "NORMALIZE_PATH"
              • "NORMALIZE_PATH_WIN"
              • "REMOVE_NULLS"
              • "REPLACE_NULLS"
              • "BASE64_DECODE_EXT"
              • "URL_DECODE_UNI"
              • "UTF8_TO_UNICODE"
        • SizeConstraintStatement — (map)

          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 first 8192 bytes (8 KB). If the request body for your web requests never exceeds 8192 bytes, you can create a size constraint condition and block requests that have a request body greater than 8192 bytes.

          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.

          • FieldToMatch — required — (map)

            The part of a web request that you want WAF to inspect. For more information, see FieldToMatch.

            • SingleHeader — (map)

              Inspect a single header. Provide the name of the header to inspect, for example, User-Agent or Referer. This setting isn't case sensitive.

              Example JSON: "SingleHeader": { "Name": "haystack" }

              • Name — required — (String)

                The name of the query header to inspect.

            • SingleQueryArgument — (map)

              Inspect a single query argument. Provide the name of the query argument to inspect, such as UserName or SalesRegion. The name can be up to 30 characters long and isn't case sensitive.

              This is used only to indicate the web request component for WAF to inspect, in the FieldToMatch specification.

              Example JSON: "SingleQueryArgument": { "Name": "myArgument" }

              • Name — required — (String)

                The name of the query argument to inspect.

            • AllQueryArguments — (map)

              Inspect all query arguments.

            • UriPath — (map)

              Inspect the request URI path. This is the part of a web request that identifies a resource, for example, /images/daily-ad.jpg.

            • QueryString — (map)

              Inspect the query string. This is the part of a URL that appears after a ? character, if any.

            • Body — (map)

              Inspect the request body as plain text. The request body immediately follows the request headers. This is the part of a request that contains any additional data that you want to send to your web server as the HTTP request body, such as data from a form.

              Note that only the first 8 KB (8192 bytes) of the request body are forwarded to WAF for inspection by the underlying host service. If you don't need to inspect more than 8 KB, you can guarantee that you don't allow additional bytes in by combining a statement that inspects the body of the web request, such as ByteMatchStatement or RegexPatternSetReferenceStatement, with a SizeConstraintStatement that enforces an 8 KB size limit on the body of the request. WAF doesn't support inspecting the entire contents of web requests whose bodies exceed the 8 KB limit.

            • Method — (map)

              Inspect the HTTP method. The method indicates the type of operation that the request is asking the origin to perform.

            • JsonBody — (map)

              Inspect the request body as JSON. The request body immediately follows the request headers. This is the part of a request that contains any additional data that you want to send to your web server as the HTTP request body, such as data from a form.

              Note that only the first 8 KB (8192 bytes) of the request body are forwarded to WAF for inspection by the underlying host service. If you don't need to inspect more than 8 KB, you can guarantee that you don't allow additional bytes in by combining a statement that inspects the body of the web request, such as ByteMatchStatement or RegexPatternSetReferenceStatement, with a SizeConstraintStatement that enforces an 8 KB size limit on the body of the request. WAF doesn't support inspecting the entire contents of web requests whose bodies exceed the 8 KB limit.

              • MatchPattern — required — (map)

                The patterns to look for in the JSON body. WAF inspects the results of these pattern matches against the rule inspection criteria.

                • All — (map)

                  Match all of the elements. See also MatchScope in JsonBody.

                  You must specify either this setting or the IncludedPaths setting, but not both.

                • IncludedPaths — (Array<String>)

                  Match only the specified include paths. See also MatchScope in JsonBody.

                  Provide the include paths using JSON Pointer syntax. For example, "IncludedPaths": ["/dogs/0/name", "/dogs/1/name"]. For information about this syntax, see the Internet Engineering Task Force (IETF) documentation JavaScript Object Notation (JSON) Pointer.

                  You must specify either this setting or the All setting, but not both.

                  Note: Don't use this option to include all paths. Instead, use the All setting.
              • MatchScope — required — (String)

                The parts of the JSON to match against using the MatchPattern. If you specify All, WAF matches against keys and values.

                Possible values include:
                • "ALL"
                • "KEY"
                • "VALUE"
              • InvalidFallbackBehavior — (String)

                What WAF should do if it fails to completely parse the JSON body. The options are the following:

                • EVALUATE_AS_STRING - Inspect the body as plain text. WAF applies the text transformations and inspection criteria that you defined for the JSON inspection to the body text string.

                • MATCH - Treat the web request as matching the rule statement. WAF applies the rule action to the request.

                • NO_MATCH - Treat the web request as not matching the rule statement.

                If you don't provide this setting, WAF parses and evaluates the content only up to the first parsing failure that it encounters.

                WAF does its best to parse the entire JSON body, but might be forced to stop for reasons such as invalid characters, duplicate keys, truncation, and any content whose root node isn't an object or an array.

                WAF parses the JSON in the following examples as two valid key, value pairs:

                • Missing comma: {"key1":"value1""key2":"value2"}

                • Missing colon: {"key1":"value1","key2""value2"}

                • Extra colons: {"key1"::"value1","key2""value2"}

                Possible values include:
                • "MATCH"
                • "NO_MATCH"
                • "EVALUATE_AS_STRING"
          • ComparisonOperator — required — (String)

            The operator to use to compare the request part to the size setting.

            Possible values include:
            • "EQ"
            • "NE"
            • "LE"
            • "LT"
            • "GE"
            • "GT"
          • Size — required — (Integer)

            The size, in byte, to compare to the request part, after any transformations.

          • TextTransformations — required — (Array<map>)

            Text transformations eliminate some of the unusual formatting that attackers use in web requests in an effort to bypass detection. If you specify one or more transformations in a rule statement, WAF performs all transformations on the content of the request component identified by FieldToMatch, starting from the lowest priority setting, before inspecting the content for a match.

            • Priority — required — (Integer)

              Sets the relative processing order for multiple transformations that are defined for a rule statement. WAF processes all transformations, from lowest priority to highest, before inspecting the transformed content. The priorities don't need to be consecutive, but they must all be different.

            • Type — required — (String)

              You can specify the following transformation types:

              BASE64_DECODE - Decode a Base64-encoded string.

              BASE64_DECODE_EXT - Decode a Base64-encoded string, but use a forgiving implementation that ignores characters that aren't valid.

              CMD_LINE - Command-line transformations. These are helpful in reducing effectiveness of attackers who inject an operating system command-line command and use unusual formatting to disguise some or all of the command.

              • Delete the following characters: \ " ' ^

              • Delete spaces before the following characters: / (

              • Replace the following characters with a space: , ;

              • Replace multiple spaces with one space

              • Convert uppercase letters (A-Z) to lowercase (a-z)

              COMPRESS_WHITE_SPACE - Replace these characters with a space character (decimal 32):

              • \f, formfeed, decimal 12

              • \t, tab, decimal 9

              • \n, newline, decimal 10

              • \r, carriage return, decimal 13

              • \v, vertical tab, decimal 11

              • Non-breaking space, decimal 160

              COMPRESS_WHITE_SPACE also replaces multiple spaces with one space.

              CSS_DECODE - Decode characters that were encoded using CSS 2.x escape rules syndata.html#characters. This function uses up to two bytes in the decoding process, so it can help to uncover ASCII characters that were encoded using CSS encoding that wouldn’t typically be encoded. It's also useful in countering evasion, which is a combination of a backslash and non-hexadecimal characters. For example, ja\vascript for javascript.

              ESCAPE_SEQ_DECODE - Decode the following ANSI C escape sequences: \a, \b, \f, \n, \r, \t, \v, \, \?, \', \", \xHH (hexadecimal), \0OOO (octal). Encodings that aren't valid remain in the output.

              HEX_DECODE - Decode a string of hexadecimal characters into a binary.

              HTML_ENTITY_DECODE - Replace HTML-encoded characters with unencoded characters. HTML_ENTITY_DECODE performs these operations:

              • Replaces (ampersand)quot; with "

              • Replaces (ampersand)nbsp; with a non-breaking space, decimal 160

              • Replaces (ampersand)lt; with a "less than" symbol

              • Replaces (ampersand)gt; with >

              • Replaces characters that are represented in hexadecimal format, (ampersand)#xhhhh;, with the corresponding characters

              • Replaces characters that are represented in decimal format, (ampersand)#nnnn;, with the corresponding characters

              JS_DECODE - Decode JavaScript escape sequences. If a \ u HHHH code is in the full-width ASCII code range of FF01-FF5E, then the higher byte is used to detect and adjust the lower byte. If not, only the lower byte is used and the higher byte is zeroed, causing a possible loss of information.

              LOWERCASE - Convert uppercase letters (A-Z) to lowercase (a-z).

              MD5 - Calculate an MD5 hash from the data in the input. The computed hash is in a raw binary form.

              NONE - Specify NONE if you don't want any text transformations.

              NORMALIZE_PATH - Remove multiple slashes, directory self-references, and directory back-references that are not at the beginning of the input from an input string.

              NORMALIZE_PATH_WIN - This is the same as NORMALIZE_PATH, but first converts backslash characters to forward slashes.

              REMOVE_NULLS - Remove all NULL bytes from the input.

              REPLACE_COMMENTS - Replace each occurrence of a C-style comment (/* ... */) with a single space. Multiple consecutive occurrences are not compressed. Unterminated comments are also replaced with a space (ASCII 0x20). However, a standalone termination of a comment (*/) is not acted upon.

              REPLACE_NULLS - Replace NULL bytes in the input with space characters (ASCII 0x20).

              SQL_HEX_DECODE - Decode SQL hex data. Example (0x414243) will be decoded to (ABC).

              URL_DECODE - Decode a URL-encoded value.

              URL_DECODE_UNI - Like URL_DECODE, but with support for Microsoft-specific %u encoding. If the code is in the full-width ASCII code range of FF01-FF5E, the higher byte is used to detect and adjust the lower byte. Otherwise, only the lower byte is used and the higher byte is zeroed.

              UTF8_TO_UNICODE - Convert all UTF-8 character sequences to Unicode. This helps input normalization, and minimizing false-positives and false-negatives for non-English languages.

              Possible values include:
              • "NONE"
              • "COMPRESS_WHITE_SPACE"
              • "HTML_ENTITY_DECODE"
              • "LOWERCASE"
              • "CMD_LINE"
              • "URL_DECODE"
              • "BASE64_DECODE"
              • "HEX_DECODE"
              • "MD5"
              • "REPLACE_COMMENTS"
              • "ESCAPE_SEQ_DECODE"
              • "SQL_HEX_DECODE"
              • "CSS_DECODE"
              • "JS_DECODE"
              • "NORMALIZE_PATH"
              • "NORMALIZE_PATH_WIN"
              • "REMOVE_NULLS"
              • "REPLACE_NULLS"
              • "BASE64_DECODE_EXT"
              • "URL_DECODE_UNI"
              • "UTF8_TO_UNICODE"
        • GeoMatchStatement — (map)

          A rule statement used to identify web requests based on country of origin.

          • CountryCodes — (Array<String>)

            An array of two-character country codes, for example, [ "US", "CN" ], from the alpha-2 country ISO codes of the ISO 3166 international standard.

          • ForwardedIPConfig — (map)

            The configuration for inspecting IP addresses in an HTTP header that you specify, instead of using the IP address that's reported by the web request origin. Commonly, this is the X-Forwarded-For (XFF) header, but you can specify any header name.

            Note: If the specified header isn't present in the request, WAF doesn't apply the rule to the web request at all.
            • HeaderName — required — (String)

              The name of the HTTP header to use for the IP address. For example, to use the X-Forwarded-For (XFF) header, set this to X-Forwarded-For.

              Note: If the specified header isn't present in the request, WAF doesn't apply the rule to the web request at all.
            • FallbackBehavior — required — (String)

              The match status to assign to the web request if the request doesn't have a valid IP address in the specified position.

              Note: If the specified header isn't present in the request, WAF doesn't apply the rule to the web request at all.

              You can specify the following fallback behaviors:

              • MATCH - Treat the web request as matching the rule statement. WAF applies the rule action to the request.

              • NO_MATCH - Treat the web request as not matching the rule statement.

              Possible values include:
              • "MATCH"
              • "NO_MATCH"
        • RuleGroupReferenceStatement — (map)

          A rule statement used to run the rules that are defined in a RuleGroup. To use this, create a rule group with your rules, then provide the ARN of the rule group in this statement.

          You cannot nest a RuleGroupReferenceStatement, for example for use inside a NotStatement or OrStatement. You can only use a rule group reference statement at the top level inside a web ACL.

          • ARN — required — (String)

            The Amazon Resource Name (ARN) of the entity.

          • ExcludedRules — (Array<map>)

            The rules in the referenced rule group whose actions are set to Count. When you exclude a rule, WAF evaluates it exactly as it would if the rule action setting were Count. This is a useful option for testing the rules in a rule group without modifying how they handle your web traffic.

            • Name — required — (String)

              The name of the rule whose action you want to override to Count.

        • IPSetReferenceStatement — (map)

          A rule statement used to detect web requests coming from particular IP addresses or address ranges. To use this, create an IPSet that specifies the addresses you want to detect, then use the ARN of that set in this statement. To create an IP set, see CreateIPSet.

          Each IP set rule statement references an IP set. You create and maintain the set independent of your rules. This allows you to use the single set in multiple rules. When you update the referenced set, WAF automatically updates all rules that reference it.

          • ARN — required — (String)

            The Amazon Resource Name (ARN) of the IPSet that this statement references.

          • IPSetForwardedIPConfig — (map)

            The configuration for inspecting IP addresses in an HTTP header that you specify, instead of using the IP address that's reported by the web request origin. Commonly, this is the X-Forwarded-For (XFF) header, but you can specify any header name.

            Note: If the specified header isn't present in the request, WAF doesn't apply the rule to the web request at all.
            • HeaderName — required — (String)

              The name of the HTTP header to use for the IP address. For example, to use the X-Forwarded-For (XFF) header, set this to X-Forwarded-For.

              Note: If the specified header isn't present in the request, WAF doesn't apply the rule to the web request at all.
            • FallbackBehavior — required — (String)

              The match status to assign to the web request if the request doesn't have a valid IP address in the specified position.

              Note: If the specified header isn't present in the request, WAF doesn't apply the rule to the web request at all.

              You can specify the following fallback behaviors:

              • MATCH - Treat the web request as matching the rule statement. WAF applies the rule action to the request.

              • NO_MATCH - Treat the web request as not matching the rule statement.

              Possible values include:
              • "MATCH"
              • "NO_MATCH"
            • Position — required — (String)

              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:

              • FIRST - Inspect the first IP address in the list of IP addresses in the header. This is usually the client's original IP.

              • LAST - Inspect the last IP address in the list of IP addresses in the header.

              • ANY - Inspect all IP addresses in the header for a match. If the header contains more than 10 IP addresses, WAF inspects the last 10.

              Possible values include:
              • "FIRST"
              • "LAST"
              • "ANY"
        • RegexPatternSetReferenceStatement — (map)

          A rule statement used to search web request components for matches with regular expressions. To use this, create a RegexPatternSet that specifies the expressions that you want to detect, then use the ARN of that set in this statement. A web request matches the pattern set rule statement if the request component matches any of the patterns in the set. To create a regex pattern set, see CreateRegexPatternSet.

          Each regex pattern set rule statement references a regex pattern set. You create and maintain the set independent of your rules. This allows you to use the single set in multiple rules. When you update the referenced set, WAF automatically updates all rules that reference it.

          • ARN — required — (String)

            The Amazon Resource Name (ARN) of the RegexPatternSet that this statement references.

          • FieldToMatch — required — (map)

            The part of a web request that you want WAF to inspect. For more information, see FieldToMatch.

            • SingleHeader — (map)

              Inspect a single header. Provide the name of the header to inspect, for example, User-Agent or Referer. This setting isn't case sensitive.

              Example JSON: "SingleHeader": { "Name": "haystack" }

              • Name — required — (String)

                The name of the query header to inspect.

            • SingleQueryArgument — (map)

              Inspect a single query argument. Provide the name of the query argument to inspect, such as UserName or SalesRegion. The name can be up to 30 characters long and isn't case sensitive.

              This is used only to indicate the web request component for WAF to inspect, in the FieldToMatch specification.

              Example JSON: "SingleQueryArgument": { "Name": "myArgument" }

              • Name — required — (String)

                The name of the query argument to inspect.

            • AllQueryArguments — (map)

              Inspect all query arguments.

            • UriPath — (map)

              Inspect the request URI path. This is the part of a web request that identifies a resource, for example, /images/daily-ad.jpg.

            • QueryString — (map)

              Inspect the query string. This is the part of a URL that appears after a ? character, if any.

            • Body — (map)

              Inspect the request body as plain text. The request body immediately follows the request headers. This is the part of a request that contains any additional data that you want to send to your web server as the HTTP request body, such as data from a form.

              Note that only the first 8 KB (8192 bytes) of the request body are forwarded to WAF for inspection by the underlying host service. If you don't need to inspect more than 8 KB, you can guarantee that you don't allow additional bytes in by combining a statement that inspects the body of the web request, such as ByteMatchStatement or RegexPatternSetReferenceStatement, with a SizeConstraintStatement that enforces an 8 KB size limit on the body of the request. WAF doesn't support inspecting the entire contents of web requests whose bodies exceed the 8 KB limit.

            • Method — (map)

              Inspect the HTTP method. The method indicates the type of operation that the request is asking the origin to perform.

            • JsonBody — (map)

              Inspect the request body as JSON. The request body immediately follows the request headers. This is the part of a request that contains any additional data that you want to send to your web server as the HTTP request body, such as data from a form.

              Note that only the first 8 KB (8192 bytes) of the request body are forwarded to WAF for inspection by the underlying host service. If you don't need to inspect more than 8 KB, you can guarantee that you don't allow additional bytes in by combining a statement that inspects the body of the web request, such as ByteMatchStatement or RegexPatternSetReferenceStatement, with a SizeConstraintStatement that enforces an 8 KB size limit on the body of the request. WAF doesn't support inspecting the entire contents of web requests whose bodies exceed the 8 KB limit.

              • MatchPattern — required — (map)

                The patterns to look for in the JSON body. WAF inspects the results of these pattern matches against the rule inspection criteria.

                • All — (map)

                  Match all of the elements. See also MatchScope in JsonBody.

                  You must specify either this setting or the IncludedPaths setting, but not both.

                • IncludedPaths — (Array<String>)

                  Match only the specified include paths. See also MatchScope in JsonBody.

                  Provide the include paths using JSON Pointer syntax. For example, "IncludedPaths": ["/dogs/0/name", "/dogs/1/name"]. For information about this syntax, see the Internet Engineering Task Force (IETF) documentation JavaScript Object Notation (JSON) Pointer.

                  You must specify either this setting or the All setting, but not both.

                  Note: Don't use this option to include all paths. Instead, use the All setting.
              • MatchScope — required — (String)

                The parts of the JSON to match against using the MatchPattern. If you specify All, WAF matches against keys and values.

                Possible values include:
                • "ALL"
                • "KEY"
                • "VALUE"
              • InvalidFallbackBehavior — (String)

                What WAF should do if it fails to completely parse the JSON body. The options are the following:

                • EVALUATE_AS_STRING - Inspect the body as plain text. WAF applies the text transformations and inspection criteria that you defined for the JSON inspection to the body text string.

                • MATCH - Treat the web request as matching the rule statement. WAF applies the rule action to the request.

                • NO_MATCH - Treat the web request as not matching the rule statement.

                If you don't provide this setting, WAF parses and evaluates the content only up to the first parsing failure that it encounters.

                WAF does its best to parse the entire JSON body, but might be forced to stop for reasons such as invalid characters, duplicate keys, truncation, and any content whose root node isn't an object or an array.

                WAF parses the JSON in the following examples as two valid key, value pairs:

                • Missing comma: {"key1":"value1""key2":"value2"}

                • Missing colon: {"key1":"value1","key2""value2"}

                • Extra colons: {"key1"::"value1","key2""value2"}

                Possible values include:
                • "MATCH"
                • "NO_MATCH"
                • "EVALUATE_AS_STRING"
          • TextTransformations — required — (Array<map>)

            Text transformations eliminate some of the unusual formatting that attackers use in web requests in an effort to bypass detection. If you specify one or more transformations in a rule statement, WAF performs all transformations on the content of the request component identified by FieldToMatch, starting from the lowest priority setting, before inspecting the content for a match.

            • Priority — required — (Integer)

              Sets the relative processing order for multiple transformations that are defined for a rule statement. WAF processes all transformations, from lowest priority to highest, before inspecting the transformed content. The priorities don't need to be consecutive, but they must all be different.

            • Type — required — (String)

              You can specify the following transformation types:

              BASE64_DECODE - Decode a Base64-encoded string.

              BASE64_DECODE_EXT - Decode a Base64-encoded string, but use a forgiving implementation that ignores characters that aren't valid.

              CMD_LINE - Command-line transformations. These are helpful in reducing effectiveness of attackers who inject an operating system command-line command and use unusual formatting to disguise some or all of the command.

              • Delete the following characters: \ " ' ^

              • Delete spaces before the following characters: / (

              • Replace the following characters with a space: , ;

              • Replace multiple spaces with one space

              • Convert uppercase letters (A-Z) to lowercase (a-z)

              COMPRESS_WHITE_SPACE - Replace these characters with a space character (decimal 32):

              • \f, formfeed, decimal 12

              • \t, tab, decimal 9

              • \n, newline, decimal 10

              • \r, carriage return, decimal 13

              • \v, vertical tab, decimal 11

              • Non-breaking space, decimal 160

              COMPRESS_WHITE_SPACE also replaces multiple spaces with one space.

              CSS_DECODE - Decode characters that were encoded using CSS 2.x escape rules syndata.html#characters. This function uses up to two bytes in the decoding process, so it can help to uncover ASCII characters that were encoded using CSS encoding that wouldn’t typically be encoded. It's also useful in countering evasion, which is a combination of a backslash and non-hexadecimal characters. For example, ja\vascript for javascript.

              ESCAPE_SEQ_DECODE - Decode the following ANSI C escape sequences: \a, \b, \f, \n, \r, \t, \v, \, \?, \', \", \xHH (hexadecimal), \0OOO (octal). Encodings that aren't valid remain in the output.

              HEX_DECODE - Decode a string of hexadecimal characters into a binary.

              HTML_ENTITY_DECODE - Replace HTML-encoded characters with unencoded characters. HTML_ENTITY_DECODE performs these operations:

              • Replaces (ampersand)quot; with "

              • Replaces (ampersand)nbsp; with a non-breaking space, decimal 160

              • Replaces (ampersand)lt; with a "less than" symbol

              • Replaces (ampersand)gt; with >

              • Replaces characters that are represented in hexadecimal format, (ampersand)#xhhhh;, with the corresponding characters

              • Replaces characters that are represented in decimal format, (ampersand)#nnnn;, with the corresponding characters

              JS_DECODE - Decode JavaScript escape sequences. If a \ u HHHH code is in the full-width ASCII code range of FF01-FF5E, then the higher byte is used to detect and adjust the lower byte. If not, only the lower byte is used and the higher byte is zeroed, causing a possible loss of information.

              LOWERCASE - Convert uppercase letters (A-Z) to lowercase (a-z).

              MD5 - Calculate an MD5 hash from the data in the input. The computed hash is in a raw binary form.

              NONE - Specify NONE if you don't want any text transformations.

              NORMALIZE_PATH - Remove multiple slashes, directory self-references, and directory back-references that are not at the beginning of the input from an input string.

              NORMALIZE_PATH_WIN - This is the same as NORMALIZE_PATH, but first converts backslash characters to forward slashes.

              REMOVE_NULLS - Remove all NULL bytes from the input.

              REPLACE_COMMENTS - Replace each occurrence of a C-style comment (/* ... */) with a single space. Multiple consecutive occurrences are not compressed. Unterminated comments are also replaced with a space (ASCII 0x20). However, a standalone termination of a comment (*/) is not acted upon.

              REPLACE_NULLS - Replace NULL bytes in the input with space characters (ASCII 0x20).

              SQL_HEX_DECODE - Decode SQL hex data. Example (0x414243) will be decoded to (ABC).

              URL_DECODE - Decode a URL-encoded value.

              URL_DECODE_UNI - Like URL_DECODE, but with support for Microsoft-specific %u encoding. If the code is in the full-width ASCII code range of FF01-FF5E, the higher byte is used to detect and adjust the lower byte. Otherwise, only the lower byte is used and the higher byte is zeroed.

              UTF8_TO_UNICODE - Convert all UTF-8 character sequences to Unicode. This helps input normalization, and minimizing false-positives and false-negatives for non-English languages.

              Possible values include:
              • "NONE"
              • "COMPRESS_WHITE_SPACE"
              • "HTML_ENTITY_DECODE"
              • "LOWERCASE"
              • "CMD_LINE"
              • "URL_DECODE"
              • "BASE64_DECODE"
              • "HEX_DECODE"
              • "MD5"
              • "REPLACE_COMMENTS"
              • "ESCAPE_SEQ_DECODE"
              • "SQL_HEX_DECODE"
              • "CSS_DECODE"
              • "JS_DECODE"
              • "NORMALIZE_PATH"
              • "NORMALIZE_PATH_WIN"
              • "REMOVE_NULLS"
              • "REPLACE_NULLS"
              • "BASE64_DECODE_EXT"
              • "URL_DECODE_UNI"
              • "UTF8_TO_UNICODE"
        • RateBasedStatement — (map)

          A rate-based rule tracks the rate of requests for each originating IP address, and triggers the rule action when the rate exceeds a limit that you specify on the number of requests in any 5-minute time span. You can use this to put a temporary block on requests from an IP address that is sending excessive requests.

          WAF tracks and manages web requests separately for each instance of a rate-based rule that you use. For example, if you provide the same rate-based rule settings in two web ACLs, each of the two rule statements represents a separate instance of the rate-based rule and gets its own tracking and management by WAF. If you define a rate-based rule inside a rule group, and then use that rule group in multiple places, each use creates a separate instance of the rate-based rule that gets its own tracking and management by WAF.

          When the rule action triggers, WAF blocks additional requests from the IP address until the request rate falls below the limit.

          You can optionally nest another statement inside the rate-based statement, to narrow the scope of the rule so that it only counts requests that match the nested statement. For example, based on recent requests that you have seen from an attacker, you might create a rate-based rule with a nested AND rule statement that contains the following nested statements:

          • An IP match statement with an IP set that specified the address 192.0.2.44.

          • A string match statement that searches in the User-Agent header for the string BadBot.

          In this rate-based rule, you also define a rate limit. For this example, the rate limit is 1,000. Requests that meet both of the conditions in the statements are counted. If the count exceeds 1,000 requests per five minutes, the rule action triggers. Requests that do not meet both conditions are not counted towards the rate limit and are not affected by this rule.

          You cannot nest a RateBasedStatement inside another statement, for example inside a NotStatement or OrStatement. You can define a RateBasedStatement inside a web ACL and inside a rule group.

          • Limit — required — (Integer)

            The limit on requests per 5-minute period for a single originating IP address. If the statement includes a ScopeDownStatement, this limit is applied only to the requests that match the statement.

          • AggregateKeyType — required — (String)

            Setting that indicates how to aggregate the request counts. The options are the following:

            • IP - Aggregate the request counts on the IP address from the web request origin.

            • FORWARDED_IP - Aggregate the request counts on the first IP address in an HTTP header. If you use this, configure the ForwardedIPConfig, to specify the header to use.

            Possible values include:
            • "IP"
            • "FORWARDED_IP"
          • ForwardedIPConfig — (map)

            The configuration for inspecting IP addresses in an HTTP header that you specify, instead of using the IP address that's reported by the web request origin. Commonly, this is the X-Forwarded-For (XFF) header, but you can specify any header name.

            Note: If the specified header isn't present in the request, WAF doesn't apply the rule to the web request at all.

            This is required if AggregateKeyType is set to FORWARDED_IP.

            • HeaderName — required — (String)

              The name of the HTTP header to use for the IP address. For example, to use the X-Forwarded-For (XFF) header, set this to X-Forwarded-For.

              Note: If the specified header isn't present in the request, WAF doesn't apply the rule to the web request at all.
            • FallbackBehavior — required — (String)

              The match status to assign to the web request if the request doesn't have a valid IP address in the specified position.

              Note: If the specified header isn't present in the request, WAF doesn't apply the rule to the web request at all.

              You can specify the following fallback behaviors:

              • MATCH - Treat the web request as matching the rule statement. WAF applies the rule action to the request.

              • NO_MATCH - Treat the web request as not matching the rule statement.

              Possible values include:
              • "MATCH"
              • "NO_MATCH"
        • AndStatement — (map)

          A logical rule statement used to combine other rule statements with AND logic. You provide more than one Statement within the AndStatement.

          • Statements — required — (Array<map>)

            The statements to combine with AND logic. You can use any statements that can be nested.

        • OrStatement — (map)

          A logical rule statement used to combine other rule statements with OR logic. You provide more than one Statement within the OrStatement.

          • Statements — required — (Array<map>)

            The statements to combine with OR logic. You can use any statements that can be nested.

        • NotStatement — (map)

          A logical rule statement used to negate the results of another rule statement. You provide one Statement within the NotStatement.

        • ManagedRuleGroupStatement — (map)

          A rule statement used to run the rules that are defined in a managed rule group. To use this, provide the vendor name and the name of the rule group in this statement. You can retrieve the required names by calling ListAvailableManagedRuleGroups.

          You cannot nest a ManagedRuleGroupStatement, for example for use inside a NotStatement or OrStatement. It can only be referenced as a top-level statement within a rule.

          • VendorName — required — (String)

            The name of the managed rule group vendor. You use this, along with the rule group name, to identify the rule group.

          • Name — required — (String)

            The name of the managed rule group. You use this, along with the vendor name, to identify the rule group.

          • Version — (String)

            The version of the managed rule group to use. If you specify this, the version setting is fixed until you change it. If you don't specify this, WAF uses the vendor's default version, and then keeps the version at the vendor's default when the vendor updates the managed rule group settings.

          • ExcludedRules — (Array<map>)

            The rules in the referenced rule group whose actions are set to Count. When you exclude a rule, WAF evaluates it exactly as it would if the rule action setting were Count. This is a useful option for testing the rules in a rule group without modifying how they handle your web traffic.

            • Name — required — (String)

              The name of the rule whose action you want to override to Count.

        • LabelMatchStatement — (map)

          A rule statement that defines a string match search against labels that have been added to the web request by rules that have already run in the web ACL.

          The label match statement provides the label or namespace string to search for. The label string can represent a part or all of the fully qualified label name that had been added to the web request. Fully qualified labels have a prefix, optional namespaces, and label name. The prefix identifies the rule group or web ACL context of the rule that added the label. If you do not provide the fully qualified name in your label match string, WAF performs the search for labels that were added in the same context as the label match statement.

          • Scope — required — (String)

            Specify whether you want to match using the label name or just the namespace.

            Possible values include:
            • "LABEL"
            • "NAMESPACE"
          • Key — required — (String)

            The string to match against. The setting you provide for this depends on the match statement's Scope setting:

            • If the Scope indicates LABEL, then this specification must include the name and can include any number of preceding namespace specifications and prefix up to providing the fully qualified label name.

            • If the Scope indicates NAMESPACE, then this specification can include any number of contiguous namespace strings, and can include the entire label namespace prefix from the rule group or web ACL where the label originates.

            Labels are case sensitive and components of a label must be separated by colon, for example NS1:NS2:name.

        • RegexMatchStatement — (map)

          A rule statement used to search web request components for a match against a single regular expression.

          • RegexString — required — (String)

            The string representing the regular expression.

          • FieldToMatch — required — (map)

            The part of a web request that you want WAF to inspect. For more information, see FieldToMatch.

            • SingleHeader — (map)

              Inspect a single header. Provide the name of the header to inspect, for example, User-Agent or Referer. This setting isn't case sensitive.

              Example JSON: "SingleHeader": { "Name": "haystack" }

              • Name — required — (String)

                The name of the query header to inspect.

            • SingleQueryArgument — (map)

              Inspect a single query argument. Provide the name of the query argument to inspect, such as UserName or SalesRegion. The name can be up to 30 characters long and isn't case sensitive.

              This is used only to indicate the web request component for WAF to inspect, in the FieldToMatch specification.

              Example JSON: "SingleQueryArgument": { "Name": "myArgument" }

              • Name — required — (String)

                The name of the query argument to inspect.

            • AllQueryArguments — (map)

              Inspect all query arguments.

            • UriPath — (map)

              Inspect the request URI path. This is the part of a web request that identifies a resource, for example, /images/daily-ad.jpg.

            • QueryString — (map)

              Inspect the query string. This is the part of a URL that appears after a ? character, if any.

            • Body — (map)

              Inspect the request body as plain text. The request body immediately follows the request headers. This is the part of a request that contains any additional data that you want to send to your web server as the HTTP request body, such as data from a form.

              Note that only the first 8 KB (8192 bytes) of the request body are forwarded to WAF for inspection by the underlying host service. If you don't need to inspect more than 8 KB, you can guarantee that you don't allow additional bytes in by combining a statement that inspects the body of the web request, such as ByteMatchStatement or RegexPatternSetReferenceStatement, with a SizeConstraintStatement that enforces an 8 KB size limit on the body of the request. WAF doesn't support inspecting the entire contents of web requests whose bodies exceed the 8 KB limit.

            • Method — (map)

              Inspect the HTTP method. The method indicates the type of operation that the request is asking the origin to perform.

            • JsonBody — (map)

              Inspect the request body as JSON. The request body immediately follows the request headers. This is the part of a request that contains any additional data that you want to send to your web server as the HTTP request body, such as data from a form.

              Note that only the first 8 KB (8192 bytes) of the request body are forwarded to WAF for inspection by the underlying host service. If you don't need to inspect more than 8 KB, you can guarantee that you don't allow additional bytes in by combining a statement that inspects the body of the web request, such as ByteMatchStatement or RegexPatternSetReferenceStatement, with a SizeConstraintStatement that enforces an 8 KB size limit on the body of the request. WAF doesn't support inspecting the entire contents of web requests whose bodies exceed the 8 KB limit.

              • MatchPattern — required — (map)

                The patterns to look for in the JSON body. WAF inspects the results of these pattern matches against the rule inspection criteria.

                • All — (map)

                  Match all of the elements. See also MatchScope in JsonBody.

                  You must specify either this setting or the IncludedPaths setting, but not both.

                • IncludedPaths — (Array<String>)

                  Match only the specified include paths. See also MatchScope in JsonBody.

                  Provide the include paths using JSON Pointer syntax. For example, "IncludedPaths": ["/dogs/0/name", "/dogs/1/name"]. For information about this syntax, see the Internet Engineering Task Force (IETF) documentation JavaScript Object Notation (JSON) Pointer.

                  You must specify either this setting or the All setting, but not both.

                  Note: Don't use this option to include all paths. Instead, use the All setting.
              • MatchScope — required — (String)

                The parts of the JSON to match against using the MatchPattern. If you specify All, WAF matches against keys and values.

                Possible values include:
                • "ALL"
                • "KEY"
                • "VALUE"
              • InvalidFallbackBehavior — (String)

                What WAF should do if it fails to completely parse the JSON body. The options are the following:

                • EVALUATE_AS_STRING - Inspect the body as plain text. WAF applies the text transformations and inspection criteria that you defined for the JSON inspection to the body text string.

                • MATCH - Treat the web request as matching the rule statement. WAF applies the rule action to the request.

                • NO_MATCH - Treat the web request as not matching the rule statement.

                If you don't provide this setting, WAF parses and evaluates the content only up to the first parsing failure that it encounters.

                WAF does its best to parse the entire JSON body, but might be forced to stop for reasons such as invalid characters, duplicate keys, truncation, and any content whose root node isn't an object or an array.

                WAF parses the JSON in the following examples as two valid key, value pairs:

                • Missing comma: {"key1":"value1""key2":"value2"}

                • Missing colon: {"key1":"value1","key2""value2"}

                • Extra colons: {"key1"::"value1","key2""value2"}

                Possible values include:
                • "MATCH"
                • "NO_MATCH"
                • "EVALUATE_AS_STRING"
          • TextTransformations — required — (Array<map>)

            Text transformations eliminate some of the unusual formatting that attackers use in web requests in an effort to bypass detection. If you specify one or more transformations in a rule statement, WAF performs all transformations on the content of the request component identified by FieldToMatch, starting from the lowest priority setting, before inspecting the content for a match.

            • Priority — required — (Integer)

              Sets the relative processing order for multiple transformations that are defined for a rule statement. WAF processes all transformations, from lowest priority to highest, before inspecting the transformed content. The priorities don't need to be consecutive, but they must all be different.

            • Type — required — (String)

              You can specify the following transformation types:

              BASE64_DECODE - Decode a Base64-encoded string.

              BASE64_DECODE_EXT - Decode a Base64-encoded string, but use a forgiving implementation that ignores characters that aren't valid.

              CMD_LINE - Command-line transformations. These are helpful in reducing effectiveness of attackers who inject an operating system command-line command and use unusual formatting to disguise some or all of the command.

              • Delete the following characters: \ " ' ^

              • Delete spaces before the following characters: / (

              • Replace the following characters with a space: , ;

              • Replace multiple spaces with one space

              • Convert uppercase letters (A-Z) to lowercase (a-z)

              COMPRESS_WHITE_SPACE - Replace these characters with a space character (decimal 32):

              • \f, formfeed, decimal 12

              • \t, tab, decimal 9

              • \n, newline, decimal 10

              • \r, carriage return, decimal 13

              • \v, vertical tab, decimal 11

              • Non-breaking space, decimal 160

              COMPRESS_WHITE_SPACE also replaces multiple spaces with one space.

              CSS_DECODE - Decode characters that were encoded using CSS 2.x escape rules syndata.html#characters. This function uses up to two bytes in the decoding process, so it can help to uncover ASCII characters that were encoded using CSS encoding that wouldn’t typically be encoded. It's also useful in countering evasion, which is a combination of a backslash and non-hexadecimal characters. For example, ja\vascript for javascript.

              ESCAPE_SEQ_DECODE - Decode the following ANSI C escape sequences: \a, \b, \f, \n, \r, \t, \v, \, \?, \', \", \xHH (hexadecimal), \0OOO (octal). Encodings that aren't valid remain in the output.

              HEX_DECODE - Decode a string of hexadecimal characters into a binary.

              HTML_ENTITY_DECODE - Replace HTML-encoded characters with unencoded characters. HTML_ENTITY_DECODE performs these operations:

              • Replaces (ampersand)quot; with "

              • Replaces (ampersand)nbsp; with a non-breaking space, decimal 160

              • Replaces (ampersand)lt; with a "less than" symbol

              • Replaces (ampersand)gt; with >

              • Replaces characters that are represented in hexadecimal format, (ampersand)#xhhhh;, with the corresponding characters

              • Replaces characters that are represented in decimal format, (ampersand)#nnnn;, with the corresponding characters

              JS_DECODE - Decode JavaScript escape sequences. If a \ u HHHH code is in the full-width ASCII code range of FF01-FF5E, then the higher byte is used to detect and adjust the lower byte. If not, only the lower byte is used and the higher byte is zeroed, causing a possible loss of information.

              LOWERCASE - Convert uppercase letters (A-Z) to lowercase (a-z).

              MD5 - Calculate an MD5 hash from the data in the input. The computed hash is in a raw binary form.

              NONE - Specify NONE if you don't want any text transformations.

              NORMALIZE_PATH - Remove multiple slashes, directory self-references, and directory back-references that are not at the beginning of the input from an input string.

              NORMALIZE_PATH_WIN - This is the same as NORMALIZE_PATH, but first converts backslash characters to forward slashes.

              REMOVE_NULLS - Remove all NULL bytes from the input.

              REPLACE_COMMENTS - Replace each occurrence of a C-style comment (/* ... */) with a single space. Multiple consecutive occurrences are not compressed. Unterminated comments are also replaced with a space (ASCII 0x20). However, a standalone termination of a comment (*/) is not acted upon.

              REPLACE_NULLS - Replace NULL bytes in the input with space characters (ASCII 0x20).

              SQL_HEX_DECODE - Decode SQL hex data. Example (0x414243) will be decoded to (ABC).

              URL_DECODE - Decode a URL-encoded value.

              URL_DECODE_UNI - Like URL_DECODE, but with support for Microsoft-specific %u encoding. If the code is in the full-width ASCII code range of FF01-FF5E, the higher byte is used to detect and adjust the lower byte. Otherwise, only the lower byte is used and the higher byte is zeroed.

              UTF8_TO_UNICODE - Convert all UTF-8 character sequences to Unicode. This helps input normalization, and minimizing false-positives and false-negatives for non-English languages.

              Possible values include:
              • "NONE"
              • "COMPRESS_WHITE_SPACE"
              • "HTML_ENTITY_DECODE"
              • "LOWERCASE"
              • "CMD_LINE"
              • "URL_DECODE"
              • "BASE64_DECODE"
              • "HEX_DECODE"
              • "MD5"
              • "REPLACE_COMMENTS"
              • "ESCAPE_SEQ_DECODE"
              • "SQL_HEX_DECODE"
              • "CSS_DECODE"
              • "JS_DECODE"
              • "NORMALIZE_PATH"
              • "NORMALIZE_PATH_WIN"
              • "REMOVE_NULLS"
              • "REPLACE_NULLS"
              • "BASE64_DECODE_EXT"
              • "URL_DECODE_UNI"
              • "UTF8_TO_UNICODE"
      • Action — (map)

        The action that WAF should take on a web request when it matches the rule statement. Settings at the web ACL level can override the rule action setting.

        This is used only for rules whose statements do not reference a rule group. Rule statements that reference a rule group include RuleGroupReferenceStatement and ManagedRuleGroupStatement.

        You must specify either this Action setting or the rule OverrideAction setting, but not both:

        • If the rule statement does not reference a rule group, use this rule action setting and not the rule override action setting.

        • If the rule statement references a rule group, use the override action setting and not this action setting.

        • Block — (map)

          Instructs WAF to block the web request.

          • CustomResponse — (map)

            Defines a custom response for the web request.

            For information about customizing web requests and responses, see Customizing web requests and responses in WAF in the WAF Developer Guide.

            • ResponseCode — required — (Integer)

              The HTTP status code to return to the client.

              For a list of status codes that you can use in your custom reqponses, see Supported status codes for custom response in the WAF Developer Guide.

            • CustomResponseBodyKey — (String)

              References the response body that you want WAF to return to the web request client. You can define a custom response for a rule action or a default web ACL action that is set to block. To do this, you first define the response body key and value in the CustomResponseBodies setting for the WebACL or RuleGroup where you want to use it. Then, in the rule action or web ACL default action BlockAction setting, you reference the response body using this key.

            • ResponseHeaders — (Array<map>)

              The HTTP headers to use in the response. Duplicate header names are not allowed.

              For information about the limits on count and size for custom request and response settings, see WAF quotas in the WAF Developer Guide.

              • Name — required — (String)

                The name of the custom header.

                For custom request header insertion, when WAF inserts the header into the request, it prefixes this name x-amzn-waf-, to avoid confusion with the headers that are already in the request. For example, for the header name sample, WAF inserts the header x-amzn-waf-sample.

              • Value — required — (String)

                The value of the custom header.

        • Allow — (map)

          Instructs WAF to allow the web request.

          • CustomRequestHandling — (map)

            Defines custom handling for the web request.

            For information about customizing web requests and responses, see Customizing web requests and responses in WAF in the WAF Developer Guide.

            • InsertHeaders — required — (Array<map>)

              The HTTP headers to insert into the request. Duplicate header names are not allowed.

              For information about the limits on count and size for custom request and response settings, see WAF quotas in the WAF Developer Guide.

              • Name — required — (String)

                The name of the custom header.

                For custom request header insertion, when WAF inserts the header into the request, it prefixes this name x-amzn-waf-, to avoid confusion with the headers that are already in the request. For example, for the header name sample, WAF inserts the header x-amzn-waf-sample.

              • Value — required — (String)

                The value of the custom header.

        • Count — (map)

          Instructs WAF to count the web request and allow it.

          • CustomRequestHandling — (map)

            Defines custom handling for the web request.

            For information about customizing web requests and responses, see Customizing web requests and responses in WAF in the WAF Developer Guide.

            • InsertHeaders — required — (Array<map>)

              The HTTP headers to insert into the request. Duplicate header names are not allowed.

              For information about the limits on count and size for custom request and response settings, see WAF quotas in the WAF Developer Guide.

              • Name — required — (String)

                The name of the custom header.

                For custom request header insertion, when WAF inserts the header into the request, it prefixes this name x-amzn-waf-, to avoid confusion with the headers that are already in the request. For example, for the header name sample, WAF inserts the header x-amzn-waf-sample.

              • Value — required — (String)

                The value of the custom header.

        • Captcha — (map)

          Instructs WAF to run a CAPTCHA check against the web request.

          • CustomRequestHandling — (map)

            Defines custom handling for the web request.

            For information about customizing web requests and responses, see Customizing web requests and responses in WAF in the WAF Developer Guide.

            • InsertHeaders — required — (Array<map>)

              The HTTP headers to insert into the request. Duplicate header names are not allowed.

              For information about the limits on count and size for custom request and response settings, see WAF quotas in the WAF Developer Guide.

              • Name — required — (String)

                The name of the custom header.

                For custom request header insertion, when WAF inserts the header into the request, it prefixes this name x-amzn-waf-, to avoid confusion with the headers that are already in the request. For example, for the header name sample, WAF inserts the header x-amzn-waf-sample.

              • Value — required — (String)

                The value of the custom header.

      • OverrideAction — (map)

        The action to use in the place of the action that results from the rule group evaluation. Set the override action to none to leave the result of the rule group alone. Set it to count to override the result to count only.

        You can only use this for rule statements that reference a rule group, like RuleGroupReferenceStatement and ManagedRuleGroupStatement.

        Note: This option is usually set to none. It does not affect how the rules in the rule group are evaluated. If you want the rules in the rule group to only count matches, do not use this and instead exclude those rules in your rule group reference statement settings.
        • Count — (map)

          Override the rule group evaluation result to count only.

          Note: This option is usually set to none. It does not affect how the rules in the rule group are evaluated. If you want the rules in the rule group to only count matches, do not use this and instead exclude those rules in your rule group reference statement settings.
          • CustomRequestHandling — (map)

            Defines custom handling for the web request.

            For information about customizing web requests and responses, see Customizing web requests and responses in WAF in the WAF Developer Guide.

            • InsertHeaders — required — (Array<map>)

              The HTTP headers to insert into the request. Duplicate header names are not allowed.

              For information about the limits on count and size for custom request and response settings, see WAF quotas in the WAF Developer Guide.

              • Name — required — (String)

                The name of the custom header.

                For custom request header insertion, when WAF inserts the header into the request, it prefixes this name x-amzn-waf-, to avoid confusion with the headers that are already in the request. For example, for the header name sample, WAF inserts the header x-amzn-waf-sample.

              • Value — required — (String)

                The value of the custom header.

        • None — (map)

          Don't override the rule group evaluation result. This is the most common setting.

      • RuleLabels — (Array<map>)

        Labels to apply to web requests that match the rule match statement. WAF applies fully qualified labels to matching web requests. A fully qualified label is the concatenation of a label namespace and a rule label. The rule's rule group or web ACL defines the label namespace.

        Rules that run after this rule in the web ACL can match against these labels using a LabelMatchStatement.

        For each label, provide a case-sensitive string containing optional namespaces and a label name, according to the following guidelines:

        • Separate each component of the label with a colon.

        • Each namespace or name can have up to 128 characters.

        • You can specify up to 5 namespaces in a label.

        • Don't use the following reserved words in your label specification: aws, waf, managed, rulegroup, webacl, regexpatternset, or ipset.

        For example, myLabelName or nameSpace1:nameSpace2:myLabelName.

        • Name — required — (String)

          The label string.

      • VisibilityConfig — required — (map)

        Defines and enables Amazon CloudWatch metrics and web request sample collection.

        • SampledRequestsEnabled — required — (Boolean)

          A boolean indicating whether WAF should store a sampling of the web requests that match the rules. You can view the sampled requests through the WAF console.

        • CloudWatchMetricsEnabled — required — (Boolean)

          A boolean indicating whether the associated resource sends metrics to Amazon CloudWatch. For the list of available metrics, see WAF Metrics.

        • MetricName — required — (String)

          A name of the Amazon CloudWatch metric. The name can contain only the characters: A-Z, a-z, 0-9, - (hyphen), and _ (underscore). The name can be from one to 128 characters long. It can't contain whitespace or metric names reserved for WAF, for example "All" and "Default_Action."

      • CaptchaConfig — (map)

        Specifies how WAF should handle CAPTCHA evaluations. If you don't specify this, WAF uses the CAPTCHA configuration that's defined for the web ACL.

        • ImmunityTimeProperty — (map)

          Determines how long a CAPTCHA token remains valid after the client successfully solves a CAPTCHA puzzle.

          • ImmunityTime — required — (Integer)

            The amount of time, in seconds, that a CAPTCHA token is valid. The default setting is 300.

    • VisibilityConfig — (map)

      Defines and enables Amazon CloudWatch metrics and web request sample collection.

      • SampledRequestsEnabled — required — (Boolean)

        A boolean indicating whether WAF should store a sampling of the web requests that match the rules. You can view the sampled requests through the WAF console.

      • CloudWatchMetricsEnabled — required — (Boolean)

        A boolean indicating whether the associated resource sends metrics to Amazon CloudWatch. For the list of available metrics, see WAF Metrics.

      • MetricName — required — (String)

        A name of the Amazon CloudWatch metric. The name can contain only the characters: A-Z, a-z, 0-9, - (hyphen), and _ (underscore). The name can be from one to 128 characters long. It can't contain whitespace or metric names reserved for WAF, for example "All" and "Default_Action."

    • Tags — (Array<map>)

      An array of key:value pairs to associate with the resource.

      • Key — required — (String)

        Part of the key:value pair that defines a tag. You can use a tag key to describe a category of information, such as "customer." Tag keys are case-sensitive.

      • Value — required — (String)

        Part of the key:value pair that defines a tag. You can use a tag value to describe a specific value within a category, such as "companyA" or "companyB." Tag values are case-sensitive.

    • CustomResponseBodies — (map<map>)

      A map of custom response keys and content bodies. When you create a rule with a block action, you can send a custom response to the web request. You define these for the rule group, and then use them in the rules that you define in the rule group.

      For information about customizing web requests and responses, see Customizing web requests and responses in WAF in the WAF Developer Guide.

      For information about the limits on count and size for custom request and response settings, see WAF quotas in the WAF Developer Guide.

      • ContentType — required — (String)

        The type of content in the payload that you are defining in the Content string.

        Possible values include:
        • "TEXT_PLAIN"
        • "TEXT_HTML"
        • "APPLICATION_JSON"
      • Content — required — (String)

        The payload of the custom response.

        You can use JSON escape strings in JSON content. To do this, you must specify JSON content in the ContentType setting.

        For information about the limits on count and size for custom request and response settings, see WAF quotas in the WAF Developer Guide.

Callback (callback):

  • function(err, data) { ... }

    Called when a response from the service is returned. If a callback is not supplied, you must call AWS.Request.send() on the returned request object to initiate the request.

    Context (this):

    • (AWS.Response) —

      the response object containing error, data properties, and the original request object.

    Parameters:

    • err (Error) —

      the error object returned from the request. Set to null if the request is successful.

    • data (Object) —

      the de-serialized data returned from the request. Set to null if a request error occurs. The data object has the following properties:

      • Summary — (map)

        High-level information about a RuleGroup, returned by operations like create and list. This provides information like the ID, that you can use to retrieve and manage a RuleGroup, and the ARN, that you provide to the RuleGroupReferenceStatement to use the rule group in a Rule.

        • Name — (String)

          The name of the data type instance. You cannot change the name after you create the instance.

        • Id — (String)

          A unique identifier for the rule group. This ID is returned in the responses to create and list commands. You provide it to operations like update and delete.

        • Description — (String)

          A description of the rule group that helps with identification.

        • LockToken — (String)

          A token used for optimistic locking. WAF returns a token to your get and list requests, to mark the state of the entity at the time of the request. To make changes to the entity associated with the token, you provide the token to operations like update and delete. WAF uses the token to ensure that no changes have been made to the entity since you last retrieved it. If a change has been made, the update fails with a WAFOptimisticLockException. If this happens, perform another get, and use the new token returned by that operation.

        • ARN — (String)

          The Amazon Resource Name (ARN) of the entity.

Returns:

  • (AWS.Request) —

    a handle to the operation request for subsequent event callback registration.

createWebACL(params = {}, callback) ⇒ AWS.Request

Creates a WebACL per the specifications provided.

A web ACL defines a collection of rules to use to inspect and control web requests. Each rule has an action defined (allow, block, or count) for requests that match the statement of the rule. In the web ACL, you assign a default action to take (allow, block) for any request that does not match any of the rules. The rules in a web ACL can be a combination of the types Rule, RuleGroup, and managed rule group. You can associate a web ACL with one or more Amazon Web Services resources to protect. The resources can be an Amazon CloudFront distribution, an Amazon API Gateway REST API, an Application Load Balancer, or an AppSync GraphQL API.

Service Reference:

Examples:

Calling the createWebACL operation

var params = {
  DefaultAction: { /* required */
    Allow: {
      CustomRequestHandling: {
        InsertHeaders: [ /* required */
          {
            Name: 'STRING_VALUE', /* required */
            Value: 'STRING_VALUE' /* required */
          },
          /* more items */
        ]
      }
    },
    Block: {
      CustomResponse: {
        ResponseCode: 'NUMBER_VALUE', /* required */
        CustomResponseBodyKey: 'STRING_VALUE',
        ResponseHeaders: [
          {
            Name: 'STRING_VALUE', /* required */
            Value: 'STRING_VALUE' /* required */
          },
          /* more items */
        ]
      }
    }
  },
  Name: 'STRING_VALUE', /* required */
  Scope: CLOUDFRONT | REGIONAL, /* required */
  VisibilityConfig: { /* required */
    CloudWatchMetricsEnabled: true || false, /* required */
    MetricName: 'STRING_VALUE', /* required */
    SampledRequestsEnabled: true || false /* required */
  },
  CaptchaConfig: {
    ImmunityTimeProperty: {
      ImmunityTime: 'NUMBER_VALUE' /* required */
    }
  },
  CustomResponseBodies: {
    '<EntityName>': {
      Content: 'STRING_VALUE', /* required */
      ContentType: TEXT_PLAIN | TEXT_HTML | APPLICATION_JSON /* required */
    },
    /* '<EntityName>': ... */
  },
  Description: 'STRING_VALUE',
  Rules: [
    {
      Name: 'STRING_VALUE', /* required */
      Priority: 'NUMBER_VALUE', /* required */
      Statement: { /* Statement */ /* required */
        AndStatement: {
          Statements: [ /* required */
            /* recursive Statement */,
            /* more items */
          ]
        },
        ByteMatchStatement: {
          FieldToMatch: { /* required */
            AllQueryArguments: {
            },
            Body: {
            },
            JsonBody: {
              MatchPattern: { /* required */
                All: {
                },
                IncludedPaths: [
                  'STRING_VALUE',
                  /* more items */
                ]
              },
              MatchScope: ALL | KEY | VALUE, /* required */
              InvalidFallbackBehavior: MATCH | NO_MATCH | EVALUATE_AS_STRING
            },
            Method: {
            },
            QueryString: {
            },
            SingleHeader: {
              Name: 'STRING_VALUE' /* required */
            },
            SingleQueryArgument: {
              Name: 'STRING_VALUE' /* required */
            },
            UriPath: {
            }
          },
          PositionalConstraint: EXACTLY | STARTS_WITH | ENDS_WITH | CONTAINS | CONTAINS_WORD, /* required */
          SearchString: Buffer.from('...') || 'STRING_VALUE' /* Strings will be Base-64 encoded on your behalf */, /* required */
          TextTransformations: [ /* required */
            {
              Priority: 'NUMBER_VALUE', /* required */
              Type: NONE | COMPRESS_WHITE_SPACE | HTML_ENTITY_DECODE | LOWERCASE | CMD_LINE | URL_DECODE | BASE64_DECODE | HEX_DECODE | MD5 | REPLACE_COMMENTS | ESCAPE_SEQ_DECODE | SQL_HEX_DECODE | CSS_DECODE | JS_DECODE | NORMALIZE_PATH | NORMALIZE_PATH_WIN | REMOVE_NULLS | REPLACE_NULLS | BASE64_DECODE_EXT | URL_DECODE_UNI | UTF8_TO_UNICODE /* required */
            },
            /* more items */
          ]
        },
        GeoMatchStatement: {
          CountryCodes: [
            AF | AX | AL | DZ | AS | AD | AO | AI | AQ | AG | AR | AM | AW | AU | AT | AZ | BS | BH | BD | BB | BY | BE | BZ | BJ | BM | BT | BO | BQ | BA | BW | BV | BR | IO | BN | BG | BF | BI | KH | CM | CA | CV | KY | CF | TD | CL | CN | CX | CC | CO | KM | CG | CD | CK | CR | CI | HR | CU | CW | CY | CZ | DK | DJ | DM | DO | EC | EG | SV | GQ | ER | EE | ET | FK | FO | FJ | FI | FR | GF | PF | TF | GA | GM | GE | DE | GH | GI | GR | GL | GD | GP | GU | GT | GG | GN | GW | GY | HT | HM | VA | HN | HK | HU | IS | IN | ID | IR | IQ | IE | IM | IL | IT | JM | JP | JE | JO | KZ | KE | KI | KP | KR | KW | KG | LA | LV | LB | LS | LR | LY | LI | LT | LU | MO | MK | MG | MW | MY | MV | ML | MT | MH | MQ | MR | MU | YT | MX | FM | MD | MC | MN | ME | MS | MA | MZ | MM | NA | NR | NP | NL | NC | NZ | NI | NE | NG | NU | NF | MP | NO | OM | PK | PW | PS | PA | PG | PY | PE | PH | PN | PL | PT | PR | QA | RE | RO | RU | RW | BL | SH | KN | LC | MF | PM | VC | WS | SM | ST | SA | SN | RS | SC | SL | SG | SX | SK | SI | SB | SO | ZA | GS | SS | ES | LK | SD | SR | SJ | SZ | SE | CH | SY | TW | TJ | TZ | TH | TL | TG | TK | TO | TT | TN | TR | TM | TC | TV | UG | UA | AE | GB | US | UM | UY | UZ | VU | VE | VN | VG | VI | WF | EH | YE | ZM | ZW,
            /* more items */
          ],
          ForwardedIPConfig: {
            FallbackBehavior: MATCH | NO_MATCH, /* required */
            HeaderName: 'STRING_VALUE' /* required */
          }
        },
        IPSetReferenceStatement: {
          ARN: 'STRING_VALUE', /* required */
          IPSetForwardedIPConfig: {
            FallbackBehavior: MATCH | NO_MATCH, /* required */
            HeaderName: 'STRING_VALUE', /* required */
            Position: FIRST | LAST | ANY /* required */
          }
        },
        LabelMatchStatement: {
          Key: 'STRING_VALUE', /* required */
          Scope: LABEL | NAMESPACE /* required */
        },
        ManagedRuleGroupStatement: {
          Name: 'STRING_VALUE', /* required */
          VendorName: 'STRING_VALUE', /* required */
          ExcludedRules: [
            {
              Name: 'STRING_VALUE' /* required */
            },
            /* more items */
          ],
          ScopeDownStatement: /* recursive Statement */,
          Version: 'STRING_VALUE'
        },
        NotStatement: {
          Statement: /* recursive Statement */
        },
        OrStatement: {
          Statements: [ /* required */
            /* recursive Statement */,
            /* more items */
          ]
        },
        RateBasedStatement: {
          AggregateKeyType: IP | FORWARDED_IP, /* required */
          Limit: 'NUMBER_VALUE', /* required */
          ForwardedIPConfig: {
            FallbackBehavior: MATCH | NO_MATCH, /* required */
            HeaderName: 'STRING_VALUE' /* required */
          },
          ScopeDownStatement: /* recursive Statement */
        },
        RegexMatchStatement: {
          FieldToMatch: { /* required */
            AllQueryArguments: {
            },
            Body: {
            },
            JsonBody: {
              MatchPattern: { /* required */
                All: {
                },
                IncludedPaths: [
                  'STRING_VALUE',
                  /* more items */
                ]
              },
              MatchScope: ALL | KEY | VALUE, /* required */
              InvalidFallbackBehavior: MATCH | NO_MATCH | EVALUATE_AS_STRING
            },
            Method: {
            },
            QueryString: {
            },
            SingleHeader: {
              Name: 'STRING_VALUE' /* required */
            },
            SingleQueryArgument: {
              Name: 'STRING_VALUE' /* required */
            },
            UriPath: {
            }
          },
          RegexString: 'STRING_VALUE', /* required */
          TextTransformations: [ /* required */
            {
              Priority: 'NUMBER_VALUE', /* required */
              Type: NONE | COMPRESS_WHITE_SPACE | HTML_ENTITY_DECODE | LOWERCASE | CMD_LINE | URL_DECODE | BASE64_DECODE | HEX_DECODE | MD5 | REPLACE_COMMENTS | ESCAPE_SEQ_DECODE | SQL_HEX_DECODE | CSS_DECODE | JS_DECODE | NORMALIZE_PATH | NORMALIZE_PATH_WIN | REMOVE_NULLS | REPLACE_NULLS | BASE64_DECODE_EXT | URL_DECODE_UNI | UTF8_TO_UNICODE /* required */
            },
            /* more items */
          ]
        },
        RegexPatternSetReferenceStatement: {
          ARN: 'STRING_VALUE', /* required */
          FieldToMatch: { /* required */
            AllQueryArguments: {
            },
            Body: {
            },
            JsonBody: {
              MatchPattern: { /* required */
                All: {
                },
                IncludedPaths: [
                  'STRING_VALUE',
                  /* more items */
                ]
              },
              MatchScope: ALL | KEY | VALUE, /* required */
              InvalidFallbackBehavior: MATCH | NO_MATCH | EVALUATE_AS_STRING
            },
            Method: {
            },
            QueryString: {
            },
            SingleHeader: {
              Name: 'STRING_VALUE' /* required */
            },
            SingleQueryArgument: {
              Name: 'STRING_VALUE' /* required */
            },
            UriPath: {
            }
          },
          TextTransformations: [ /* required */
            {
              Priority: 'NUMBER_VALUE', /* required */
              Type: NONE | COMPRESS_WHITE_SPACE | HTML_ENTITY_DECODE | LOWERCASE | CMD_LINE | URL_DECODE | BASE64_DECODE | HEX_DECODE | MD5 | REPLACE_COMMENTS | ESCAPE_SEQ_DECODE | SQL_HEX_DECODE | CSS_DECODE | JS_DECODE | NORMALIZE_PATH | NORMALIZE_PATH_WIN | REMOVE_NULLS | REPLACE_NULLS | BASE64_DECODE_EXT | URL_DECODE_UNI | UTF8_TO_UNICODE /* required */
            },
            /* more items */
          ]
        },
        RuleGroupReferenceStatement: {
          ARN: 'STRING_VALUE', /* required */
          ExcludedRules: [
            {
              Name: 'STRING_VALUE' /* required */
            },
            /* more items */
          ]
        },
        SizeConstraintStatement: {
          ComparisonOperator: EQ | NE | LE | LT | GE | GT, /* required */
          FieldToMatch: { /* required */
            AllQueryArguments: {
            },
            Body: {
            },
            JsonBody: {
              MatchPattern: { /* required */
                All: {
                },
                IncludedPaths: [
                  'STRING_VALUE',
                  /* more items */
                ]
              },
              MatchScope: ALL | KEY | VALUE, /* required */
              InvalidFallbackBehavior: MATCH | NO_MATCH | EVALUATE_AS_STRING
            },
            Method: {
            },
            QueryString: {
            },
            SingleHeader: {
              Name: 'STRING_VALUE' /* required */
            },
            SingleQueryArgument: {
              Name: 'STRING_VALUE' /* required */
            },
            UriPath: {
            }
          },
          Size: 'NUMBER_VALUE', /* required */
          TextTransformations: [ /* required */
            {
              Priority: 'NUMBER_VALUE', /* required */
              Type: NONE | COMPRESS_WHITE_SPACE | HTML_ENTITY_DECODE | LOWERCASE | CMD_LINE | URL_DECODE | BASE64_DECODE | HEX_DECODE | MD5 | REPLACE_COMMENTS | ESCAPE_SEQ_DECODE | SQL_HEX_DECODE | CSS_DECODE | JS_DECODE | NORMALIZE_PATH | NORMALIZE_PATH_WIN | REMOVE_NULLS | REPLACE_NULLS | BASE64_DECODE_EXT | URL_DECODE_UNI | UTF8_TO_UNICODE /* required */
            },
            /* more items */
          ]
        },
        SqliMatchStatement: {
          FieldToMatch: { /* required */
            AllQueryArguments: {
            },
            Body: {
            },
            JsonBody: {
              MatchPattern: { /* required */
                All: {
                },
                IncludedPaths: [
                  'STRING_VALUE',
                  /* more items */
                ]
              },
              MatchScope: ALL | KEY | VALUE, /* required */
              InvalidFallbackBehavior: MATCH | NO_MATCH | EVALUATE_AS_STRING
            },
            Method: {
            },
            QueryString: {
            },
            SingleHeader: {
              Name: 'STRING_VALUE' /* required */
            },
            SingleQueryArgument: {
              Name: 'STRING_VALUE' /* required */
            },
            UriPath: {
            }
          },
          TextTransformations: [ /* required */
            {
              Priority: 'NUMBER_VALUE', /* required */
              Type: NONE | COMPRESS_WHITE_SPACE | HTML_ENTITY_DECODE | LOWERCASE | CMD_LINE | URL_DECODE | BASE64_DECODE | HEX_DECODE | MD5 | REPLACE_COMMENTS | ESCAPE_SEQ_DECODE | SQL_HEX_DECODE | CSS_DECODE | JS_DECODE | NORMALIZE_PATH | NORMALIZE_PATH_WIN | REMOVE_NULLS | REPLACE_NULLS | BASE64_DECODE_EXT | URL_DECODE_UNI | UTF8_TO_UNICODE /* required */
            },
            /* more items */
          ]
        },
        XssMatchStatement: {
          FieldToMatch: { /* required */
            AllQueryArguments: {
            },
            Body: {
            },
            JsonBody: {
              MatchPattern: { /* required */
                All: {
                },
                IncludedPaths: [
                  'STRING_VALUE',
                  /* more items */
                ]
              },
              MatchScope: ALL | KEY | VALUE, /* required */
              InvalidFallbackBehavior: MATCH | NO_MATCH | EVALUATE_AS_STRING
            },
            Method: {
            },
            QueryString: {
            },
            SingleHeader: {
              Name: 'STRING_VALUE' /* required */
            },
            SingleQueryArgument: {
              Name: 'STRING_VALUE' /* required */
            },
            UriPath: {
            }
          },
          TextTransformations: [ /* required */
            {
              Priority: 'NUMBER_VALUE', /* required */
              Type: NONE | COMPRESS_WHITE_SPACE | HTML_ENTITY_DECODE | LOWERCASE | CMD_LINE | URL_DECODE | BASE64_DECODE | HEX_DECODE | MD5 | REPLACE_COMMENTS | ESCAPE_SEQ_DECODE | SQL_HEX_DECODE | CSS_DECODE | JS_DECODE | NORMALIZE_PATH | NORMALIZE_PATH_WIN | REMOVE_NULLS | REPLACE_NULLS | BASE64_DECODE_EXT | URL_DECODE_UNI | UTF8_TO_UNICODE /* required */
            },
            /* more items */
          ]
        }
      },
      VisibilityConfig: { /* required */
        CloudWatchMetricsEnabled: true || false, /* required */
        MetricName: 'STRING_VALUE', /* required */
        SampledRequestsEnabled: true || false /* required */
      },
      Action: {
        Allow: {
          CustomRequestHandling: {
            InsertHeaders: [ /* required */
              {
                Name: 'STRING_VALUE', /* required */
                Value: 'STRING_VALUE' /* required */
              },
              /* more items */
            ]
          }
        },
        Block: {
          CustomResponse: {
            ResponseCode: 'NUMBER_VALUE', /* required */
            CustomResponseBodyKey: 'STRING_VALUE',
            ResponseHeaders: [
              {
                Name: 'STRING_VALUE', /* required */
                Value: 'STRING_VALUE' /* required */
              },
              /* more items */
            ]
          }
        },
        Captcha: {
          CustomRequestHandling: {
            InsertHeaders: [ /* required */
              {
                Name: 'STRING_VALUE', /* required */
                Value: 'STRING_VALUE' /* required */
              },
              /* more items */
            ]
          }
        },
        Count: {
          CustomRequestHandling: {
            InsertHeaders: [ /* required */
              {
                Name: 'STRING_VALUE', /* required */
                Value: 'STRING_VALUE' /* required */
              },
              /* more items */
            ]
          }
        }
      },
      CaptchaConfig: {
        ImmunityTimeProperty: {
          ImmunityTime: 'NUMBER_VALUE' /* required */
        }
      },
      OverrideAction: {
        Count: {
          CustomRequestHandling: {
            InsertHeaders: [ /* required */
              {
                Name: 'STRING_VALUE', /* required */
                Value: 'STRING_VALUE' /* required */
              },
              /* more items */
            ]
          }
        },
        None: {
        }
      },
      RuleLabels: [
        {
          Name: 'STRING_VALUE' /* required */
        },
        /* more items */
      ]
    },
    /* more items */
  ],
  Tags: [
    {
      Key: 'STRING_VALUE', /* required */
      Value: 'STRING_VALUE' /* required */
    },
    /* more items */
  ]
};
wafv2.createWebACL(params, function(err, data) {
  if (err) console.log(err, err.stack); // an error occurred
  else     console.log(data);           // successful response
});

Parameters:

  • params (Object) (defaults to: {}) —
    • Name — (String)

      The name of the web ACL. You cannot change the name of a web ACL after you create it.

    • Scope — (String)

      Specifies whether this is for an Amazon CloudFront distribution or for a regional application. A regional application can be an Application Load Balancer (ALB), an Amazon API Gateway REST API, or an AppSync GraphQL API.

      To work with CloudFront, you must also specify the Region US East (N. Virginia) as follows:

      • CLI - Specify the Region when you use the CloudFront scope: --scope=CLOUDFRONT --region=us-east-1.

      • API and SDKs - For all calls, use the Region endpoint us-east-1.

      Possible values include:
      • "CLOUDFRONT"
      • "REGIONAL"
    • DefaultAction — (map)

      The action to perform if none of the Rules contained in the WebACL match.

      • Block — (map)

        Specifies that WAF should block requests by default.

        • CustomResponse — (map)

          Defines a custom response for the web request.

          For information about customizing web requests and responses, see Customizing web requests and responses in WAF in the WAF Developer Guide.

          • ResponseCode — required — (Integer)

            The HTTP status code to return to the client.

            For a list of status codes that you can use in your custom reqponses, see Supported status codes for custom response in the WAF Developer Guide.

          • CustomResponseBodyKey — (String)

            References the response body that you want WAF to return to the web request client. You can define a custom response for a rule action or a default web ACL action that is set to block. To do this, you first define the response body key and value in the CustomResponseBodies setting for the WebACL or RuleGroup where you want to use it. Then, in the rule action or web ACL default action BlockAction setting, you reference the response body using this key.

          • ResponseHeaders — (Array<map>)

            The HTTP headers to use in the response. Duplicate header names are not allowed.

            For information about the limits on count and size for custom request and response settings, see WAF quotas in the WAF Developer Guide.

            • Name — required — (String)

              The name of the custom header.

              For custom request header insertion, when WAF inserts the header into the request, it prefixes this name x-amzn-waf-, to avoid confusion with the headers that are already in the request. For example, for the header name sample, WAF inserts the header x-amzn-waf-sample.

            • Value — required — (String)

              The value of the custom header.

      • Allow — (map)

        Specifies that WAF should allow requests by default.

        • CustomRequestHandling — (map)

          Defines custom handling for the web request.

          For information about customizing web requests and responses, see Customizing web requests and responses in WAF in the WAF Developer Guide.

          • InsertHeaders — required — (Array<map>)

            The HTTP headers to insert into the request. Duplicate header names are not allowed.

            For information about the limits on count and size for custom request and response settings, see WAF quotas in the WAF Developer Guide.

            • Name — required — (String)

              The name of the custom header.

              For custom request header insertion, when WAF inserts the header into the request, it prefixes this name x-amzn-waf-, to avoid confusion with the headers that are already in the request. For example, for the header name sample, WAF inserts the header x-amzn-waf-sample.

            • Value — required — (String)

              The value of the custom header.

    • Description — (String)

      A description of the web ACL that helps with identification.

    • Rules — (Array<map>)

      The Rule statements used to identify the web requests that you want to allow, block, or count. Each rule includes one top-level statement that WAF uses to identify matching web requests, and parameters that govern how WAF handles them.

      • Name — required — (String)

        The name of the rule. You can't change the name of a Rule after you create it.

      • Priority — required — (Integer)

        If you define more than one Rule in a WebACL, WAF evaluates each request against the Rules in order based on the value of Priority. WAF processes rules with lower priority first. The priorities don't need to be consecutive, but they must all be different.

      • Statement — required — (map)

        The WAF processing statement for the rule, for example ByteMatchStatement or SizeConstraintStatement.

        • ByteMatchStatement — (map)

          A rule statement that defines a string match search for WAF to apply to web requests. The byte match statement provides the bytes to search for, the location in requests that you want WAF to search, and other settings. The bytes to search for are typically a string that corresponds with ASCII characters. In the WAF console and the developer guide, this is refered to as a string match statement.

          • SearchString — required — (Buffer, Typed Array, Blob, String)

            A string value that you want WAF to search for. WAF searches only in the part of web requests that you designate for inspection in FieldToMatch. The maximum length of the value is 50 bytes.

            Valid values depend on the component that you specify for inspection in FieldToMatch:

            • Method: The HTTP method that you want WAF to search for. This indicates the type of operation specified in the request.

            • UriPath: The value that you want WAF to search for in the URI path, for example, /images/daily-ad.jpg.

            If SearchString includes alphabetic characters A-Z and a-z, note that the value is case sensitive.

            If you're using the WAF API

            Specify a base64-encoded version of the value. The maximum length of the value before you base64-encode it is 50 bytes.

            For example, suppose the value of Type is HEADER and the value of Data is User-Agent. If you want to search the User-Agent header for the value BadBot, you base64-encode BadBot using MIME base64-encoding and include the resulting value, QmFkQm90, in the value of SearchString.

            If you're using the CLI or one of the Amazon Web Services SDKs

            The value that you want WAF to search for. The SDK automatically base64 encodes the value.

          • FieldToMatch — required — (map)

            The part of a web request that you want WAF to inspect. For more information, see FieldToMatch.

            • SingleHeader — (map)

              Inspect a single header. Provide the name of the header to inspect, for example, User-Agent or Referer. This setting isn't case sensitive.

              Example JSON: "SingleHeader": { "Name": "haystack" }

              • Name — required — (String)

                The name of the query header to inspect.

            • SingleQueryArgument — (map)

              Inspect a single query argument. Provide the name of the query argument to inspect, such as UserName or SalesRegion. The name can be up to 30 characters long and isn't case sensitive.

              This is used only to indicate the web request component for WAF to inspect, in the FieldToMatch specification.

              Example JSON: "SingleQueryArgument": { "Name": "myArgument" }

              • Name — required — (String)

                The name of the query argument to inspect.

            • AllQueryArguments — (map)

              Inspect all query arguments.

            • UriPath — (map)

              Inspect the request URI path. This is the part of a web request that identifies a resource, for example, /images/daily-ad.jpg.

            • QueryString — (map)

              Inspect the query string. This is the part of a URL that appears after a ? character, if any.

            • Body — (map)

              Inspect the request body as plain text. The request body immediately follows the request headers. This is the part of a request that contains any additional data that you want to send to your web server as the HTTP request body, such as data from a form.

              Note that only the first 8 KB (8192 bytes) of the request body are forwarded to WAF for inspection by the underlying host service. If you don't need to inspect more than 8 KB, you can guarantee that you don't allow additional bytes in by combining a statement that inspects the body of the web request, such as ByteMatchStatement or RegexPatternSetReferenceStatement, with a SizeConstraintStatement that enforces an 8 KB size limit on the body of the request. WAF doesn't support inspecting the entire contents of web requests whose bodies exceed the 8 KB limit.

            • Method — (map)

              Inspect the HTTP method. The method indicates the type of operation that the request is asking the origin to perform.

            • JsonBody — (map)

              Inspect the request body as JSON. The request body immediately follows the request headers. This is the part of a request that contains any additional data that you want to send to your web server as the HTTP request body, such as data from a form.

              Note that only the first 8 KB (8192 bytes) of the request body are forwarded to WAF for inspection by the underlying host service. If you don't need to inspect more than 8 KB, you can guarantee that you don't allow additional bytes in by combining a statement that inspects the body of the web request, such as ByteMatchStatement or RegexPatternSetReferenceStatement, with a SizeConstraintStatement that enforces an 8 KB size limit on the body of the request. WAF doesn't support inspecting the entire contents of web requests whose bodies exceed the 8 KB limit.

              • MatchPattern — required — (map)

                The patterns to look for in the JSON body. WAF inspects the results of these pattern matches against the rule inspection criteria.

                • All — (map)

                  Match all of the elements. See also MatchScope in JsonBody.

                  You must specify either this setting or the IncludedPaths setting, but not both.

                • IncludedPaths — (Array<String>)

                  Match only the specified include paths. See also MatchScope in JsonBody.

                  Provide the include paths using JSON Pointer syntax. For example, "IncludedPaths": ["/dogs/0/name", "/dogs/1/name"]. For information about this syntax, see the Internet Engineering Task Force (IETF) documentation JavaScript Object Notation (JSON) Pointer.

                  You must specify either this setting or the All setting, but not both.

                  Note: Don't use this option to include all paths. Instead, use the All setting.
              • MatchScope — required — (String)

                The parts of the JSON to match against using the MatchPattern. If you specify All, WAF matches against keys and values.

                Possible values include:
                • "ALL"
                • "KEY"
                • "VALUE"
              • InvalidFallbackBehavior — (String)

                What WAF should do if it fails to completely parse the JSON body. The options are the following:

                • EVALUATE_AS_STRING - Inspect the body as plain text. WAF applies the text transformations and inspection criteria that you defined for the JSON inspection to the body text string.

                • MATCH - Treat the web request as matching the rule statement. WAF applies the rule action to the request.

                • NO_MATCH - Treat the web request as not matching the rule statement.

                If you don't provide this setting, WAF parses and evaluates the content only up to the first parsing failure that it encounters.

                WAF does its best to parse the entire JSON body, but might be forced to stop for reasons such as invalid characters, duplicate keys, truncation, and any content whose root node isn't an object or an array.

                WAF parses the JSON in the following examples as two valid key, value pairs:

                • Missing comma: {"key1":"value1""key2":"value2"}

                • Missing colon: {"key1":"value1","key2""value2"}

                • Extra colons: {"key1"::"value1","key2""value2"}

                Possible values include:
                • "MATCH"
                • "NO_MATCH"
                • "EVALUATE_AS_STRING"
          • TextTransformations — required — (Array<map>)

            Text transformations eliminate some of the unusual formatting that attackers use in web requests in an effort to bypass detection. If you specify one or more transformations in a rule statement, WAF performs all transformations on the content of the request component identified by FieldToMatch, starting from the lowest priority setting, before inspecting the content for a match.

            • Priority — required — (Integer)

              Sets the relative processing order for multiple transformations that are defined for a rule statement. WAF processes all transformations, from lowest priority to highest, before inspecting the transformed content. The priorities don't need to be consecutive, but they must all be different.

            • Type — required — (String)

              You can specify the following transformation types:

              BASE64_DECODE - Decode a Base64-encoded string.

              BASE64_DECODE_EXT - Decode a Base64-encoded string, but use a forgiving implementation that ignores characters that aren't valid.

              CMD_LINE - Command-line transformations. These are helpful in reducing effectiveness of attackers who inject an operating system command-line command and use unusual formatting to disguise some or all of the command.

              • Delete the following characters: \ " ' ^

              • Delete spaces before the following characters: / (

              • Replace the following characters with a space: , ;

              • Replace multiple spaces with one space

              • Convert uppercase letters (A-Z) to lowercase (a-z)

              COMPRESS_WHITE_SPACE - Replace these characters with a space character (decimal 32):

              • \f, formfeed, decimal 12

              • \t, tab, decimal 9

              • \n, newline, decimal 10

              • \r, carriage return, decimal 13

              • \v, vertical tab, decimal 11

              • Non-breaking space, decimal 160

              COMPRESS_WHITE_SPACE also replaces multiple spaces with one space.

              CSS_DECODE - Decode characters that were encoded using CSS 2.x escape rules syndata.html#characters. This function uses up to two bytes in the decoding process, so it can help to uncover ASCII characters that were encoded using CSS encoding that wouldn’t typically be encoded. It's also useful in countering evasion, which is a combination of a backslash and non-hexadecimal characters. For example, ja\vascript for javascript.

              ESCAPE_SEQ_DECODE - Decode the following ANSI C escape sequences: \a, \b, \f, \n, \r, \t, \v, \, \?, \', \", \xHH (hexadecimal), \0OOO (octal). Encodings that aren't valid remain in the output.

              HEX_DECODE - Decode a string of hexadecimal characters into a binary.

              HTML_ENTITY_DECODE - Replace HTML-encoded characters with unencoded characters. HTML_ENTITY_DECODE performs these operations:

              • Replaces (ampersand)quot; with "

              • Replaces (ampersand)nbsp; with a non-breaking space, decimal 160

              • Replaces (ampersand)lt; with a "less than" symbol

              • Replaces (ampersand)gt; with >

              • Replaces characters that are represented in hexadecimal format, (ampersand)#xhhhh;, with the corresponding characters

              • Replaces characters that are represented in decimal format, (ampersand)#nnnn;, with the corresponding characters

              JS_DECODE - Decode JavaScript escape sequences. If a \ u HHHH code is in the full-width ASCII code range of FF01-FF5E, then the higher byte is used to detect and adjust the lower byte. If not, only the lower byte is used and the higher byte is zeroed, causing a possible loss of information.

              LOWERCASE - Convert uppercase letters (A-Z) to lowercase (a-z).

              MD5 - Calculate an MD5 hash from the data in the input. The computed hash is in a raw binary form.

              NONE - Specify NONE if you don't want any text transformations.

              NORMALIZE_PATH - Remove multiple slashes, directory self-references, and directory back-references that are not at the beginning of the input from an input string.

              NORMALIZE_PATH_WIN - This is the same as NORMALIZE_PATH, but first converts backslash characters to forward slashes.

              REMOVE_NULLS - Remove all NULL bytes from the input.

              REPLACE_COMMENTS - Replace each occurrence of a C-style comment (/* ... */) with a single space. Multiple consecutive occurrences are not compressed. Unterminated comments are also replaced with a space (ASCII 0x20). However, a standalone termination of a comment (*/) is not acted upon.

              REPLACE_NULLS - Replace NULL bytes in the input with space characters (ASCII 0x20).

              SQL_HEX_DECODE - Decode SQL hex data. Example (0x414243) will be decoded to (ABC).

              URL_DECODE - Decode a URL-encoded value.

              URL_DECODE_UNI - Like URL_DECODE, but with support for Microsoft-specific %u encoding. If the code is in the full-width ASCII code range of FF01-FF5E, the higher byte is used to detect and adjust the lower byte. Otherwise, only the lower byte is used and the higher byte is zeroed.

              UTF8_TO_UNICODE - Convert all UTF-8 character sequences to Unicode. This helps input normalization, and minimizing false-positives and false-negatives for non-English languages.

              Possible values include:
              • "NONE"
              • "COMPRESS_WHITE_SPACE"
              • "HTML_ENTITY_DECODE"
              • "LOWERCASE"
              • "CMD_LINE"
              • "URL_DECODE"
              • "BASE64_DECODE"
              • "HEX_DECODE"
              • "MD5"
              • "REPLACE_COMMENTS"
              • "ESCAPE_SEQ_DECODE"
              • "SQL_HEX_DECODE"
              • "CSS_DECODE"
              • "JS_DECODE"
              • "NORMALIZE_PATH"
              • "NORMALIZE_PATH_WIN"
              • "REMOVE_NULLS"
              • "REPLACE_NULLS"
              • "BASE64_DECODE_EXT"
              • "URL_DECODE_UNI"
              • "UTF8_TO_UNICODE"
          • PositionalConstraint — required — (String)

            The area within the portion of a web request that you want WAF to search for SearchString. Valid values include the following:

            CONTAINS

            The specified part of the web request must include the value of SearchString, but the location doesn't matter.

            CONTAINS_WORD

            The specified part of the web request must include the value of SearchString, and SearchString must contain only alphanumeric characters or underscore (A-Z, a-z, 0-9, or ). In addition, SearchString must be a word, which means that both of the following are true:

            • SearchString is at the beginning of the specified part of the web request or is preceded by a character other than an alphanumeric character or underscore (). Examples include the value of a header and ;BadBot.

            • SearchString is at the end of the specified part of the web request or is followed by a character other than an alphanumeric character or underscore (_), for example, BadBot; and -BadBot;.

            EXACTLY

            The value of the specified part of the web request must exactly match the value of SearchString.

            STARTS_WITH

            The value of SearchString must appear at the beginning of the specified part of the web request.

            ENDS_WITH

            The value of SearchString must appear at the end of the specified part of the web request.

            Possible values include:
            • "EXACTLY"
            • "STARTS_WITH"
            • "ENDS_WITH"
            • "CONTAINS"
            • "CONTAINS_WORD"
        • SqliMatchStatement — (map)

          Attackers sometimes insert malicious SQL code into web requests in an effort to extract data from your database. To allow or block web requests that appear to contain malicious SQL code, create one or more SQL injection match conditions. An SQL injection match condition identifies the part of web requests, such as the URI or the query string, that you want WAF to inspect. Later in the process, when you create a web ACL, you specify whether to allow or block requests that appear to contain malicious SQL code.

          • FieldToMatch — required — (map)

            The part of a web request that you want WAF to inspect. For more information, see FieldToMatch.

            • SingleHeader — (map)

              Inspect a single header. Provide the name of the header to inspect, for example, User-Agent or Referer. This setting isn't case sensitive.

              Example JSON: "SingleHeader": { "Name": "haystack" }

              • Name — required — (String)

                The name of the query header to inspect.

            • SingleQueryArgument — (map)

              Inspect a single query argument. Provide the name of the query argument to inspect, such as UserName or SalesRegion. The name can be up to 30 characters long and isn't case sensitive.

              This is used only to indicate the web request component for WAF to inspect, in the FieldToMatch specification.

              Example JSON: "SingleQueryArgument": { "Name": "myArgument" }

              • Name — required — (String)

                The name of the query argument to inspect.

            • AllQueryArguments — (map)

              Inspect all query arguments.

            • UriPath — (map)

              Inspect the request URI path. This is the part of a web request that identifies a resource, for example, /images/daily-ad.jpg.

            • QueryString — (map)

              Inspect the query string. This is the part of a URL that appears after a ? character, if any.

            • Body — (map)

              Inspect the request body as plain text. The request body immediately follows the request headers. This is the part of a request that contains any additional data that you want to send to your web server as the HTTP request body, such as data from a form.

              Note that only the first 8 KB (8192 bytes) of the request body are forwarded to WAF for inspection by the underlying host service. If you don't need to inspect more than 8 KB, you can guarantee that you don't allow additional bytes in by combining a statement that inspects the body of the web request, such as ByteMatchStatement or RegexPatternSetReferenceStatement, with a SizeConstraintStatement that enforces an 8 KB size limit on the body of the request. WAF doesn't support inspecting the entire contents of web requests whose bodies exceed the 8 KB limit.

            • Method — (map)

              Inspect the HTTP method. The method indicates the type of operation that the request is asking the origin to perform.

            • JsonBody — (map)

              Inspect the request body as JSON. The request body immediately follows the request headers. This is the part of a request that contains any additional data that you want to send to your web server as the HTTP request body, such as data from a form.

              Note that only the first 8 KB (8192 bytes) of the request body are forwarded to WAF for inspection by the underlying host service. If you don't need to inspect more than 8 KB, you can guarantee that you don't allow additional bytes in by combining a statement that inspects the body of the web request, such as ByteMatchStatement or RegexPatternSetReferenceStatement, with a SizeConstraintStatement that enforces an 8 KB size limit on the body of the request. WAF doesn't support inspecting the entire contents of web requests whose bodies exceed the 8 KB limit.

              • MatchPattern — required — (map)

                The patterns to look for in the JSON body. WAF inspects the results of these pattern matches against the rule inspection criteria.

                • All — (map)

                  Match all of the elements. See also MatchScope in JsonBody.

                  You must specify either this setting or the IncludedPaths setting, but not both.

                • IncludedPaths — (Array<String>)

                  Match only the specified include paths. See also MatchScope in JsonBody.

                  Provide the include paths using JSON Pointer syntax. For example, "IncludedPaths": ["/dogs/0/name", "/dogs/1/name"]. For information about this syntax, see the Internet Engineering Task Force (IETF) documentation JavaScript Object Notation (JSON) Pointer.

                  You must specify either this setting or the All setting, but not both.

                  Note: Don't use this option to include all paths. Instead, use the All setting.
              • MatchScope — required — (String)

                The parts of the JSON to match against using the MatchPattern. If you specify All, WAF matches against keys and values.

                Possible values include:
                • "ALL"
                • "KEY"
                • "VALUE"
              • InvalidFallbackBehavior — (String)

                What WAF should do if it fails to completely parse the JSON body. The options are the following:

                • EVALUATE_AS_STRING - Inspect the body as plain text. WAF applies the text transformations and inspection criteria that you defined for the JSON inspection to the body text string.

                • MATCH - Treat the web request as matching the rule statement. WAF applies the rule action to the request.

                • NO_MATCH - Treat the web request as not matching the rule statement.

                If you don't provide this setting, WAF parses and evaluates the content only up to the first parsing failure that it encounters.

                WAF does its best to parse the entire JSON body, but might be forced to stop for reasons such as invalid characters, duplicate keys, truncation, and any content whose root node isn't an object or an array.

                WAF parses the JSON in the following examples as two valid key, value pairs:

                • Missing comma: {"key1":"value1""key2":"value2"}

                • Missing colon: {"key1":"value1","key2""value2"}

                • Extra colons: {"key1"::"value1","key2""value2"}

                Possible values include:
                • "MATCH"
                • "NO_MATCH"
                • "EVALUATE_AS_STRING"
          • TextTransformations — required — (Array<map>)

            Text transformations eliminate some of the unusual formatting that attackers use in web requests in an effort to bypass detection. If you specify one or more transformations in a rule statement, WAF performs all transformations on the content of the request component identified by FieldToMatch, starting from the lowest priority setting, before inspecting the content for a match.

            • Priority — required — (Integer)

              Sets the relative processing order for multiple transformations that are defined for a rule statement. WAF processes all transformations, from lowest priority to highest, before inspecting the transformed content. The priorities don't need to be consecutive, but they must all be different.

            • Type — required — (String)

              You can specify the following transformation types:

              BASE64_DECODE - Decode a Base64-encoded string.

              BASE64_DECODE_EXT - Decode a Base64-encoded string, but use a forgiving implementation that ignores characters that aren't valid.

              CMD_LINE - Command-line transformations. These are helpful in reducing effectiveness of attackers who inject an operating system command-line command and use unusual formatting to disguise some or all of the command.

              • Delete the following characters: \ " ' ^

              • Delete spaces before the following characters: / (

              • Replace the following characters with a space: , ;

              • Replace multiple spaces with one space

              • Convert uppercase letters (A-Z) to lowercase (a-z)

              COMPRESS_WHITE_SPACE - Replace these characters with a space character (decimal 32):

              • \f, formfeed, decimal 12

              • \t, tab, decimal 9

              • \n, newline, decimal 10

              • \r, carriage return, decimal 13

              • \v, vertical tab, decimal 11

              • Non-breaking space, decimal 160

              COMPRESS_WHITE_SPACE also replaces multiple spaces with one space.

              CSS_DECODE - Decode characters that were encoded using CSS 2.x escape rules syndata.html#characters. This function uses up to two bytes in the decoding process, so it can help to uncover ASCII characters that were encoded using CSS encoding that wouldn’t typically be encoded. It's also useful in countering evasion, which is a combination of a backslash and non-hexadecimal characters. For example, ja\vascript for javascript.

              ESCAPE_SEQ_DECODE - Decode the following ANSI C escape sequences: \a, \b, \f, \n, \r, \t, \v, \, \?, \', \", \xHH (hexadecimal), \0OOO (octal). Encodings that aren't valid remain in the output.

              HEX_DECODE - Decode a string of hexadecimal characters into a binary.

              HTML_ENTITY_DECODE - Replace HTML-encoded characters with unencoded characters. HTML_ENTITY_DECODE performs these operations:

              • Replaces (ampersand)quot; with "

              • Replaces (ampersand)nbsp; with a non-breaking space, decimal 160

              • Replaces (ampersand)lt; with a "less than" symbol

              • Replaces (ampersand)gt; with >

              • Replaces characters that are represented in hexadecimal format, (ampersand)#xhhhh;, with the corresponding characters

              • Replaces characters that are represented in decimal format, (ampersand)#nnnn;, with the corresponding characters

              JS_DECODE - Decode JavaScript escape sequences. If a \ u HHHH code is in the full-width ASCII code range of FF01-FF5E, then the higher byte is used to detect and adjust the lower byte. If not, only the lower byte is used and the higher byte is zeroed, causing a possible loss of information.

              LOWERCASE - Convert uppercase letters (A-Z) to lowercase (a-z).

              MD5 - Calculate an MD5 hash from the data in the input. The computed hash is in a raw binary form.

              NONE - Specify NONE if you don't want any text transformations.

              NORMALIZE_PATH - Remove multiple slashes, directory self-references, and directory back-references that are not at the beginning of the input from an input string.

              NORMALIZE_PATH_WIN - This is the same as NORMALIZE_PATH, but first converts backslash characters to forward slashes.

              REMOVE_NULLS - Remove all NULL bytes from the input.

              REPLACE_COMMENTS - Replace each occurrence of a C-style comment (/* ... */) with a single space. Multiple consecutive occurrences are not compressed. Unterminated comments are also replaced with a space (ASCII 0x20). However, a standalone termination of a comment (*/) is not acted upon.

              REPLACE_NULLS - Replace NULL bytes in the input with space characters (ASCII 0x20).

              SQL_HEX_DECODE - Decode SQL hex data. Example (0x414243) will be decoded to (ABC).

              URL_DECODE - Decode a URL-encoded value.

              URL_DECODE_UNI - Like URL_DECODE, but with support for Microsoft-specific %u encoding. If the code is in the full-width ASCII code range of FF01-FF5E, the higher byte is used to detect and adjust the lower byte. Otherwise, only the lower byte is used and the higher byte is zeroed.

              UTF8_TO_UNICODE - Convert all UTF-8 character sequences to Unicode. This helps input normalization, and minimizing false-positives and false-negatives for non-English languages.

              Possible values include:
              • "NONE"
              • "COMPRESS_WHITE_SPACE"
              • "HTML_ENTITY_DECODE"
              • "LOWERCASE"
              • "CMD_LINE"
              • "URL_DECODE"
              • "BASE64_DECODE"
              • "HEX_DECODE"
              • "MD5"
              • "REPLACE_COMMENTS"
              • "ESCAPE_SEQ_DECODE"
              • "SQL_HEX_DECODE"
              • "CSS_DECODE"
              • "JS_DECODE"
              • "NORMALIZE_PATH"
              • "NORMALIZE_PATH_WIN"
              • "REMOVE_NULLS"
              • "REPLACE_NULLS"
              • "BASE64_DECODE_EXT"
              • "URL_DECODE_UNI"
              • "UTF8_TO_UNICODE"
        • XssMatchStatement — (map)

          A rule statement that defines a cross-site scripting (XSS) match search for WAF to apply to web requests. XSS attacks are those where the attacker uses vulnerabilities in a benign website as a vehicle to inject malicious client-site scripts into other legitimate web browsers. The XSS match statement provides the location in requests that you want WAF to search and text transformations to use on the search area before WAF searches for character sequences that are likely to be malicious strings.

          • FieldToMatch — required — (map)

            The part of a web request that you want WAF to inspect. For more information, see FieldToMatch.

            • SingleHeader — (map)

              Inspect a single header. Provide the name of the header to inspect, for example, User-Agent or Referer. This setting isn't case sensitive.

              Example JSON: "SingleHeader": { "Name": "haystack" }

              • Name — required — (String)

                The name of the query header to inspect.

            • SingleQueryArgument — (map)

              Inspect a single query argument. Provide the name of the query argument to inspect, such as UserName or SalesRegion. The name can be up to 30 characters long and isn't case sensitive.

              This is used only to indicate the web request component for WAF to inspect, in the FieldToMatch specification.

              Example JSON: "SingleQueryArgument": { "Name": "myArgument" }

              • Name — required — (String)

                The name of the query argument to inspect.

            • AllQueryArguments — (map)

              Inspect all query arguments.

            • UriPath — (map)

              Inspect the request URI path. This is the part of a web request that identifies a resource, for example, /images/daily-ad.jpg.

            • QueryString — (map)

              Inspect the query string. This is the part of a URL that appears after a ? character, if any.

            • Body — (map)

              Inspect the request body as plain text. The request body immediately follows the request headers. This is the part of a request that contains any additional data that you want to send to your web server as the HTTP request body, such as data from a form.

              Note that only the first 8 KB (8192 bytes) of the request body are forwarded to WAF for inspection by the underlying host service. If you don't need to inspect more than 8 KB, you can guarantee that you don't allow additional bytes in by combining a statement that inspects the body of the web request, such as ByteMatchStatement or RegexPatternSetReferenceStatement, with a SizeConstraintStatement that enforces an 8 KB size limit on the body of the request. WAF doesn't support inspecting the entire contents of web requests whose bodies exceed the 8 KB limit.

            • Method — (map)

              Inspect the HTTP method. The method indicates the type of operation that the request is asking the origin to perform.

            • JsonBody — (map)

              Inspect the request body as JSON. The request body immediately follows the request headers. This is the part of a request that contains any additional data that you want to send to your web server as the HTTP request body, such as data from a form.

              Note that only the first 8 KB (8192 bytes) of the request body are forwarded to WAF for inspection by the underlying host service. If you don't need to inspect more than 8 KB, you can guarantee that you don't allow additional bytes in by combining a statement that inspects the body of the web request, such as ByteMatchStatement or RegexPatternSetReferenceStatement, with a SizeConstraintStatement that enforces an 8 KB size limit on the body of the request. WAF doesn't support inspecting the entire contents of web requests whose bodies exceed the 8 KB limit.

              • MatchPattern — required — (map)

                The patterns to look for in the JSON body. WAF inspects the results of these pattern matches against the rule inspection criteria.

                • All — (map)

                  Match all of the elements. See also MatchScope in JsonBody.

                  You must specify either this setting or the IncludedPaths setting, but not both.

                • IncludedPaths — (Array<String>)

                  Match only the specified include paths. See also MatchScope in JsonBody.

                  Provide the include paths using JSON Pointer syntax. For example, "IncludedPaths": ["/dogs/0/name", "/dogs/1/name"]. For information about this syntax, see the Internet Engineering Task Force (IETF) documentation JavaScript Object Notation (JSON) Pointer.

                  You must specify either this setting or the All setting, but not both.

                  Note: Don't use this option to include all paths. Instead, use the All setting.
              • MatchScope — required — (String)

                The parts of the JSON to match against using the MatchPattern. If you specify All, WAF matches against keys and values.

                Possible values include:
                • "ALL"
                • "KEY"
                • "VALUE"
              • InvalidFallbackBehavior — (String)

                What WAF should do if it fails to completely parse the JSON body. The options are the following:

                • EVALUATE_AS_STRING - Inspect the body as plain text. WAF applies the text transformations and inspection criteria that you defined for the JSON inspection to the body text string.

                • MATCH - Treat the web request as matching the rule statement. WAF applies the rule action to the request.

                • NO_MATCH - Treat the web request as not matching the rule statement.

                If you don't provide this setting, WAF parses and evaluates the content only up to the first parsing failure that it encounters.

                WAF does its best to parse the entire JSON body, but might be forced to stop for reasons such as invalid characters, duplicate keys, truncation, and any content whose root node isn't an object or an array.

                WAF parses the JSON in the following examples as two valid key, value pairs:

                • Missing comma: {"key1":"value1""key2":"value2"}

                • Missing colon: {"key1":"value1","key2""value2"}

                • Extra colons: {"key1"::"value1","key2""value2"}

                Possible values include:
                • "MATCH"
                • "NO_MATCH"
                • "EVALUATE_AS_STRING"
          • TextTransformations — required — (Array<map>)

            Text transformations eliminate some of the unusual formatting that attackers use in web requests in an effort to bypass detection. If you specify one or more transformations in a rule statement, WAF performs all transformations on the content of the request component identified by FieldToMatch, starting from the lowest priority setting, before inspecting the content for a match.

            • Priority — required — (Integer)

              Sets the relative processing order for multiple transformations that are defined for a rule statement. WAF processes all transformations, from lowest priority to highest, before inspecting the transformed content. The priorities don't need to be consecutive, but they must all be different.

            • Type — required — (String)

              You can specify the following transformation types:

              BASE64_DECODE - Decode a Base64-encoded string.

              BASE64_DECODE_EXT - Decode a Base64-encoded string, but use a forgiving implementation that ignores characters that aren't valid.

              CMD_LINE - Command-line transformations. These are helpful in reducing effectiveness of attackers who inject an operating system command-line command and use unusual formatting to disguise some or all of the command.

              • Delete the following characters: \ " ' ^

              • Delete spaces before the following characters: / (

              • Replace the following characters with a space: , ;

              • Replace multiple spaces with one space

              • Convert uppercase letters (A-Z) to lowercase (a-z)

              COMPRESS_WHITE_SPACE - Replace these characters with a space character (decimal 32):

              • \f, formfeed, decimal 12

              • \t, tab, decimal 9

              • \n, newline, decimal 10

              • \r, carriage return, decimal 13

              • \v, vertical tab, decimal 11

              • Non-breaking space, decimal 160

              COMPRESS_WHITE_SPACE also replaces multiple spaces with one space.

              CSS_DECODE - Decode characters that were encoded using CSS 2.x escape rules syndata.html#characters. This function uses up to two bytes in the decoding process, so it can help to uncover ASCII characters that were encoded using CSS encoding that wouldn’t typically be encoded. It's also useful in countering evasion, which is a combination of a backslash and non-hexadecimal characters. For example, ja\vascript for javascript.

              ESCAPE_SEQ_DECODE - Decode the following ANSI C escape sequences: \a, \b, \f, \n, \r, \t, \v, \, \?, \', \", \xHH (hexadecimal), \0OOO (octal). Encodings that aren't valid remain in the output.

              HEX_DECODE - Decode a string of hexadecimal characters into a binary.

              HTML_ENTITY_DECODE - Replace HTML-encoded characters with unencoded characters. HTML_ENTITY_DECODE performs these operations:

              • Replaces (ampersand)quot; with "

              • Replaces (ampersand)nbsp; with a non-breaking space, decimal 160

              • Replaces (ampersand)lt; with a "less than" symbol

              • Replaces (ampersand)gt; with >

              • Replaces characters that are represented in hexadecimal format, (ampersand)#xhhhh;, with the corresponding characters

              • Replaces characters that are represented in decimal format, (ampersand)#nnnn;, with the corresponding characters

              JS_DECODE - Decode JavaScript escape sequences. If a \ u HHHH code is in the full-width ASCII code range of FF01-FF5E, then the higher byte is used to detect and adjust the lower byte. If not, only the lower byte is used and the higher byte is zeroed, causing a possible loss of information.

              LOWERCASE - Convert uppercase letters (A-Z) to lowercase (a-z).

              MD5 - Calculate an MD5 hash from the data in the input. The computed hash is in a raw binary form.

              NONE - Specify NONE if you don't want any text transformations.

              NORMALIZE_PATH - Remove multiple slashes, directory self-references, and directory back-references that are not at the beginning of the input from an input string.

              NORMALIZE_PATH_WIN - This is the same as NORMALIZE_PATH, but first converts backslash characters to forward slashes.

              REMOVE_NULLS - Remove all NULL bytes from the input.

              REPLACE_COMMENTS - Replace each occurrence of a C-style comment (/* ... */) with a single space. Multiple consecutive occurrences are not compressed. Unterminated comments are also replaced with a space (ASCII 0x20). However, a standalone termination of a comment (*/) is not acted upon.

              REPLACE_NULLS - Replace NULL bytes in the input with space characters (ASCII 0x20).

              SQL_HEX_DECODE - Decode SQL hex data. Example (0x414243) will be decoded to (ABC).

              URL_DECODE - Decode a URL-encoded value.

              URL_DECODE_UNI - Like URL_DECODE, but with support for Microsoft-specific %u encoding. If the code is in the full-width ASCII code range of FF01-FF5E, the higher byte is used to detect and adjust the lower byte. Otherwise, only the lower byte is used and the higher byte is zeroed.

              UTF8_TO_UNICODE - Convert all UTF-8 character sequences to Unicode. This helps input normalization, and minimizing false-positives and false-negatives for non-English languages.

              Possible values include:
              • "NONE"
              • "COMPRESS_WHITE_SPACE"
              • "HTML_ENTITY_DECODE"
              • "LOWERCASE"
              • "CMD_LINE"
              • "URL_DECODE"
              • "BASE64_DECODE"
              • "HEX_DECODE"
              • "MD5"
              • "REPLACE_COMMENTS"
              • "ESCAPE_SEQ_DECODE"
              • "SQL_HEX_DECODE"
              • "CSS_DECODE"
              • "JS_DECODE"
              • "NORMALIZE_PATH"
              • "NORMALIZE_PATH_WIN"
              • "REMOVE_NULLS"
              • "REPLACE_NULLS"
              • "BASE64_DECODE_EXT"
              • "URL_DECODE_UNI"
              • "UTF8_TO_UNICODE"
        • SizeConstraintStatement — (map)

          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 first 8192 bytes (8 KB). If the request body for your web requests never exceeds 8192 bytes, you can create a size constraint condition and block requests that have a request body greater than 8192 bytes.

          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.

          • FieldToMatch — required — (map)

            The part of a web request that you want WAF to inspect. For more information, see FieldToMatch.

            • SingleHeader — (map)

              Inspect a single header. Provide the name of the header to inspect, for example, User-Agent or Referer. This setting isn't case sensitive.

              Example JSON: "SingleHeader": { "Name": "haystack" }

              • Name — required — (String)

                The name of the query header to inspect.

            • SingleQueryArgument — (map)

              Inspect a single query argument. Provide the name of the query argument to inspect, such as UserName or SalesRegion. The name can be up to 30 characters long and isn't case sensitive.

              This is used only to indicate the web request component for WAF to inspect, in the FieldToMatch specification.

              Example JSON: "SingleQueryArgument": { "Name": "myArgument" }

              • Name — required — (String)

                The name of the query argument to inspect.

            • AllQueryArguments — (map)

              Inspect all query arguments.

            • UriPath — (map)

              Inspect the request URI path. This is the part of a web request that identifies a resource, for example, /images/daily-ad.jpg.

            • QueryString — (map)

              Inspect the query string. This is the part of a URL that appears after a ? character, if any.

            • Body — (map)

              Inspect the request body as plain text. The request body immediately follows the request headers. This is the part of a request that contains any additional data that you want to send to your web server as the HTTP request body, such as data from a form.

              Note that only the first 8 KB (8192 bytes) of the request body are forwarded to WAF for inspection by the underlying host service. If you don't need to inspect more than 8 KB, you can guarantee that you don't allow additional bytes in by combining a statement that inspects the body of the web request, such as ByteMatchStatement or RegexPatternSetReferenceStatement, with a SizeConstraintStatement that enforces an 8 KB size limit on the body of the request. WAF doesn't support inspecting the entire contents of web requests whose bodies exceed the 8 KB limit.

            • Method — (map)

              Inspect the HTTP method. The method indicates the type of operation that the request is asking the origin to perform.

            • JsonBody — (map)

              Inspect the request body as JSON. The request body immediately follows the request headers. This is the part of a request that contains any additional data that you want to send to your web server as the HTTP request body, such as data from a form.

              Note that only the first 8 KB (8192 bytes) of the request body are forwarded to WAF for inspection by the underlying host service. If you don't need to inspect more than 8 KB, you can guarantee that you don't allow additional bytes in by combining a statement that inspects the body of the web request, such as ByteMatchStatement or RegexPatternSetReferenceStatement, with a SizeConstraintStatement that enforces an 8 KB size limit on the body of the request. WAF doesn't support inspecting the entire contents of web requests whose bodies exceed the 8 KB limit.

              • MatchPattern — required — (map)

                The patterns to look for in the JSON body. WAF inspects the results of these pattern matches against the rule inspection criteria.

                • All — (map)

                  Match all of the elements. See also MatchScope in JsonBody.

                  You must specify either this setting or the IncludedPaths setting, but not both.

                • IncludedPaths — (Array<String>)

                  Match only the specified include paths. See also MatchScope in JsonBody.

                  Provide the include paths using JSON Pointer syntax. For example, "IncludedPaths": ["/dogs/0/name", "/dogs/1/name"]. For information about this syntax, see the Internet Engineering Task Force (IETF) documentation JavaScript Object Notation (JSON) Pointer.

                  You must specify either this setting or the All setting, but not both.

                  Note: Don't use this option to include all paths. Instead, use the All setting.
              • MatchScope — required — (String)

                The parts of the JSON to match against using the MatchPattern. If you specify All, WAF matches against keys and values.

                Possible values include:
                • "ALL"
                • "KEY"
                • "VALUE"
              • InvalidFallbackBehavior — (String)

                What WAF should do if it fails to completely parse the JSON body. The options are the following:

                • EVALUATE_AS_STRING - Inspect the body as plain text. WAF applies the text transformations and inspection criteria that you defined for the JSON inspection to the body text string.

                • MATCH - Treat the web request as matching the rule statement. WAF applies the rule action to the request.

                • NO_MATCH - Treat the web request as not matching the rule statement.

                If you don't provide this setting, WAF parses and evaluates the content only up to the first parsing failure that it encounters.

                WAF does its best to parse the entire JSON body, but might be forced to stop for reasons such as invalid characters, duplicate keys, truncation, and any content whose root node isn't an object or an array.

                WAF parses the JSON in the following examples as two valid key, value pairs:

                • Missing comma: {"key1":"value1""key2":"value2"}

                • Missing colon: {"key1":"value1","key2""value2"}

                • Extra colons: {"key1"::"value1","key2""value2"}

                Possible values include:
                • "MATCH"
                • "NO_MATCH"
                • "EVALUATE_AS_STRING"
          • ComparisonOperator — required — (String)

            The operator to use to compare the request part to the size setting.

            Possible values include:
            • "EQ"
            • "NE"
            • "LE"
            • "LT"
            • "GE"
            • "GT"
          • Size — required — (Integer)

            The size, in byte, to compare to the request part, after any transformations.

          • TextTransformations — required — (Array<map>)

            Text transformations eliminate some of the unusual formatting that attackers use in web requests in an effort to bypass detection. If you specify one or more transformations in a rule statement, WAF performs all transformations on the content of the request component identified by FieldToMatch, starting from the lowest priority setting, before inspecting the content for a match.

            • Priority — required — (Integer)

              Sets the relative processing order for multiple transformations that are defined for a rule statement. WAF processes all transformations, from lowest priority to highest, before inspecting the transformed content. The priorities don't need to be consecutive, but they must all be different.

            • Type — required — (String)

              You can specify the following transformation types:

              BASE64_DECODE - Decode a Base64-encoded string.

              BASE64_DECODE_EXT - Decode a Base64-encoded string, but use a forgiving implementation that ignores characters that aren't valid.

              CMD_LINE - Command-line transformations. These are helpful in reducing effectiveness of attackers who inject an operating system command-line command and use unusual formatting to disguise some or all of the command.

              • Delete the following characters: \ " ' ^

              • Delete spaces before the following characters: / (

              • Replace the following characters with a space: , ;

              • Replace multiple spaces with one space

              • Convert uppercase letters (A-Z) to lowercase (a-z)

              COMPRESS_WHITE_SPACE - Replace these characters with a space character (decimal 32):

              • \f, formfeed, decimal 12

              • \t, tab, decimal 9

              • \n, newline, decimal 10

              • \r, carriage return, decimal 13

              • \v, vertical tab, decimal 11

              • Non-breaking space, decimal 160

              COMPRESS_WHITE_SPACE also replaces multiple spaces with one space.

              CSS_DECODE - Decode characters that were encoded using CSS 2.x escape rules syndata.html#characters. This function uses up to two bytes in the decoding process, so it can help to uncover ASCII characters that were encoded using CSS encoding that wouldn’t typically be encoded. It's also useful in countering evasion, which is a combination of a backslash and non-hexadecimal characters. For example, ja\vascript for javascript.

              ESCAPE_SEQ_DECODE - Decode the following ANSI C escape sequences: \a, \b, \f, \n, \r, \t, \v, \, \?, \', \", \xHH (hexadecimal), \0OOO (octal). Encodings that aren't valid remain in the output.

              HEX_DECODE - Decode a string of hexadecimal characters into a binary.

              HTML_ENTITY_DECODE - Replace HTML-encoded characters with unencoded characters. HTML_ENTITY_DECODE performs these operations:

              • Replaces (ampersand)quot; with "

              • Replaces (ampersand)nbsp; with a non-breaking space, decimal 160

              • Replaces (ampersand)lt; with a "less than" symbol

              • Replaces (ampersand)gt; with >

              • Replaces characters that are represented in hexadecimal format, (ampersand)#xhhhh;, with the corresponding characters

              • Replaces characters that are represented in decimal format, (ampersand)#nnnn;, with the corresponding characters

              JS_DECODE - Decode JavaScript escape sequences. If a \ u HHHH code is in the full-width ASCII code range of FF01-FF5E, then the higher byte is used to detect and adjust the lower byte. If not, only the lower byte is used and the higher byte is zeroed, causing a possible loss of information.

              LOWERCASE - Convert uppercase letters (A-Z) to lowercase (a-z).

              MD5 - Calculate an MD5 hash from the data in the input. The computed hash is in a raw binary form.

              NONE - Specify NONE if you don't want any text transformations.

              NORMALIZE_PATH - Remove multiple slashes, directory self-references, and directory back-references that are not at the beginning of the input from an input string.

              NORMALIZE_PATH_WIN - This is the same as NORMALIZE_PATH, but first converts backslash characters to forward slashes.

              REMOVE_NULLS - Remove all NULL bytes from the input.

              REPLACE_COMMENTS - Replace each occurrence of a C-style comment (/* ... */) with a single space. Multiple consecutive occurrences are not compressed. Unterminated comments are also replaced with a space (ASCII 0x20). However, a standalone termination of a comment (*/) is not acted upon.

              REPLACE_NULLS - Replace NULL bytes in the input with space characters (ASCII 0x20).

              SQL_HEX_DECODE - Decode SQL hex data. Example (0x414243) will be decoded to (ABC).

              URL_DECODE - Decode a URL-encoded value.

              URL_DECODE_UNI - Like URL_DECODE, but with support for Microsoft-specific %u encoding. If the code is in the full-width ASCII code range of FF01-FF5E, the higher byte is used to detect and adjust the lower byte. Otherwise, only the lower byte is used and the higher byte is zeroed.

              UTF8_TO_UNICODE - Convert all UTF-8 character sequences to Unicode. This helps input normalization, and minimizing false-positives and false-negatives for non-English languages.

              Possible values include:
              • "NONE"
              • "COMPRESS_WHITE_SPACE"
              • "HTML_ENTITY_DECODE"
              • "LOWERCASE"
              • "CMD_LINE"
              • "URL_DECODE"
              • "BASE64_DECODE"
              • "HEX_DECODE"
              • "MD5"
              • "REPLACE_COMMENTS"
              • "ESCAPE_SEQ_DECODE"
              • "SQL_HEX_DECODE"
              • "CSS_DECODE"
              • "JS_DECODE"
              • "NORMALIZE_PATH"
              • "NORMALIZE_PATH_WIN"
              • "REMOVE_NULLS"
              • "REPLACE_NULLS"
              • "BASE64_DECODE_EXT"
              • "URL_DECODE_UNI"
              • "UTF8_TO_UNICODE"
        • GeoMatchStatement — (map)

          A rule statement used to identify web requests based on country of origin.

          • CountryCodes — (Array<String>)

            An array of two-character country codes, for example, [ "US", "CN" ], from the alpha-2 country ISO codes of the ISO 3166 international standard.

          • ForwardedIPConfig — (map)

            The configuration for inspecting IP addresses in an HTTP header that you specify, instead of using the IP address that's reported by the web request origin. Commonly, this is the X-Forwarded-For (XFF) header, but you can specify any header name.

            Note: If the specified header isn't present in the request, WAF doesn't apply the rule to the web request at all.
            • HeaderName — required — (String)

              The name of the HTTP header to use for the IP address. For example, to use the X-Forwarded-For (XFF) header, set this to X-Forwarded-For.

              Note: If the specified header isn't present in the request, WAF doesn't apply the rule to the web request at all.
            • FallbackBehavior — required — (String)

              The match status to assign to the web request if the request doesn't have a valid IP address in the specified position.

              Note: If the specified header isn't present in the request, WAF doesn't apply the rule to the web request at all.

              You can specify the following fallback behaviors:

              • MATCH - Treat the web request as matching the rule statement. WAF applies the rule action to the request.

              • NO_MATCH - Treat the web request as not matching the rule statement.

              Possible values include:
              • "MATCH"
              • "NO_MATCH"
        • RuleGroupReferenceStatement — (map)

          A rule statement used to run the rules that are defined in a RuleGroup. To use this, create a rule group with your rules, then provide the ARN of the rule group in this statement.

          You cannot nest a RuleGroupReferenceStatement, for example for use inside a NotStatement or OrStatement. You can only use a rule group reference statement at the top level inside a web ACL.

          • ARN — required — (String)

            The Amazon Resource Name (ARN) of the entity.

          • ExcludedRules — (Array<map>)

            The rules in the referenced rule group whose actions are set to Count. When you exclude a rule, WAF evaluates it exactly as it would if the rule action setting were Count. This is a useful option for testing the rules in a rule group without modifying how they handle your web traffic.

            • Name — required — (String)

              The name of the rule whose action you want to override to Count.

        • IPSetReferenceStatement — (map)

          A rule statement used to detect web requests coming from particular IP addresses or address ranges. To use this, create an IPSet that specifies the addresses you want to detect, then use the ARN of that set in this statement. To create an IP set, see CreateIPSet.

          Each IP set rule statement references an IP set. You create and maintain the set independent of your rules. This allows you to use the single set in multiple rules. When you update the referenced set, WAF automatically updates all rules that reference it.

          • ARN — required — (String)

            The Amazon Resource Name (ARN) of the IPSet that this statement references.

          • IPSetForwardedIPConfig — (map)

            The configuration for inspecting IP addresses in an HTTP header that you specify, instead of using the IP address that's reported by the web request origin. Commonly, this is the X-Forwarded-For (XFF) header, but you can specify any header name.

            Note: If the specified header isn't present in the request, WAF doesn't apply the rule to the web request at all.
            • HeaderName — required — (String)

              The name of the HTTP header to use for the IP address. For example, to use the X-Forwarded-For (XFF) header, set this to X-Forwarded-For.

              Note: If the specified header isn't present in the request, WAF doesn't apply the rule to the web request at all.
            • FallbackBehavior — required — (String)

              The match status to assign to the web request if the request doesn't have a valid IP address in the specified position.

              Note: If the specified header isn't present in the request, WAF doesn't apply the rule to the web request at all.

              You can specify the following fallback behaviors:

              • MATCH - Treat the web request as matching the rule statement. WAF applies the rule action to the request.

              • NO_MATCH - Treat the web request as not matching the rule statement.

              Possible values include:
              • "MATCH"
              • "NO_MATCH"
            • Position — required — (String)

              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:

              • FIRST - Inspect the first IP address in the list of IP addresses in the header. This is usually the client's original IP.

              • LAST - Inspect the last IP address in the list of IP addresses in the header.

              • ANY - Inspect all IP addresses in the header for a match. If the header contains more than 10 IP addresses, WAF inspects the last 10.

              Possible values include:
              • "FIRST"
              • "LAST"
              • "ANY"
        • RegexPatternSetReferenceStatement — (map)

          A rule statement used to search web request components for matches with regular expressions. To use this, create a RegexPatternSet that specifies the expressions that you want to detect, then use the ARN of that set in this statement. A web request matches the pattern set rule statement if the request component matches any of the patterns in the set. To create a regex pattern set, see CreateRegexPatternSet.

          Each regex pattern set rule statement references a regex pattern set. You create and maintain the set independent of your rules. This allows you to use the single set in multiple rules. When you update the referenced set, WAF automatically updates all rules that reference it.

          • ARN — required — (String)

            The Amazon Resource Name (ARN) of the RegexPatternSet that this statement references.

          • FieldToMatch — required — (map)

            The part of a web request that you want WAF to inspect. For more information, see FieldToMatch.

            • SingleHeader — (map)

              Inspect a single header. Provide the name of the header to inspect, for example, User-Agent or Referer. This setting isn't case sensitive.

              Example JSON: "SingleHeader": { "Name": "haystack" }

              • Name — required — (String)

                The name of the query header to inspect.

            • SingleQueryArgument — (map)

              Inspect a single query argument. Provide the name of the query argument to inspect, such as UserName or SalesRegion. The name can be up to 30 characters long and isn't case sensitive.

              This is used only to indicate the web request component for WAF to inspect, in the FieldToMatch specification.

              Example JSON: "SingleQueryArgument": { "Name": "myArgument" }

              • Name — required — (String)

                The name of the query argument to inspect.

            • AllQueryArguments — (map)

              Inspect all query arguments.

            • UriPath — (map)

              Inspect the request URI path. This is the part of a web request that identifies a resource, for example, /images/daily-ad.jpg.

            • QueryString — (map)

              Inspect the query string. This is the part of a URL that appears after a ? character, if any.

            • Body — (map)

              Inspect the request body as plain text. The request body immediately follows the request headers. This is the part of a request that contains any additional data that you want to send to your web server as the HTTP request body, such as data from a form.

              Note that only the first 8 KB (8192 bytes) of the request body are forwarded to WAF for inspection by the underlying host service. If you don't need to inspect more than 8 KB, you can guarantee that you don't allow additional bytes in by combining a statement that inspects the body of the web request, such as ByteMatchStatement or RegexPatternSetReferenceStatement, with a SizeConstraintStatement that enforces an 8 KB size limit on the body of the request. WAF doesn't support inspecting the entire contents of web requests whose bodies exceed the 8 KB limit.

            • Method — (map)

              Inspect the HTTP method. The method indicates the type of operation that the request is asking the origin to perform.

            • JsonBody — (map)

              Inspect the request body as JSON. The request body immediately follows the request headers. This is the part of a request that contains any additional data that you want to send to your web server as the HTTP request body, such as data from a form.

              Note that only the first 8 KB (8192 bytes) of the request body are forwarded to WAF for inspection by the underlying host service. If you don't need to inspect more than 8 KB, you can guarantee that you don't allow additional bytes in by combining a statement that inspects the body of the web request, such as ByteMatchStatement or RegexPatternSetReferenceStatement, with a SizeConstraintStatement that enforces an 8 KB size limit on the body of the request. WAF doesn't support inspecting the entire contents of web requests whose bodies exceed the 8 KB limit.

              • MatchPattern — required — (map)

                The patterns to look for in the JSON body. WAF inspects the results of these pattern matches against the rule inspection criteria.

                • All — (map)

                  Match all of the elements. See also MatchScope in JsonBody.

                  You must specify either this setting or the IncludedPaths setting, but not both.

                • IncludedPaths — (Array<String>)

                  Match only the specified include paths. See also MatchScope in JsonBody.

                  Provide the include paths using JSON Pointer syntax. For example, "IncludedPaths": ["/dogs/0/name", "/dogs/1/name"]. For information about this syntax, see the Internet Engineering Task Force (IETF) documentation JavaScript Object Notation (JSON) Pointer.

                  You must specify either this setting or the All setting, but not both.

                  Note: Don't use this option to include all paths. Instead, use the All setting.
              • MatchScope — required — (String)

                The parts of the JSON to match against using the MatchPattern. If you specify All, WAF matches against keys and values.

                Possible values include:
                • "ALL"
                • "KEY"
                • "VALUE"
              • InvalidFallbackBehavior — (String)

                What WAF should do if it fails to completely parse the JSON body. The options are the following:

                • EVALUATE_AS_STRING - Inspect the body as plain text. WAF applies the text transformations and inspection criteria that you defined for the JSON inspection to the body text string.

                • MATCH - Treat the web request as matching the rule statement. WAF applies the rule action to the request.

                • NO_MATCH - Treat the web request as not matching the rule statement.

                If you don't provide this setting, WAF parses and evaluates the content only up to the first parsing failure that it encounters.

                WAF does its best to parse the entire JSON body, but might be forced to stop for reasons such as invalid characters, duplicate keys, truncation, and any content whose root node isn't an object or an array.

                WAF parses the JSON in the following examples as two valid key, value pairs:

                • Missing comma: {"key1":"value1""key2":"value2"}

                • Missing colon: {"key1":"value1","key2""value2"}

                • Extra colons: {"key1"::"value1","key2""value2"}

                Possible values include:
                • "MATCH"
                • "NO_MATCH"
                • "EVALUATE_AS_STRING"
          • TextTransformations — required — (Array<map>)

            Text transformations eliminate some of the unusual formatting that attackers use in web requests in an effort to bypass detection. If you specify one or more transformations in a rule statement, WAF performs all transformations on the content of the request component identified by FieldToMatch, starting from the lowest priority setting, before inspecting the content for a match.

            • Priority — required — (Integer)

              Sets the relative processing order for multiple transformations that are defined for a rule statement. WAF processes all transformations, from lowest priority to highest, before inspecting the transformed content. The priorities don't need to be consecutive, but they must all be different.

            • Type — required — (String)

              You can specify the following transformation types:

              BASE64_DECODE - Decode a Base64-encoded string.

              BASE64_DECODE_EXT - Decode a Base64-encoded string, but use a forgiving implementation that ignores characters that aren't valid.

              CMD_LINE - Command-line transformations. These are helpful in reducing effectiveness of attackers who inject an operating system command-line command and use unusual formatting to disguise some or all of the command.

              • Delete the following characters: \ " ' ^

              • Delete spaces before the following characters: / (

              • Replace the following characters with a space: , ;

              • Replace multiple spaces with one space

              • Convert uppercase letters (A-Z) to lowercase (a-z)

              COMPRESS_WHITE_SPACE - Replace these characters with a space character (decimal 32):

              • \f, formfeed, decimal 12

              • \t, tab, decimal 9

              • \n, newline, decimal 10

              • \r, carriage return, decimal 13

              • \v, vertical tab, decimal 11

              • Non-breaking space, decimal 160

              COMPRESS_WHITE_SPACE also replaces multiple spaces with one space.

              CSS_DECODE - Decode characters that were encoded using CSS 2.x escape rules syndata.html#characters. This function uses up to two bytes in the decoding process, so it can help to uncover ASCII characters that were encoded using CSS encoding that wouldn’t typically be encoded. It's also useful in countering evasion, which is a combination of a backslash and non-hexadecimal characters. For example, ja\vascript for javascript.

              ESCAPE_SEQ_DECODE - Decode the following ANSI C escape sequences: \a, \b, \f, \n, \r, \t, \v, \, \?, \', \", \xHH (hexadecimal), \0OOO (octal). Encodings that aren't valid remain in the output.

              HEX_DECODE - Decode a string of hexadecimal characters into a binary.

              HTML_ENTITY_DECODE - Replace HTML-encoded characters with unencoded characters. HTML_ENTITY_DECODE performs these operations:

              • Replaces (ampersand)quot; with "

              • Replaces (ampersand)nbsp; with a non-breaking space, decimal 160

              • Replaces (ampersand)lt; with a "less than" symbol

              • Replaces (ampersand)gt; with >

              • Replaces characters that are represented in hexadecimal format, (ampersand)#xhhhh;, with the corresponding characters

              • Replaces characters that are represented in decimal format, (ampersand)#nnnn;, with the corresponding characters

              JS_DECODE - Decode JavaScript escape sequences. If a \ u HHHH code is in the full-width ASCII code range of FF01-FF5E, then the higher byte is used to detect and adjust the lower byte. If not, only the lower byte is used and the higher byte is zeroed, causing a possible loss of information.

              LOWERCASE - Convert uppercase letters (A-Z) to lowercase (a-z).

              MD5 - Calculate an MD5 hash from the data in the input. The computed hash is in a raw binary form.

              NONE - Specify NONE if you don't want any text transformations.

              NORMALIZE_PATH - Remove multiple slashes, directory self-references, and directory back-references that are not at the beginning of the input from an input string.

              NORMALIZE_PATH_WIN - This is the same as NORMALIZE_PATH, but first converts backslash characters to forward slashes.

              REMOVE_NULLS - Remove all NULL bytes from the input.

              REPLACE_COMMENTS - Replace each occurrence of a C-style comment (/* ... */) with a single space. Multiple consecutive occurrences are not compressed. Unterminated comments are also replaced with a space (ASCII 0x20). However, a standalone termination of a comment (*/) is not acted upon.

              REPLACE_NULLS - Replace NULL bytes in the input with space characters (ASCII 0x20).

              SQL_HEX_DECODE - Decode SQL hex data. Example (0x414243) will be decoded to (ABC).

              URL_DECODE - Decode a URL-encoded value.

              URL_DECODE_UNI - Like URL_DECODE, but with support for Microsoft-specific %u encoding. If the code is in the full-width ASCII code range of FF01-FF5E, the higher byte is used to detect and adjust the lower byte. Otherwise, only the lower byte is used and the higher byte is zeroed.

              UTF8_TO_UNICODE - Convert all UTF-8 character sequences to Unicode. This helps input normalization, and minimizing false-positives and false-negatives for non-English languages.

              Possible values include:
              • "NONE"
              • "COMPRESS_WHITE_SPACE"
              • "HTML_ENTITY_DECODE"
              • "LOWERCASE"
              • "CMD_LINE"
              • "URL_DECODE"
              • "BASE64_DECODE"
              • "HEX_DECODE"
              • "MD5"
              • "REPLACE_COMMENTS"
              • "ESCAPE_SEQ_DECODE"
              • "SQL_HEX_DECODE"
              • "CSS_DECODE"
              • "JS_DECODE"
              • "NORMALIZE_PATH"
              • "NORMALIZE_PATH_WIN"
              • "REMOVE_NULLS"
              • "REPLACE_NULLS"
              • "BASE64_DECODE_EXT"
              • "URL_DECODE_UNI"
              • "UTF8_TO_UNICODE"
        • RateBasedStatement — (map)

          A rate-based rule tracks the rate of requests for each originating IP address, and triggers the rule action when the rate exceeds a limit that you specify on the number of requests in any 5-minute time span. You can use this to put a temporary block on requests from an IP address that is sending excessive requests.

          WAF tracks and manages web requests separately for each instance of a rate-based rule that you use. For example, if you provide the same rate-based rule settings in two web ACLs, each of the two rule statements represents a separate instance of the rate-based rule and gets its own tracking and management by WAF. If you define a rate-based rule inside a rule group, and then use that rule group in multiple places, each use creates a separate instance of the rate-based rule that gets its own tracking and management by WAF.

          When the rule action triggers, WAF blocks additional requests from the IP address until the request rate falls below the limit.

          You can optionally nest another statement inside the rate-based statement, to narrow the scope of the rule so that it only counts requests that match the nested statement. For example, based on recent requests that you have seen from an attacker, you might create a rate-based rule with a nested AND rule statement that contains the following nested statements:

          • An IP match statement with an IP set that specified the address 192.0.2.44.

          • A string match statement that searches in the User-Agent header for the string BadBot.

          In this rate-based rule, you also define a rate limit. For this example, the rate limit is 1,000. Requests that meet both of the conditions in the statements are counted. If the count exceeds 1,000 requests per five minutes, the rule action triggers. Requests that do not meet both conditions are not counted towards the rate limit and are not affected by this rule.

          You cannot nest a RateBasedStatement inside another statement, for example inside a NotStatement or OrStatement. You can define a RateBasedStatement inside a web ACL and inside a rule group.

          • Limit — required — (Integer)

            The limit on requests per 5-minute period for a single originating IP address. If the statement includes a ScopeDownStatement, this limit is applied only to the requests that match the statement.

          • AggregateKeyType — required — (String)

            Setting that indicates how to aggregate the request counts. The options are the following:

            • IP - Aggregate the request counts on the IP address from the web request origin.

            • FORWARDED_IP - Aggregate the request counts on the first IP address in an HTTP header. If you use this, configure the ForwardedIPConfig, to specify the header to use.

            Possible values include:
            • "IP"
            • "FORWARDED_IP"
          • ForwardedIPConfig — (map)

            The configuration for inspecting IP addresses in an HTTP header that you specify, instead of using the IP address that's reported by the web request origin. Commonly, this is the X-Forwarded-For (XFF) header, but you can specify any header name.

            Note: If the specified header isn't present in the request, WAF doesn't apply the rule to the web request at all.

            This is required if AggregateKeyType is set to FORWARDED_IP.

            • HeaderName — required — (String)

              The name of the HTTP header to use for the IP address. For example, to use the X-Forwarded-For (XFF) header, set this to X-Forwarded-For.

              Note: If the specified header isn't present in the request, WAF doesn't apply the rule to the web request at all.
            • FallbackBehavior — required — (String)

              The match status to assign to the web request if the request doesn't have a valid IP address in the specified position.

              Note: If the specified header isn't present in the request, WAF doesn't apply the rule to the web request at all.

              You can specify the following fallback behaviors:

              • MATCH - Treat the web request as matching the rule statement. WAF applies the rule action to the request.

              • NO_MATCH - Treat the web request as not matching the rule statement.

              Possible values include:
              • "MATCH"
              • "NO_MATCH"
        • AndStatement — (map)

          A logical rule statement used to combine other rule statements with AND logic. You provide more than one Statement within the AndStatement.

          • Statements — required — (Array<map>)

            The statements to combine with AND logic. You can use any statements that can be nested.

        • OrStatement — (map)

          A logical rule statement used to combine other rule statements with OR logic. You provide more than one Statement within the OrStatement.

          • Statements — required — (Array<map>)

            The statements to combine with OR logic. You can use any statements that can be nested.

        • NotStatement — (map)

          A logical rule statement used to negate the results of another rule statement. You provide one Statement within the NotStatement.

        • ManagedRuleGroupStatement — (map)

          A rule statement used to run the rules that are defined in a managed rule group. To use this, provide the vendor name and the name of the rule group in this statement. You can retrieve the required names by calling ListAvailableManagedRuleGroups.

          You cannot nest a ManagedRuleGroupStatement, for example for use inside a NotStatement or OrStatement. It can only be referenced as a top-level statement within a rule.

          • VendorName — required — (String)

            The name of the managed rule group vendor. You use this, along with the rule group name, to identify the rule group.

          • Name — required — (String)

            The name of the managed rule group. You use this, along with the vendor name, to identify the rule group.

          • Version — (String)

            The version of the managed rule group to use. If you specify this, the version setting is fixed until you change it. If you don't specify this, WAF uses the vendor's default version, and then keeps the version at the vendor's default when the vendor updates the managed rule group settings.

          • ExcludedRules — (Array<map>)

            The rules in the referenced rule group whose actions are set to Count. When you exclude a rule, WAF evaluates it exactly as it would if the rule action setting were Count. This is a useful option for testing the rules in a rule group without modifying how they handle your web traffic.

            • Name — required — (String)

              The name of the rule whose action you want to override to Count.

        • LabelMatchStatement — (map)

          A rule statement that defines a string match search against labels that have been added to the web request by rules that have already run in the web ACL.

          The label match statement provides the label or namespace string to search for. The label string can represent a part or all of the fully qualified label name that had been added to the web request. Fully qualified labels have a prefix, optional namespaces, and label name. The prefix identifies the rule group or web ACL context of the rule that added the label. If you do not provide the fully qualified name in your label match string, WAF performs the search for labels that were added in the same context as the label match statement.

          • Scope — required — (String)

            Specify whether you want to match using the label name or just the namespace.

            Possible values include:
            • "LABEL"
            • "NAMESPACE"
          • Key — required — (String)

            The string to match against. The setting you provide for this depends on the match statement's Scope setting:

            • If the Scope indicates LABEL, then this specification must include the name and can include any number of preceding namespace specifications and prefix up to providing the fully qualified label name.

            • If the Scope indicates NAMESPACE, then this specification can include any number of contiguous namespace strings, and can include the entire label namespace prefix from the rule group or web ACL where the label originates.

            Labels are case sensitive and components of a label must be separated by colon, for example NS1:NS2:name.

        • RegexMatchStatement — (map)

          A rule statement used to search web request components for a match against a single regular expression.

          • RegexString — required — (String)

            The string representing the regular expression.

          • FieldToMatch — required — (map)

            The part of a web request that you want WAF to inspect. For more information, see FieldToMatch.

            • SingleHeader — (map)

              Inspect a single header. Provide the name of the header to inspect, for example, User-Agent or Referer. This setting isn't case sensitive.

              Example JSON: "SingleHeader": { "Name": "haystack" }

              • Name — required — (String)

                The name of the query header to inspect.

            • SingleQueryArgument — (map)

              Inspect a single query argument. Provide the name of the query argument to inspect, such as UserName or SalesRegion. The name can be up to 30 characters long and isn't case sensitive.

              This is used only to indicate the web request component for WAF to inspect, in the FieldToMatch specification.

              Example JSON: "SingleQueryArgument": { "Name": "myArgument" }

              • Name — required — (String)

                The name of the query argument to inspect.

            • AllQueryArguments — (map)

              Inspect all query arguments.

            • UriPath — (map)

              Inspect the request URI path. This is the part of a web request that identifies a resource, for example, /images/daily-ad.jpg.

            • QueryString — (map)

              Inspect the query string. This is the part of a URL that appears after a ? character, if any.

            • Body — (map)

              Inspect the request body as plain text. The request body immediately follows the request headers. This is the part of a request that contains any additional data that you want to send to your web server as the HTTP request body, such as data from a form.

              Note that only the first 8 KB (8192 bytes) of the request body are forwarded to WAF for inspection by the underlying host service. If you don't need to inspect more than 8 KB, you can guarantee that you don't allow additional bytes in by combining a statement that inspects the body of the web request, such as ByteMatchStatement or RegexPatternSetReferenceStatement, with a SizeConstraintStatement that enforces an 8 KB size limit on the body of the request. WAF doesn't support inspecting the entire contents of web requests whose bodies exceed the 8 KB limit.

            • Method — (map)

              Inspect the HTTP method. The method indicates the type of operation that the request is asking the origin to perform.

            • JsonBody — (map)

              Inspect the request body as JSON. The request body immediately follows the request headers. This is the part of a request that contains any additional data that you want to send to your web server as the HTTP request body, such as data from a form.

              Note that only the first 8 KB (8192 bytes) of the request body are forwarded to WAF for inspection by the underlying host service. If you don't need to inspect more than 8 KB, you can guarantee that you don't allow additional bytes in by combining a statement that inspects the body of the web request, such as ByteMatchStatement or RegexPatternSetReferenceStatement, with a SizeConstraintStatement that enforces an 8 KB size limit on the body of the request. WAF doesn't support inspecting the entire contents of web requests whose bodies exceed the 8 KB limit.

              • MatchPattern — required — (map)

                The patterns to look for in the JSON body. WAF inspects the results of these pattern matches against the rule inspection criteria.

                • All — (map)

                  Match all of the elements. See also MatchScope in JsonBody.

                  You must specify either this setting or the IncludedPaths setting, but not both.

                • IncludedPaths — (Array<String>)

                  Match only the specified include paths. See also MatchScope in JsonBody.

                  Provide the include paths using JSON Pointer syntax. For example, "IncludedPaths": ["/dogs/0/name", "/dogs/1/name"]. For information about this syntax, see the Internet Engineering Task Force (IETF) documentation JavaScript Object Notation (JSON) Pointer.

                  You must specify either this setting or the All setting, but not both.

                  Note: Don't use this option to include all paths. Instead, use the All setting.
              • MatchScope — required — (String)

                The parts of the JSON to match against using the MatchPattern. If you specify All, WAF matches against keys and values.

                Possible values include:
                • "ALL"
                • "KEY"
                • "VALUE"
              • InvalidFallbackBehavior — (String)

                What WAF should do if it fails to completely parse the JSON body. The options are the following:

                • EVALUATE_AS_STRING - Inspect the body as plain text. WAF applies the text transformations and inspection criteria that you defined for the JSON inspection to the body text string.

                • MATCH - Treat the web request as matching the rule statement. WAF applies the rule action to the request.

                • NO_MATCH - Treat the web request as not matching the rule statement.

                If you don't provide this setting, WAF parses and evaluates the content only up to the first parsing failure that it encounters.

                WAF does its best to parse the entire JSON body, but might be forced to stop for reasons such as invalid characters, duplicate keys, truncation, and any content whose root node isn't an object or an array.

                WAF parses the JSON in the following examples as two valid key, value pairs:

                • Missing comma: {"key1":"value1""key2":"value2"}

                • Missing colon: {"key1":"value1","key2""value2"}

                • Extra colons: {"key1"::"value1","key2""value2"}

                Possible values include:
                • "MATCH"
                • "NO_MATCH"
                • "EVALUATE_AS_STRING"
          • TextTransformations — required — (Array<map>)

            Text transformations eliminate some of the unusual formatting that attackers use in web requests in an effort to bypass detection. If you specify one or more transformations in a rule statement, WAF performs all transformations on the content of the request component identified by FieldToMatch, starting from the lowest priority setting, before inspecting the content for a match.

            • Priority — required — (Integer)

              Sets the relative processing order for multiple transformations that are defined for a rule statement. WAF processes all transformations, from lowest priority to highest, before inspecting the transformed content. The priorities don't need to be consecutive, but they must all be different.

            • Type — required — (String)

              You can specify the following transformation types:

              BASE64_DECODE - Decode a Base64-encoded string.

              BASE64_DECODE_EXT - Decode a Base64-encoded string, but use a forgiving implementation that ignores characters that aren't valid.

              CMD_LINE - Command-line transformations. These are helpful in reducing effectiveness of attackers who inject an operating system command-line command and use unusual formatting to disguise some or all of the command.

              • Delete the following characters: \ " ' ^

              • Delete spaces before the following characters: / (

              • Replace the following characters with a space: , ;

              • Replace multiple spaces with one space

              • Convert uppercase letters (A-Z) to lowercase (a-z)

              COMPRESS_WHITE_SPACE - Replace these characters with a space character (decimal 32):

              • \f, formfeed, decimal 12

              • \t, tab, decimal 9

              • \n, newline, decimal 10

              • \r, carriage return, decimal 13

              • \v, vertical tab, decimal 11

              • Non-breaking space, decimal 160

              COMPRESS_WHITE_SPACE also replaces multiple spaces with one space.

              CSS_DECODE - Decode characters that were encoded using CSS 2.x escape rules syndata.html#characters. This function uses up to two bytes in the decoding process, so it can help to uncover ASCII characters that were encoded using CSS encoding that wouldn’t typically be encoded. It's also useful in countering evasion, which is a combination of a backslash and non-hexadecimal characters. For example, ja\vascript for javascript.

              ESCAPE_SEQ_DECODE - Decode the following ANSI C escape sequences: \a, \b, \f, \n, \r, \t, \v, \, \?, \', \", \xHH (hexadecimal), \0OOO (octal). Encodings that aren't valid remain in the output.

              HEX_DECODE - Decode a string of hexadecimal characters into a binary.

              HTML_ENTITY_DECODE - Replace HTML-encoded characters with unencoded characters. HTML_ENTITY_DECODE performs these operations:

              • Replaces (ampersand)quot; with "

              • Replaces (ampersand)nbsp; with a non-breaking space, decimal 160

              • Replaces (ampersand)lt; with a "less than" symbol

              • Replaces (ampersand)gt; with >

              • Replaces characters that are represented in hexadecimal format, (ampersand)#xhhhh;, with the corresponding characters

              • Replaces characters that are represented in decimal format, (ampersand)#nnnn;, with the corresponding characters

              JS_DECODE - Decode JavaScript escape sequences. If a \ u HHHH code is in the full-width ASCII code range of FF01-FF5E, then the higher byte is used to detect and adjust the lower byte. If not, only the lower byte is used and the higher byte is zeroed, causing a possible loss of information.

              LOWERCASE - Convert uppercase letters (A-Z) to lowercase (a-z).

              MD5 - Calculate an MD5 hash from the data in the input. The computed hash is in a raw binary form.

              NONE - Specify NONE if you don't want any text transformations.

              NORMALIZE_PATH - Remove multiple slashes, directory self-references, and directory back-references that are not at the beginning of the input from an input string.

              NORMALIZE_PATH_WIN - This is the same as NORMALIZE_PATH, but first converts backslash characters to forward slashes.

              REMOVE_NULLS - Remove all NULL bytes from the input.

              REPLACE_COMMENTS - Replace each occurrence of a C-style comment (/* ... */) with a single space. Multiple consecutive occurrences are not compressed. Unterminated comments are also replaced with a space (ASCII 0x20). However, a standalone termination of a comment (*/) is not acted upon.

              REPLACE_NULLS - Replace NULL bytes in the input with space characters (ASCII 0x20).

              SQL_HEX_DECODE - Decode SQL hex data. Example (0x414243) will be decoded to (ABC).

              URL_DECODE - Decode a URL-encoded value.

              URL_DECODE_UNI - Like URL_DECODE, but with support for Microsoft-specific %u encoding. If the code is in the full-width ASCII code range of FF01-FF5E, the higher byte is used to detect and adjust the lower byte. Otherwise, only the lower byte is used and the higher byte is zeroed.

              UTF8_TO_UNICODE - Convert all UTF-8 character sequences to Unicode. This helps input normalization, and minimizing false-positives and false-negatives for non-English languages.

              Possible values include:
              • "NONE"
              • "COMPRESS_WHITE_SPACE"
              • "HTML_ENTITY_DECODE"
              • "LOWERCASE"
              • "CMD_LINE"
              • "URL_DECODE"
              • "BASE64_DECODE"
              • "HEX_DECODE"
              • "MD5"
              • "REPLACE_COMMENTS"
              • "ESCAPE_SEQ_DECODE"
              • "SQL_HEX_DECODE"
              • "CSS_DECODE"
              • "JS_DECODE"
              • "NORMALIZE_PATH"
              • "NORMALIZE_PATH_WIN"
              • "REMOVE_NULLS"
              • "REPLACE_NULLS"
              • "BASE64_DECODE_EXT"
              • "URL_DECODE_UNI"
              • "UTF8_TO_UNICODE"
      • Action — (map)

        The action that WAF should take on a web request when it matches the rule statement. Settings at the web ACL level can override the rule action setting.

        This is used only for rules whose statements do not reference a rule group. Rule statements that reference a rule group include RuleGroupReferenceStatement and ManagedRuleGroupStatement.

        You must specify either this Action setting or the rule OverrideAction setting, but not both:

        • If the rule statement does not reference a rule group, use this rule action setting and not the rule override action setting.

        • If the rule statement references a rule group, use the override action setting and not this action setting.

        • Block — (map)

          Instructs WAF to block the web request.

          • CustomResponse — (map)

            Defines a custom response for the web request.

            For information about customizing web requests and responses, see Customizing web requests and responses in WAF in the WAF Developer Guide.

            • ResponseCode — required — (Integer)

              The HTTP status code to return to the client.

              For a list of status codes that you can use in your custom reqponses, see Supported status codes for custom response in the WAF Developer Guide.

            • CustomResponseBodyKey — (String)

              References the response body that you want WAF to return to the web request client. You can define a custom response for a rule action or a default web ACL action that is set to block. To do this, you first define the response body key and value in the CustomResponseBodies setting for the WebACL or RuleGroup where you want to use it. Then, in the rule action or web ACL default action BlockAction setting, you reference the response body using this key.

            • ResponseHeaders — (Array<map>)

              The HTTP headers to use in the response. Duplicate header names are not allowed.

              For information about the limits on count and size for custom request and response settings, see WAF quotas in the WAF Developer Guide.

              • Name — required — (String)

                The name of the custom header.

                For custom request header insertion, when WAF inserts the header into the request, it prefixes this name x-amzn-waf-, to avoid confusion with the headers that are already in the request. For example, for the header name sample, WAF inserts the header x-amzn-waf-sample.

              • Value — required — (String)

                The value of the custom header.

        • Allow — (map)

          Instructs WAF to allow the web request.

          • CustomRequestHandling — (map)

            Defines custom handling for the web request.

            For information about customizing web requests and responses, see Customizing web requests and responses in WAF in the WAF Developer Guide.

            • InsertHeaders — required — (Array<map>)

              The HTTP headers to insert into the request. Duplicate header names are not allowed.

              For information about the limits on count and size for custom request and response settings, see WAF quotas in the WAF Developer Guide.

              • Name — required — (String)

                The name of the custom header.

                For custom request header insertion, when WAF inserts the header into the request, it prefixes this name x-amzn-waf-, to avoid confusion with the headers that are already in the request. For example, for the header name sample, WAF inserts the header x-amzn-waf-sample.

              • Value — required — (String)

                The value of the custom header.

        • Count — (map)

          Instructs WAF to count the web request and allow it.

          • CustomRequestHandling — (map)

            Defines custom handling for the web request.

            For information about customizing web requests and responses, see Customizing web requests and responses in WAF in the WAF Developer Guide.

            • InsertHeaders — required — (Array<map>)

              The HTTP headers to insert into the request. Duplicate header names are not allowed.

              For information about the limits on count and size for custom request and response settings, see WAF quotas in the WAF Developer Guide.

              • Name — required — (String)

                The name of the custom header.

                For custom request header insertion, when WAF inserts the header into the request, it prefixes this name x-amzn-waf-, to avoid confusion with the headers that are already in the request. For example, for the header name sample, WAF inserts the header x-amzn-waf-sample.

              • Value — required — (String)

                The value of the custom header.

        • Captcha — (map)

          Instructs WAF to run a CAPTCHA check against the web request.

          • CustomRequestHandling — (map)

            Defines custom handling for the web request.

            For information about customizing web requests and responses, see Customizing web requests and responses in WAF in the WAF Developer Guide.

            • InsertHeaders — required — (Array<map>)

              The HTTP headers to insert into the request. Duplicate header names are not allowed.

              For information about the limits on count and size for custom request and response settings, see WAF quotas in the WAF Developer Guide.

              • Name — required — (String)

                The name of the custom header.

                For custom request header insertion, when WAF inserts the header into the request, it prefixes this name x-amzn-waf-, to avoid confusion with the headers that are already in the request. For example, for the header name sample, WAF inserts the header x-amzn-waf-sample.

              • Value — required — (String)

                The value of the custom header.

      • OverrideAction — (map)

        The action to use in the place of the action that results from the rule group evaluation. Set the override action to none to leave the result of the rule group alone. Set it to count to override the result to count only.

        You can only use this for rule statements that reference a rule group, like RuleGroupReferenceStatement and ManagedRuleGroupStatement.

        Note: This option is usually set to none. It does not affect how the rules in the rule group are evaluated. If you want the rules in the rule group to only count matches, do not use this and instead exclude those rules in your rule group reference statement settings.
        • Count — (map)

          Override the rule group evaluation result to count only.

          Note: This option is usually set to none. It does not affect how the rules in the rule group are evaluated. If you want the rules in the rule group to only count matches, do not use this and instead exclude those rules in your rule group reference statement settings.
          • CustomRequestHandling — (map)

            Defines custom handling for the web request.

            For information about customizing web requests and responses, see Customizing web requests and responses in WAF in the WAF Developer Guide.

            • InsertHeaders — required — (Array<map>)

              The HTTP headers to insert into the request. Duplicate header names are not allowed.

              For information about the limits on count and size for custom request and response settings, see WAF quotas in the WAF Developer Guide.

              • Name — required — (String)

                The name of the custom header.

                For custom request header insertion, when WAF inserts the header into the request, it prefixes this name x-amzn-waf-, to avoid confusion with the headers that are already in the request. For example, for the header name sample, WAF inserts the header x-amzn-waf-sample.

              • Value — required — (String)

                The value of the custom header.

        • None — (map)

          Don't override the rule group evaluation result. This is the most common setting.

      • RuleLabels — (Array<map>)

        Labels to apply to web requests that match the rule match statement. WAF applies fully qualified labels to matching web requests. A fully qualified label is the concatenation of a label namespace and a rule label. The rule's rule group or web ACL defines the label namespace.

        Rules that run after this rule in the web ACL can match against these labels using a LabelMatchStatement.

        For each label, provide a case-sensitive string containing optional namespaces and a label name, according to the following guidelines:

        • Separate each component of the label with a colon.

        • Each namespace or name can have up to 128 characters.

        • You can specify up to 5 namespaces in a label.

        • Don't use the following reserved words in your label specification: aws, waf, managed, rulegroup, webacl, regexpatternset, or ipset.

        For example, myLabelName or nameSpace1:nameSpace2:myLabelName.

        • Name — required — (String)

          The label string.

      • VisibilityConfig — required — (map)

        Defines and enables Amazon CloudWatch metrics and web request sample collection.

        • SampledRequestsEnabled — required — (Boolean)

          A boolean indicating whether WAF should store a sampling of the web requests that match the rules. You can view the sampled requests through the WAF console.

        • CloudWatchMetricsEnabled — required — (Boolean)

          A boolean indicating whether the associated resource sends metrics to Amazon CloudWatch. For the list of available metrics, see WAF Metrics.

        • MetricName — required — (String)

          A name of the Amazon CloudWatch metric. The name can contain only the characters: A-Z, a-z, 0-9, - (hyphen), and _ (underscore). The name can be from one to 128 characters long. It can't contain whitespace or metric names reserved for WAF, for example "All" and "Default_Action."

      • CaptchaConfig — (map)

        Specifies how WAF should handle CAPTCHA evaluations. If you don't specify this, WAF uses the CAPTCHA configuration that's defined for the web ACL.

        • ImmunityTimeProperty — (map)

          Determines how long a CAPTCHA token remains valid after the client successfully solves a CAPTCHA puzzle.

          • ImmunityTime — required — (Integer)

            The amount of time, in seconds, that a CAPTCHA token is valid. The default setting is 300.

    • VisibilityConfig — (map)

      Defines and enables Amazon CloudWatch metrics and web request sample collection.

      • SampledRequestsEnabled — required — (Boolean)

        A boolean indicating whether WAF should store a sampling of the web requests that match the rules. You can view the sampled requests through the WAF console.

      • CloudWatchMetricsEnabled — required — (Boolean)

        A boolean indicating whether the associated resource sends metrics to Amazon CloudWatch. For the list of available metrics, see WAF Metrics.

      • MetricName — required — (String)

        A name of the Amazon CloudWatch metric. The name can contain only the characters: A-Z, a-z, 0-9, - (hyphen), and _ (underscore). The name can be from one to 128 characters long. It can't contain whitespace or metric names reserved for WAF, for example "All" and "Default_Action."

    • Tags — (Array<map>)

      An array of key:value pairs to associate with the resource.

      • Key — required — (String)

        Part of the key:value pair that defines a tag. You can use a tag key to describe a category of information, such as "customer." Tag keys are case-sensitive.

      • Value — required — (String)

        Part of the key:value pair that defines a tag. You can use a tag value to describe a specific value within a category, such as "companyA" or "companyB." Tag values are case-sensitive.

    • CustomResponseBodies — (map<map>)

      A map of custom response keys and content bodies. When you create a rule with a block action, you can send a custom response to the web request. You define these for the web ACL, and then use them in the rules and default actions that you define in the web ACL.

      For information about customizing web requests and responses, see Customizing web requests and responses in WAF in the WAF Developer Guide.

      For information about the limits on count and size for custom request and response settings, see WAF quotas in the WAF Developer Guide.

      • ContentType — required — (String)

        The type of content in the payload that you are defining in the Content string.

        Possible values include:
        • "TEXT_PLAIN"
        • "TEXT_HTML"
        • "APPLICATION_JSON"
      • Content — required — (String)

        The payload of the custom response.

        You can use JSON escape strings in JSON content. To do this, you must specify JSON content in the ContentType setting.

        For information about the limits on count and size for custom request and response settings, see WAF quotas in the WAF Developer Guide.

    • CaptchaConfig — (map)

      Specifies how WAF should handle CAPTCHA evaluations for rules that don't have their own CaptchaConfig settings. If you don't specify this, WAF uses its default settings for CaptchaConfig.

      • ImmunityTimeProperty — (map)

        Determines how long a CAPTCHA token remains valid after the client successfully solves a CAPTCHA puzzle.

        • ImmunityTime — required — (Integer)

          The amount of time, in seconds, that a CAPTCHA token is valid. The default setting is 300.

Callback (callback):

  • function(err, data) { ... }

    Called when a response from the service is returned. If a callback is not supplied, you must call AWS.Request.send() on the returned request object to initiate the request.

    Context (this):

    • (AWS.Response) —

      the response object containing error, data properties, and the original request object.

    Parameters:

    • err (Error) —

      the error object returned from the request. Set to null if the request is successful.

    • data (Object) —

      the de-serialized data returned from the request. Set to null if a request error occurs. The data object has the following properties:

      • Summary — (map)

        High-level information about a WebACL, returned by operations like create and list. This provides information like the ID, that you can use to retrieve and manage a WebACL, and the ARN, that you provide to operations like AssociateWebACL.

        • Name — (String)

          The name of the web ACL. You cannot change the name of a web ACL after you create it.

        • Id — (String)

          The unique identifier for the web ACL. This ID is returned in the responses to create and list commands. You provide it to operations like update and delete.

        • Description — (String)

          A description of the web ACL that helps with identification.

        • LockToken — (String)

          A token used for optimistic locking. WAF returns a token to your get and list requests, to mark the state of the entity at the time of the request. To make changes to the entity associated with the token, you provide the token to operations like update and delete. WAF uses the token to ensure that no changes have been made to the entity since you last retrieved it. If a change has been made, the update fails with a WAFOptimisticLockException. If this happens, perform another get, and use the new token returned by that operation.

        • ARN — (String)

          The Amazon Resource Name (ARN) of the entity.

Returns:

  • (AWS.Request) —

    a handle to the operation request for subsequent event callback registration.

deleteFirewallManagerRuleGroups(params = {}, callback) ⇒ AWS.Request

Deletes all rule groups that are managed by Firewall Manager for the specified web ACL.

You can only use this if ManagedByFirewallManager is false in the specified WebACL.

Service Reference:

Examples:

Calling the deleteFirewallManagerRuleGroups operation

var params = {
  WebACLArn: 'STRING_VALUE', /* required */
  WebACLLockToken: 'STRING_VALUE' /* required */
};
wafv2.deleteFirewallManagerRuleGroups(params, function(err, data) {
  if (err) console.log(err, err.stack); // an error occurred
  else     console.log(data);           // successful response
});

Parameters:

  • params (Object) (defaults to: {}) —
    • WebACLArn — (String)

      The Amazon Resource Name (ARN) of the web ACL.

    • WebACLLockToken — (String)

      A token used for optimistic locking. WAF returns a token to your get and list requests, to mark the state of the entity at the time of the request. To make changes to the entity associated with the token, you provide the token to operations like update and delete. WAF uses the token to ensure that no changes have been made to the entity since you last retrieved it. If a change has been made, the update fails with a WAFOptimisticLockException. If this happens, perform another get, and use the new token returned by that operation.

Callback (callback):

  • function(err, data) { ... }

    Called when a response from the service is returned. If a callback is not supplied, you must call AWS.Request.send() on the returned request object to initiate the request.

    Context (this):

    • (AWS.Response) —

      the response object containing error, data properties, and the original request object.

    Parameters:

    • err (Error) —

      the error object returned from the request. Set to null if the request is successful.

    • data (Object) —

      the de-serialized data returned from the request. Set to null if a request error occurs. The data object has the following properties:

      • NextWebACLLockToken — (String)

        A token used for optimistic locking. WAF returns a token to your get and list requests, to mark the state of the entity at the time of the request. To make changes to the entity associated with the token, you provide the token to operations like update and delete. WAF uses the token to ensure that no changes have been made to the entity since you last retrieved it. If a change has been made, the update fails with a WAFOptimisticLockException. If this happens, perform another get, and use the new token returned by that operation.

Returns:

  • (AWS.Request) —

    a handle to the operation request for subsequent event callback registration.

deleteIPSet(params = {}, callback) ⇒ AWS.Request

Deletes the specified IPSet.

Service Reference:

Examples:

Calling the deleteIPSet operation

var params = {
  Id: 'STRING_VALUE', /* required */
  LockToken: 'STRING_VALUE', /* required */
  Name: 'STRING_VALUE', /* required */
  Scope: CLOUDFRONT | REGIONAL /* required */
};
wafv2.deleteIPSet(params, function(err, data) {
  if (err) console.log(err, err.stack); // an error occurred
  else     console.log(data);           // successful response
});

Parameters:

  • params (Object) (defaults to: {}) —
    • Name — (String)

      The name of the IP set. You cannot change the name of an IPSet after you create it.

    • Scope — (String)

      Specifies whether this is for an Amazon CloudFront distribution or for a regional application. A regional application can be an Application Load Balancer (ALB), an Amazon API Gateway REST API, or an AppSync GraphQL API.

      To work with CloudFront, you must also specify the Region US East (N. Virginia) as follows:

      • CLI - Specify the Region when you use the CloudFront scope: --scope=CLOUDFRONT --region=us-east-1.

      • API and SDKs - For all calls, use the Region endpoint us-east-1.

      Possible values include:
      • "CLOUDFRONT"
      • "REGIONAL"
    • Id — (String)

      A unique identifier for the set. This ID is returned in the responses to create and list commands. You provide it to operations like update and delete.

    • LockToken — (String)

      A token used for optimistic locking. WAF returns a token to your get and list requests, to mark the state of the entity at the time of the request. To make changes to the entity associated with the token, you provide the token to operations like update and delete. WAF uses the token to ensure that no changes have been made to the entity since you last retrieved it. If a change has been made, the update fails with a WAFOptimisticLockException. If this happens, perform another get, and use the new token returned by that operation.

Callback (callback):

  • function(err, data) { ... }

    Called when a response from the service is returned. If a callback is not supplied, you must call AWS.Request.send() on the returned request object to initiate the request.

    Context (this):

    • (AWS.Response) —

      the response object containing error, data properties, and the original request object.

    Parameters:

    • err (Error) —

      the error object returned from the request. Set to null if the request is successful.

    • data (Object) —

      the de-serialized data returned from the request. Set to null if a request error occurs.

Returns:

  • (AWS.Request) —

    a handle to the operation request for subsequent event callback registration.

deleteLoggingConfiguration(params = {}, callback) ⇒ AWS.Request

Deletes the LoggingConfiguration from the specified web ACL.

Service Reference:

Examples:

Calling the deleteLoggingConfiguration operation

var params = {
  ResourceArn: 'STRING_VALUE' /* required */
};
wafv2.deleteLoggingConfiguration(params, function(err, data) {
  if (err) console.log(err, err.stack); // an error occurred
  else     console.log(data);           // successful response
});

Parameters:

  • params (Object) (defaults to: {}) —
    • ResourceArn — (String)

      The Amazon Resource Name (ARN) of the web ACL from which you want to delete the LoggingConfiguration.

Callback (callback):

  • function(err, data) { ... }

    Called when a response from the service is returned. If a callback is not supplied, you must call AWS.Request.send() on the returned request object to initiate the request.

    Context (this):

    • (AWS.Response) —

      the response object containing error, data properties, and the original request object.

    Parameters:

    • err (Error) —

      the error object returned from the request. Set to null if the request is successful.

    • data (Object) —

      the de-serialized data returned from the request. Set to null if a request error occurs.

Returns:

  • (AWS.Request) —

    a handle to the operation request for subsequent event callback registration.

deletePermissionPolicy(params = {}, callback) ⇒ AWS.Request

Permanently deletes an IAM policy from the specified rule group.

You must be the owner of the rule group to perform this operation.

Service Reference:

Examples:

Calling the deletePermissionPolicy operation

var params = {
  ResourceArn: 'STRING_VALUE' /* required */
};
wafv2.deletePermissionPolicy(params, function(err, data) {
  if (err) console.log(err, err.stack); // an error occurred
  else     console.log(data);           // successful response
});

Parameters:

  • params (Object) (defaults to: {}) —
    • ResourceArn — (String)

      The Amazon Resource Name (ARN) of the rule group from which you want to delete the policy.

      You must be the owner of the rule group to perform this operation.

Callback (callback):

  • function(err, data) { ... }

    Called when a response from the service is returned. If a callback is not supplied, you must call AWS.Request.send() on the returned request object to initiate the request.

    Context (this):

    • (AWS.Response) —

      the response object containing error, data properties, and the original request object.

    Parameters:

    • err (Error) —

      the error object returned from the request. Set to null if the request is successful.

    • data (Object) —

      the de-serialized data returned from the request. Set to null if a request error occurs.

Returns:

  • (AWS.Request) —

    a handle to the operation request for subsequent event callback registration.

deleteRegexPatternSet(params = {}, callback) ⇒ AWS.Request

Deletes the specified RegexPatternSet.

Service Reference:

Examples:

Calling the deleteRegexPatternSet operation

var params = {
  Id: 'STRING_VALUE', /* required */
  LockToken: 'STRING_VALUE', /* required */
  Name: 'STRING_VALUE', /* required */
  Scope: CLOUDFRONT | REGIONAL /* required */
};
wafv2.deleteRegexPatternSet(params, function(err, data) {
  if (err) console.log(err, err.stack); // an error occurred
  else     console.log(data);           // successful response
});

Parameters:

  • params (Object) (defaults to: {}) —
    • Name — (String)

      The name of the set. You cannot change the name after you create the set.

    • Scope — (String)

      Specifies whether this is for an Amazon CloudFront distribution or for a regional application. A regional application can be an Application Load Balancer (ALB), an Amazon API Gateway REST API, or an AppSync GraphQL API.

      To work with CloudFront, you must also specify the Region US East (N. Virginia) as follows:

      • CLI - Specify the Region when you use the CloudFront scope: --scope=CLOUDFRONT --region=us-east-1.

      • API and SDKs - For all calls, use the Region endpoint us-east-1.

      Possible values include:
      • "CLOUDFRONT"
      • "REGIONAL"
    • Id — (String)

      A unique identifier for the set. This ID is returned in the responses to create and list commands. You provide it to operations like update and delete.

    • LockToken — (String)

      A token used for optimistic locking. WAF returns a token to your get and list requests, to mark the state of the entity at the time of the request. To make changes to the entity associated with the token, you provide the token to operations like update and delete. WAF uses the token to ensure that no changes have been made to the entity since you last retrieved it. If a change has been made, the update fails with a WAFOptimisticLockException. If this happens, perform another get, and use the new token returned by that operation.

Callback (callback):

  • function(err, data) { ... }

    Called when a response from the service is returned. If a callback is not supplied, you must call AWS.Request.send() on the returned request object to initiate the request.

    Context (this):

    • (AWS.Response) —

      the response object containing error, data properties, and the original request object.

    Parameters:

    • err (Error) —

      the error object returned from the request. Set to null if the request is successful.

    • data (Object) —

      the de-serialized data returned from the request. Set to null if a request error occurs.

Returns:

  • (AWS.Request) —

    a handle to the operation request for subsequent event callback registration.

deleteRuleGroup(params = {}, callback) ⇒ AWS.Request

Deletes the specified RuleGroup.

Service Reference:

Examples:

Calling the deleteRuleGroup operation

var params = {
  Id: 'STRING_VALUE', /* required */
  LockToken: 'STRING_VALUE', /* required */
  Name: 'STRING_VALUE', /* required */
  Scope: CLOUDFRONT | REGIONAL /* required */
};
wafv2.deleteRuleGroup(params, function(err, data) {
  if (err) console.log(err, err.stack); // an error occurred
  else     console.log(data);           // successful response
});

Parameters:

  • params (Object) (defaults to: {}) —
    • Name — (String)

      The name of the rule group. You cannot change the name of a rule group after you create it.

    • Scope — (String)

      Specifies whether this is for an Amazon CloudFront distribution or for a regional application. A regional application can be an Application Load Balancer (ALB), an Amazon API Gateway REST API, or an AppSync GraphQL API.

      To work with CloudFront, you must also specify the Region US East (N. Virginia) as follows:

      • CLI - Specify the Region when you use the CloudFront scope: --scope=CLOUDFRONT --region=us-east-1.

      • API and SDKs - For all calls, use the Region endpoint us-east-1.

      Possible values include:
      • "CLOUDFRONT"
      • "REGIONAL"
    • Id — (String)

      A unique identifier for the rule group. This ID is returned in the responses to create and list commands. You provide it to operations like update and delete.

    • LockToken — (String)

      A token used for optimistic locking. WAF returns a token to your get and list requests, to mark the state of the entity at the time of the request. To make changes to the entity associated with the token, you provide the token to operations like update and delete. WAF uses the token to ensure that no changes have been made to the entity since you last retrieved it. If a change has been made, the update fails with a WAFOptimisticLockException. If this happens, perform another get, and use the new token returned by that operation.

Callback (callback):

  • function(err, data) { ... }

    Called when a response from the service is returned. If a callback is not supplied, you must call AWS.Request.send() on the returned request object to initiate the request.

    Context (this):

    • (AWS.Response) —

      the response object containing error, data properties, and the original request object.

    Parameters:

    • err (Error) —

      the error object returned from the request. Set to null if the request is successful.

    • data (Object) —

      the de-serialized data returned from the request. Set to null if a request error occurs.

Returns:

  • (AWS.Request) —

    a handle to the operation request for subsequent event callback registration.

deleteWebACL(params = {}, callback) ⇒ AWS.Request

Deletes the specified WebACL.

You can only use this if ManagedByFirewallManager is false in the specified WebACL.

Service Reference:

Examples:

Calling the deleteWebACL operation

var params = {
  Id: 'STRING_VALUE', /* required */
  LockToken: 'STRING_VALUE', /* required */
  Name: 'STRING_VALUE', /* required */
  Scope: CLOUDFRONT | REGIONAL /* required */
};
wafv2.deleteWebACL(params, function(err, data) {
  if (err) console.log(err, err.stack); // an error occurred
  else     console.log(data);           // successful response
});

Parameters:

  • params (Object) (defaults to: {}) —
    • Name — (String)

      The name of the web ACL. You cannot change the name of a web ACL after you create it.

    • Scope — (String)

      Specifies whether this is for an Amazon CloudFront distribution or for a regional application. A regional application can be an Application Load Balancer (ALB), an Amazon API Gateway REST API, or an AppSync GraphQL API.

      To work with CloudFront, you must also specify the Region US East (N. Virginia) as follows:

      • CLI - Specify the Region when you use the CloudFront scope: --scope=CLOUDFRONT --region=us-east-1.

      • API and SDKs - For all calls, use the Region endpoint us-east-1.

      Possible values include:
      • "CLOUDFRONT"
      • "REGIONAL"
    • Id — (String)

      The unique identifier for the web ACL. This ID is returned in the responses to create and list commands. You provide it to operations like update and delete.

    • LockToken — (String)

      A token used for optimistic locking. WAF returns a token to your get and list requests, to mark the state of the entity at the time of the request. To make changes to the entity associated with the token, you provide the token to operations like update and delete. WAF uses the token to ensure that no changes have been made to the entity since you last retrieved it. If a change has been made, the update fails with a WAFOptimisticLockException. If this happens, perform another get, and use the new token returned by that operation.

Callback (callback):

  • function(err, data) { ... }

    Called when a response from the service is returned. If a callback is not supplied, you must call AWS.Request.send() on the returned request object to initiate the request.

    Context (this):

    • (AWS.Response) —

      the response object containing error, data properties, and the original request object.

    Parameters:

    • err (Error) —

      the error object returned from the request. Set to null if the request is successful.

    • data (Object) —

      the de-serialized data returned from the request. Set to null if a request error occurs.

Returns:

  • (AWS.Request) —

    a handle to the operation request for subsequent event callback registration.

describeManagedRuleGroup(params = {}, callback) ⇒ AWS.Request

Provides high-level information for a managed rule group, including descriptions of the rules.

Service Reference:

Examples:

Calling the describeManagedRuleGroup operation

var params = {
  Name: 'STRING_VALUE', /* required */
  Scope: CLOUDFRONT | REGIONAL, /* required */
  VendorName: 'STRING_VALUE', /* required */
  VersionName: 'STRING_VALUE'
};
wafv2.describeManagedRuleGroup(params, function(err, data) {
  if (err) console.log(err, err.stack); // an error occurred
  else     console.log(data);           // successful response
});

Parameters:

  • params (Object) (defaults to: {}) —
    • VendorName — (String)

      The name of the managed rule group vendor. You use this, along with the rule group name, to identify the rule group.

    • Name — (String)

      The name of the managed rule group. You use this, along with the vendor name, to identify the rule group.

    • Scope — (String)

      Specifies whether this is for an Amazon CloudFront distribution or for a regional application. A regional application can be an Application Load Balancer (ALB), an Amazon API Gateway REST API, or an AppSync GraphQL API.

      To work with CloudFront, you must also specify the Region US East (N. Virginia) as follows:

      • CLI - Specify the Region when you use the CloudFront scope: --scope=CLOUDFRONT --region=us-east-1.

      • API and SDKs - For all calls, use the Region endpoint us-east-1.

      Possible values include:
      • "CLOUDFRONT"
      • "REGIONAL"
    • VersionName — (String)

      The version of the rule group. You can only use a version that is not scheduled for expiration. If you don't provide this, WAF uses the vendor's default version.

Callback (callback):

  • function(err, data) { ... }

    Called when a response from the service is returned. If a callback is not supplied, you must call AWS.Request.send() on the returned request object to initiate the request.

    Context (this):

    • (AWS.Response) —

      the response object containing error, data properties, and the original request object.

    Parameters:

    • err (Error) —

      the error object returned from the request. Set to null if the request is successful.

    • data (Object) —

      the de-serialized data returned from the request. Set to null if a request error occurs. The data object has the following properties:

      • VersionName — (String)

        The managed rule group's version.

      • SnsTopicArn — (String)

        The Amazon resource name (ARN) of the Amazon Simple Notification Service SNS topic that's used to record changes to the managed rule group. You can subscribe to the SNS topic to receive notifications when the managed rule group is modified, such as for new versions and for version expiration. For more information, see the Amazon Simple Notification Service Developer Guide.

      • Capacity — (Integer)

        The web ACL capacity units (WCUs) required for this rule group. WAF uses web ACL capacity units (WCU) to calculate and control the operating resources that are used to run your rules, rule groups, and web ACLs. WAF calculates capacity differently for each rule type, to reflect each rule's relative cost. Rule group capacity is fixed at creation, so users can plan their web ACL WCU usage when they use a rule group. The WCU limit for web ACLs is 1,500.

      • Rules — (Array<map>)

        • Name — (String)

          The name of the rule.

        • Action — (map)

          The action that WAF should take on a web request when it matches a rule's statement. Settings at the web ACL level can override the rule action setting.

          • Block — (map)

            Instructs WAF to block the web request.

            • CustomResponse — (map)

              Defines a custom response for the web request.

              For information about customizing web requests and responses, see Customizing web requests and responses in WAF in the WAF Developer Guide.

              • ResponseCode — required — (Integer)

                The HTTP status code to return to the client.

                For a list of status codes that you can use in your custom reqponses, see Supported status codes for custom response in the WAF Developer Guide.

              • CustomResponseBodyKey — (String)

                References the response body that you want WAF to return to the web request client. You can define a custom response for a rule action or a default web ACL action that is set to block. To do this, you first define the response body key and value in the CustomResponseBodies setting for the WebACL or RuleGroup where you want to use it. Then, in the rule action or web ACL default action BlockAction setting, you reference the response body using this key.

              • ResponseHeaders — (Array<map>)

                The HTTP headers to use in the response. Duplicate header names are not allowed.

                For information about the limits on count and size for custom request and response settings, see WAF quotas in the WAF Developer Guide.

                • Name — required — (String)

                  The name of the custom header.

                  For custom request header insertion, when WAF inserts the header into the request, it prefixes this name x-amzn-waf-, to avoid confusion with the headers that are already in the request. For example, for the header name sample, WAF inserts the header x-amzn-waf-sample.

                • Value — required — (String)

                  The value of the custom header.

          • Allow — (map)

            Instructs WAF to allow the web request.

            • CustomRequestHandling — (map)

              Defines custom handling for the web request.

              For information about customizing web requests and responses, see Customizing web requests and responses in WAF in the WAF Developer Guide.

              • InsertHeaders — required — (Array<map>)

                The HTTP headers to insert into the request. Duplicate header names are not allowed.

                For information about the limits on count and size for custom request and response settings, see WAF quotas in the WAF Developer Guide.

                • Name — required — (String)

                  The name of the custom header.

                  For custom request header insertion, when WAF inserts the header into the request, it prefixes this name x-amzn-waf-, to avoid confusion with the headers that are already in the request. For example, for the header name sample, WAF inserts the header x-amzn-waf-sample.

                • Value — required — (String)

                  The value of the custom header.

          • Count — (map)

            Instructs WAF to count the web request and allow it.

            • CustomRequestHandling — (map)

              Defines custom handling for the web request.

              For information about customizing web requests and responses, see Customizing web requests and responses in WAF in the WAF Developer Guide.

              • InsertHeaders — required — (Array<map>)

                The HTTP headers to insert into the request. Duplicate header names are not allowed.

                For information about the limits on count and size for custom request and response settings, see WAF quotas in the WAF Developer Guide.

                • Name — required — (String)

                  The name of the custom header.

                  For custom request header insertion, when WAF inserts the header into the request, it prefixes this name x-amzn-waf-, to avoid confusion with the headers that are already in the request. For example, for the header name sample, WAF inserts the header x-amzn-waf-sample.

                • Value — required — (String)

                  The value of the custom header.

          • Captcha — (map)

            Instructs WAF to run a CAPTCHA check against the web request.

            • CustomRequestHandling — (map)

              Defines custom handling for the web request.

              For information about customizing web requests and responses, see Customizing web requests and responses in WAF in the WAF Developer Guide.

              • InsertHeaders — required — (Array<map>)

                The HTTP headers to insert into the request. Duplicate header names are not allowed.

                For information about the limits on count and size for custom request and response settings, see WAF quotas in the WAF Developer Guide.

                • Name — required — (String)

                  The name of the custom header.

                  For custom request header insertion, when WAF inserts the header into the request, it prefixes this name x-amzn-waf-, to avoid confusion with the headers that are already in the request. For example, for the header name sample, WAF inserts the header x-amzn-waf-sample.

                • Value — required — (String)

                  The value of the custom header.

      • LabelNamespace — (String)

        The label namespace prefix for this rule group. All labels added by rules in this rule group have this prefix.

        • The syntax for the label namespace prefix for a managed rule group is the following:

          awswaf:managed:<vendor>:<rule group name>:

        • When a rule with a label matches a web request, WAF adds the fully qualified label to the request. A fully qualified label is made up of the label namespace from the rule group or web ACL where the rule is defined and the label from the rule, separated by a colon:

          <label namespace>:<label from rule>

      • AvailableLabels — (Array<map>)

        The labels that one or more rules in this rule group add to matching web requests. These labels are defined in the RuleLabels for a Rule.

        • Name — (String)

          An individual label specification.

      • ConsumedLabels — (Array<map>)

        The labels that one or more rules in this rule group match against in label match statements. These labels are defined in a LabelMatchStatement specification, in the Statement definition of a rule.

        • Name — (String)

          An individual label specification.

Returns:

  • (AWS.Request) —

    a handle to the operation request for subsequent event callback registration.

disassociateWebACL(params = {}, callback) ⇒ AWS.Request

Disassociates a web ACL from a regional application resource. A regional application can be an Application Load Balancer (ALB), an Amazon API Gateway REST API, or an AppSync GraphQL API.

For Amazon CloudFront, don't use this call. Instead, use your CloudFront distribution configuration. To disassociate a web ACL, provide an empty web ACL ID in the CloudFront call UpdateDistribution. For information, see UpdateDistribution.

Service Reference:

Examples:

Calling the disassociateWebACL operation

var params = {
  ResourceArn: 'STRING_VALUE' /* required */
};
wafv2.disassociateWebACL(params, function(err, data) {
  if (err) console.log(err, err.stack); // an error occurred
  else     console.log(data);           // successful response
});

Parameters:

  • params (Object) (defaults to: {}) —
    • ResourceArn — (String)

      The Amazon Resource Name (ARN) of the resource to disassociate from the web ACL.

      The ARN must be in one of the following formats:

      • For an Application Load Balancer: arn:aws:elasticloadbalancing:region:account-id:loadbalancer/app/load-balancer-name/load-balancer-id

      • For an Amazon API Gateway REST API: arn:aws:apigateway:region::/restapis/api-id/stages/stage-name

      • For an AppSync GraphQL API: arn:aws:appsync:region:account-id:apis/GraphQLApiId

Callback (callback):

  • function(err, data) { ... }

    Called when a response from the service is returned. If a callback is not supplied, you must call AWS.Request.send() on the returned request object to initiate the request.

    Context (this):

    • (AWS.Response) —

      the response object containing error, data properties, and the original request object.

    Parameters:

    • err (Error) —

      the error object returned from the request. Set to null if the request is successful.

    • data (Object) —

      the de-serialized data returned from the request. Set to null if a request error occurs.

Returns:

  • (AWS.Request) —

    a handle to the operation request for subsequent event callback registration.

getIPSet(params = {}, callback) ⇒ AWS.Request

Retrieves the specified IPSet.

Service Reference:

Examples:

Calling the getIPSet operation

var params = {
  Id: 'STRING_VALUE', /* required */
  Name: 'STRING_VALUE', /* required */
  Scope: CLOUDFRONT | REGIONAL /* required */
};
wafv2.getIPSet(params, function(err, data) {
  if (err) console.log(err, err.stack); // an error occurred
  else     console.log(data);           // successful response
});

Parameters:

  • params (Object) (defaults to: {}) —
    • Name — (String)

      The name of the IP set. You cannot change the name of an IPSet after you create it.

    • Scope — (String)

      Specifies whether this is for an Amazon CloudFront distribution or for a regional application. A regional application can be an Application Load Balancer (ALB), an Amazon API Gateway REST API, or an AppSync GraphQL API.

      To work with CloudFront, you must also specify the Region US East (N. Virginia) as follows:

      • CLI - Specify the Region when you use the CloudFront scope: --scope=CLOUDFRONT --region=us-east-1.

      • API and SDKs - For all calls, use the Region endpoint us-east-1.

      Possible values include:
      • "CLOUDFRONT"
      • "REGIONAL"
    • Id — (String)

      A unique identifier for the set. This ID is returned in the responses to create and list commands. You provide it to operations like update and delete.

Callback (callback):

  • function(err, data) { ... }

    Called when a response from the service is returned. If a callback is not supplied, you must call AWS.Request.send() on the returned request object to initiate the request.

    Context (this):

    • (AWS.Response) —

      the response object containing error, data properties, and the original request object.

    Parameters:

    • err (Error) —

      the error object returned from the request. Set to null if the request is successful.

    • data (Object) —

      the de-serialized data returned from the request. Set to null if a request error occurs. The data object has the following properties:

      • IPSet — (map)

        • Name — required — (String)

          The name of the IP set. You cannot change the name of an IPSet after you create it.

        • Id — required — (String)

          A unique identifier for the set. This ID is returned in the responses to create and list commands. You provide it to operations like update and delete.

        • ARN — required — (String)

          The Amazon Resource Name (ARN) of the entity.

        • Description — (String)

          A description of the IP set that helps with identification.

        • IPAddressVersion — required — (String)

          The version of the IP addresses, either IPV4 or IPV6.

          Possible values include:
          • "IPV4"
          • "IPV6"
        • Addresses — required — (Array<String>)

          Contains an array of strings that specify one or more IP addresses or blocks of IP addresses in Classless Inter-Domain Routing (CIDR) notation. WAF supports all IPv4 and IPv6 CIDR ranges except for /0.

          Examples:

          • To configure WAF to allow, block, or count requests that originated from the IP address 192.0.2.44, specify 192.0.2.44/32.

          • To configure WAF to allow, block, or count requests that originated from IP addresses from 192.0.2.0 to 192.0.2.255, specify 192.0.2.0/24.

          • To configure WAF to allow, block, or count requests that originated from the IP address 1111:0000:0000:0000:0000:0000:0000:0111, specify 1111:0000:0000:0000:0000:0000:0000:0111/128.

          • To configure WAF to allow, block, or count requests that originated from IP addresses 1111:0000:0000:0000:0000:0000:0000:0000 to 1111:0000:0000:0000:ffff:ffff:ffff:ffff, specify 1111:0000:0000:0000:0000:0000:0000:0000/64.

          For more information about CIDR notation, see the Wikipedia entry Classless Inter-Domain Routing.

      • LockToken — (String)

        A token used for optimistic locking. WAF returns a token to your get and list requests, to mark the state of the entity at the time of the request. To make changes to the entity associated with the token, you provide the token to operations like update and delete. WAF uses the token to ensure that no changes have been made to the entity since you last retrieved it. If a change has been made, the update fails with a WAFOptimisticLockException. If this happens, perform another get, and use the new token returned by that operation.

Returns:

  • (AWS.Request) —

    a handle to the operation request for subsequent event callback registration.

getLoggingConfiguration(params = {}, callback) ⇒ AWS.Request

Returns the LoggingConfiguration for the specified web ACL.

Service Reference:

Examples:

Calling the getLoggingConfiguration operation

var params = {
  ResourceArn: 'STRING_VALUE' /* required */
};
wafv2.getLoggingConfiguration(params, function(err, data) {
  if (err) console.log(err, err.stack); // an error occurred
  else     console.log(data);           // successful response
});

Parameters:

  • params (Object) (defaults to: {}) —
    • ResourceArn — (String)

      The Amazon Resource Name (ARN) of the web ACL for which you want to get the LoggingConfiguration.

Callback (callback):

  • function(err, data) { ... }

    Called when a response from the service is returned. If a callback is not supplied, you must call AWS.Request.send() on the returned request object to initiate the request.

    Context (this):

    • (AWS.Response) —

      the response object containing error, data properties, and the original request object.

    Parameters:

    • err (Error) —

      the error object returned from the request. Set to null if the request is successful.

    • data (Object) —

      the de-serialized data returned from the request. Set to null if a request error occurs. The data object has the following properties:

      • LoggingConfiguration — (map)

        The LoggingConfiguration for the specified web ACL.

        • ResourceArn — required — (String)

          The Amazon Resource Name (ARN) of the web ACL that you want to associate with LogDestinationConfigs.

        • LogDestinationConfigs — required — (Array<String>)

          The Amazon Kinesis Data Firehose Amazon Resource Name (ARNs) that you want to associate with the web ACL.

        • RedactedFields — (Array<map>)

          The parts of the request that you want to keep out of the logs. For example, if you redact the SingleHeader field, the HEADER field in the firehose will be xxx.

          Note: You can specify only the following fields for redaction: UriPath, QueryString, SingleHeader, Method, and JsonBody.
          • SingleHeader — (map)

            Inspect a single header. Provide the name of the header to inspect, for example, User-Agent or Referer. This setting isn't case sensitive.

            Example JSON: "SingleHeader": { "Name": "haystack" }

            • Name — required — (String)

              The name of the query header to inspect.

          • SingleQueryArgument — (map)

            Inspect a single query argument. Provide the name of the query argument to inspect, such as UserName or SalesRegion. The name can be up to 30 characters long and isn't case sensitive.

            This is used only to indicate the web request component for WAF to inspect, in the FieldToMatch specification.

            Example JSON: "SingleQueryArgument": { "Name": "myArgument" }

            • Name — required — (String)

              The name of the query argument to inspect.

          • AllQueryArguments — (map)

            Inspect all query arguments.

          • UriPath — (map)

            Inspect the request URI path. This is the part of a web request that identifies a resource, for example, /images/daily-ad.jpg.

          • QueryString — (map)

            Inspect the query string. This is the part of a URL that appears after a ? character, if any.

          • Body — (map)

            Inspect the request body as plain text. The request body immediately follows the request headers. This is the part of a request that contains any additional data that you want to send to your web server as the HTTP request body, such as data from a form.

            Note that only the first 8 KB (8192 bytes) of the request body are forwarded to WAF for inspection by the underlying host service. If you don't need to inspect more than 8 KB, you can guarantee that you don't allow additional bytes in by combining a statement that inspects the body of the web request, such as ByteMatchStatement or RegexPatternSetReferenceStatement, with a SizeConstraintStatement that enforces an 8 KB size limit on the body of the request. WAF doesn't support inspecting the entire contents of web requests whose bodies exceed the 8 KB limit.

          • Method — (map)

            Inspect the HTTP method. The method indicates the type of operation that the request is asking the origin to perform.

          • JsonBody — (map)

            Inspect the request body as JSON. The request body immediately follows the request headers. This is the part of a request that contains any additional data that you want to send to your web server as the HTTP request body, such as data from a form.

            Note that only the first 8 KB (8192 bytes) of the request body are forwarded to WAF for inspection by the underlying host service. If you don't need to inspect more than 8 KB, you can guarantee that you don't allow additional bytes in by combining a statement that inspects the body of the web request, such as ByteMatchStatement or RegexPatternSetReferenceStatement, with a SizeConstraintStatement that enforces an 8 KB size limit on the body of the request. WAF doesn't support inspecting the entire contents of web requests whose bodies exceed the 8 KB limit.

            • MatchPattern — required — (map)

              The patterns to look for in the JSON body. WAF inspects the results of these pattern matches against the rule inspection criteria.

              • All — (map)

                Match all of the elements. See also MatchScope in JsonBody.

                You must specify either this setting or the IncludedPaths setting, but not both.

              • IncludedPaths — (Array<String>)

                Match only the specified include paths. See also MatchScope in JsonBody.

                Provide the include paths using JSON Pointer syntax. For example, "IncludedPaths": ["/dogs/0/name", "/dogs/1/name"]. For information about this syntax, see the Internet Engineering Task Force (IETF) documentation JavaScript Object Notation (JSON) Pointer.

                You must specify either this setting or the All setting, but not both.

                Note: Don't use this option to include all paths. Instead, use the All setting.
            • MatchScope — required — (String)

              The parts of the JSON to match against using the MatchPattern. If you specify All, WAF matches against keys and values.

              Possible values include:
              • "ALL"
              • "KEY"
              • "VALUE"
            • InvalidFallbackBehavior — (String)

              What WAF should do if it fails to completely parse the JSON body. The options are the following:

              • EVALUATE_AS_STRING - Inspect the body as plain text. WAF applies the text transformations and inspection criteria that you defined for the JSON inspection to the body text string.

              • MATCH - Treat the web request as matching the rule statement. WAF applies the rule action to the request.

              • NO_MATCH - Treat the web request as not matching the rule statement.

              If you don't provide this setting, WAF parses and evaluates the content only up to the first parsing failure that it encounters.

              WAF does its best to parse the entire JSON body, but might be forced to stop for reasons such as invalid characters, duplicate keys, truncation, and any content whose root node isn't an object or an array.

              WAF parses the JSON in the following examples as two valid key, value pairs:

              • Missing comma: {"key1":"value1""key2":"value2"}

              • Missing colon: {"key1":"value1","key2""value2"}

              • Extra colons: {"key1"::"value1","key2""value2"}

              Possible values include:
              • "MATCH"
              • "NO_MATCH"
              • "EVALUATE_AS_STRING"
        • ManagedByFirewallManager — (Boolean)

          Indicates whether the logging configuration was created by Firewall Manager, as part of an WAF policy configuration. If true, only Firewall Manager can modify or delete the configuration.

        • LoggingFilter — (map)

          Filtering that specifies which web requests are kept in the logs and which are dropped. You can filter on the rule action and on the web request labels that were applied by matching rules during web ACL evaluation.

          • Filters — required — (Array<map>)

            The filters that you want to apply to the logs.

            • Behavior — required — (String)

              How to handle logs that satisfy the filter's conditions and requirement.

              Possible values include:
              • "KEEP"
              • "DROP"
            • Requirement — required — (String)

              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.

              Possible values include:
              • "MEETS_ALL"
              • "MEETS_ANY"
            • Conditions — required — (Array<map>)

              Match conditions for the filter.

              • ActionCondition — (map)

                A single action condition.

                • Action — required — (String)

                  The action setting that a log record must contain in order to meet the condition.

                  Possible values include:
                  • "ALLOW"
                  • "BLOCK"
                  • "COUNT"
                  • "CAPTCHA"
                  • "EXCLUDED_AS_COUNT"
              • LabelNameCondition — (map)

                A single label name condition.

                • LabelName — required — (String)

                  The label name that a log record must contain in order to meet the condition. This must be a fully qualified label name. Fully qualified labels have a prefix, optional namespaces, and label name. The prefix identifies the rule group or web ACL context of the rule that added the label.

          • DefaultBehavior — required — (String)

            Default handling for logs that don't match any of the specified filtering conditions.

            Possible values include:
            • "KEEP"
            • "DROP"

Returns:

  • (AWS.Request) —

    a handle to the operation request for subsequent event callback registration.

getManagedRuleSet(params = {}, callback) ⇒ AWS.Request

Retrieves the specified managed rule set.

Note: This is intended for use only by vendors of managed rule sets. Vendors are Amazon Web Services and Amazon Web Services Marketplace sellers. Vendors, you can use the managed rule set APIs to provide controlled rollout of your versioned managed rule group offerings for your customers. The APIs are ListManagedRuleSets, GetManagedRuleSet, PutManagedRuleSetVersions, and UpdateManagedRuleSetVersionExpiryDate.

Service Reference:

Examples:

Calling the getManagedRuleSet operation

var params = {
  Id: 'STRING_VALUE', /* required */
  Name: 'STRING_VALUE', /* required */
  Scope: CLOUDFRONT | REGIONAL /* required */
};
wafv2.getManagedRuleSet(params, function(err, data) {
  if (err) console.log(err, err.stack); // an error occurred
  else     console.log(data);           // successful response
});

Parameters:

  • params (Object) (defaults to: {}) —
    • Name — (String)

      The name of the managed rule set. You use this, along with the rule set ID, to identify the rule set.

      This name is assigned to the corresponding managed rule group, which your customers can access and use.

    • Scope — (String)

      Specifies whether this is for an Amazon CloudFront distribution or for a regional application. A regional application can be an Application Load Balancer (ALB), an Amazon API Gateway REST API, or an AppSync GraphQL API.

      To work with CloudFront, you must also specify the Region US East (N. Virginia) as follows:

      • CLI - Specify the Region when you use the CloudFront scope: --scope=CLOUDFRONT --region=us-east-1.

      • API and SDKs - For all calls, use the Region endpoint us-east-1.

      Possible values include:
      • "CLOUDFRONT"
      • "REGIONAL"
    • Id — (String)

      A unique identifier for the managed rule set. The ID is returned in the responses to commands like list. You provide it to operations like get and update.

Callback (callback):

  • function(err, data) { ... }

    Called when a response from the service is returned. If a callback is not supplied, you must call AWS.Request.send() on the returned request object to initiate the request.

    Context (this):

    • (AWS.Response) —

      the response object containing error, data properties, and the original request object.

    Parameters:

    • err (Error) —

      the error object returned from the request. Set to null if the request is successful.

    • data (Object) —

      the de-serialized data returned from the request. Set to null if a request error occurs. The data object has the following properties:

      • ManagedRuleSet — (map)

        The managed rule set that you requested.

        • Name — required — (String)

          The name of the managed rule set. You use this, along with the rule set ID, to identify the rule set.

          This name is assigned to the corresponding managed rule group, which your customers can access and use.

        • Id — required — (String)

          A unique identifier for the managed rule set. The ID is returned in the responses to commands like list. You provide it to operations like get and update.

        • ARN — required — (String)

          The Amazon Resource Name (ARN) of the entity.

        • Description — (String)

          A description of the set that helps with identification.

        • PublishedVersions — (map<map>)

          The versions of this managed rule set that are available for use by customers.

          • AssociatedRuleGroupArn — (String)

            The Amazon Resource Name (ARN) of the vendor rule group that's used to define the published version of your managed rule group.

          • Capacity — (Integer)

            The web ACL capacity units (WCUs) required for this rule group.

            WAF uses WCUs to calculate and control the operating resources that are used to run your rules, rule groups, and web ACLs. WAF calculates capacity differently for each rule type, to reflect the relative cost of each rule. Simple rules that cost little to run use fewer WCUs than more complex rules that use more processing power. Rule group capacity is fixed at creation, which helps users plan their web ACL WCU usage when they use a rule group. The WCU limit for web ACLs is 1,500.

          • ForecastedLifetime — (Integer)

            The amount of time you expect this version of your managed rule group to last, in days.

          • PublishTimestamp — (Date)

            The time that you first published this version.

            Times are in Coordinated Universal Time (UTC) format. UTC format includes the special designator, Z. For example, "2016-09-27T14:50Z".

          • LastUpdateTimestamp — (Date)

            The last time that you updated this version.

            Times are in Coordinated Universal Time (UTC) format. UTC format includes the special designator, Z. For example, "2016-09-27T14:50Z".

          • ExpiryTimestamp — (Date)

            The time that this version is set to expire.

            Times are in Coordinated Universal Time (UTC) format. UTC format includes the special designator, Z. For example, "2016-09-27T14:50Z".

        • RecommendedVersion — (String)

          The version that you would like your customers to use.

        • LabelNamespace — (String)

          The label namespace prefix for the managed rule groups that are offered to customers from this managed rule set. All labels that are added by rules in the managed rule group have this prefix.

          • The syntax for the label namespace prefix for a managed rule group is the following:

            awswaf:managed:<vendor>:<rule group name>:

          • When a rule with a label matches a web request, WAF adds the fully qualified label to the request. A fully qualified label is made up of the label namespace from the rule group or web ACL where the rule is defined and the label from the rule, separated by a colon:

            <label namespace>:<label from rule>

      • LockToken — (String)

        A token used for optimistic locking. WAF returns a token to your get and list requests, to mark the state of the entity at the time of the request. To make changes to the entity associated with the token, you provide the token to operations like update and delete. WAF uses the token to ensure that no changes have been made to the entity since you last retrieved it. If a change has been made, the update fails with a WAFOptimisticLockException. If this happens, perform another get, and use the new token returned by that operation.

Returns:

  • (AWS.Request) —

    a handle to the operation request for subsequent event callback registration.

getPermissionPolicy(params = {}, callback) ⇒ AWS.Request

Returns the IAM policy that is attached to the specified rule group.

You must be the owner of the rule group to perform this operation.

Service Reference:

Examples:

Calling the getPermissionPolicy operation

var params = {
  ResourceArn: 'STRING_VALUE' /* required */
};
wafv2.getPermissionPolicy(params, function(err, data) {
  if (err) console.log(err, err.stack); // an error occurred
  else     console.log(data);           // successful response
});

Parameters:

  • params (Object) (defaults to: {}) —
    • ResourceArn — (String)

      The Amazon Resource Name (ARN) of the rule group for which you want to get the policy.

Callback (callback):

  • function(err, data) { ... }

    Called when a response from the service is returned. If a callback is not supplied, you must call AWS.Request.send() on the returned request object to initiate the request.

    Context (this):

    • (AWS.Response) —

      the response object containing error, data properties, and the original request object.

    Parameters:

    • err (Error) —

      the error object returned from the request. Set to null if the request is successful.

    • data (Object) —

      the de-serialized data returned from the request. Set to null if a request error occurs. The data object has the following properties:

      • Policy — (String)

        The IAM policy that is attached to the specified rule group.

Returns:

  • (AWS.Request) —

    a handle to the operation request for subsequent event callback registration.

getRateBasedStatementManagedKeys(params = {}, callback) ⇒ AWS.Request

Retrieves the keys that are currently blocked by a rate-based rule instance. The maximum number of managed keys that can be blocked for a single rate-based rule instance is 10,000. If more than 10,000 addresses exceed the rate limit, those with the highest rates are blocked.

For a rate-based rule that you've defined inside a rule group, provide the name of the rule group reference statement in your request, in addition to the rate-based rule name and the web ACL name.

WAF monitors web requests and manages keys independently for each unique combination of web ACL, optional rule group, and rate-based rule. For example, if you define a rate-based rule inside a rule group, and then use the rule group in a web ACL, WAF monitors web requests and manages keys for that web ACL, rule group reference statement, and rate-based rule instance. If you use the same rule group in a second web ACL, WAF monitors web requests and manages keys for this second usage completely independent of your first.

Service Reference:

Examples:

Calling the getRateBasedStatementManagedKeys operation

var params = {
  RuleName: 'STRING_VALUE', /* required */
  Scope: CLOUDFRONT | REGIONAL, /* required */
  WebACLId: 'STRING_VALUE', /* required */
  WebACLName: 'STRING_VALUE', /* required */
  RuleGroupRuleName: 'STRING_VALUE'
};
wafv2.getRateBasedStatementManagedKeys(params, function(err, data) {
  if (err) console.log(err, err.stack); // an error occurred
  else     console.log(data);           // successful response
});

Parameters:

  • params (Object) (defaults to: {}) —
    • Scope — (String)

      Specifies whether this is for an Amazon CloudFront distribution or for a regional application. A regional application can be an Application Load Balancer (ALB), an Amazon API Gateway REST API, or an AppSync GraphQL API.

      To work with CloudFront, you must also specify the Region US East (N. Virginia) as follows:

      • CLI - Specify the Region when you use the CloudFront scope: --scope=CLOUDFRONT --region=us-east-1.

      • API and SDKs - For all calls, use the Region endpoint us-east-1.

      Possible values include:
      • "CLOUDFRONT"
      • "REGIONAL"
    • WebACLName — (String)

      The name of the web ACL. You cannot change the name of a web ACL after you create it.

    • WebACLId — (String)

      The unique identifier for the web ACL. This ID is returned in the responses to create and list commands. You provide it to operations like update and delete.

    • RuleGroupRuleName — (String)

      The name of the rule group reference statement in your web ACL. This is required only when you have the rate-based rule nested inside a rule group.

    • RuleName — (String)

      The name of the rate-based rule to get the keys for. If you have the rule defined inside a rule group that you're using in your web ACL, also provide the name of the rule group reference statement in the request parameter RuleGroupRuleName.

Callback (callback):

  • function(err, data) { ... }

    Called when a response from the service is returned. If a callback is not supplied, you must call AWS.Request.send() on the returned request object to initiate the request.

    Context (this):

    • (AWS.Response) —

      the response object containing error, data properties, and the original request object.

    Parameters:

    • err (Error) —

      the error object returned from the request. Set to null if the request is successful.

    • data (Object) —

      the de-serialized data returned from the request. Set to null if a request error occurs. The data object has the following properties:

      • ManagedKeysIPV4 — (map)

        The keys that are of Internet Protocol version 4 (IPv4).

        • IPAddressVersion — (String)

          The version of the IP addresses, either IPV4 or IPV6.

          Possible values include:
          • "IPV4"
          • "IPV6"
        • Addresses — (Array<String>)

          The IP addresses that are currently blocked.

      • ManagedKeysIPV6 — (map)

        The keys that are of Internet Protocol version 6 (IPv6).

        • IPAddressVersion — (String)

          The version of the IP addresses, either IPV4 or IPV6.

          Possible values include:
          • "IPV4"
          • "IPV6"
        • Addresses — (Array<String>)

          The IP addresses that are currently blocked.

Returns:

  • (AWS.Request) —

    a handle to the operation request for subsequent event callback registration.

getRegexPatternSet(params = {}, callback) ⇒ AWS.Request

Retrieves the specified RegexPatternSet.

Service Reference:

Examples:

Calling the getRegexPatternSet operation

var params = {
  Id: 'STRING_VALUE', /* required */
  Name: 'STRING_VALUE', /* required */
  Scope: CLOUDFRONT | REGIONAL /* required */
};
wafv2.getRegexPatternSet(params, function(err, data) {
  if (err) console.log(err, err.stack); // an error occurred
  else     console.log(data);           // successful response
});

Parameters:

  • params (Object) (defaults to: {}) —
    • Name — (String)

      The name of the set. You cannot change the name after you create the set.

    • Scope — (String)

      Specifies whether this is for an Amazon CloudFront distribution or for a regional application. A regional application can be an Application Load Balancer (ALB), an Amazon API Gateway REST API, or an AppSync GraphQL API.

      To work with CloudFront, you must also specify the Region US East (N. Virginia) as follows:

      • CLI - Specify the Region when you use the CloudFront scope: --scope=CLOUDFRONT --region=us-east-1.

      • API and SDKs - For all calls, use the Region endpoint us-east-1.

      Possible values include:
      • "CLOUDFRONT"
      • "REGIONAL"
    • Id — (String)

      A unique identifier for the set. This ID is returned in the responses to create and list commands. You provide it to operations like update and delete.

Callback (callback):

  • function(err, data) { ... }

    Called when a response from the service is returned. If a callback is not supplied, you must call AWS.Request.send() on the returned request object to initiate the request.

    Context (this):

    • (AWS.Response) —

      the response object containing error, data properties, and the original request object.

    Parameters:

    • err (Error) —

      the error object returned from the request. Set to null if the request is successful.

    • data (Object) —

      the de-serialized data returned from the request. Set to null if a request error occurs. The data object has the following properties:

      • RegexPatternSet — (map)

        • Name — (String)

          The name of the set. You cannot change the name after you create the set.

        • Id — (String)

          A unique identifier for the set. This ID is returned in the responses to create and list commands. You provide it to operations like update and delete.

        • ARN — (String)

          The Amazon Resource Name (ARN) of the entity.

        • Description — (String)

          A description of the set that helps with identification.

        • RegularExpressionList — (Array<map>)

          The regular expression patterns in the set.

          • RegexString — (String)

            The string representing the regular expression.

      • LockToken — (String)

        A token used for optimistic locking. WAF returns a token to your get and list requests, to mark the state of the entity at the time of the request. To make changes to the entity associated with the token, you provide the token to operations like update and delete. WAF uses the token to ensure that no changes have been made to the entity since you last retrieved it. If a change has been made, the update fails with a WAFOptimisticLockException. If this happens, perform another get, and use the new token returned by that operation.

Returns:

  • (AWS.Request) —

    a handle to the operation request for subsequent event callback registration.

getRuleGroup(params = {}, callback) ⇒ AWS.Request

Retrieves the specified RuleGroup.

Service Reference:

Examples:

Calling the getRuleGroup operation

var params = {
  ARN: 'STRING_VALUE',
  Id: 'STRING_VALUE',
  Name: 'STRING_VALUE',
  Scope: CLOUDFRONT | REGIONAL
};
wafv2.getRuleGroup(params, function(err, data) {
  if (err) console.log(err, err.stack); // an error occurred
  else     console.log(data);           // successful response
});

Parameters:

  • params (Object) (defaults to: {}) —
    • Name — (String)

      The name of the rule group. You cannot change the name of a rule group after you create it.

    • Scope — (String)

      Specifies whether this is for an Amazon CloudFront distribution or for a regional application. A regional application can be an Application Load Balancer (ALB), an Amazon API Gateway REST API, or an AppSync GraphQL API.

      To work with CloudFront, you must also specify the Region US East (N. Virginia) as follows:

      • CLI - Specify the Region when you use the CloudFront scope: --scope=CLOUDFRONT --region=us-east-1.

      • API and SDKs - For all calls, use the Region endpoint us-east-1.

      Possible values include:
      • "CLOUDFRONT"
      • "REGIONAL"
    • Id — (String)

      A unique identifier for the rule group. This ID is returned in the responses to create and list commands. You provide it to operations like update and delete.

    • ARN — (String)

      The Amazon Resource Name (ARN) of the entity.

Callback (callback):

  • function(err, data) { ... }

    Called when a response from the service is returned. If a callback is not supplied, you must call AWS.Request.send() on the returned request object to initiate the request.

    Context (this):

    • (AWS.Response) —

      the response object containing error, data properties, and the original request object.

    Parameters:

    • err (Error) —

      the error object returned from the request. Set to null if the request is successful.

    • data (Object) —

      the de-serialized data returned from the request. Set to null if a request error occurs. The data object has the following properties:

      • RuleGroup — (map)

        • Name — required — (String)

          The name of the rule group. You cannot change the name of a rule group after you create it.

        • Id — required — (String)

          A unique identifier for the rule group. This ID is returned in the responses to create and list commands. You provide it to operations like update and delete.

        • Capacity — required — (Integer)

          The web ACL capacity units (WCUs) required for this rule group.

          When you create your own rule group, you define this, and you cannot change it after creation. When you add or modify the rules in a rule group, WAF enforces this limit. You can check the capacity for a set of rules using CheckCapacity.

          WAF uses WCUs to calculate and control the operating resources that are used to run your rules, rule groups, and web ACLs. WAF calculates capacity differently for each rule type, to reflect the relative cost of each rule. Simple rules that cost little to run use fewer WCUs than more complex rules that use more processing power. Rule group capacity is fixed at creation, which helps users plan their web ACL WCU usage when they use a rule group. The WCU limit for web ACLs is 1,500.

        • ARN — required — (String)

          The Amazon Resource Name (ARN) of the entity.

        • Description — (String)

          A description of the rule group that helps with identification.

        • Rules — (Array<map>)

          The Rule statements used to identify the web requests that you want to allow, block, or count. Each rule includes one top-level statement that WAF uses to identify matching web requests, and parameters that govern how WAF handles them.

          • Name — required — (String)

            The name of the rule. You can't change the name of a Rule after you create it.

          • Priority — required — (Integer)

            If you define more than one Rule in a WebACL, WAF evaluates each request against the Rules in order based on the value of Priority. WAF processes rules with lower priority first. The priorities don't need to be consecutive, but they must all be different.

          • Statement — required — (map)

            The WAF processing statement for the rule, for example ByteMatchStatement or SizeConstraintStatement.

            • ByteMatchStatement — (map)

              A rule statement that defines a string match search for WAF to apply to web requests. The byte match statement provides the bytes to search for, the location in requests that you want WAF to search, and other settings. The bytes to search for are typically a string that corresponds with ASCII characters. In the WAF console and the developer guide, this is refered to as a string match statement.

              • SearchString — required — (Buffer, Typed Array, Blob, String)

                A string value that you want WAF to search for. WAF searches only in the part of web requests that you designate for inspection in FieldToMatch. The maximum length of the value is 50 bytes.

                Valid values depend on the component that you specify for inspection in FieldToMatch:

                • Method: The HTTP method that you want WAF to search for. This indicates the type of operation specified in the request.

                • UriPath: The value that you want WAF to search for in the URI path, for example, /images/daily-ad.jpg.

                If SearchString includes alphabetic characters A-Z and a-z, note that the value is case sensitive.

                If you're using the WAF API

                Specify a base64-encoded version of the value. The maximum length of the value before you base64-encode it is 50 bytes.

                For example, suppose the value of Type is HEADER and the value of Data is User-Agent. If you want to search the User-Agent header for the value BadBot, you base64-encode BadBot using MIME base64-encoding and include the resulting value, QmFkQm90, in the value of SearchString.

                If you're using the CLI or one of the Amazon Web Services SDKs

                The value that you want WAF to search for. The SDK automatically base64 encodes the value.

              • FieldToMatch — required — (map)

                The part of a web request that you want WAF to inspect. For more information, see FieldToMatch.

                • SingleHeader — (map)

                  Inspect a single header. Provide the name of the header to inspect, for example, User-Agent or Referer. This setting isn't case sensitive.

                  Example JSON: "SingleHeader": { "Name": "haystack" }

                  • Name — required — (String)

                    The name of the query header to inspect.

                • SingleQueryArgument — (map)

                  Inspect a single query argument. Provide the name of the query argument to inspect, such as UserName or SalesRegion. The name can be up to 30 characters long and isn't case sensitive.

                  This is used only to indicate the web request component for WAF to inspect, in the FieldToMatch specification.

                  Example JSON: "SingleQueryArgument": { "Name": "myArgument" }

                  • Name — required — (String)

                    The name of the query argument to inspect.

                • AllQueryArguments — (map)

                  Inspect all query arguments.

                • UriPath — (map)

                  Inspect the request URI path. This is the part of a web request that identifies a resource, for example, /images/daily-ad.jpg.

                • QueryString — (map)

                  Inspect the query string. This is the part of a URL that appears after a ? character, if any.

                • Body — (map)

                  Inspect the request body as plain text. The request body immediately follows the request headers. This is the part of a request that contains any additional data that you want to send to your web server as the HTTP request body, such as data from a form.

                  Note that only the first 8 KB (8192 bytes) of the request body are forwarded to WAF for inspection by the underlying host service. If you don't need to inspect more than 8 KB, you can guarantee that you don't allow additional bytes in by combining a statement that inspects the body of the web request, such as ByteMatchStatement or RegexPatternSetReferenceStatement, with a SizeConstraintStatement that enforces an 8 KB size limit on the body of the request. WAF doesn't support inspecting the entire contents of web requests whose bodies exceed the 8 KB limit.

                • Method — (map)

                  Inspect the HTTP method. The method indicates the type of operation that the request is asking the origin to perform.

                • JsonBody — (map)

                  Inspect the request body as JSON. The request body immediately follows the request headers. This is the part of a request that contains any additional data that you want to send to your web server as the HTTP request body, such as data from a form.

                  Note that only the first 8 KB (8192 bytes) of the request body are forwarded to WAF for inspection by the underlying host service. If you don't need to inspect more than 8 KB, you can guarantee that you don't allow additional bytes in by combining a statement that inspects the body of the web request, such as ByteMatchStatement or RegexPatternSetReferenceStatement, with a SizeConstraintStatement that enforces an 8 KB size limit on the body of the request. WAF doesn't support inspecting the entire contents of web requests whose bodies exceed the 8 KB limit.

                  • MatchPattern — required — (map)

                    The patterns to look for in the JSON body. WAF inspects the results of these pattern matches against the rule inspection criteria.

                    • All — (map)

                      Match all of the elements. See also MatchScope in JsonBody.

                      You must specify either this setting or the IncludedPaths setting, but not both.

                    • IncludedPaths — (Array<String>)

                      Match only the specified include paths. See also MatchScope in JsonBody.

                      Provide the include paths using JSON Pointer syntax. For example, "IncludedPaths": ["/dogs/0/name", "/dogs/1/name"]. For information about this syntax, see the Internet Engineering Task Force (IETF) documentation JavaScript Object Notation (JSON) Pointer.

                      You must specify either this setting or the All setting, but not both.

                      Note: Don't use this option to include all paths. Instead, use the All setting.
                  • MatchScope — required — (String)

                    The parts of the JSON to match against using the MatchPattern. If you specify All, WAF matches against keys and values.

                    Possible values include:
                    • "ALL"
                    • "KEY"
                    • "VALUE"
                  • InvalidFallbackBehavior — (String)

                    What WAF should do if it fails to completely parse the JSON body. The options are the following:

                    • EVALUATE_AS_STRING - Inspect the body as plain text. WAF applies the text transformations and inspection criteria that you defined for the JSON inspection to the body text string.

                    • MATCH - Treat the web request as matching the rule statement. WAF applies the rule action to the request.

                    • NO_MATCH - Treat the web request as not matching the rule statement.

                    If you don't provide this setting, WAF parses and evaluates the content only up to the first parsing failure that it encounters.

                    WAF does its best to parse the entire JSON body, but might be forced to stop for reasons such as invalid characters, duplicate keys, truncation, and any content whose root node isn't an object or an array.

                    WAF parses the JSON in the following examples as two valid key, value pairs:

                    • Missing comma: {"key1":"value1""key2":"value2"}

                    • Missing colon: {"key1":"value1","key2""value2"}

                    • Extra colons: {"key1"::"value1","key2""value2"}

                    Possible values include:
                    • "MATCH"
                    • "NO_MATCH"
                    • "EVALUATE_AS_STRING"
              • TextTransformations — required — (Array<map>)

                Text transformations eliminate some of the unusual formatting that attackers use in web requests in an effort to bypass detection. If you specify one or more transformations in a rule statement, WAF performs all transformations on the content of the request component identified by FieldToMatch, starting from the lowest priority setting, before inspecting the content for a match.

                • Priority — required — (Integer)

                  Sets the relative processing order for multiple transformations that are defined for a rule statement. WAF processes all transformations, from lowest priority to highest, before inspecting the transformed content. The priorities don't need to be consecutive, but they must all be different.

                • Type — required — (String)

                  You can specify the following transformation types:

                  BASE64_DECODE - Decode a Base64-encoded string.

                  BASE64_DECODE_EXT - Decode a Base64-encoded string, but use a forgiving implementation that ignores characters that aren't valid.

                  CMD_LINE - Command-line transformations. These are helpful in reducing effectiveness of attackers who inject an operating system command-line command and use unusual formatting to disguise some or all of the command.

                  • Delete the following characters: \ " ' ^

                  • Delete spaces before the following characters: / (

                  • Replace the following characters with a space: , ;

                  • Replace multiple spaces with one space

                  • Convert uppercase letters (A-Z) to lowercase (a-z)

                  COMPRESS_WHITE_SPACE - Replace these characters with a space character (decimal 32):

                  • \f, formfeed, decimal 12

                  • \t, tab, decimal 9

                  • \n, newline, decimal 10

                  • \r, carriage return, decimal 13

                  • \v, vertical tab, decimal 11

                  • Non-breaking space, decimal 160

                  COMPRESS_WHITE_SPACE also replaces multiple spaces with one space.

                  CSS_DECODE - Decode characters that were encoded using CSS 2.x escape rules syndata.html#characters. This function uses up to two bytes in the decoding process, so it can help to uncover ASCII characters that were encoded using CSS encoding that wouldn’t typically be encoded. It's also useful in countering evasion, which is a combination of a backslash and non-hexadecimal characters. For example, ja\vascript for javascript.

                  ESCAPE_SEQ_DECODE - Decode the following ANSI C escape sequences: \a, \b, \f, \n, \r, \t, \v, \, \?, \', \", \xHH (hexadecimal), \0OOO (octal). Encodings that aren't valid remain in the output.

                  HEX_DECODE - Decode a string of hexadecimal characters into a binary.

                  HTML_ENTITY_DECODE - Replace HTML-encoded characters with unencoded characters. HTML_ENTITY_DECODE performs these operations:

                  • Replaces (ampersand)quot; with "

                  • Replaces (ampersand)nbsp; with a non-breaking space, decimal 160

                  • Replaces (ampersand)lt; with a "less than" symbol

                  • Replaces (ampersand)gt; with >

                  • Replaces characters that are represented in hexadecimal format, (ampersand)#xhhhh;, with the corresponding characters

                  • Replaces characters that are represented in decimal format, (ampersand)#nnnn;, with the corresponding characters

                  JS_DECODE - Decode JavaScript escape sequences. If a \ u HHHH code is in the full-width ASCII code range of FF01-FF5E, then the higher byte is used to detect and adjust the lower byte. If not, only the lower byte is used and the higher byte is zeroed, causing a possible loss of information.

                  LOWERCASE - Convert uppercase letters (A-Z) to lowercase (a-z).

                  MD5 - Calculate an MD5 hash from the data in the input. The computed hash is in a raw binary form.

                  NONE - Specify NONE if you don't want any text transformations.

                  NORMALIZE_PATH - Remove multiple slashes, directory self-references, and directory back-references that are not at the beginning of the input from an input string.

                  NORMALIZE_PATH_WIN - This is the same as NORMALIZE_PATH, but first converts backslash characters to forward slashes.

                  REMOVE_NULLS - Remove all NULL bytes from the input.

                  REPLACE_COMMENTS - Replace each occurrence of a C-style comment (/* ... */) with a single space. Multiple consecutive occurrences are not compressed. Unterminated comments are also replaced with a space (ASCII 0x20). However, a standalone termination of a comment (*/) is not acted upon.

                  REPLACE_NULLS - Replace NULL bytes in the input with space characters (ASCII 0x20).

                  SQL_HEX_DECODE - Decode SQL hex data. Example (0x414243) will be decoded to (ABC).

                  URL_DECODE - Decode a URL-encoded value.

                  URL_DECODE_UNI - Like URL_DECODE, but with support for Microsoft-specific %u encoding. If the code is in the full-width ASCII code range of FF01-FF5E, the higher byte is used to detect and adjust the lower byte. Otherwise, only the lower byte is used and the higher byte is zeroed.

                  UTF8_TO_UNICODE - Convert all UTF-8 character sequences to Unicode. This helps input normalization, and minimizing false-positives and false-negatives for non-English languages.

                  Possible values include:
                  • "NONE"
                  • "COMPRESS_WHITE_SPACE"
                  • "HTML_ENTITY_DECODE"
                  • "LOWERCASE"
                  • "CMD_LINE"
                  • "URL_DECODE"
                  • "BASE64_DECODE"
                  • "HEX_DECODE"
                  • "MD5"
                  • "REPLACE_COMMENTS"
                  • "ESCAPE_SEQ_DECODE"
                  • "SQL_HEX_DECODE"
                  • "CSS_DECODE"
                  • "JS_DECODE"
                  • "NORMALIZE_PATH"
                  • "NORMALIZE_PATH_WIN"
                  • "REMOVE_NULLS"
                  • "REPLACE_NULLS"
                  • "BASE64_DECODE_EXT"
                  • "URL_DECODE_UNI"
                  • "UTF8_TO_UNICODE"
              • PositionalConstraint — required — (String)

                The area within the portion of a web request that you want WAF to search for SearchString. Valid values include the following:

                CONTAINS

                The specified part of the web request must include the value of SearchString, but the location doesn't matter.

                CONTAINS_WORD

                The specified part of the web request must include the value of SearchString, and SearchString must contain only alphanumeric characters or underscore (A-Z, a-z, 0-9, or ). In addition, SearchString must be a word, which means that both of the following are true:

                • SearchString is at the beginning of the specified part of the web request or is preceded by a character other than an alphanumeric character or underscore (). Examples include the value of a header and ;BadBot.

                • SearchString is at the end of the specified part of the web request or is followed by a character other than an alphanumeric character or underscore (_), for example, BadBot; and -BadBot;.

                EXACTLY

                The value of the specified part of the web request must exactly match the value of SearchString.

                STARTS_WITH

                The value of SearchString must appear at the beginning of the specified part of the web request.

                ENDS_WITH

                The value of SearchString must appear at the end of the specified part of the web request.

                Possible values include:
                • "EXACTLY"
                • "STARTS_WITH"
                • "ENDS_WITH"
                • "CONTAINS"
                • "CONTAINS_WORD"
            • SqliMatchStatement — (map)

              Attackers sometimes insert malicious SQL code into web requests in an effort to extract data from your database. To allow or block web requests that appear to contain malicious SQL code, create one or more SQL injection match conditions. An SQL injection match condition identifies the part of web requests, such as the URI or the query string, that you want WAF to inspect. Later in the process, when you create a web ACL, you specify whether to allow or block requests that appear to contain malicious SQL code.

              • FieldToMatch — required — (map)

                The part of a web request that you want WAF to inspect. For more information, see FieldToMatch.

                • SingleHeader — (map)

                  Inspect a single header. Provide the name of the header to inspect, for example, User-Agent or Referer. This setting isn't case sensitive.

                  Example JSON: "SingleHeader": { "Name": "haystack" }

                  • Name — required — (String)

                    The name of the query header to inspect.

                • SingleQueryArgument — (map)

                  Inspect a single query argument. Provide the name of the query argument to inspect, such as UserName or SalesRegion. The name can be up to 30 characters long and isn't case sensitive.

                  This is used only to indicate the web request component for WAF to inspect, in the FieldToMatch specification.

                  Example JSON: "SingleQueryArgument": { "Name": "myArgument" }

                  • Name — required — (String)

                    The name of the query argument to inspect.

                • AllQueryArguments — (map)

                  Inspect all query arguments.

                • UriPath — (map)

                  Inspect the request URI path. This is the part of a web request that identifies a resource, for example, /images/daily-ad.jpg.

                • QueryString — (map)

                  Inspect the query string. This is the part of a URL that appears after a ? character, if any.

                • Body — (map)

                  Inspect the request body as plain text. The request body immediately follows the request headers. This is the part of a request that contains any additional data that you want to send to your web server as the HTTP request body, such as data from a form.

                  Note that only the first 8 KB (8192 bytes) of the request body are forwarded to WAF for inspection by the underlying host service. If you don't need to inspect more than 8 KB, you can guarantee that you don't allow additional bytes in by combining a statement that inspects the body of the web request, such as ByteMatchStatement or RegexPatternSetReferenceStatement, with a SizeConstraintStatement that enforces an 8 KB size limit on the body of the request. WAF doesn't support inspecting the entire contents of web requests whose bodies exceed the 8 KB limit.

                • Method — (map)

                  Inspect the HTTP method. The method indicates the type of operation that the request is asking the origin to perform.

                • JsonBody — (map)

                  Inspect the request body as JSON. The request body immediately follows the request headers. This is the part of a request that contains any additional data that you want to send to your web server as the HTTP request body, such as data from a form.

                  Note that only the first 8 KB (8192 bytes) of the request body are forwarded to WAF for inspection by the underlying host service. If you don't need to inspect more than 8 KB, you can guarantee that you don't allow additional bytes in by combining a statement that inspects the body of the web request, such as ByteMatchStatement or RegexPatternSetReferenceStatement, with a SizeConstraintStatement that enforces an 8 KB size limit on the body of the request. WAF doesn't support inspecting the entire contents of web requests whose bodies exceed the 8 KB limit.

                  • MatchPattern — required — (map)

                    The patterns to look for in the JSON body. WAF inspects the results of these pattern matches against the rule inspection criteria.

                    • All — (map)

                      Match all of the elements. See also MatchScope in JsonBody.

                      You must specify either this setting or the IncludedPaths setting, but not both.

                    • IncludedPaths — (Array<String>)

                      Match only the specified include paths. See also MatchScope in JsonBody.

                      Provide the include paths using JSON Pointer syntax. For example, "IncludedPaths": ["/dogs/0/name", "/dogs/1/name"]. For information about this syntax, see the Internet Engineering Task Force (IETF) documentation JavaScript Object Notation (JSON) Pointer.

                      You must specify either this setting or the All setting, but not both.

                      Note: Don't use this option to include all paths. Instead, use the All setting.
                  • MatchScope — required — (String)

                    The parts of the JSON to match against using the MatchPattern. If you specify All, WAF matches against keys and values.

                    Possible values include:
                    • "ALL"
                    • "KEY"
                    • "VALUE"
                  • InvalidFallbackBehavior — (String)

                    What WAF should do if it fails to completely parse the JSON body. The options are the following:

                    • EVALUATE_AS_STRING - Inspect the body as plain text. WAF applies the text transformations and inspection criteria that you defined for the JSON inspection to the body text string.

                    • MATCH - Treat the web request as matching the rule statement. WAF applies the rule action to the request.

                    • NO_MATCH - Treat the web request as not matching the rule statement.

                    If you don't provide this setting, WAF parses and evaluates the content only up to the first parsing failure that it encounters.

                    WAF does its best to parse the entire JSON body, but might be forced to stop for reasons such as invalid characters, duplicate keys, truncation, and any content whose root node isn't an object or an array.

                    WAF parses the JSON in the following examples as two valid key, value pairs:

                    • Missing comma: {"key1":"value1""key2":"value2"}

                    • Missing colon: {"key1":"value1","key2""value2"}

                    • Extra colons: {"key1"::"value1","key2""value2"}

                    Possible values include:
                    • "MATCH"
                    • "NO_MATCH"
                    • "EVALUATE_AS_STRING"
              • TextTransformations — required — (Array<map>)

                Text transformations eliminate some of the unusual formatting that attackers use in web requests in an effort to bypass detection. If you specify one or more transformations in a rule statement, WAF performs all transformations on the content of the request component identified by FieldToMatch, starting from the lowest priority setting, before inspecting the content for a match.

                • Priority — required — (Integer)

                  Sets the relative processing order for multiple transformations that are defined for a rule statement. WAF processes all transformations, from lowest priority to highest, before inspecting the transformed content. The priorities don't need to be consecutive, but they must all be different.

                • Type — required — (String)

                  You can specify the following transformation types:

                  BASE64_DECODE - Decode a Base64-encoded string.

                  BASE64_DECODE_EXT - Decode a Base64-encoded string, but use a forgiving implementation that ignores characters that aren't valid.

                  CMD_LINE - Command-line transformations. These are helpful in reducing effectiveness of attackers who inject an operating system command-line command and use unusual formatting to disguise some or all of the command.

                  • Delete the following characters: \ " ' ^

                  • Delete spaces before the following characters: / (

                  • Replace the following characters with a space: , ;

                  • Replace multiple spaces with one space

                  • Convert uppercase letters (A-Z) to lowercase (a-z)

                  COMPRESS_WHITE_SPACE - Replace these characters with a space character (decimal 32):

                  • \f, formfeed, decimal 12

                  • \t, tab, decimal 9

                  • \n, newline, decimal 10

                  • \r, carriage return, decimal 13

                  • \v, vertical tab, decimal 11

                  • Non-breaking space, decimal 160

                  COMPRESS_WHITE_SPACE also replaces multiple spaces with one space.

                  CSS_DECODE - Decode characters that were encoded using CSS 2.x escape rules syndata.html#characters. This function uses up to two bytes in the decoding process, so it can help to uncover ASCII characters that were encoded using CSS encoding that wouldn’t typically be encoded. It's also useful in countering evasion, which is a combination of a backslash and non-hexadecimal characters. For example, ja\vascript for javascript.

                  ESCAPE_SEQ_DECODE - Decode the following ANSI C escape sequences: \a, \b, \f, \n, \r, \t, \v, \, \?, \', \", \xHH (hexadecimal), \0OOO (octal). Encodings that aren't valid remain in the output.

                  HEX_DECODE - Decode a string of hexadecimal characters into a binary.

                  HTML_ENTITY_DECODE - Replace HTML-encoded characters with unencoded characters. HTML_ENTITY_DECODE performs these operations:

                  • Replaces (ampersand)quot; with "

                  • Replaces (ampersand)nbsp; with a non-breaking space, decimal 160

                  • Replaces (ampersand)lt; with a "less than" symbol

                  • Replaces (ampersand)gt; with >

                  • Replaces characters that are represented in hexadecimal format, (ampersand)#xhhhh;, with the corresponding characters

                  • Replaces characters that are represented in decimal format, (ampersand)#nnnn;, with the corresponding characters

                  JS_DECODE - Decode JavaScript escape sequences. If a \ u HHHH code is in the full-width ASCII code range of FF01-FF5E, then the higher byte is used to detect and adjust the lower byte. If not, only the lower byte is used and the higher byte is zeroed, causing a possible loss of information.

                  LOWERCASE - Convert uppercase letters (A-Z) to lowercase (a-z).

                  MD5 - Calculate an MD5 hash from the data in the input. The computed hash is in a raw binary form.

                  NONE - Specify NONE if you don't want any text transformations.

                  NORMALIZE_PATH - Remove multiple slashes, directory self-references, and directory back-references that are not at the beginning of the input from an input string.

                  NORMALIZE_PATH_WIN - This is the same as NORMALIZE_PATH, but first converts backslash characters to forward slashes.

                  REMOVE_NULLS - Remove all NULL bytes from the input.

                  REPLACE_COMMENTS - Replace each occurrence of a C-style comment (/* ... */) with a single space. Multiple consecutive occurrences are not compressed. Unterminated comments are also replaced with a space (ASCII 0x20). However, a standalone termination of a comment (*/) is not acted upon.

                  REPLACE_NULLS - Replace NULL bytes in the input with space characters (ASCII 0x20).

                  SQL_HEX_DECODE - Decode SQL hex data. Example (0x414243) will be decoded to (ABC).

                  URL_DECODE - Decode a URL-encoded value.

                  URL_DECODE_UNI - Like URL_DECODE, but with support for Microsoft-specific %u encoding. If the code is in the full-width ASCII code range of FF01-FF5E, the higher byte is used to detect and adjust the lower byte. Otherwise, only the lower byte is used and the higher byte is zeroed.

                  UTF8_TO_UNICODE - Convert all UTF-8 character sequences to Unicode. This helps input normalization, and minimizing false-positives and false-negatives for non-English languages.

                  Possible values include:
                  • "NONE"
                  • "COMPRESS_WHITE_SPACE"
                  • "HTML_ENTITY_DECODE"
                  • "LOWERCASE"
                  • "CMD_LINE"
                  • "URL_DECODE"
                  • "BASE64_DECODE"
                  • "HEX_DECODE"
                  • "MD5"
                  • "REPLACE_COMMENTS"
                  • "ESCAPE_SEQ_DECODE"
                  • "SQL_HEX_DECODE"
                  • "CSS_DECODE"
                  • "JS_DECODE"
                  • "NORMALIZE_PATH"
                  • "NORMALIZE_PATH_WIN"
                  • "REMOVE_NULLS"
                  • "REPLACE_NULLS"
                  • "BASE64_DECODE_EXT"
                  • "URL_DECODE_UNI"
                  • "UTF8_TO_UNICODE"
            • XssMatchStatement — (map)

              A rule statement that defines a cross-site scripting (XSS) match search for WAF to apply to web requests. XSS attacks are those where the attacker uses vulnerabilities in a benign website as a vehicle to inject malicious client-site scripts into other legitimate web browsers. The XSS match statement provides the location in requests that you want WAF to search and text transformations to use on the search area before WAF searches for character sequences that are likely to be malicious strings.

              • FieldToMatch — required — (map)

                The part of a web request that you want WAF to inspect. For more information, see FieldToMatch.

                • SingleHeader — (map)

                  Inspect a single header. Provide the name of the header to inspect, for example, User-Agent or Referer. This setting isn't case sensitive.

                  Example JSON: "SingleHeader": { "Name": "haystack" }

                  • Name — required — (String)

                    The name of the query header to inspect.

                • SingleQueryArgument — (map)

                  Inspect a single query argument. Provide the name of the query argument to inspect, such as UserName or SalesRegion. The name can be up to 30 characters long and isn't case sensitive.

                  This is used only to indicate the web request component for WAF to inspect, in the FieldToMatch specification.

                  Example JSON: "SingleQueryArgument": { "Name": "myArgument" }

                  • Name — required — (String)

                    The name of the query argument to inspect.

                • AllQueryArguments — (map)

                  Inspect all query arguments.

                • UriPath — (map)

                  Inspect the request URI path. This is the part of a web request that identifies a resource, for example, /images/daily-ad.jpg.

                • QueryString — (map)

                  Inspect the query string. This is the part of a URL that appears after a ? character, if any.

                • Body — (map)

                  Inspect the request body as plain text. The request body immediately follows the request headers. This is the part of a request that contains any additional data that you want to send to your web server as the HTTP request body, such as data from a form.

                  Note that only the first 8 KB (8192 bytes) of the request body are forwarded to WAF for inspection by the underlying host service. If you don't need to inspect more than 8 KB, you can guarantee that you don't allow additional bytes in by combining a statement that inspects the body of the web request, such as ByteMatchStatement or RegexPatternSetReferenceStatement, with a SizeConstraintStatement that enforces an 8 KB size limit on the body of the request. WAF doesn't support inspecting the entire contents of web requests whose bodies exceed the 8 KB limit.

                • Method — (map)

                  Inspect the HTTP method. The method indicates the type of operation that the request is asking the origin to perform.

                • JsonBody — (map)

                  Inspect the request body as JSON. The request body immediately follows the request headers. This is the part of a request that contains any additional data that you want to send to your web server as the HTTP request body, such as data from a form.

                  Note that only the first 8 KB (8192 bytes) of the request body are forwarded to WAF for inspection by the underlying host service. If you don't need to inspect more than 8 KB, you can guarantee that you don't allow additional bytes in by combining a statement that inspects the body of the web request, such as ByteMatchStatement or RegexPatternSetReferenceStatement, with a SizeConstraintStatement that enforces an 8 KB size limit on the body of the request. WAF doesn't support inspecting the entire contents of web requests whose bodies exceed the 8 KB limit.

                  • MatchPattern — required — (map)

                    The patterns to look for in the JSON body. WAF inspects the results of these pattern matches against the rule inspection criteria.

                    • All — (map)

                      Match all of the elements. See also MatchScope in JsonBody.

                      You must specify either this setting or the IncludedPaths setting, but not both.

                    • IncludedPaths — (Array<String>)

                      Match only the specified include paths. See also MatchScope in JsonBody.

                      Provide the include paths using JSON Pointer syntax. For example, "IncludedPaths": ["/dogs/0/name", "/dogs/1/name"]. For information about this syntax, see the Internet Engineering Task Force (IETF) documentation JavaScript Object Notation (JSON) Pointer.

                      You must specify either this setting or the All setting, but not both.

                      Note: Don't use this option to include all paths. Instead, use the All setting.
                  • MatchScope — required — (String)

                    The parts of the JSON to match against using the MatchPattern. If you specify All, WAF matches against keys and values.

                    Possible values include:
                    • "ALL"
                    • "KEY"
                    • "VALUE"
                  • InvalidFallbackBehavior — (String)

                    What WAF should do if it fails to completely parse the JSON body. The options are the following:

                    • EVALUATE_AS_STRING - Inspect the body as plain text. WAF applies the text transformations and inspection criteria that you defined for the JSON inspection to the body text string.

                    • MATCH - Treat the web request as matching the rule statement. WAF applies the rule action to the request.

                    • NO_MATCH - Treat the web request as not matching the rule statement.

                    If you don't provide this setting, WAF parses and evaluates the content only up to the first parsing failure that it encounters.

                    WAF does its best to parse the entire JSON body, but might be forced to stop for reasons such as invalid characters, duplicate keys, truncation, and any content whose root node isn't an object or an array.

                    WAF parses the JSON in the following examples as two valid key, value pairs:

                    • Missing comma: {"key1":"value1""key2":"value2"}

                    • Missing colon: {"key1":"value1","key2""value2"}

                    • Extra colons: {"key1"::"value1","key2""value2"}

                    Possible values include:
                    • "MATCH"
                    • "NO_MATCH"
                    • "EVALUATE_AS_STRING"
              • TextTransformations — required — (Array<map>)

                Text transformations eliminate some of the unusual formatting that attackers use in web requests in an effort to bypass detection. If you specify one or more transformations in a rule statement, WAF performs all transformations on the content of the request component identified by FieldToMatch, starting from the lowest priority setting, before inspecting the content for a match.

                • Priority — required — (Integer)

                  Sets the relative processing order for multiple transformations that are defined for a rule statement. WAF processes all transformations, from lowest priority to highest, before inspecting the transformed content. The priorities don't need to be consecutive, but they must all be different.

                • Type — required — (String)

                  You can specify the following transformation types:

                  BASE64_DECODE - Decode a Base64-encoded string.

                  BASE64_DECODE_EXT - Decode a Base64-encoded string, but use a forgiving implementation that ignores characters that aren't valid.

                  CMD_LINE - Command-line transformations. These are helpful in reducing effectiveness of attackers who inject an operating system command-line command and use unusual formatting to disguise some or all of the command.

                  • Delete the following characters: \ " ' ^

                  • Delete spaces before the following characters: / (

                  • Replace the following characters with a space: , ;

                  • Replace multiple spaces with one space

                  • Convert uppercase letters (A-Z) to lowercase (a-z)

                  COMPRESS_WHITE_SPACE - Replace these characters with a space character (decimal 32):

                  • \f, formfeed, decimal 12

                  • \t, tab, decimal 9

                  • \n, newline, decimal 10

                  • \r, carriage return, decimal 13

                  • \v, vertical tab, decimal 11

                  • Non-breaking space, decimal 160

                  COMPRESS_WHITE_SPACE also replaces multiple spaces with one space.

                  CSS_DECODE - Decode characters that were encoded using CSS 2.x escape rules syndata.html#characters. This function uses up to two bytes in the decoding process, so it can help to uncover ASCII characters that were encoded using CSS encoding that wouldn’t typically be encoded. It's also useful in countering evasion, which is a combination of a backslash and non-hexadecimal characters. For example, ja\vascript for javascript.

                  ESCAPE_SEQ_DECODE - Decode the following ANSI C escape sequences: \a, \b, \f, \n, \r, \t, \v, \, \?, \', \", \xHH (hexadecimal), \0OOO (octal). Encodings that aren't valid remain in the output.

                  HEX_DECODE - Decode a string of hexadecimal characters into a binary.

                  HTML_ENTITY_DECODE - Replace HTML-encoded characters with unencoded characters. HTML_ENTITY_DECODE performs these operations:

                  • Replaces (ampersand)quot; with "

                  • Replaces (ampersand)nbsp; with a non-breaking space, decimal 160

                  • Replaces (ampersand)lt; with a "less than" symbol

                  • Replaces (ampersand)gt; with >

                  • Replaces characters that are represented in hexadecimal format, (ampersand)#xhhhh;, with the corresponding characters

                  • Replaces characters that are represented in decimal format, (ampersand)#nnnn;, with the corresponding characters

                  JS_DECODE - Decode JavaScript escape sequences. If a \ u HHHH code is in the full-width ASCII code range of FF01-FF5E, then the higher byte is used to detect and adjust the lower byte. If not, only the lower byte is used and the higher byte is zeroed, causing a possible loss of information.

                  LOWERCASE - Convert uppercase letters (A-Z) to lowercase (a-z).

                  MD5 - Calculate an MD5 hash from the data in the input. The computed hash is in a raw binary form.

                  NONE - Specify NONE if you don't want any text transformations.

                  NORMALIZE_PATH - Remove multiple slashes, directory self-references, and directory back-references that are not at the beginning of the input from an input string.

                  NORMALIZE_PATH_WIN - This is the same as NORMALIZE_PATH, but first converts backslash characters to forward slashes.

                  REMOVE_NULLS - Remove all NULL bytes from the input.

                  REPLACE_COMMENTS - Replace each occurrence of a C-style comment (/* ... */) with a single space. Multiple consecutive occurrences are not compressed. Unterminated comments are also replaced with a space (ASCII 0x20). However, a standalone termination of a comment (*/) is not acted upon.

                  REPLACE_NULLS - Replace NULL bytes in the input with space characters (ASCII 0x20).

                  SQL_HEX_DECODE - Decode SQL hex data. Example (0x414243) will be decoded to (ABC).

                  URL_DECODE - Decode a URL-encoded value.

                  URL_DECODE_UNI - Like URL_DECODE, but with support for Microsoft-specific %u encoding. If the code is in the full-width ASCII code range of FF01-FF5E, the higher byte is used to detect and adjust the lower byte. Otherwise, only the lower byte is used and the higher byte is zeroed.

                  UTF8_TO_UNICODE - Convert all UTF-8 character sequences to Unicode. This helps input normalization, and minimizing false-positives and false-negatives for non-English languages.

                  Possible values include:
                  • "NONE"
                  • "COMPRESS_WHITE_SPACE"
                  • "HTML_ENTITY_DECODE"
                  • "LOWERCASE"
                  • "CMD_LINE"
                  • "URL_DECODE"
                  • "BASE64_DECODE"
                  • "HEX_DECODE"
                  • "MD5"
                  • "REPLACE_COMMENTS"
                  • "ESCAPE_SEQ_DECODE"
                  • "SQL_HEX_DECODE"
                  • "CSS_DECODE"
                  • "JS_DECODE"
                  • "NORMALIZE_PATH"
                  • "NORMALIZE_PATH_WIN"
                  • "REMOVE_NULLS"
                  • "REPLACE_NULLS"
                  • "BASE64_DECODE_EXT"
                  • "URL_DECODE_UNI"
                  • "UTF8_TO_UNICODE"
            • SizeConstraintStatement — (map)

              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 first 8192 bytes (8 KB). If the request body for your web requests never exceeds 8192 bytes, you can create a size constraint condition and block requests that have a request body greater than 8192 bytes.

              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.

              • FieldToMatch — required — (map)

                The part of a web request that you want WAF to inspect. For more information, see FieldToMatch.

                • SingleHeader — (map)

                  Inspect a single header. Provide the name of the header to inspect, for example, User-Agent or Referer. This setting isn't case sensitive.

                  Example JSON: "SingleHeader": { "Name": "haystack" }

                  • Name — required — (String)

                    The name of the query header to inspect.

                • SingleQueryArgument — (map)

                  Inspect a single query argument. Provide the name of the query argument to inspect, such as UserName or SalesRegion. The name can be up to 30 characters long and isn't case sensitive.

                  This is used only to indicate the web request component for WAF to inspect, in the FieldToMatch specification.

                  Example JSON: "SingleQueryArgument": { "Name": "myArgument" }

                  • Name — required — (String)

                    The name of the query argument to inspect.

                • AllQueryArguments — (map)

                  Inspect all query arguments.

                • UriPath — (map)

                  Inspect the request URI path. This is the part of a web request that identifies a resource, for example, /images/daily-ad.jpg.

                • QueryString — (map)

                  Inspect the query string. This is the part of a URL that appears after a ? character, if any.

                • Body — (map)

                  Inspect the request body as plain text. The request body immediately follows the request headers. This is the part of a request that contains any additional data that you want to send to your web server as the HTTP request body, such as data from a form.

                  Note that only the first 8 KB (8192 bytes) of the request body are forwarded to WAF for inspection by the underlying host service. If you don't need to inspect more than 8 KB, you can guarantee that you don't allow additional bytes in by combining a statement that inspects the body of the web request, such as ByteMatchStatement or RegexPatternSetReferenceStatement, with a SizeConstraintStatement that enforces an 8 KB size limit on the body of the request. WAF doesn't support inspecting the entire contents of web requests whose bodies exceed the 8 KB limit.

                • Method — (map)

                  Inspect the HTTP method. The method indicates the type of operation that the request is asking the origin to perform.

                • JsonBody — (map)

                  Inspect the request body as JSON. The request body immediately follows the request headers. This is the part of a request that contains any additional data that you want to send to your web server as the HTTP request body, such as data from a form.

                  Note that only the first 8 KB (8192 bytes) of the request body are forwarded to WAF for inspection by the underlying host service. If you don't need to inspect more than 8 KB, you can guarantee that you don't allow additional bytes in by combining a statement that inspects the body of the web request, such as ByteMatchStatement or RegexPatternSetReferenceStatement, with a SizeConstraintStatement that enforces an 8 KB size limit on the body of the request. WAF doesn't support inspecting the entire contents of web requests whose bodies exceed the 8 KB limit.

                  • MatchPattern — required — (map)

                    The patterns to look for in the JSON body. WAF inspects the results of these pattern matches against the rule inspection criteria.

                    • All — (map)

                      Match all of the elements. See also MatchScope in JsonBody.

                      You must specify either this setting or the IncludedPaths setting, but not both.

                    • IncludedPaths — (Array<String>)

                      Match only the specified include paths. See also MatchScope in JsonBody.

                      Provide the include paths using JSON Pointer syntax. For example, "IncludedPaths": ["/dogs/0/name", "/dogs/1/name"]. For information about this syntax, see the Internet Engineering Task Force (IETF) documentation JavaScript Object Notation (JSON) Pointer.

                      You must specify either this setting or the All setting, but not both.

                      Note: Don't use this option to include all paths. Instead, use the All setting.
                  • MatchScope — required — (String)

                    The parts of the JSON to match against using the MatchPattern. If you specify All, WAF matches against keys and values.

                    Possible values include:
                    • "ALL"
                    • "KEY"
                    • "VALUE"
                  • InvalidFallbackBehavior — (String)

                    What WAF should do if it fails to completely parse the JSON body. The options are the following:

                    • EVALUATE_AS_STRING - Inspect the body as plain text. WAF applies the text transformations and inspection criteria that you defined for the JSON inspection to the body text string.

                    • MATCH - Treat the web request as matching the rule statement. WAF applies the rule action to the request.

                    • NO_MATCH - Treat the web request as not matching the rule statement.

                    If you don't provide this setting, WAF parses and evaluates the content only up to the first parsing failure that it encounters.

                    WAF does its best to parse the entire JSON body, but might be forced to stop for reasons such as invalid characters, duplicate keys, truncation, and any content whose root node isn't an object or an array.

                    WAF parses the JSON in the following examples as two valid key, value pairs:

                    • Missing comma: {"key1":"value1""key2":"value2"}

                    • Missing colon: {"key1":"value1","key2""value2"}

                    • Extra colons: {"key1"::"value1","key2""value2"}

                    Possible values include:
                    • "MATCH"
                    • "NO_MATCH"
                    • "EVALUATE_AS_STRING"
              • ComparisonOperator — required — (String)

                The operator to use to compare the request part to the size setting.

                Possible values include:
                • "EQ"
                • "NE"
                • "LE"
                • "LT"
                • "GE"
                • "GT"
              • Size — required — (Integer)

                The size, in byte, to compare to the request part, after any transformations.

              • TextTransformations — required — (Array<map>)

                Text transformations eliminate some of the unusual formatting that attackers use in web requests in an effort to bypass detection. If you specify one or more transformations in a rule statement, WAF performs all transformations on the content of the request component identified by FieldToMatch, starting from the lowest priority setting, before inspecting the content for a match.

                • Priority — required — (Integer)

                  Sets the relative processing order for multiple transformations that are defined for a rule statement. WAF processes all transformations, from lowest priority to highest, before inspecting the transformed content. The priorities don't need to be consecutive, but they must all be different.

                • Type — required — (String)

                  You can specify the following transformation types:

                  BASE64_DECODE - Decode a Base64-encoded string.

                  BASE64_DECODE_EXT - Decode a Base64-encoded string, but use a forgiving implementation that ignores characters that aren't valid.

                  CMD_LINE - Command-line transformations. These are helpful in reducing effectiveness of attackers who inject an operating system command-line command and use unusual formatting to disguise some or all of the command.

                  • Delete the following characters: \ " ' ^

                  • Delete spaces before the following characters: / (

                  • Replace the following characters with a space: , ;

                  • Replace multiple spaces with one space

                  • Convert uppercase letters (A-Z) to lowercase (a-z)

                  COMPRESS_WHITE_SPACE - Replace these characters with a space character (decimal 32):

                  • \f, formfeed, decimal 12

                  • \t, tab, decimal 9

                  • \n, newline, decimal 10

                  • \r, carriage return, decimal 13

                  • \v, vertical tab, decimal 11

                  • Non-breaking space, decimal 160

                  COMPRESS_WHITE_SPACE also replaces multiple spaces with one space.

                  CSS_DECODE - Decode characters that were encoded using CSS 2.x escape rules syndata.html#characters. This function uses up to two bytes in the decoding process, so it can help to uncover ASCII characters that were encoded using CSS encoding that wouldn’t typically be encoded. It's also useful in countering evasion, which is a combination of a backslash and non-hexadecimal characters. For example, ja\vascript for javascript.

                  ESCAPE_SEQ_DECODE - Decode the following ANSI C escape sequences: \a, \b, \f, \n, \r, \t, \v, \, \?, \', \", \xHH (hexadecimal), \0OOO (octal). Encodings that aren't valid remain in the output.

                  HEX_DECODE - Decode a string of hexadecimal characters into a binary.

                  HTML_ENTITY_DECODE - Replace HTML-encoded characters with unencoded characters. HTML_ENTITY_DECODE performs these operations:

                  • Replaces (ampersand)quot; with "

                  • Replaces (ampersand)nbsp; with a non-breaking space, decimal 160

                  • Replaces (ampersand)lt; with a "less than" symbol

                  • Replaces (ampersand)gt; with >

                  • Replaces characters that are represented in hexadecimal format, (ampersand)#xhhhh;, with the corresponding characters

                  • Replaces characters that are represented in decimal format, (ampersand)#nnnn;, with the corresponding characters

                  JS_DECODE - Decode JavaScript escape sequences. If a \ u HHHH code is in the full-width ASCII code range of FF01-FF5E, then the higher byte is used to detect and adjust the lower byte. If not, only the lower byte is used and the higher byte is zeroed, causing a possible loss of information.

                  LOWERCASE - Convert uppercase letters (A-Z) to lowercase (a-z).

                  MD5 - Calculate an MD5 hash from the data in the input. The computed hash is in a raw binary form.

                  NONE - Specify NONE if you don't want any text transformations.

                  NORMALIZE_PATH - Remove multiple slashes, directory self-references, and directory back-references that are not at the beginning of the input from an input string.

                  NORMALIZE_PATH_WIN - This is the same as NORMALIZE_PATH, but first converts backslash characters to forward slashes.

                  REMOVE_NULLS - Remove all NULL bytes from the input.

                  REPLACE_COMMENTS - Replace each occurrence of a C-style comment (/* ... */) with a single space. Multiple consecutive occurrences are not compressed. Unterminated comments are also replaced with a space (ASCII 0x20). However, a standalone termination of a comment (*/) is not acted upon.

                  REPLACE_NULLS - Replace NULL bytes in the input with space characters (ASCII 0x20).

                  SQL_HEX_DECODE - Decode SQL hex data. Example (0x414243) will be decoded to (ABC).

                  URL_DECODE - Decode a URL-encoded value.

                  URL_DECODE_UNI - Like URL_DECODE, but with support for Microsoft-specific %u encoding. If the code is in the full-width ASCII code range of FF01-FF5E, the higher byte is used to detect and adjust the lower byte. Otherwise, only the lower byte is used and the higher byte is zeroed.

                  UTF8_TO_UNICODE - Convert all UTF-8 character sequences to Unicode. This helps input normalization, and minimizing false-positives and false-negatives for non-English languages.

                  Possible values include:
                  • "NONE"
                  • "COMPRESS_WHITE_SPACE"
                  • "HTML_ENTITY_DECODE"
                  • "LOWERCASE"
                  • "CMD_LINE"
                  • "URL_DECODE"
                  • "BASE64_DECODE"
                  • "HEX_DECODE"
                  • "MD5"
                  • "REPLACE_COMMENTS"
                  • "ESCAPE_SEQ_DECODE"
                  • "SQL_HEX_DECODE"
                  • "CSS_DECODE"
                  • "JS_DECODE"
                  • "NORMALIZE_PATH"
                  • "NORMALIZE_PATH_WIN"
                  • "REMOVE_NULLS"
                  • "REPLACE_NULLS"
                  • "BASE64_DECODE_EXT"
                  • "URL_DECODE_UNI"
                  • "UTF8_TO_UNICODE"
            • GeoMatchStatement — (map)

              A rule statement used to identify web requests based on country of origin.

              • CountryCodes — (Array<String>)

                An array of two-character country codes, for example, [ "US", "CN" ], from the alpha-2 country ISO codes of the ISO 3166 international standard.

              • ForwardedIPConfig — (map)

                The configuration for inspecting IP addresses in an HTTP header that you specify, instead of using the IP address that's reported by the web request origin. Commonly, this is the X-Forwarded-For (XFF) header, but you can specify any header name.

                Note: If the specified header isn't present in the request, WAF doesn't apply the rule to the web request at all.
                • HeaderName — required — (String)

                  The name of the HTTP header to use for the IP address. For example, to use the X-Forwarded-For (XFF) header, set this to X-Forwarded-For.

                  Note: If the specified header isn't present in the request, WAF doesn't apply the rule to the web request at all.
                • FallbackBehavior — required — (String)

                  The match status to assign to the web request if the request doesn't have a valid IP address in the specified position.

                  Note: If the specified header isn't present in the request, WAF doesn't apply the rule to the web request at all.

                  You can specify the following fallback behaviors:

                  • MATCH - Treat the web request as matching the rule statement. WAF applies the rule action to the request.

                  • NO_MATCH - Treat the web request as not matching the rule statement.

                  Possible values include:
                  • "MATCH"
                  • "NO_MATCH"
            • RuleGroupReferenceStatement — (map)

              A rule statement used to run the rules that are defined in a RuleGroup. To use this, create a rule group with your rules, then provide the ARN of the rule group in this statement.

              You cannot nest a RuleGroupReferenceStatement, for example for use inside a NotStatement or OrStatement. You can only use a rule group reference statement at the top level inside a web ACL.

              • ARN — required — (String)

                The Amazon Resource Name (ARN) of the entity.

              • ExcludedRules — (Array<map>)

                The rules in the referenced rule group whose actions are set to Count. When you exclude a rule, WAF evaluates it exactly as it would if the rule action setting were Count. This is a useful option for testing the rules in a rule group without modifying how they handle your web traffic.

                • Name — required — (String)

                  The name of the rule whose action you want to override to Count.

            • IPSetReferenceStatement — (map)

              A rule statement used to detect web requests coming from particular IP addresses or address ranges. To use this, create an IPSet that specifies the addresses you want to detect, then use the ARN of that set in this statement. To create an IP set, see CreateIPSet.

              Each IP set rule statement references an IP set. You create and maintain the set independent of your rules. This allows you to use the single set in multiple rules. When you update the referenced set, WAF automatically updates all rules that reference it.

              • ARN — required — (String)

                The Amazon Resource Name (ARN) of the IPSet that this statement references.

              • IPSetForwardedIPConfig — (map)

                The configuration for inspecting IP addresses in an HTTP header that you specify, instead of using the IP address that's reported by the web request origin. Commonly, this is the X-Forwarded-For (XFF) header, but you can specify any header name.

                Note: If the specified header isn't present in the request, WAF doesn't apply the rule to the web request at all.
                • HeaderName — required — (String)

                  The name of the HTTP header to use for the IP address. For example, to use the X-Forwarded-For (XFF) header, set this to X-Forwarded-For.

                  Note: If the specified header isn't present in the request, WAF doesn't apply the rule to the web request at all.
                • FallbackBehavior — required — (String)

                  The match status to assign to the web request if the request doesn't have a valid IP address in the specified position.

                  Note: If the specified header isn't present in the request, WAF doesn't apply the rule to the web request at all.

                  You can specify the following fallback behaviors:

                  • MATCH - Treat the web request as matching the rule statement. WAF applies the rule action to the request.

                  • NO_MATCH - Treat the web request as not matching the rule statement.

                  Possible values include:
                  • "MATCH"
                  • "NO_MATCH"
                • Position — required — (String)

                  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:

                  • FIRST - Inspect the first IP address in the list of IP addresses in the header. This is usually the client's original IP.

                  • LAST - Inspect the last IP address in the list of IP addresses in the header.

                  • ANY - Inspect all IP addresses in the header for a match. If the header contains more than 10 IP addresses, WAF inspects the last 10.

                  Possible values include:
                  • "FIRST"
                  • "LAST"
                  • "ANY"
            • RegexPatternSetReferenceStatement — (map)

              A rule statement used to search web request components for matches with regular expressions. To use this, create a RegexPatternSet that specifies the expressions that you want to detect, then use the ARN of that set in this statement. A web request matches the pattern set rule statement if the request component matches any of the patterns in the set. To create a regex pattern set, see CreateRegexPatternSet.

              Each regex pattern set rule statement references a regex pattern set. You create and maintain the set independent of your rules. This allows you to use the single set in multiple rules. When you update the referenced set, WAF automatically updates all rules that reference it.

              • ARN — required — (String)

                The Amazon Resource Name (ARN) of the RegexPatternSet that this statement references.

              • FieldToMatch — required — (map)

                The part of a web request that you want WAF to inspect. For more information, see FieldToMatch.

                • SingleHeader — (map)

                  Inspect a single header. Provide the name of the header to inspect, for example, User-Agent or Referer. This setting isn't case sensitive.

                  Example JSON: "SingleHeader": { "Name": "haystack" }

                  • Name — required — (String)

                    The name of the query header to inspect.

                • SingleQueryArgument — (map)

                  Inspect a single query argument. Provide the name of the query argument to inspect, such as UserName or SalesRegion. The name can be up to 30 characters long and isn't case sensitive.

                  This is used only to indicate the web request component for WAF to inspect, in the FieldToMatch specification.

                  Example JSON: "SingleQueryArgument": { "Name": "myArgument" }

                  • Name — required — (String)

                    The name of the query argument to inspect.

                • AllQueryArguments — (map)

                  Inspect all query arguments.

                • UriPath — (map)

                  Inspect the request URI path. This is the part of a web request that identifies a resource, for example, /images/daily-ad.jpg.

                • QueryString — (map)

                  Inspect the query string. This is the part of a URL that appears after a ? character, if any.

                • Body — (map)

                  Inspect the request body as plain text. The request body immediately follows the request headers. This is the part of a request that contains any additional data that you want to send to your web server as the HTTP request body, such as data from a form.

                  Note that only the first 8 KB (8192 bytes) of the request body are forwarded to WAF for inspection by the underlying host service. If you don't need to inspect more than 8 KB, you can guarantee that you don't allow additional bytes in by combining a statement that inspects the body of the web request, such as ByteMatchStatement or RegexPatternSetReferenceStatement, with a SizeConstraintStatement that enforces an 8 KB size limit on the body of the request. WAF doesn't support inspecting the entire contents of web requests whose bodies exceed the 8 KB limit.

                • Method — (map)

                  Inspect the HTTP method. The method indicates the type of operation that the request is asking the origin to perform.

                • JsonBody — (map)

                  Inspect the request body as JSON. The request body immediately follows the request headers. This is the part of a request that contains any additional data that you want to send to your web server as the HTTP request body, such as data from a form.

                  Note that only the first 8 KB (8192 bytes) of the request body are forwarded to WAF for inspection by the underlying host service. If you don't need to inspect more than 8 KB, you can guarantee that you don't allow additional bytes in by combining a statement that inspects the body of the web request, such as ByteMatchStatement or RegexPatternSetReferenceStatement, with a SizeConstraintStatement that enforces an 8 KB size limit on the body of the request. WAF doesn't support inspecting the entire contents of web requests whose bodies exceed the 8 KB limit.

                  • MatchPattern — required — (map)

                    The patterns to look for in the JSON body. WAF inspects the results of these pattern matches against the rule inspection criteria.

                    • All — (map)

                      Match all of the elements. See also MatchScope in JsonBody.

                      You must specify either this setting or the IncludedPaths setting, but not both.

                    • IncludedPaths — (Array<String>)

                      Match only the specified include paths. See also MatchScope in JsonBody.

                      Provide the include paths using JSON Pointer syntax. For example, "IncludedPaths": ["/dogs/0/name", "/dogs/1/name"]. For information about this syntax, see the Internet Engineering Task Force (IETF) documentation JavaScript Object Notation (JSON) Pointer.

                      You must specify either this setting or the All setting, but not both.

                      Note: Don't use this option to include all paths. Instead, use the All setting.
                  • MatchScope — required — (String)

                    The parts of the JSON to match against using the MatchPattern. If you specify All, WAF matches against keys and values.

                    Possible values include:
                    • "ALL"
                    • "KEY"
                    • "VALUE"
                  • InvalidFallbackBehavior — (String)

                    What WAF should do if it fails to completely parse the JSON body. The options are the following:

                    • EVALUATE_AS_STRING - Inspect the body as plain text. WAF applies the text transformations and inspection criteria that you defined for the JSON inspection to the body text string.

                    • MATCH - Treat the web request as matching the rule statement. WAF applies the rule action to the request.

                    • NO_MATCH - Treat the web request as not matching the rule statement.

                    If you don't provide this setting, WAF parses and evaluates the content only up to the first parsing failure that it encounters.

                    WAF does its best to parse the entire JSON body, but might be forced to stop for reasons such as invalid characters, duplicate keys, truncation, and any content whose root node isn't an object or an array.

                    WAF parses the JSON in the following examples as two valid key, value pairs:

                    • Missing comma: {"key1":"value1""key2":"value2"}

                    • Missing colon: {"key1":"value1","key2""value2"}

                    • Extra colons: {"key1"::"value1","key2""value2"}

                    Possible values include:
                    • "MATCH"
                    • "NO_MATCH"
                    • "EVALUATE_AS_STRING"
              • TextTransformations — required — (Array<map>)

                Text transformations eliminate some of the unusual formatting that attackers use in web requests in an effort to bypass detection. If you specify one or more transformations in a rule statement, WAF performs all transformations on the content of the request component identified by FieldToMatch, starting from the lowest priority setting, before inspecting the content for a match.

                • Priority — required — (Integer)

                  Sets the relative processing order for multiple transformations that are defined for a rule statement. WAF processes all transformations, from lowest priority to highest, before inspecting the transformed content. The priorities don't need to be consecutive, but they must all be different.

                • Type — required — (String)

                  You can specify the following transformation types:

                  BASE64_DECODE - Decode a Base64-encoded string.

                  BASE64_DECODE_EXT - Decode a Base64-encoded string, but use a forgiving implementation that ignores characters that aren't valid.

                  CMD_LINE - Command-line transformations. These are helpful in reducing effectiveness of attackers who inject an operating system command-line command and use unusual formatting to disguise some or all of the command.

                  • Delete the following characters: \ " ' ^

                  • Delete spaces before the following characters: / (

                  • Replace the following characters with a space: , ;

                  • Replace multiple spaces with one space

                  • Convert uppercase letters (A-Z) to lowercase (a-z)

                  COMPRESS_WHITE_SPACE - Replace these characters with a space character (decimal 32):

                  • \f, formfeed, decimal 12

                  • \t, tab, decimal 9

                  • \n, newline, decimal 10

                  • \r, carriage return, decimal 13

                  • \v, vertical tab, decimal 11

                  • Non-breaking space, decimal 160

                  COMPRESS_WHITE_SPACE also replaces multiple spaces with one space.

                  CSS_DECODE - Decode characters that were encoded using CSS 2.x escape rules syndata.html#characters. This function uses up to two bytes in the decoding process, so it can help to uncover ASCII characters that were encoded using CSS encoding that wouldn’t typically be encoded. It's also useful in countering evasion, which is a combination of a backslash and non-hexadecimal characters. For example, ja\vascript for javascript.

                  ESCAPE_SEQ_DECODE - Decode the following ANSI C escape sequences: \a, \b, \f, \n, \r, \t, \v, \, \?, \', \", \xHH (hexadecimal), \0OOO (octal). Encodings that aren't valid remain in the output.

                  HEX_DECODE - Decode a string of hexadecimal characters into a binary.

                  HTML_ENTITY_DECODE - Replace HTML-encoded characters with unencoded characters. HTML_ENTITY_DECODE performs these operations:

                  • Replaces (ampersand)quot; with "

                  • Replaces (ampersand)nbsp; with a non-breaking space, decimal 160

                  • Replaces (ampersand)lt; with a "less than" symbol

                  • Replaces (ampersand)gt; with >

                  • Replaces characters that are represented in hexadecimal format, (ampersand)#xhhhh;, with the corresponding characters

                  • Replaces characters that are represented in decimal format, (ampersand)#nnnn;, with the corresponding characters

                  JS_DECODE - Decode JavaScript escape sequences. If a \ u HHHH code is in the full-width ASCII code range of FF01-FF5E, then the higher byte is used to detect and adjust the lower byte. If not, only the lower byte is used and the higher byte is zeroed, causing a possible loss of information.

                  LOWERCASE - Convert uppercase letters (A-Z) to lowercase (a-z).

                  MD5 - Calculate an MD5 hash from the data in the input. The computed hash is in a raw binary form.

                  NONE - Specify NONE if you don't want any text transformations.

                  NORMALIZE_PATH - Remove multiple slashes, directory self-references, and directory back-references that are not at the beginning of the input from an input string.

                  NORMALIZE_PATH_WIN - This is the same as NORMALIZE_PATH, but first converts backslash characters to forward slashes.

                  REMOVE_NULLS - Remove all NULL bytes from the input.

                  REPLACE_COMMENTS - Replace each occurrence of a C-style comment (/* ... */) with a single space. Multiple consecutive occurrences are not compressed. Unterminated comments are also replaced with a space (ASCII 0x20). However, a standalone termination of a comment (*/) is not acted upon.

                  REPLACE_NULLS - Replace NULL bytes in the input with space characters (ASCII 0x20).

                  SQL_HEX_DECODE - Decode SQL hex data. Example (0x414243) will be decoded to (ABC).

                  URL_DECODE - Decode a URL-encoded value.

                  URL_DECODE_UNI - Like URL_DECODE, but with support for Microsoft-specific %u encoding. If the code is in the full-width ASCII code range of FF01-FF5E, the higher byte is used to detect and adjust the lower byte. Otherwise, only the lower byte is used and the higher byte is zeroed.

                  UTF8_TO_UNICODE - Convert all UTF-8 character sequences to Unicode. This helps input normalization, and minimizing false-positives and false-negatives for non-English languages.

                  Possible values include:
                  • "NONE"
                  • "COMPRESS_WHITE_SPACE"
                  • "HTML_ENTITY_DECODE"
                  • "LOWERCASE"
                  • "CMD_LINE"
                  • "URL_DECODE"
                  • "BASE64_DECODE"
                  • "HEX_DECODE"
                  • "MD5"
                  • "REPLACE_COMMENTS"
                  • "ESCAPE_SEQ_DECODE"
                  • "SQL_HEX_DECODE"
                  • "CSS_DECODE"
                  • "JS_DECODE"
                  • "NORMALIZE_PATH"
                  • "NORMALIZE_PATH_WIN"
                  • "REMOVE_NULLS"
                  • "REPLACE_NULLS"
                  • "BASE64_DECODE_EXT"
                  • "URL_DECODE_UNI"
                  • "UTF8_TO_UNICODE"
            • RateBasedStatement — (map)

              A rate-based rule tracks the rate of requests for each originating IP address, and triggers the rule action when the rate exceeds a limit that you specify on the number of requests in any 5-minute time span. You can use this to put a temporary block on requests from an IP address that is sending excessive requests.

              WAF tracks and manages web requests separately for each instance of a rate-based rule that you use. For example, if you provide the same rate-based rule settings in two web ACLs, each of the two rule statements represents a separate instance of the rate-based rule and gets its own tracking and management by WAF. If you define a rate-based rule inside a rule group, and then use that rule group in multiple places, each use creates a separate instance of the rate-based rule that gets its own tracking and management by WAF.

              When the rule action triggers, WAF blocks additional requests from the IP address until the request rate falls below the limit.

              You can optionally nest another statement inside the rate-based statement, to narrow the scope of the rule so that it only counts requests that match the nested statement. For example, based on recent requests that you have seen from an attacker, you might create a rate-based rule with a nested AND rule statement that contains the following nested statements:

              • An IP match statement with an IP set that specified the address 192.0.2.44.

              • A string match statement that searches in the User-Agent header for the string BadBot.

              In this rate-based rule, you also define a rate limit. For this example, the rate limit is 1,000. Requests that meet both of the conditions in the statements are counted. If the count exceeds 1,000 requests per five minutes, the rule action triggers. Requests that do not meet both conditions are not counted towards the rate limit and are not affected by this rule.

              You cannot nest a RateBasedStatement inside another statement, for example inside a NotStatement or OrStatement. You can define a RateBasedStatement inside a web ACL and inside a rule group.

              • Limit — required — (Integer)

                The limit on requests per 5-minute period for a single originating IP address. If the statement includes a ScopeDownStatement, this limit is applied only to the requests that match the statement.

              • AggregateKeyType — required — (String)

                Setting that indicates how to aggregate the request counts. The options are the following:

                • IP - Aggregate the request counts on the IP address from the web request origin.

                • FORWARDED_IP - Aggregate the request counts on the first IP address in an HTTP header. If you use this, configure the ForwardedIPConfig, to specify the header to use.

                Possible values include:
                • "IP"
                • "FORWARDED_IP"
              • ForwardedIPConfig — (map)

                The configuration for inspecting IP addresses in an HTTP header that you specify, instead of using the IP address that's reported by the web request origin. Commonly, this is the X-Forwarded-For (XFF) header, but you can specify any header name.

                Note: If the specified header isn't present in the request, WAF doesn't apply the rule to the web request at all.

                This is required if AggregateKeyType is set to FORWARDED_IP.

                • HeaderName — required — (String)

                  The name of the HTTP header to use for the IP address. For example, to use the X-Forwarded-For (XFF) header, set this to X-Forwarded-For.

                  Note: If the specified header isn't present in the request, WAF doesn't apply the rule to the web request at all.
                • FallbackBehavior — required — (String)

                  The match status to assign to the web request if the request doesn't have a valid IP address in the specified position.

                  Note: If the specified header isn't present in the request, WAF doesn't apply the rule to the web request at all.

                  You can specify the following fallback behaviors:

                  • MATCH - Treat the web request as matching the rule statement. WAF applies the rule action to the request.

                  • NO_MATCH - Treat the web request as not matching the rule statement.

                  Possible values include:
                  • "MATCH"
                  • "NO_MATCH"
            • AndStatement — (map)

              A logical rule statement used to combine other rule statements with AND logic. You provide more than one Statement within the AndStatement.

              • Statements — required — (Array<map>)

                The statements to combine with AND logic. You can use any statements that can be nested.

            • OrStatement — (map)

              A logical rule statement used to combine other rule statements with OR logic. You provide more than one Statement within the OrStatement.

              • Statements — required — (Array<map>)

                The statements to combine with OR logic. You can use any statements that can be nested.

            • NotStatement — (map)

              A logical rule statement used to negate the results of another rule statement. You provide one Statement within the NotStatement.

            • ManagedRuleGroupStatement — (map)

              A rule statement used to run the rules that are defined in a managed rule group. To use this, provide the vendor name and the name of the rule group in this statement. You can retrieve the required names by calling ListAvailableManagedRuleGroups.

              You cannot nest a ManagedRuleGroupStatement, for example for use inside a NotStatement or OrStatement. It can only be referenced as a top-level statement within a rule.

              • VendorName — required — (String)

                The name of the managed rule group vendor. You use this, along with the rule group name, to identify the rule group.

              • Name — required — (String)

                The name of the managed rule group. You use this, along with the vendor name, to identify the rule group.

              • Version — (String)

                The version of the managed rule group to use. If you specify this, the version setting is fixed until you change it. If you don't specify this, WAF uses the vendor's default version, and then keeps the version at the vendor's default when the vendor updates the managed rule group settings.

              • ExcludedRules — (Array<map>)

                The rules in the referenced rule group whose actions are set to Count. When you exclude a rule, WAF evaluates it exactly as it would if the rule action setting were Count. This is a useful option for testing the rules in a rule group without modifying how they handle your web traffic.

                • Name — required — (String)

                  The name of the rule whose action you want to override to Count.

            • LabelMatchStatement — (map)

              A rule statement that defines a string match search against labels that have been added to the web request by rules that have already run in the web ACL.

              The label match statement provides the label or namespace string to search for. The label string can represent a part or all of the fully qualified label name that had been added to the web request. Fully qualified labels have a prefix, optional namespaces, and label name. The prefix identifies the rule group or web ACL context of the rule that added the label. If you do not provide the fully qualified name in your label match string, WAF performs the search for labels that were added in the same context as the label match statement.

              • Scope — required — (String)

                Specify whether you want to match using the label name or just the namespace.

                Possible values include:
                • "LABEL"
                • "NAMESPACE"
              • Key — required — (String)

                The string to match against. The setting you provide for this depends on the match statement's Scope setting:

                • If the Scope indicates LABEL, then this specification must include the name and can include any number of preceding namespace specifications and prefix up to providing the fully qualified label name.

                • If the Scope indicates NAMESPACE, then this specification can include any number of contiguous namespace strings, and can include the entire label namespace prefix from the rule group or web ACL where the label originates.

                Labels are case sensitive and components of a label must be separated by colon, for example NS1:NS2:name.

            • RegexMatchStatement — (map)

              A rule statement used to search web request components for a match against a single regular expression.

              • RegexString — required — (String)

                The string representing the regular expression.

              • FieldToMatch — required — (map)

                The part of a web request that you want WAF to inspect. For more information, see FieldToMatch.

                • SingleHeader — (map)

                  Inspect a single header. Provide the name of the header to inspect, for example, User-Agent or Referer. This setting isn't case sensitive.

                  Example JSON: "SingleHeader": { "Name": "haystack" }

                  • Name — required — (String)

                    The name of the query header to inspect.

                • SingleQueryArgument — (map)

                  Inspect a single query argument. Provide the name of the query argument to inspect, such as UserName or SalesRegion. The name can be up to 30 characters long and isn't case sensitive.

                  This is used only to indicate the web request component for WAF to inspect, in the FieldToMatch specification.

                  Example JSON: "SingleQueryArgument": { "Name": "myArgument" }

                  • Name — required — (String)

                    The name of the query argument to inspect.

                • AllQueryArguments — (map)

                  Inspect all query arguments.

                • UriPath — (map)

                  Inspect the request URI path. This is the part of a web request that identifies a resource, for example, /images/daily-ad.jpg.

                • QueryString — (map)

                  Inspect the query string. This is the part of a URL that appears after a ? character, if any.

                • Body — (map)

                  Inspect the request body as plain text. The request body immediately follows the request headers. This is the part of a request that contains any additional data that you want to send to your web server as the HTTP request body, such as data from a form.

                  Note that only the first 8 KB (8192 bytes) of the request body are forwarded to WAF for inspection by the underlying host service. If you don't need to inspect more than 8 KB, you can guarantee that you don't allow additional bytes in by combining a statement that inspects the body of the web request, such as ByteMatchStatement or RegexPatternSetReferenceStatement, with a SizeConstraintStatement that enforces an 8 KB size limit on the body of the request. WAF doesn't support inspecting the entire contents of web requests whose bodies exceed the 8 KB limit.

                • Method — (map)

                  Inspect the HTTP method. The method indicates the type of operation that the request is asking the origin to perform.

                • JsonBody — (map)

                  Inspect the request body as JSON. The request body immediately follows the request headers. This is the part of a request that contains any additional data that you want to send to your web server as the HTTP request body, such as data from a form.

                  Note that only the first 8 KB (8192 bytes) of the request body are forwarded to WAF for inspection by the underlying host service. If you don't need to inspect more than 8 KB, you can guarantee that you don't allow additional bytes in by combining a statement that inspects the body of the web request, such as ByteMatchStatement or RegexPatternSetReferenceStatement, with a SizeConstraintStatement that enforces an 8 KB size limit on the body of the request. WAF doesn't support inspecting the entire contents of web requests whose bodies exceed the 8 KB limit.

                  • MatchPattern — required — (map)

                    The patterns to look for in the JSON body. WAF inspects the results of these pattern matches against the rule inspection criteria.

                    • All — (map)

                      Match all of the elements. See also MatchScope in JsonBody.

                      You must specify either this setting or the IncludedPaths setting, but not both.

                    • IncludedPaths — (Array<String>)

                      Match only the specified include paths. See also MatchScope in JsonBody.

                      Provide the include paths using JSON Pointer syntax. For example, "IncludedPaths": ["/dogs/0/name", "/dogs/1/name"]. For information about this syntax, see the Internet Engineering Task Force (IETF) documentation JavaScript Object Notation (JSON) Pointer.

                      You must specify either this setting or the All setting, but not both.

                      Note: Don't use this option to include all paths. Instead, use the All setting.
                  • MatchScope — required — (String)

                    The parts of the JSON to match against using the MatchPattern. If you specify All, WAF matches against keys and values.

                    Possible values include:
                    • "ALL"
                    • "KEY"
                    • "VALUE"
                  • InvalidFallbackBehavior — (String)

                    What WAF should do if it fails to completely parse the JSON body. The options are the following:

                    • EVALUATE_AS_STRING - Inspect the body as plain text. WAF applies the text transformations and inspection criteria that you defined for the JSON inspection to the body text string.

                    • MATCH - Treat the web request as matching the rule statement. WAF applies the rule action to the request.

                    • NO_MATCH - Treat the web request as not matching the rule statement.

                    If you don't provide this setting, WAF parses and evaluates the content only up to the first parsing failure that it encounters.

                    WAF does its best to parse the entire JSON body, but might be forced to stop for reasons such as invalid characters, duplicate keys, truncation, and any content whose root node isn't an object or an array.

                    WAF parses the JSON in the following examples as two valid key, value pairs:

                    • Missing comma: {"key1":"value1""key2":"value2"}

                    • Missing colon: {"key1":"value1","key2""value2"}

                    • Extra colons: {"key1"::"value1","key2""value2"}

                    Possible values include:
                    • "MATCH"
                    • "NO_MATCH"
                    • "EVALUATE_AS_STRING"
              • TextTransformations — required — (Array<map>)

                Text transformations eliminate some of the unusual formatting that attackers use in web requests in an effort to bypass detection. If you specify one or more transformations in a rule statement, WAF performs all transformations on the content of the request component identified by FieldToMatch, starting from the lowest priority setting, before inspecting the content for a match.

                • Priority — required — (Integer)

                  Sets the relative processing order for multiple transformations that are defined for a rule statement. WAF processes all transformations, from lowest priority to highest, before inspecting the transformed content. The priorities don't need to be consecutive, but they must all be different.

                • Type — required — (String)

                  You can specify the following transformation types:

                  BASE64_DECODE - Decode a Base64-encoded string.

                  BASE64_DECODE_EXT - Decode a Base64-encoded string, but use a forgiving implementation that ignores characters that aren't valid.

                  CMD_LINE - Command-line transformations. These are helpful in reducing effectiveness of attackers who inject an operating system command-line command and use unusual formatting to disguise some or all of the command.

                  • Delete the following characters: \ " ' ^

                  • Delete spaces before the following characters: / (

                  • Replace the following characters with a space: , ;

                  • Replace multiple spaces with one space

                  • Convert uppercase letters (A-Z) to lowercase (a-z)

                  COMPRESS_WHITE_SPACE - Replace these characters with a space character (decimal 32):

                  • \f, formfeed, decimal 12

                  • \t, tab, decimal 9

                  • \n, newline, decimal 10

                  • \r, carriage return, decimal 13

                  • \v, vertical tab, decimal 11

                  • Non-breaking space, decimal 160

                  COMPRESS_WHITE_SPACE also replaces multiple spaces with one space.

                  CSS_DECODE - Decode characters that were encoded using CSS 2.x escape rules syndata.html#characters. This function uses up to two bytes in the decoding process, so it can help to uncover ASCII characters that were encoded using CSS encoding that wouldn’t typically be encoded. It's also useful in countering evasion, which is a combination of a backslash and non-hexadecimal characters. For example, ja\vascript for javascript.

                  ESCAPE_SEQ_DECODE - Decode the following ANSI C escape sequences: \a, \b, \f, \n, \r, \t, \v, \, \?, \', \", \xHH (hexadecimal), \0OOO (octal). Encodings that aren't valid remain in the output.

                  HEX_DECODE - Decode a string of hexadecimal characters into a binary.

                  HTML_ENTITY_DECODE - Replace HTML-encoded characters with unencoded characters. HTML_ENTITY_DECODE performs these operations:

                  • Replaces (ampersand)quot; with "

                  • Replaces (ampersand)nbsp; with a non-breaking space, decimal 160

                  • Replaces (ampersand)lt; with a "less than" symbol

                  • Replaces (ampersand)gt; with >

                  • Replaces characters that are represented in hexadecimal format, (ampersand)#xhhhh;, with the corresponding characters

                  • Replaces characters that are represented in decimal format, (ampersand)#nnnn;, with the corresponding characters

                  JS_DECODE - Decode JavaScript escape sequences. If a \ u HHHH code is in the full-width ASCII code range of FF01-FF5E, then the higher byte is used to detect and adjust the lower byte. If not, only the lower byte is used and the higher byte is zeroed, causing a possible loss of information.

                  LOWERCASE - Convert uppercase letters (A-Z) to lowercase (a-z).

                  MD5 - Calculate an MD5 hash from the data in the input. The computed hash is in a raw binary form.

                  NONE - Specify NONE if you don't want any text transformations.

                  NORMALIZE_PATH - Remove multiple slashes, directory self-references, and directory back-references that are not at the beginning of the input from an input string.

                  NORMALIZE_PATH_WIN - This is the same as NORMALIZE_PATH, but first converts backslash characters to forward slashes.

                  REMOVE_NULLS - Remove all NULL bytes from the input.

                  REPLACE_COMMENTS - Replace each occurrence of a C-style comment (/* ... */) with a single space. Multiple consecutive occurrences are not compressed. Unterminated comments are also replaced with a space (ASCII 0x20). However, a standalone termination of a comment (*/) is not acted upon.

                  REPLACE_NULLS - Replace NULL bytes in the input with space characters (ASCII 0x20).

                  SQL_HEX_DECODE - Decode SQL hex data. Example (0x414243) will be decoded to (ABC).

                  URL_DECODE - Decode a URL-encoded value.

                  URL_DECODE_UNI - Like URL_DECODE, but with support for Microsoft-specific %u encoding. If the code is in the full-width ASCII code range of FF01-FF5E, the higher byte is used to detect and adjust the lower byte. Otherwise, only the lower byte is used and the higher byte is zeroed.

                  UTF8_TO_UNICODE - Convert all UTF-8 character sequences to Unicode. This helps input normalization, and minimizing false-positives and false-negatives for non-English languages.

                  Possible values include:
                  • "NONE"
                  • "COMPRESS_WHITE_SPACE"
                  • "HTML_ENTITY_DECODE"
                  • "LOWERCASE"
                  • "CMD_LINE"
                  • "URL_DECODE"
                  • "BASE64_DECODE"
                  • "HEX_DECODE"
                  • "MD5"
                  • "REPLACE_COMMENTS"
                  • "ESCAPE_SEQ_DECODE"
                  • "SQL_HEX_DECODE"
                  • "CSS_DECODE"
                  • "JS_DECODE"
                  • "NORMALIZE_PATH"
                  • "NORMALIZE_PATH_WIN"
                  • "REMOVE_NULLS"
                  • "REPLACE_NULLS"
                  • "BASE64_DECODE_EXT"
                  • "URL_DECODE_UNI"
                  • "UTF8_TO_UNICODE"
          • Action — (map)

            The action that WAF should take on a web request when it matches the rule statement. Settings at the web ACL level can override the rule action setting.

            This is used only for rules whose statements do not reference a rule group. Rule statements that reference a rule group include RuleGroupReferenceStatement and ManagedRuleGroupStatement.

            You must specify either this Action setting or the rule OverrideAction setting, but not both:

            • If the rule statement does not reference a rule group, use this rule action setting and not the rule override action setting.

            • If the rule statement references a rule group, use the override action setting and not this action setting.

            • Block — (map)

              Instructs WAF to block the web request.

              • CustomResponse — (map)

                Defines a custom response for the web request.

                For information about customizing web requests and responses, see Customizing web requests and responses in WAF in the WAF Developer Guide.

                • ResponseCode — required — (Integer)

                  The HTTP status code to return to the client.

                  For a list of status codes that you can use in your custom reqponses, see Supported status codes for custom response in the WAF Developer Guide.

                • CustomResponseBodyKey — (String)

                  References the response body that you want WAF to return to the web request client. You can define a custom response for a rule action or a default web ACL action that is set to block. To do this, you first define the response body key and value in the CustomResponseBodies setting for the WebACL or RuleGroup where you want to use it. Then, in the rule action or web ACL default action BlockAction setting, you reference the response body using this key.

                • ResponseHeaders — (Array<map>)

                  The HTTP headers to use in the response. Duplicate header names are not allowed.

                  For information about the limits on count and size for custom request and response settings, see WAF quotas in the WAF Developer Guide.

                  • Name — required — (String)

                    The name of the custom header.

                    For custom request header insertion, when WAF inserts the header into the request, it prefixes this name x-amzn-waf-, to avoid confusion with the headers that are already in the request. For example, for the header name sample, WAF inserts the header x-amzn-waf-sample.

                  • Value — required — (String)

                    The value of the custom header.

            • Allow — (map)

              Instructs WAF to allow the web request.

              • CustomRequestHandling — (map)

                Defines custom handling for the web request.

                For information about customizing web requests and responses, see Customizing web requests and responses in WAF in the WAF Developer Guide.

                • InsertHeaders — required — (Array<map>)

                  The HTTP headers to insert into the request. Duplicate header names are not allowed.

                  For information about the limits on count and size for custom request and response settings, see WAF quotas in the WAF Developer Guide.

                  • Name — required — (String)

                    The name of the custom header.

                    For custom request header insertion, when WAF inserts the header into the request, it prefixes this name x-amzn-waf-, to avoid confusion with the headers that are already in the request. For example, for the header name sample, WAF inserts the header x-amzn-waf-sample.

                  • Value — required — (String)

                    The value of the custom header.

            • Count — (map)

              Instructs WAF to count the web request and allow it.

              • CustomRequestHandling — (map)

                Defines custom handling for the web request.

                For information about customizing web requests and responses, see Customizing web requests and responses in WAF in the WAF Developer Guide.

                • InsertHeaders — required — (Array<map>)

                  The HTTP headers to insert into the request. Duplicate header names are not allowed.

                  For information about the limits on count and size for custom request and response settings, see WAF quotas in the WAF Developer Guide.

                  • Name — required — (String)

                    The name of the custom header.

                    For custom request header insertion, when WAF inserts the header into the request, it prefixes this name x-amzn-waf-, to avoid confusion with the headers that are already in the request. For example, for the header name sample, WAF inserts the header x-amzn-waf-sample.

                  • Value — required — (String)

                    The value of the custom header.

            • Captcha — (map)

              Instructs WAF to run a CAPTCHA check against the web request.

              • CustomRequestHandling — (map)

                Defines custom handling for the web request.

                For information about customizing web requests and responses, see Customizing web requests and responses in WAF in the WAF Developer Guide.

                • InsertHeaders — required — (Array<map>)

                  The HTTP headers to insert into the request. Duplicate header names are not allowed.

                  For information about the limits on count and size for custom request and response settings, see WAF quotas in the WAF Developer Guide.

                  • Name — required — (String)

                    The name of the custom header.

                    For custom request header insertion, when WAF inserts the header into the request, it prefixes this name x-amzn-waf-, to avoid confusion with the headers that are already in the request. For example, for the header name sample, WAF inserts the header x-amzn-waf-sample.

                  • Value — required — (String)

                    The value of the custom header.

          • OverrideAction — (map)

            The action to use in the place of the action that results from the rule group evaluation. Set the override action to none to leave the result of the rule group alone. Set it to count to override the result to count only.

            You can only use this for rule statements that reference a rule group, like RuleGroupReferenceStatement and ManagedRuleGroupStatement.

            Note: This option is usually set to none. It does not affect how the rules in the rule group are evaluated. If you want the rules in the rule group to only count matches, do not use this and instead exclude those rules in your rule group reference statement settings.
            • Count — (map)

              Override the rule group evaluation result to count only.

              Note: This option is usually set to none. It does not affect how the rules in the rule group are evaluated. If you want the rules in the rule group to only count matches, do not use this and instead exclude those rules in your rule group reference statement settings.
              • CustomRequestHandling — (map)

                Defines custom handling for the web request.

                For information about customizing web requests and responses, see Customizing web requests and responses in WAF in the WAF Developer Guide.

                • InsertHeaders — required — (Array<map>)

                  The HTTP headers to insert into the request. Duplicate header names are not allowed.

                  For information about the limits on count and size for custom request and response settings, see WAF quotas in the WAF Developer Guide.

                  • Name — required — (String)

                    The name of the custom header.

                    For custom request header insertion, when WAF inserts the header into the request, it prefixes this name x-amzn-waf-, to avoid confusion with the headers that are already in the request. For example, for the header name sample, WAF inserts the header x-amzn-waf-sample.

                  • Value — required — (String)

                    The value of the custom header.

            • None — (map)

              Don't override the rule group evaluation result. This is the most common setting.

          • RuleLabels — (Array<map>)

            Labels to apply to web requests that match the rule match statement. WAF applies fully qualified labels to matching web requests. A fully qualified label is the concatenation of a label namespace and a rule label. The rule's rule group or web ACL defines the label namespace.

            Rules that run after this rule in the web ACL can match against these labels using a LabelMatchStatement.

            For each label, provide a case-sensitive string containing optional namespaces and a label name, according to the following guidelines:

            • Separate each component of the label with a colon.

            • Each namespace or name can have up to 128 characters.

            • You can specify up to 5 namespaces in a label.

            • Don't use the following reserved words in your label specification: aws, waf, managed, rulegroup, webacl, regexpatternset, or ipset.

            For example, myLabelName or nameSpace1:nameSpace2:myLabelName.

            • Name — required — (String)

              The label string.

          • VisibilityConfig — required — (map)

            Defines and enables Amazon CloudWatch metrics and web request sample collection.

            • SampledRequestsEnabled — required — (Boolean)

              A boolean indicating whether WAF should store a sampling of the web requests that match the rules. You can view the sampled requests through the WAF console.

            • CloudWatchMetricsEnabled — required — (Boolean)

              A boolean indicating whether the associated resource sends metrics to Amazon CloudWatch. For the list of available metrics, see WAF Metrics.

            • MetricName — required — (String)

              A name of the Amazon CloudWatch metric. The name can contain only the characters: A-Z, a-z, 0-9, - (hyphen), and _ (underscore). The name can be from one to 128 characters long. It can't contain whitespace or metric names reserved for WAF, for example "All" and "Default_Action."

          • CaptchaConfig — (map)

            Specifies how WAF should handle CAPTCHA evaluations. If you don't specify this, WAF uses the CAPTCHA configuration that's defined for the web ACL.

            • ImmunityTimeProperty — (map)

              Determines how long a CAPTCHA token remains valid after the client successfully solves a CAPTCHA puzzle.

              • ImmunityTime — required — (Integer)

                The amount of time, in seconds, that a CAPTCHA token is valid. The default setting is 300.

        • VisibilityConfig — required — (map)

          Defines and enables Amazon CloudWatch metrics and web request sample collection.

          • SampledRequestsEnabled — required — (Boolean)

            A boolean indicating whether WAF should store a sampling of the web requests that match the rules. You can view the sampled requests through the WAF console.

          • CloudWatchMetricsEnabled — required — (Boolean)

            A boolean indicating whether the associated resource sends metrics to Amazon CloudWatch. For the list of available metrics, see WAF Metrics.

          • MetricName — required — (String)

            A name of the Amazon CloudWatch metric. The name can contain only the characters: A-Z, a-z, 0-9, - (hyphen), and _ (underscore). The name can be from one to 128 characters long. It can't contain whitespace or metric names reserved for WAF, for example "All" and "Default_Action."

        • LabelNamespace — (String)

          The label namespace prefix for this rule group. All labels added by rules in this rule group have this prefix.

          • The syntax for the label namespace prefix for your rule groups is the following:

            awswaf:<account ID>:rulegroup:<rule group name>:

          • When a rule with a label matches a web request, WAF adds the fully qualified label to the request. A fully qualified label is made up of the label namespace from the rule group or web ACL where the rule is defined and the label from the rule, separated by a colon:

            <label namespace>:<label from rule>

        • CustomResponseBodies — (map<map>)

          A map of custom response keys and content bodies. When you create a rule with a block action, you can send a custom response to the web request. You define these for the rule group, and then use them in the rules that you define in the rule group.

          For information about customizing web requests and responses, see Customizing web requests and responses in WAF in the WAF Developer Guide.

          For information about the limits on count and size for custom request and response settings, see WAF quotas in the WAF Developer Guide.

          • ContentType — required — (String)

            The type of content in the payload that you are defining in the Content string.

            Possible values include:
            • "TEXT_PLAIN"
            • "TEXT_HTML"
            • "APPLICATION_JSON"
          • Content — required — (String)

            The payload of the custom response.

            You can use JSON escape strings in JSON content. To do this, you must specify JSON content in the ContentType setting.

            For information about the limits on count and size for custom request and response settings, see WAF quotas in the WAF Developer Guide.

        • AvailableLabels — (Array<map>)

          The labels that one or more rules in this rule group add to matching web requests. These labels are defined in the RuleLabels for a Rule.

          • Name — (String)

            An individual label specification.

        • ConsumedLabels — (Array<map>)

          The labels that one or more rules in this rule group match against in label match statements. These labels are defined in a LabelMatchStatement specification, in the Statement definition of a rule.

          • Name — (String)

            An individual label specification.

      • LockToken — (String)

        A token used for optimistic locking. WAF returns a token to your get and list requests, to mark the state of the entity at the time of the request. To make changes to the entity associated with the token, you provide the token to operations like update and delete. WAF uses the token to ensure that no changes have been made to the entity since you last retrieved it. If a change has been made, the update fails with a WAFOptimisticLockException. If this happens, perform another get, and use the new token returned by that operation.

Returns:

  • (AWS.Request) —

    a handle to the operation request for subsequent event callback registration.

getSampledRequests(params = {}, callback) ⇒ AWS.Request

Gets detailed information about a specified number of requests--a sample--that WAF randomly selects from among the first 5,000 requests that your Amazon Web Services 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 WAF selected the requests in the sample.

Service Reference:

Examples:

Calling the getSampledRequests operation

var params = {
  MaxItems: 'NUMBER_VALUE', /* required */
  RuleMetricName: 'STRING_VALUE', /* required */
  Scope: CLOUDFRONT | REGIONAL, /* required */
  TimeWindow: { /* required */
    EndTime: new Date || 'Wed Dec 31 1969 16:00:00 GMT-0800 (PST)' || 123456789, /* required */
    StartTime: new Date || 'Wed Dec 31 1969 16:00:00 GMT-0800 (PST)' || 123456789 /* required */
  },
  WebAclArn: 'STRING_VALUE' /* required */
};
wafv2.getSampledRequests(params, function(err, data) {
  if (err) console.log(err, err.stack); // an error occurred
  else     console.log(data);           // successful response
});

Parameters:

  • params (Object) (defaults to: {}) —
    • WebAclArn — (String)

      The Amazon resource name (ARN) of the WebACL for which you want a sample of requests.

    • RuleMetricName — (String)

      The metric name assigned to the Rule or RuleGroup for which you want a sample of requests.

    • Scope — (String)

      Specifies whether this is for an Amazon CloudFront distribution or for a regional application. A regional application can be an Application Load Balancer (ALB), an Amazon API Gateway REST API, or an AppSync GraphQL API.

      To work with CloudFront, you must also specify the Region US East (N. Virginia) as follows:

      • CLI - Specify the Region when you use the CloudFront scope: --scope=CLOUDFRONT --region=us-east-1.

      • API and SDKs - For all calls, use the Region endpoint us-east-1.

      Possible values include:
      • "CLOUDFRONT"
      • "REGIONAL"
    • TimeWindow — (map)

      The start date and time and the end date and time of the range for which you want GetSampledRequests to return a sample of requests. You must specify the times in Coordinated Universal Time (UTC) format. UTC format includes the special designator, Z. For example, "2016-09-27T14:50Z". You can specify any time range in the previous three hours. If you specify a start time that's earlier than three hours ago, WAF sets it to three hours ago.

      • StartTime — required — (Date)

        The beginning of the time range from which you want GetSampledRequests to return a sample of the requests that your Amazon Web Services resource received. You must specify the times in Coordinated Universal Time (UTC) format. UTC format includes the special designator, Z. For example, "2016-09-27T14:50Z". You can specify any time range in the previous three hours.

      • EndTime — required — (Date)

        The end of the time range from which you want GetSampledRequests to return a sample of the requests that your Amazon Web Services resource received. You must specify the times in Coordinated Universal Time (UTC) format. UTC format includes the special designator, Z. For example, "2016-09-27T14:50Z". You can specify any time range in the previous three hours.

    • MaxItems — (Integer)

      The number of requests that you want WAF to return from among the first 5,000 requests that your Amazon Web Services resource received during the time range. If your resource received fewer requests than the value of MaxItems, GetSampledRequests returns information about all of them.

Callback (callback):

  • function(err, data) { ... }

    Called when a response from the service is returned. If a callback is not supplied, you must call AWS.Request.send() on the returned request object to initiate the request.

    Context (this):

    • (AWS.Response) —

      the response object containing error, data properties, and the original request object.

    Parameters:

    • err (Error) —

      the error object returned from the request. Set to null if the request is successful.

    • data (Object) —

      the de-serialized data returned from the request. Set to null if a request error occurs. The data object has the following properties:

      • SampledRequests — (Array<map>)

        A complex type that contains detailed information about each of the requests in the sample.

        • Request — required — (map)

          A complex type that contains detailed information about the request.

          • ClientIP — (String)

            The IP address that the request originated from. If the web ACL is associated with a CloudFront distribution, this is the value of one of the following fields in CloudFront access logs:

            • c-ip, if the viewer did not use an HTTP proxy or a load balancer to send the request

            • x-forwarded-for, if the viewer did use an HTTP proxy or a load balancer to send the request

          • Country — (String)

            The two-letter country code for the country that the request originated from. For a current list of country codes, see the Wikipedia entry ISO 3166-1 alpha-2.

          • URI — (String)

            The URI path of the request, which identifies the resource, for example, /images/daily-ad.jpg.

          • Method — (String)

            The HTTP method specified in the sampled web request.

          • HTTPVersion — (String)

            The HTTP version specified in the sampled web request, for example, HTTP/1.1.

          • Headers — (Array<map>)

            A complex type that contains the name and value for each header in the sampled web request.

            • Name — (String)

              The name of the HTTP header.

            • Value — (String)

              The value of the HTTP header.

        • Weight — required — (Integer)

          A value that indicates how one result in the response relates proportionally to other results in the response. For example, a result that has a weight of 2 represents roughly twice as many web requests as a result that has a weight of 1.

        • Timestamp — (Date)

          The time at which WAF received the request from your Amazon Web Services resource, in Unix time format (in seconds).

        • Action — (String)

          The action for the Rule that the request matched: Allow, Block, or Count.

        • RuleNameWithinRuleGroup — (String)

          The name of the Rule that the request matched. For managed rule groups, the format for this name is <vendor name>#<managed rule group name>#<rule name>. For your own rule groups, the format for this name is <rule group name>#<rule name>. If the rule is not in a rule group, this field is absent.

        • RequestHeadersInserted — (Array<map>)

          Custom request headers inserted by WAF into the request, according to the custom request configuration for the matching rule action.

          • Name — (String)

            The name of the HTTP header.

          • Value — (String)

            The value of the HTTP header.

        • ResponseCodeSent — (Integer)

          The response code that was sent for the request.

        • Labels — (Array<map>)

          Labels applied to the web request by matching rules. WAF applies fully qualified labels to matching web requests. A fully qualified label is the concatenation of a label namespace and a rule label. The rule's rule group or web ACL defines the label namespace.

          For example, awswaf:111122223333:myRuleGroup:testRules:testNS1:testNS2:labelNameA or awswaf:managed:aws:managed-rule-set:header:encoding:utf8.

          • Name — required — (String)

            The label string.

        • CaptchaResponse — (map)

          The CAPTCHA response for the request.

          • ResponseCode — (Integer)

            The HTTP response code indicating the status of the CAPTCHA token in the web request. If the token is missing, invalid, or expired, this code is 405 Method Not Allowed.

          • SolveTimestamp — (Integer)

            The time that the CAPTCHA puzzle was solved for the supplied token.

          • FailureReason — (String)

            The reason for failure, populated when the evaluation of the token fails.

            Possible values include:
            • "TOKEN_MISSING"
            • "TOKEN_EXPIRED"
      • PopulationSize — (Integer)

        The total number of requests from which GetSampledRequests got a sample of MaxItems requests. If PopulationSize is less than MaxItems, the sample includes every request that your Amazon Web Services resource received during the specified time range.

      • TimeWindow — (map)

        Usually, TimeWindow is the time range that you specified in the GetSampledRequests request. However, if your Amazon Web Services resource received more than 5,000 requests during the time range that you specified in the request, GetSampledRequests returns the time range for the first 5,000 requests. Times are in Coordinated Universal Time (UTC) format.

        • StartTime — required — (Date)

          The beginning of the time range from which you want GetSampledRequests to return a sample of the requests that your Amazon Web Services resource received. You must specify the times in Coordinated Universal Time (UTC) format. UTC format includes the special designator, Z. For example, "2016-09-27T14:50Z". You can specify any time range in the previous three hours.

        • EndTime — required — (Date)

          The end of the time range from which you want GetSampledRequests to return a sample of the requests that your Amazon Web Services resource received. You must specify the times in Coordinated Universal Time (UTC) format. UTC format includes the special designator, Z. For example, "2016-09-27T14:50Z". You can specify any time range in the previous three hours.

Returns:

  • (AWS.Request) —

    a handle to the operation request for subsequent event callback registration.

getWebACL(params = {}, callback) ⇒ AWS.Request

Retrieves the specified WebACL.

Service Reference:

Examples:

Calling the getWebACL operation

var params = {
  Id: 'STRING_VALUE', /* required */
  Name: 'STRING_VALUE', /* required */
  Scope: CLOUDFRONT | REGIONAL /* required */
};
wafv2.getWebACL(params, function(err, data) {
  if (err) console.log(err, err.stack); // an error occurred
  else     console.log(data);           // successful response
});

Parameters:

  • params (Object) (defaults to: {}) —
    • Name — (String)

      The name of the web ACL. You cannot change the name of a web ACL after you create it.

    • Scope — (String)

      Specifies whether this is for an Amazon CloudFront distribution or for a regional application. A regional application can be an Application Load Balancer (ALB), an Amazon API Gateway REST API, or an AppSync GraphQL API.

      To work with CloudFront, you must also specify the Region US East (N. Virginia) as follows:

      • CLI - Specify the Region when you use the CloudFront scope: --scope=CLOUDFRONT --region=us-east-1.

      • API and SDKs - For all calls, use the Region endpoint us-east-1.

      Possible values include:
      • "CLOUDFRONT"
      • "REGIONAL"
    • Id — (String)

      The unique identifier for the web ACL. This ID is returned in the responses to create and list commands. You provide it to operations like update and delete.

Callback (callback):

  • function(err, data) { ... }

    Called when a response from the service is returned. If a callback is not supplied, you must call AWS.Request.send() on the returned request object to initiate the request.

    Context (this):

    • (AWS.Response) —

      the response object containing error, data properties, and the original request object.

    Parameters:

    • err (Error) —

      the error object returned from the request. Set to null if the request is successful.

    • data (Object) —

      the de-serialized data returned from the request. Set to null if a request error occurs. The data object has the following properties:

      • WebACL — (map)

        The web ACL specification. You can modify the settings in this web ACL and use it to update this web ACL or create a new one.

        • Name — required — (String)

          The name of the web ACL. You cannot change the name of a web ACL after you create it.

        • Id — required — (String)

          A unique identifier for the WebACL. This ID is returned in the responses to create and list commands. You use this ID to do things like get, update, and delete a WebACL.

        • ARN — required — (String)

          The Amazon Resource Name (ARN) of the web ACL that you want to associate with the resource.

        • DefaultAction — required — (map)

          The action to perform if none of the Rules contained in the WebACL match.

          • Block — (map)

            Specifies that WAF should block requests by default.

            • CustomResponse — (map)

              Defines a custom response for the web request.

              For information about customizing web requests and responses, see Customizing web requests and responses in WAF in the WAF Developer Guide.

              • ResponseCode — required — (Integer)

                The HTTP status code to return to the client.

                For a list of status codes that you can use in your custom reqponses, see Supported status codes for custom response in the WAF Developer Guide.

              • CustomResponseBodyKey — (String)

                References the response body that you want WAF to return to the web request client. You can define a custom response for a rule action or a default web ACL action that is set to block. To do this, you first define the response body key and value in the CustomResponseBodies setting for the WebACL or RuleGroup where you want to use it. Then, in the rule action or web ACL default action BlockAction setting, you reference the response body using this key.

              • ResponseHeaders — (Array<map>)

                The HTTP headers to use in the response. Duplicate header names are not allowed.

                For information about the limits on count and size for custom request and response settings, see WAF quotas in the WAF Developer Guide.

                • Name — required — (String)

                  The name of the custom header.

                  For custom request header insertion, when WAF inserts the header into the request, it prefixes this name x-amzn-waf-, to avoid confusion with the headers that are already in the request. For example, for the header name sample, WAF inserts the header x-amzn-waf-sample.

                • Value — required — (String)

                  The value of the custom header.

          • Allow — (map)

            Specifies that WAF should allow requests by default.

            • CustomRequestHandling — (map)

              Defines custom handling for the web request.

              For information about customizing web requests and responses, see Customizing web requests and responses in WAF in the WAF Developer Guide.

              • InsertHeaders — required — (Array<map>)

                The HTTP headers to insert into the request. Duplicate header names are not allowed.

                For information about the limits on count and size for custom request and response settings, see WAF quotas in the WAF Developer Guide.

                • Name — required — (String)

                  The name of the custom header.

                  For custom request header insertion, when WAF inserts the header into the request, it prefixes this name x-amzn-waf-, to avoid confusion with the headers that are already in the request. For example, for the header name sample, WAF inserts the header x-amzn-waf-sample.

                • Value — required — (String)

                  The value of the custom header.

        • Description — (String)

          A description of the web ACL that helps with identification.

        • Rules — (Array<map>)

          The Rule statements used to identify the web requests that you want to allow, block, or count. Each rule includes one top-level statement that WAF uses to identify matching web requests, and parameters that govern how WAF handles them.

          • Name — required — (String)

            The name of the rule. You can't change the name of a Rule after you create it.

          • Priority — required — (Integer)

            If you define more than one Rule in a WebACL, WAF evaluates each request against the Rules in order based on the value of Priority. WAF processes rules with lower priority first. The priorities don't need to be consecutive, but they must all be different.

          • Statement — required — (map)

            The WAF processing statement for the rule, for example ByteMatchStatement or SizeConstraintStatement.

            • ByteMatchStatement — (map)

              A rule statement that defines a string match search for WAF to apply to web requests. The byte match statement provides the bytes to search for, the location in requests that you want WAF to search, and other settings. The bytes to search for are typically a string that corresponds with ASCII characters. In the WAF console and the developer guide, this is refered to as a string match statement.

              • SearchString — required — (Buffer, Typed Array, Blob, String)

                A string value that you want WAF to search for. WAF searches only in the part of web requests that you designate for inspection in FieldToMatch. The maximum length of the value is 50 bytes.

                Valid values depend on the component that you specify for inspection in FieldToMatch:

                • Method: The HTTP method that you want WAF to search for. This indicates the type of operation specified in the request.

                • UriPath: The value that you want WAF to search for in the URI path, for example, /images/daily-ad.jpg.

                If SearchString includes alphabetic characters A-Z and a-z, note that the value is case sensitive.

                If you're using the WAF API

                Specify a base64-encoded version of the value. The maximum length of the value before you base64-encode it is 50 bytes.

                For example, suppose the value of Type is HEADER and the value of Data is User-Agent. If you want to search the User-Agent header for the value BadBot, you base64-encode BadBot using MIME base64-encoding and include the resulting value, QmFkQm90, in the value of SearchString.

                If you're using the CLI or one of the Amazon Web Services SDKs

                The value that you want WAF to search for. The SDK automatically base64 encodes the value.

              • FieldToMatch — required — (map)

                The part of a web request that you want WAF to inspect. For more information, see FieldToMatch.

                • SingleHeader — (map)

                  Inspect a single header. Provide the name of the header to inspect, for example, User-Agent or Referer. This setting isn't case sensitive.

                  Example JSON: "SingleHeader": { "Name": "haystack" }

                  • Name — required — (String)

                    The name of the query header to inspect.

                • SingleQueryArgument — (map)

                  Inspect a single query argument. Provide the name of the query argument to inspect, such as UserName or SalesRegion. The name can be up to 30 characters long and isn't case sensitive.

                  This is used only to indicate the web request component for WAF to inspect, in the FieldToMatch specification.

                  Example JSON: "SingleQueryArgument": { "Name": "myArgument" }

                  • Name — required — (String)

                    The name of the query argument to inspect.

                • AllQueryArguments — (map)

                  Inspect all query arguments.

                • UriPath — (map)

                  Inspect the request URI path. This is the part of a web request that identifies a resource, for example, /images/daily-ad.jpg.

                • QueryString — (map)

                  Inspect the query string. This is the part of a URL that appears after a ? character, if any.

                • Body — (map)

                  Inspect the request body as plain text. The request body immediately follows the request headers. This is the part of a request that contains any additional data that you want to send to your web server as the HTTP request body, such as data from a form.

                  Note that only the first 8 KB (8192 bytes) of the request body are forwarded to WAF for inspection by the underlying host service. If you don't need to inspect more than 8 KB, you can guarantee that you don't allow additional bytes in by combining a statement that inspects the body of the web request, such as ByteMatchStatement or RegexPatternSetReferenceStatement, with a SizeConstraintStatement that enforces an 8 KB size limit on the body of the request. WAF doesn't support inspecting the entire contents of web requests whose bodies exceed the 8 KB limit.

                • Method — (map)

                  Inspect the HTTP method. The method indicates the type of operation that the request is asking the origin to perform.

                • JsonBody — (map)

                  Inspect the request body as JSON. The request body immediately follows the request headers. This is the part of a request that contains any additional data that you want to send to your web server as the HTTP request body, such as data from a form.

                  Note that only the first 8 KB (8192 bytes) of the request body are forwarded to WAF for inspection by the underlying host service. If you don't need to inspect more than 8 KB, you can guarantee that you don't allow additional bytes in by combining a statement that inspects the body of the web request, such as ByteMatchStatement or RegexPatternSetReferenceStatement, with a SizeConstraintStatement that enforces an 8 KB size limit on the body of the request. WAF doesn't support inspecting the entire contents of web requests whose bodies exceed the 8 KB limit.

                  • MatchPattern — required — (map)

                    The patterns to look for in the JSON body. WAF inspects the results of these pattern matches against the rule inspection criteria.

                    • All — (map)

                      Match all of the elements. See also MatchScope in JsonBody.

                      You must specify either this setting or the IncludedPaths setting, but not both.

                    • IncludedPaths — (Array<String>)

                      Match only the specified include paths. See also MatchScope in JsonBody.

                      Provide the include paths using JSON Pointer syntax. For example, "IncludedPaths": ["/dogs/0/name", "/dogs/1/name"]. For information about this syntax, see the Internet Engineering Task Force (IETF) documentation JavaScript Object Notation (JSON) Pointer.

                      You must specify either this setting or the All setting, but not both.

                      Note: Don't use this option to include all paths. Instead, use the All setting.
                  • MatchScope — required — (String)

                    The parts of the JSON to match against using the MatchPattern. If you specify All, WAF matches against keys and values.

                    Possible values include:
                    • "ALL"
                    • "KEY"
                    • "VALUE"
                  • InvalidFallbackBehavior — (String)

                    What WAF should do if it fails to completely parse the JSON body. The options are the following:

                    • EVALUATE_AS_STRING - Inspect the body as plain text. WAF applies the text transformations and inspection criteria that you defined for the JSON inspection to the body text string.

                    • MATCH - Treat the web request as matching the rule statement. WAF applies the rule action to the request.

                    • NO_MATCH - Treat the web request as not matching the rule statement.

                    If you don't provide this setting, WAF parses and evaluates the content only up to the first parsing failure that it encounters.

                    WAF does its best to parse the entire JSON body, but might be forced to stop for reasons such as invalid characters, duplicate keys, truncation, and any content whose root node isn't an object or an array.

                    WAF parses the JSON in the following examples as two valid key, value pairs:

                    • Missing comma: {"key1":"value1""key2":"value2"}

                    • Missing colon: {"key1":"value1","key2""value2"}

                    • Extra colons: {"key1"::"value1","key2""value2"}

                    Possible values include:
                    • "MATCH"
                    • "NO_MATCH"
                    • "EVALUATE_AS_STRING"
              • TextTransformations — required — (Array<map>)

                Text transformations eliminate some of the unusual formatting that attackers use in web requests in an effort to bypass detection. If you specify one or more transformations in a rule statement, WAF performs all transformations on the content of the request component identified by FieldToMatch, starting from the lowest priority setting, before inspecting the content for a match.

                • Priority — required — (Integer)

                  Sets the relative processing order for multiple transformations that are defined for a rule statement. WAF processes all transformations, from lowest priority to highest, before inspecting the transformed content. The priorities don't need to be consecutive, but they must all be different.

                • Type — required — (String)

                  You can specify the following transformation types:

                  BASE64_DECODE - Decode a Base64-encoded string.

                  BASE64_DECODE_EXT - Decode a Base64-encoded string, but use a forgiving implementation that ignores characters that aren't valid.

                  CMD_LINE - Command-line transformations. These are helpful in reducing effectiveness of attackers who inject an operating system command-line command and use unusual formatting to disguise some or all of the command.

                  • Delete the following characters: \ " ' ^

                  • Delete spaces before the following characters: / (

                  • Replace the following characters with a space: , ;

                  • Replace multiple spaces with one space

                  • Convert uppercase letters (A-Z) to lowercase (a-z)

                  COMPRESS_WHITE_SPACE - Replace these characters with a space character (decimal 32):

                  • \f, formfeed, decimal 12

                  • \t, tab, decimal 9

                  • \n, newline, decimal 10

                  • \r, carriage return, decimal 13

                  • \v, vertical tab, decimal 11

                  • Non-breaking space, decimal 160

                  COMPRESS_WHITE_SPACE also replaces multiple spaces with one space.

                  CSS_DECODE - Decode characters that were encoded using CSS 2.x escape rules syndata.html#characters. This function uses up to two bytes in the decoding process, so it can help to uncover ASCII characters that were encoded using CSS encoding that wouldn’t typically be encoded. It's also useful in countering evasion, which is a combination of a backslash and non-hexadecimal characters. For example, ja\vascript for javascript.

                  ESCAPE_SEQ_DECODE - Decode the following ANSI C escape sequences: \a, \b, \f, \n, \r, \t, \v, \, \?, \', \", \xHH (hexadecimal), \0OOO (octal). Encodings that aren't valid remain in the output.

                  HEX_DECODE - Decode a string of hexadecimal characters into a binary.

                  HTML_ENTITY_DECODE - Replace HTML-encoded characters with unencoded characters. HTML_ENTITY_DECODE performs these operations:

                  • Replaces (ampersand)quot; with "

                  • Replaces (ampersand)nbsp; with a non-breaking space, decimal 160

                  • Replaces (ampersand)lt; with a "less than" symbol

                  • Replaces (ampersand)gt; with >

                  • Replaces characters that are represented in hexadecimal format, (ampersand)#xhhhh;, with the corresponding characters

                  • Replaces characters that are represented in decimal format, (ampersand)#nnnn;, with the corresponding characters

                  JS_DECODE - Decode JavaScript escape sequences. If a \ u HHHH code is in the full-width ASCII code range of FF01-FF5E, then the higher byte is used to detect and adjust the lower byte. If not, only the lower byte is used and the higher byte is zeroed, causing a possible loss of information.

                  LOWERCASE - Convert uppercase letters (A-Z) to lowercase (a-z).

                  MD5 - Calculate an MD5 hash from the data in the input. The computed hash is in a raw binary form.

                  NONE - Specify NONE if you don't want any text transformations.

                  NORMALIZE_PATH - Remove multiple slashes, directory self-references, and directory back-references that are not at the beginning of the input from an input string.

                  NORMALIZE_PATH_WIN - This is the same as NORMALIZE_PATH, but first converts backslash characters to forward slashes.

                  REMOVE_NULLS - Remove all NULL bytes from the input.

                  REPLACE_COMMENTS - Replace each occurrence of a C-style comment (/* ... */) with a single space. Multiple consecutive occurrences are not compressed. Unterminated comments are also replaced with a space (ASCII 0x20). However, a standalone termination of a comment (*/) is not acted upon.

                  REPLACE_NULLS - Replace NULL bytes in the input with space characters (ASCII 0x20).

                  SQL_HEX_DECODE - Decode SQL hex data. Example (0x414243) will be decoded to (ABC).

                  URL_DECODE - Decode a URL-encoded value.

                  URL_DECODE_UNI - Like URL_DECODE, but with support for Microsoft-specific %u encoding. If the code is in the full-width ASCII code range of FF01-FF5E, the higher byte is used to detect and adjust the lower byte. Otherwise, only the lower byte is used and the higher byte is zeroed.

                  UTF8_TO_UNICODE - Convert all UTF-8 character sequences to Unicode. This helps input normalization, and minimizing false-positives and false-negatives for non-English languages.

                  Possible values include:
                  • "NONE"
                  • "COMPRESS_WHITE_SPACE"
                  • "HTML_ENTITY_DECODE"
                  • "LOWERCASE"
                  • "CMD_LINE"
                  • "URL_DECODE"
                  • "BASE64_DECODE"
                  • "HEX_DECODE"
                  • "MD5"
                  • "REPLACE_COMMENTS"
                  • "ESCAPE_SEQ_DECODE"
                  • "SQL_HEX_DECODE"
                  • "CSS_DECODE"
                  • "JS_DECODE"
                  • "NORMALIZE_PATH"
                  • "NORMALIZE_PATH_WIN"
                  • "REMOVE_NULLS"
                  • "REPLACE_NULLS"
                  • "BASE64_DECODE_EXT"
                  • "URL_DECODE_UNI"
                  • "UTF8_TO_UNICODE"
              • PositionalConstraint — required — (String)

                The area within the portion of a web request that you want WAF to search for SearchString. Valid values include the following:

                CONTAINS

                The specified part of the web request must include the value of SearchString, but the location doesn't matter.

                CONTAINS_WORD

                The specified part of the web request must include the value of SearchString, and SearchString must contain only alphanumeric characters or underscore (A-Z, a-z, 0-9, or ). In addition, SearchString must be a word, which means that both of the following are true:

                • SearchString is at the beginning of the specified part of the web request or is preceded by a character other than an alphanumeric character or underscore (). Examples include the value of a header and ;BadBot.

                • SearchString is at the end of the specified part of the web request or is followed by a character other than an alphanumeric character or underscore (_), for example, BadBot; and -BadBot;.

                EXACTLY

                The value of the specified part of the web request must exactly match the value of SearchString.

                STARTS_WITH

                The value of SearchString must appear at the beginning of the specified part of the web request.

                ENDS_WITH

                The value of SearchString must appear at the end of the specified part of the web request.

                Possible values include:
                • "EXACTLY"
                • "STARTS_WITH"
                • "ENDS_WITH"
                • "CONTAINS"
                • "CONTAINS_WORD"
            • SqliMatchStatement — (map)

              Attackers sometimes insert malicious SQL code into web requests in an effort to extract data from your database. To allow or block web requests that appear to contain malicious SQL code, create one or more SQL injection match conditions. An SQL injection match condition identifies the part of web requests, such as the URI or the query string, that you want WAF to inspect. Later in the process, when you create a web ACL, you specify whether to allow or block requests that appear to contain malicious SQL code.

              • FieldToMatch — required — (map)

                The part of a web request that you want WAF to inspect. For more information, see FieldToMatch.

                • SingleHeader — (map)

                  Inspect a single header. Provide the name of the header to inspect, for example, User-Agent or Referer. This setting isn't case sensitive.

                  Example JSON: "SingleHeader": { "Name": "haystack" }

                  • Name — required — (String)

                    The name of the query header to inspect.

                • SingleQueryArgument — (map)

                  Inspect a single query argument. Provide the name of the query argument to inspect, such as UserName or SalesRegion. The name can be up to 30 characters long and isn't case sensitive.

                  This is used only to indicate the web request component for WAF to inspect, in the FieldToMatch specification.

                  Example JSON: "SingleQueryArgument": { "Name": "myArgument" }

                  • Name — required — (String)

                    The name of the query argument to inspect.

                • AllQueryArguments — (map)

                  Inspect all query arguments.

                • UriPath — (map)

                  Inspect the request URI path. This is the part of a web request that identifies a resource, for example, /images/daily-ad.jpg.

                • QueryString — (map)

                  Inspect the query string. This is the part of a URL that appears after a ? character, if any.

                • Body — (map)

                  Inspect the request body as plain text. The request body immediately follows the request headers. This is the part of a request that contains any additional data that you want to send to your web server as the HTTP request body, such as data from a form.

                  Note that only the first 8 KB (8192 bytes) of the request body are forwarded to WAF for inspection by the underlying host service. If you don't need to inspect more than 8 KB, you can guarantee that you don't allow additional bytes in by combining a statement that inspects the body of the web request, such as ByteMatchStatement or RegexPatternSetReferenceStatement, with a SizeConstraintStatement that enforces an 8 KB size limit on the body of the request. WAF doesn't support inspecting the entire contents of web requests whose bodies exceed the 8 KB limit.

                • Method — (map)

                  Inspect the HTTP method. The method indicates the type of operation that the request is asking the origin to perform.

                • JsonBody — (map)

                  Inspect the request body as JSON. The request body immediately follows the request headers. This is the part of a request that contains any additional data that you want to send to your web server as the HTTP request body, such as data from a form.

                  Note that only the first 8 KB (8192 bytes) of the request body are forwarded to WAF for inspection by the underlying host service. If you don't need to inspect more than 8 KB, you can guarantee that you don't allow additional bytes in by combining a statement that inspects the body of the web request, such as ByteMatchStatement or RegexPatternSetReferenceStatement, with a SizeConstraintStatement that enforces an 8 KB size limit on the body of the request. WAF doesn't support inspecting the entire contents of web requests whose bodies exceed the 8 KB limit.

                  • MatchPattern — required — (map)

                    The patterns to look for in the JSON body. WAF inspects the results of these pattern matches against the rule inspection criteria.

                    • All — (map)

                      Match all of the elements. See also MatchScope in JsonBody.

                      You must specify either this setting or the IncludedPaths setting, but not both.

                    • IncludedPaths — (Array<String>)

                      Match only the specified include paths. See also MatchScope in JsonBody.

                      Provide the include paths using JSON Pointer syntax. For example, "IncludedPaths": ["/dogs/0/name", "/dogs/1/name"]. For information about this syntax, see the Internet Engineering Task Force (IETF) documentation JavaScript Object Notation (JSON) Pointer.

                      You must specify either this setting or the All setting, but not both.

                      Note: Don't use this option to include all paths. Instead, use the All setting.
                  • MatchScope — required — (String)

                    The parts of the JSON to match against using the MatchPattern. If you specify All, WAF matches against keys and values.

                    Possible values include:
                    • "ALL"
                    • "KEY"
                    • "VALUE"
                  • InvalidFallbackBehavior — (String)

                    What WAF should do if it fails to completely parse the JSON body. The options are the following:

                    • EVALUATE_AS_STRING - Inspect the body as plain text. WAF applies the text transformations and inspection criteria that you defined for the JSON inspection to the body text string.

                    • MATCH - Treat the web request as matching the rule statement. WAF applies the rule action to the request.

                    • NO_MATCH - Treat the web request as not matching the rule statement.

                    If you don't provide this setting, WAF parses and evaluates the content only up to the first parsing failure that it encounters.

                    WAF does its best to parse the entire JSON body, but might be forced to stop for reasons such as invalid characters, duplicate keys, truncation, and any content whose root node isn't an object or an array.

                    WAF parses the JSON in the following examples as two valid key, value pairs:

                    • Missing comma: {"key1":"value1""key2":"value2"}

                    • Missing colon: {"key1":"value1","key2""value2"}

                    • Extra colons: {"key1"::"value1","key2""value2"}

                    Possible values include:
                    • "MATCH"
                    • "NO_MATCH"
                    • "EVALUATE_AS_STRING"
              • TextTransformations — required — (Array<map>)

                Text transformations eliminate some of the unusual formatting that attackers use in web requests in an effort to bypass detection. If you specify one or more transformations in a rule statement, WAF performs all transformations on the content of the request component identified by FieldToMatch, starting from the lowest priority setting, before inspecting the content for a match.

                • Priority — required — (Integer)

                  Sets the relative processing order for multiple transformations that are defined for a rule statement. WAF processes all transformations, from lowest priority to highest, before inspecting the transformed content. The priorities don't need to be consecutive, but they must all be different.

                • Type — required — (String)

                  You can specify the following transformation types:

                  BASE64_DECODE - Decode a Base64-encoded string.

                  BASE64_DECODE_EXT - Decode a Base64-encoded string, but use a forgiving implementation that ignores characters that aren't valid.

                  CMD_LINE - Command-line transformations. These are helpful in reducing effectiveness of attackers who inject an operating system command-line command and use unusual formatting to disguise some or all of the command.

                  • Delete the following characters: \ " ' ^

                  • Delete spaces before the following characters: / (

                  • Replace the following characters with a space: , ;

                  • Replace multiple spaces with one space

                  • Convert uppercase letters (A-Z) to lowercase (a-z)

                  COMPRESS_WHITE_SPACE - Replace these characters with a space character (decimal 32):

                  • \f, formfeed, decimal 12

                  • \t, tab, decimal 9

                  • \n, newline, decimal 10

                  • \r, carriage return, decimal 13

                  • \v, vertical tab, decimal 11

                  • Non-breaking space, decimal 160

                  COMPRESS_WHITE_SPACE also replaces multiple spaces with one space.

                  CSS_DECODE - Decode characters that were encoded using CSS 2.x escape rules syndata.html#characters. This function uses up to two bytes in the decoding process, so it can help to uncover ASCII characters that were encoded using CSS encoding that wouldn’t typically be encoded. It's also useful in countering evasion, which is a combination of a backslash and non-hexadecimal characters. For example, ja\vascript for javascript.

                  ESCAPE_SEQ_DECODE - Decode the following ANSI C escape sequences: \a, \b, \f, \n, \r, \t, \v, \, \?, \', \", \xHH (hexadecimal), \0OOO (octal). Encodings that aren't valid remain in the output.

                  HEX_DECODE - Decode a string of hexadecimal characters into a binary.

                  HTML_ENTITY_DECODE - Replace HTML-encoded characters with unencoded characters. HTML_ENTITY_DECODE performs these operations:

                  • Replaces (ampersand)quot; with "

                  • Replaces (ampersand)nbsp; with a non-breaking space, decimal 160

                  • Replaces (ampersand)lt; with a "less than" symbol

                  • Replaces (ampersand)gt; with >

                  • Replaces characters that are represented in hexadecimal format, (ampersand)#xhhhh;, with the corresponding characters

                  • Replaces characters that are represented in decimal format, (ampersand)#nnnn;, with the corresponding characters

                  JS_DECODE - Decode JavaScript escape sequences. If a \ u HHHH code is in the full-width ASCII code range of FF01-FF5E, then the higher byte is used to detect and adjust the lower byte. If not, only the lower byte is used and the higher byte is zeroed, causing a possible loss of information.

                  LOWERCASE - Convert uppercase letters (A-Z) to lowercase (a-z).

                  MD5 - Calculate an MD5 hash from the data in the input. The computed hash is in a raw binary form.

                  NONE - Specify NONE if you don't want any text transformations.

                  NORMALIZE_PATH - Remove multiple slashes, directory self-references, and directory back-references that are not at the beginning of the input from an input string.

                  NORMALIZE_PATH_WIN - This is the same as NORMALIZE_PATH, but first converts backslash characters to forward slashes.

                  REMOVE_NULLS - Remove all NULL bytes from the input.

                  REPLACE_COMMENTS - Replace each occurrence of a C-style comment (/* ... */) with a single space. Multiple consecutive occurrences are not compressed. Unterminated comments are also replaced with a space (ASCII 0x20). However, a standalone termination of a comment (*/) is not acted upon.

                  REPLACE_NULLS - Replace NULL bytes in the input with space characters (ASCII 0x20).

                  SQL_HEX_DECODE - Decode SQL hex data. Example (0x414243) will be decoded to (ABC).

                  URL_DECODE - Decode a URL-encoded value.

                  URL_DECODE_UNI - Like URL_DECODE, but with support for Microsoft-specific %u encoding. If the code is in the full-width ASCII code range of FF01-FF5E, the higher byte is used to detect and adjust the lower byte. Otherwise, only the lower byte is used and the higher byte is zeroed.

                  UTF8_TO_UNICODE - Convert all UTF-8 character sequences to Unicode. This helps input normalization, and minimizing false-positives and false-negatives for non-English languages.

                  Possible values include:
                  • "NONE"
                  • "COMPRESS_WHITE_SPACE"
                  • "HTML_ENTITY_DECODE"
                  • "LOWERCASE"
                  • "CMD_LINE"
                  • "URL_DECODE"
                  • "BASE64_DECODE"
                  • "HEX_DECODE"
                  • "MD5"
                  • "REPLACE_COMMENTS"
                  • "ESCAPE_SEQ_DECODE"
                  • "SQL_HEX_DECODE"
                  • "CSS_DECODE"
                  • "JS_DECODE"
                  • "NORMALIZE_PATH"
                  • "NORMALIZE_PATH_WIN"
                  • "REMOVE_NULLS"
                  • "REPLACE_NULLS"
                  • "BASE64_DECODE_EXT"
                  • "URL_DECODE_UNI"
                  • "UTF8_TO_UNICODE"
            • XssMatchStatement — (map)

              A rule statement that defines a cross-site scripting (XSS) match search for WAF to apply to web requests. XSS attacks are those where the attacker uses vulnerabilities in a benign website as a vehicle to inject malicious client-site scripts into other legitimate web browsers. The XSS match statement provides the location in requests that you want WAF to search and text transformations to use on the search area before WAF searches for character sequences that are likely to be malicious strings.

              • FieldToMatch — required — (map)

                The part of a web request that you want WAF to inspect. For more information, see FieldToMatch.

                • SingleHeader — (map)

                  Inspect a single header. Provide the name of the header to inspect, for example, User-Agent or Referer. This setting isn't case sensitive.

                  Example JSON: "SingleHeader": { "Name": "haystack" }

                  • Name — required — (String)

                    The name of the query header to inspect.

                • SingleQueryArgument — (map)

                  Inspect a single query argument. Provide the name of the query argument to inspect, such as UserName or SalesRegion. The name can be up to 30 characters long and isn't case sensitive.

                  This is used only to indicate the web request component for WAF to inspect, in the FieldToMatch specification.

                  Example JSON: "SingleQueryArgument": { "Name": "myArgument" }

                  • Name — required — (String)

                    The name of the query argument to inspect.

                • AllQueryArguments — (map)

                  Inspect all query arguments.

                • UriPath — (map)

                  Inspect the request URI path. This is the part of a web request that identifies a resource, for example, /images/daily-ad.jpg.

                • QueryString — (map)

                  Inspect the query string. This is the part of a URL that appears after a ? character, if any.

                • Body — (map)

                  Inspect the request body as plain text. The request body immediately follows the request headers. This is the part of a request that contains any additional data that you want to send to your web server as the HTTP request body, such as data from a form.

                  Note that only the first 8 KB (8192 bytes) of the request body are forwarded to WAF for inspection by the underlying host service. If you don't need to inspect more than 8 KB, you can guarantee that you don't allow additional bytes in by combining a statement that inspects the body of the web request, such as ByteMatchStatement or RegexPatternSetReferenceStatement, with a SizeConstraintStatement that enforces an 8 KB size limit on the body of the request. WAF doesn't support inspecting the entire contents of web requests whose bodies exceed the 8 KB limit.

                • Method — (map)

                  Inspect the HTTP method. The method indicates the type of operation that the request is asking the origin to perform.

                • JsonBody — (map)

                  Inspect the request body as JSON. The request body immediately follows the request headers. This is the part of a request that contains any additional data that you want to send to your web server as the HTTP request body, such as data from a form.

                  Note that only the first 8 KB (8192 bytes) of the request body are forwarded to WAF for inspection by the underlying host service. If you don't need to inspect more than 8 KB, you can guarantee that you don't allow additional bytes in by combining a statement that inspects the body of the web request, such as ByteMatchStatement or RegexPatternSetReferenceStatement, with a SizeConstraintStatement that enforces an 8 KB size limit on the body of the request. WAF doesn't support inspecting the entire contents of web requests whose bodies exceed the 8 KB limit.

                  • MatchPattern — required — (map)

                    The patterns to look for in the JSON body. WAF inspects the results of these pattern matches against the rule inspection criteria.

                    • All — (map)

                      Match all of the elements. See also MatchScope in JsonBody.

                      You must specify either this setting or the IncludedPaths setting, but not both.

                    • IncludedPaths — (Array<String>)

                      Match only the specified include paths. See also MatchScope in JsonBody.

                      Provide the include paths using JSON Pointer syntax. For example, "IncludedPaths": ["/dogs/0/name", "/dogs/1/name"]. For information about this syntax, see the Internet Engineering Task Force (IETF) documentation JavaScript Object Notation (JSON) Pointer.

                      You must specify either this setting or the All setting, but not both.

                      Note: Don't use this option to include all paths. Instead, use the All setting.
                  • MatchScope — required — (String)

                    The parts of the JSON to match against using the MatchPattern. If you specify All, WAF matches against keys and values.

                    Possible values include:
                    • "ALL"
                    • "KEY"
                    • "VALUE"
                  • InvalidFallbackBehavior — (String)

                    What WAF should do if it fails to completely parse the JSON body. The options are the following:

                    • EVALUATE_AS_STRING - Inspect the body as plain text. WAF applies the text transformations and inspection criteria that you defined for the JSON inspection to the body text string.

                    • MATCH - Treat the web request as matching the rule statement. WAF applies the rule action to the request.

                    • NO_MATCH - Treat the web request as not matching the rule statement.

                    If you don't provide this setting, WAF parses and evaluates the content only up to the first parsing failure that it encounters.

                    WAF does its best to parse the entire JSON body, but might be forced to stop for reasons such as invalid characters, duplicate keys, truncation, and any content whose root node isn't an object or an array.

                    WAF parses the JSON in the following examples as two valid key, value pairs:

                    • Missing comma: {"key1":"value1""key2":"value2"}

                    • Missing colon: {"key1":"value1","key2""value2"}

                    • Extra colons: {"key1"::"value1","key2""value2"}

                    Possible values include:
                    • "MATCH"
                    • "NO_MATCH"
                    • "EVALUATE_AS_STRING"
              • TextTransformations — required — (Array<map>)

                Text transformations eliminate some of the unusual formatting that attackers use in web requests in an effort to bypass detection. If you specify one or more transformations in a rule statement, WAF performs all transformations on the content of the request component identified by FieldToMatch, starting from the lowest priority setting, before inspecting the content for a match.

                • Priority — required — (Integer)

                  Sets the relative processing order for multiple transformations that are defined for a rule statement. WAF processes all transformations, from lowest priority to highest, before inspecting the transformed content. The priorities don't need to be consecutive, but they must all be different.

                • Type — required — (String)

                  You can specify the following transformation types:

                  BASE64_DECODE - Decode a Base64-encoded string.

                  BASE64_DECODE_EXT - Decode a Base64-encoded string, but use a forgiving implementation that ignores characters that aren't valid.

                  CMD_LINE - Command-line transformations. These are helpful in reducing effectiveness of attackers who inject an operating system command-line command and use unusual formatting to disguise some or all of the command.

                  • Delete the following characters: \ " ' ^

                  • Delete spaces before the following characters: / (

                  • Replace the following characters with a space: , ;

                  • Replace multiple spaces with one space

                  • Convert uppercase letters (A-Z) to lowercase (a-z)

                  COMPRESS_WHITE_SPACE - Replace these characters with a space character (decimal 32):

                  • \f, formfeed, decimal 12

                  • \t, tab, decimal 9

                  • \n, newline, decimal 10

                  • \r, carriage return, decimal 13

                  • \v, vertical tab, decimal 11

                  • Non-breaking space, decimal 160

                  COMPRESS_WHITE_SPACE also replaces multiple spaces with one space.

                  CSS_DECODE - Decode characters that were encoded using CSS 2.x escape rules syndata.html#characters. This function uses up to two bytes in the decoding process, so it can help to uncover ASCII characters that were encoded using CSS encoding that wouldn’t typically be encoded. It's also useful in countering evasion, which is a combination of a backslash and non-hexadecimal characters. For example, ja\vascript for javascript.

                  ESCAPE_SEQ_DECODE - Decode the following ANSI C escape sequences: \a, \b, \f, \n, \r, \t, \v, \, \?, \', \", \xHH (hexadecimal), \0OOO (octal). Encodings that aren't valid remain in the output.

                  HEX_DECODE - Decode a string of hexadecimal characters into a binary.

                  HTML_ENTITY_DECODE - Replace HTML-encoded characters with unencoded characters. HTML_ENTITY_DECODE performs these operations:

                  • Replaces (ampersand)quot; with "

                  • Replaces (ampersand)nbsp; with a non-breaking space, decimal 160

                  • Replaces (ampersand)lt; with a "less than" symbol

                  • Replaces (ampersand)gt; with >

                  • Replaces characters that are represented in hexadecimal format, (ampersand)#xhhhh;, with the corresponding characters

                  • Replaces characters that are represented in decimal format, (ampersand)#nnnn;, with the corresponding characters

                  JS_DECODE - Decode JavaScript escape sequences. If a \ u HHHH code is in the full-width ASCII code range of FF01-FF5E, then the higher byte is used to detect and adjust the lower byte. If not, only the lower byte is used and the higher byte is zeroed, causing a possible loss of information.

                  LOWERCASE - Convert uppercase letters (A-Z) to lowercase (a-z).

                  MD5 - Calculate an MD5 hash from the data in the input. The computed hash is in a raw binary form.

                  NONE - Specify NONE if you don't want any text transformations.

                  NORMALIZE_PATH - Remove multiple slashes, directory self-references, and directory back-references that are not at the beginning of the input from an input string.

                  NORMALIZE_PATH_WIN - This is the same as NORMALIZE_PATH, but first converts backslash characters to forward slashes.

                  REMOVE_NULLS - Remove all NULL bytes from the input.

                  REPLACE_COMMENTS - Replace each occurrence of a C-style comment (/* ... */) with a single space. Multiple consecutive occurrences are not compressed. Unterminated comments are also replaced with a space (ASCII 0x20). However, a standalone termination of a comment (*/) is not acted upon.

                  REPLACE_NULLS - Replace NULL bytes in the input with space characters (ASCII 0x20).

                  SQL_HEX_DECODE - Decode SQL hex data. Example (0x414243) will be decoded to (ABC).

                  URL_DECODE - Decode a URL-encoded value.

                  URL_DECODE_UNI - Like URL_DECODE, but with support for Microsoft-specific %u encoding. If the code is in the full-width ASCII code range of FF01-FF5E, the higher byte is used to detect and adjust the lower byte. Otherwise, only the lower byte is used and the higher byte is zeroed.

                  UTF8_TO_UNICODE - Convert all UTF-8 character sequences to Unicode. This helps input normalization, and minimizing false-positives and false-negatives for non-English languages.

                  Possible values include:
                  • "NONE"
                  • "COMPRESS_WHITE_SPACE"
                  • "HTML_ENTITY_DECODE"
                  • "LOWERCASE"
                  • "CMD_LINE"
                  • "URL_DECODE"
                  • "BASE64_DECODE"
                  • "HEX_DECODE"
                  • "MD5"
                  • "REPLACE_COMMENTS"
                  • "ESCAPE_SEQ_DECODE"
                  • "SQL_HEX_DECODE"
                  • "CSS_DECODE"
                  • "JS_DECODE"
                  • "NORMALIZE_PATH"
                  • "NORMALIZE_PATH_WIN"
                  • "REMOVE_NULLS"
                  • "REPLACE_NULLS"
                  • "BASE64_DECODE_EXT"
                  • "URL_DECODE_UNI"
                  • "UTF8_TO_UNICODE"
            • SizeConstraintStatement — (map)

              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 first 8192 bytes (8 KB). If the request body for your web requests never exceeds 8192 bytes, you can create a size constraint condition and block requests that have a request body greater than 8192 bytes.

              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.

              • FieldToMatch — required — (map)

                The part of a web request that you want WAF to inspect. For more information, see FieldToMatch.

                • SingleHeader — (map)

                  Inspect a single header. Provide the name of the header to inspect, for example, User-Agent or Referer. This setting isn't case sensitive.

                  Example JSON: "SingleHeader": { "Name": "haystack" }

                  • Name — required — (String)

                    The name of the query header to inspect.

                • SingleQueryArgument — (map)

                  Inspect a single query argument. Provide the name of the query argument to inspect, such as UserName or SalesRegion. The name can be up to 30 characters long and isn't case sensitive.

                  This is used only to indicate the web request component for WAF to inspect, in the FieldToMatch specification.

                  Example JSON: "SingleQueryArgument": { "Name": "myArgument" }

                  • Name — required — (String)

                    The name of the query argument to inspect.

                • AllQueryArguments — (map)

                  Inspect all query arguments.

                • UriPath — (map)

                  Inspect the request URI path. This is the part of a web request that identifies a resource, for example, /images/daily-ad.jpg.

                • QueryString — (map)

                  Inspect the query string. This is the part of a URL that appears after a ? character, if any.

                • Body — (map)

                  Inspect the request body as plain text. The request body immediately follows the request headers. This is the part of a request that contains any additional data that you want to send to your web server as the HTTP request body, such as data from a form.

                  Note that only the first 8 KB (8192 bytes) of the request body are forwarded to WAF for inspection by the underlying host service. If you don't need to inspect more than 8 KB, you can guarantee that you don't allow additional bytes in by combining a statement that inspects the body of the web request, such as ByteMatchStatement or RegexPatternSetReferenceStatement, with a SizeConstraintStatement that enforces an 8 KB size limit on the body of the request. WAF doesn't support inspecting the entire contents of web requests whose bodies exceed the 8 KB limit.

                • Method — (map)

                  Inspect the HTTP method. The method indicates the type of operation that the request is asking the origin to perform.

                • JsonBody — (map)

                  Inspect the request body as JSON. The request body immediately follows the request headers. This is the part of a request that contains any additional data that you want to send to your web server as the HTTP request body, such as data from a form.

                  Note that only the first 8 KB (8192 bytes) of the request body are forwarded to WAF for inspection by the underlying host service. If you don't need to inspect more than 8 KB, you can guarantee that you don't allow additional bytes in by combining a statement that inspects the body of the web request, such as ByteMatchStatement or RegexPatternSetReferenceStatement, with a SizeConstraintStatement that enforces an 8 KB size limit on the body of the request. WAF doesn't support inspecting the entire contents of web requests whose bodies exceed the 8 KB limit.

                  • MatchPattern — required — (map)

                    The patterns to look for in the JSON body. WAF inspects the results of these pattern matches against the rule inspection criteria.

                    • All — (map)

                      Match all of the elements. See also MatchScope in JsonBody.

                      You must specify either this setting or the IncludedPaths setting, but not both.

                    • IncludedPaths — (Array<String>)

                      Match only the specified include paths. See also MatchScope in JsonBody.

                      Provide the include paths using JSON Pointer syntax. For example, "IncludedPaths": ["/dogs/0/name", "/dogs/1/name"]. For information about this syntax, see the Internet Engineering Task Force (IETF) documentation JavaScript Object Notation (JSON) Pointer.

                      You must specify either this setting or the All setting, but not both.

                      Note: Don't use this option to include all paths. Instead, use the All setting.
                  • MatchScope — required — (String)

                    The parts of the JSON to match against using the MatchPattern. If you specify All, WAF matches against keys and values.

                    Possible values include:
                    • "ALL"
                    • "KEY"
                    • "VALUE"
                  • InvalidFallbackBehavior — (String)

                    What WAF should do if it fails to completely parse the JSON body. The options are the following:

                    • EVALUATE_AS_STRING - Inspect the body as plain text. WAF applies the text transformations and inspection criteria that you defined for the JSON inspection to the body text string.

                    • MATCH - Treat the web request as matching the rule statement. WAF applies the rule action to the request.

                    • NO_MATCH - Treat the web request as not matching the rule statement.

                    If you don't provide this setting, WAF parses and evaluates the content only up to the first parsing failure that it encounters.

                    WAF does its best to parse the entire JSON body, but might be forced to stop for reasons such as invalid characters, duplicate keys, truncation, and any content whose root node isn't an object or an array.

                    WAF parses the JSON in the following examples as two valid key, value pairs:

                    • Missing comma: {"key1":"value1""key2":"value2"}

                    • Missing colon: {"key1":"value1","key2""value2"}

                    • Extra colons: {"key1"::"value1","key2""value2"}

                    Possible values include:
                    • "MATCH"
                    • "NO_MATCH"
                    • "EVALUATE_AS_STRING"
              • ComparisonOperator — required — (String)

                The operator to use to compare the request part to the size setting.

                Possible values include:
                • "EQ"
                • "NE"
                • "LE"
                • "LT"
                • "GE"
                • "GT"
              • Size — required — (Integer)

                The size, in byte, to compare to the request part, after any transformations.

              • TextTransformations — required — (Array<map>)

                Text transformations eliminate some of the unusual formatting that attackers use in web requests in an effort to bypass detection. If you specify one or more transformations in a rule statement, WAF performs all transformations on the content of the request component identified by FieldToMatch, starting from the lowest priority setting, before inspecting the content for a match.

                • Priority — required — (Integer)

                  Sets the relative processing order for multiple transformations that are defined for a rule statement. WAF processes all transformations, from lowest priority to highest, before inspecting the transformed content. The priorities don't need to be consecutive, but they must all be different.

                • Type — required — (String)

                  You can specify the following transformation types:

                  BASE64_DECODE - Decode a Base64-encoded string.

                  BASE64_DECODE_EXT - Decode a Base64-encoded string, but use a forgiving implementation that ignores characters that aren't valid.

                  CMD_LINE - Command-line transformations. These are helpful in reducing effectiveness of attackers who inject an operating system command-line command and use unusual formatting to disguise some or all of the command.

                  • Delete the following characters: \ " ' ^

                  • Delete spaces before the following characters: / (

                  • Replace the following characters with a space: , ;

                  • Replace multiple spaces with one space

                  • Convert uppercase letters (A-Z) to lowercase (a-z)

                  COMPRESS_WHITE_SPACE - Replace these characters with a space character (decimal 32):

                  • \f, formfeed, decimal 12

                  • \t, tab, decimal 9

                  • \n, newline, decimal 10

                  • \r, carriage return, decimal 13

                  • \v, vertical tab, decimal 11

                  • Non-breaking space, decimal 160

                  COMPRESS_WHITE_SPACE also replaces multiple spaces with one space.

                  CSS_DECODE - Decode characters that were encoded using CSS 2.x escape rules syndata.html#characters. This function uses up to two bytes in the decoding process, so it can help to uncover ASCII characters that were encoded using CSS encoding that wouldn’t typically be encoded. It's also useful in countering evasion, which is a combination of a backslash and non-hexadecimal characters. For example, ja\vascript for javascript.

                  ESCAPE_SEQ_DECODE - Decode the following ANSI C escape sequences: \a, \b, \f, \n, \r, \t, \v, \, \?, \', \", \xHH (hexadecimal), \0OOO (octal). Encodings that aren't valid remain in the output.

                  HEX_DECODE - Decode a string of hexadecimal characters into a binary.

                  HTML_ENTITY_DECODE - Replace HTML-encoded characters with unencoded characters. HTML_ENTITY_DECODE performs these operations:

                  • Replaces (ampersand)quot; with "

                  • Replaces (ampersand)nbsp; with a non-breaking space, decimal 160

                  • Replaces (ampersand)lt; with a "less than" symbol

                  • Replaces (ampersand)gt; with >

                  • Replaces characters that are represented in hexadecimal format, (ampersand)#xhhhh;, with the corresponding characters

                  • Replaces characters that are represented in decimal format, (ampersand)#nnnn;, with the corresponding characters

                  JS_DECODE - Decode JavaScript escape sequences. If a \ u HHHH code is in the full-width ASCII code range of FF01-FF5E, then the higher byte is used to detect and adjust the lower byte. If not, only the lower byte is used and the higher byte is zeroed, causing a possible loss of information.

                  LOWERCASE - Convert uppercase letters (A-Z) to lowercase (a-z).

                  MD5 - Calculate an MD5 hash from the data in the input. The computed hash is in a raw binary form.

                  NONE - Specify NONE if you don't want any text transformations.

                  NORMALIZE_PATH - Remove multiple slashes, directory self-references, and directory back-references that are not at the beginning of the input from an input string.

                  NORMALIZE_PATH_WIN - This is the same as NORMALIZE_PATH, but first converts backslash characters to forward slashes.

                  REMOVE_NULLS - Remove all NULL bytes from the input.

                  REPLACE_COMMENTS - Replace each occurrence of a C-style comment (/* ... */) with a single space. Multiple consecutive occurrences are not compressed. Unterminated comments are also replaced with a space (ASCII 0x20). However, a standalone termination of a comment (*/) is not acted upon.

                  REPLACE_NULLS - Replace NULL bytes in the input with space characters (ASCII 0x20).

                  SQL_HEX_DECODE - Decode SQL hex data. Example (0x414243) will be decoded to (ABC).

                  URL_DECODE - Decode a URL-encoded value.

                  URL_DECODE_UNI - Like URL_DECODE, but with support for Microsoft-specific %u encoding. If the code is in the full-width ASCII code range of FF01-FF5E, the higher byte is used to detect and adjust the lower byte. Otherwise, only the lower byte is used and the higher byte is zeroed.

                  UTF8_TO_UNICODE - Convert all UTF-8 character sequences to Unicode. This helps input normalization, and minimizing false-positives and false-negatives for non-English languages.

                  Possible values include:
                  • "NONE"
                  • "COMPRESS_WHITE_SPACE"
                  • "HTML_ENTITY_DECODE"
                  • "LOWERCASE"
                  • "CMD_LINE"
                  • "URL_DECODE"
                  • "BASE64_DECODE"
                  • "HEX_DECODE"
                  • "MD5"
                  • "REPLACE_COMMENTS"
                  • "ESCAPE_SEQ_DECODE"
                  • "SQL_HEX_DECODE"
                  • "CSS_DECODE"
                  • "JS_DECODE"
                  • "NORMALIZE_PATH"
                  • "NORMALIZE_PATH_WIN"
                  • "REMOVE_NULLS"
                  • "REPLACE_NULLS"
                  • "BASE64_DECODE_EXT"
                  • "URL_DECODE_UNI"
                  • "UTF8_TO_UNICODE"
            • GeoMatchStatement — (map)

              A rule statement used to identify web requests based on country of origin.

              • CountryCodes — (Array<String>)

                An array of two-character country codes, for example, [ "US", "CN" ], from the alpha-2 country ISO codes of the ISO 3166 international standard.

              • ForwardedIPConfig — (map)

                The configuration for inspecting IP addresses in an HTTP header that you specify, instead of using the IP address that's reported by the web request origin. Commonly, this is the X-Forwarded-For (XFF) header, but you can specify any header name.

                Note: If the specified header isn't present in the request, WAF doesn't apply the rule to the web request at all.
                • HeaderName — required — (String)

                  The name of the HTTP header to use for the IP address. For example, to use the X-Forwarded-For (XFF) header, set this to X-Forwarded-For.

                  Note: If the specified header isn't present in the request, WAF doesn't apply the rule to the web request at all.
                • FallbackBehavior — required — (String)

                  The match status to assign to the web request if the request doesn't have a valid IP address in the specified position.

                  Note: If the specified header isn't present in the request, WAF doesn't apply the rule to the web request at all.

                  You can specify the following fallback behaviors:

                  • MATCH - Treat the web request as matching the rule statement. WAF applies the rule action to the request.

                  • NO_MATCH - Treat the web request as not matching the rule statement.

                  Possible values include:
                  • "MATCH"
                  • "NO_MATCH"
            • RuleGroupReferenceStatement — (map)

              A rule statement used to run the rules that are defined in a RuleGroup. To use this, create a rule group with your rules, then provide the ARN of the rule group in this statement.

              You cannot nest a RuleGroupReferenceStatement, for example for use inside a NotStatement or OrStatement. You can only use a rule group reference statement at the top level inside a web ACL.

              • ARN — required — (String)

                The Amazon Resource Name (ARN) of the entity.

              • ExcludedRules — (Array<map>)

                The rules in the referenced rule group whose actions are set to Count. When you exclude a rule, WAF evaluates it exactly as it would if the rule action setting were Count. This is a useful option for testing the rules in a rule group without modifying how they handle your web traffic.

                • Name — required — (String)

                  The name of the rule whose action you want to override to Count.

            • IPSetReferenceStatement — (map)

              A rule statement used to detect web requests coming from particular IP addresses or address ranges. To use this, create an IPSet that specifies the addresses you want to detect, then use the ARN of that set in this statement. To create an IP set, see CreateIPSet.

              Each IP set rule statement references an IP set. You create and maintain the set independent of your rules. This allows you to use the single set in multiple rules. When you update the referenced set, WAF automatically updates all rules that reference it.

              • ARN — required — (String)

                The Amazon Resource Name (ARN) of the IPSet that this statement references.

              • IPSetForwardedIPConfig — (map)

                The configuration for inspecting IP addresses in an HTTP header that you specify, instead of using the IP address that's reported by the web request origin. Commonly, this is the X-Forwarded-For (XFF) header, but you can specify any header name.

                Note: If the specified header isn't present in the request, WAF doesn't apply the rule to the web request at all.
                • HeaderName — required — (String)

                  The name of the HTTP header to use for the IP address. For example, to use the X-Forwarded-For (XFF) header, set this to X-Forwarded-For.

                  Note: If the specified header isn't present in the request, WAF doesn't apply the rule to the web request at all.
                • FallbackBehavior — required — (String)

                  The match status to assign to the web request if the request doesn't have a valid IP address in the specified position.

                  Note: If the specified header isn't present in the request, WAF doesn't apply the rule to the web request at all.

                  You can specify the following fallback behaviors:

                  • MATCH - Treat the web request as matching the rule statement. WAF applies the rule action to the request.

                  • NO_MATCH - Treat the web request as not matching the rule statement.

                  Possible values include:
                  • "MATCH"
                  • "NO_MATCH"
                • Position — required — (String)

                  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:

                  • FIRST - Inspect the first IP address in the list of IP addresses in the header. This is usually the client's original IP.

                  • LAST - Inspect the last IP address in the list of IP addresses in the header.

                  • ANY - Inspect all IP addresses in the header for a match. If the header contains more than 10 IP addresses, WAF inspects the last 10.

                  Possible values include:
                  • "FIRST"
                  • "LAST"
                  • "ANY"
            • RegexPatternSetReferenceStatement — (map)

              A rule statement used to search web request components for matches with regular expressions. To use this, create a RegexPatternSet that specifies the expressions that you want to detect, then use the ARN of that set in this statement. A web request matches the pattern set rule statement if the request component matches any of the patterns in the set. To create a regex pattern set, see CreateRegexPatternSet.

              Each regex pattern set rule statement references a regex pattern set. You create and maintain the set independent of your rules. This allows you to use the single set in multiple rules. When you update the referenced set, WAF automatically updates all rules that reference it.

              • ARN — required — (String)

                The Amazon Resource Name (ARN) of the RegexPatternSet that this statement references.

              • FieldToMatch — required — (map)

                The part of a web request that you want WAF to inspect. For more information, see FieldToMatch.

                • SingleHeader — (map)

                  Inspect a single header. Provide the name of the header to inspect, for example, User-Agent or Referer. This setting isn't case sensitive.

                  Example JSON: "SingleHeader": { "Name": "haystack" }

                  • Name — required — (String)

                    The name of the query header to inspect.

                • SingleQueryArgument — (map)

                  Inspect a single query argument. Provide the name of the query argument to inspect, such as UserName or SalesRegion. The name can be up to 30 characters long and isn't case sensitive.

                  This is used only to indicate the web request component for WAF to inspect, in the FieldToMatch specification.

                  Example JSON: "SingleQueryArgument": { "Name": "myArgument" }

                  • Name — required — (String)

                    The name of the query argument to inspect.

                • AllQueryArguments — (map)

                  Inspect all query arguments.

                • UriPath — (map)

                  Inspect the request URI path. This is the part of a web request that identifies a resource, for example, /images/daily-ad.jpg.

                • QueryString — (map)

                  Inspect the query string. This is the part of a URL that appears after a ? character, if any.

                • Body — (map)

                  Inspect the request body as plain text. The request body immediately follows the request headers. This is the part of a request that contains any additional data that you want to send to your web server as the HTTP request body, such as data from a form.

                  Note that only the first 8 KB (8192 bytes) of the request body are forwarded to WAF for inspection by the underlying host service. If you don't need to inspect more than 8 KB, you can guarantee that you don't allow additional bytes in by combining a statement that inspects the body of the web request, such as ByteMatchStatement or RegexPatternSetReferenceStatement, with a SizeConstraintStatement that enforces an 8 KB size limit on the body of the request. WAF doesn't support inspecting the entire contents of web requests whose bodies exceed the 8 KB limit.

                • Method — (map)

                  Inspect the HTTP method. The method indicates the type of operation that the request is asking the origin to perform.

                • JsonBody — (map)

                  Inspect the request body as JSON. The request body immediately follows the request headers. This is the part of a request that contains any additional data that you want to send to your web server as the HTTP request body, such as data from a form.

                  Note that only the first 8 KB (8192 bytes) of the request body are forwarded to WAF for inspection by the underlying host service. If you don't need to inspect more than 8 KB, you can guarantee that you don't allow additional bytes in by combining a statement that inspects the body of the web request, such as ByteMatchStatement or RegexPatternSetReferenceStatement, with a SizeConstraintStatement that enforces an 8 KB size limit on the body of the request. WAF doesn't support inspecting the entire contents of web requests whose bodies exceed the 8 KB limit.

                  • MatchPattern — required — (map)

                    The patterns to look for in the JSON body. WAF inspects the results of these pattern matches against the rule inspection criteria.

                    • All — (map)

                      Match all of the elements. See also MatchScope in JsonBody.

                      You must specify either this setting or the IncludedPaths setting, but not both.

                    • IncludedPaths — (Array<String>)

                      Match only the specified include paths. See also MatchScope in JsonBody.

                      Provide the include paths using JSON Pointer syntax. For example, "IncludedPaths": ["/dogs/0/name", "/dogs/1/name"]. For information about this syntax, see the Internet Engineering Task Force (IETF) documentation JavaScript Object Notation (JSON) Pointer.

                      You must specify either this setting or the All setting, but not both.

                      Note: Don't use this option to include all paths. Instead, use the All setting.
                  • MatchScope — required — (String)

                    The parts of the JSON to match against using the MatchPattern. If you specify All, WAF matches against keys and values.

                    Possible values include:
                    • "ALL"
                    • "KEY"
                    • "VALUE"
                  • InvalidFallbackBehavior — (String)

                    What WAF should do if it fails to completely parse the JSON body. The options are the following:

                    • EVALUATE_AS_STRING - Inspect the body as plain text. WAF applies the text transformations and inspection criteria that you defined for the JSON inspection to the body text string.

                    • MATCH - Treat the web request as matching the rule statement. WAF applies the rule action to the request.

                    • NO_MATCH - Treat the web request as not matching the rule statement.

                    If you don't provide this setting, WAF parses and evaluates the content only up to the first parsing failure that it encounters.

                    WAF does its best to parse the entire JSON body, but might be forced to stop for reasons such as invalid characters, duplicate keys, truncation, and any content whose root node isn't an object or an array.

                    WAF parses the JSON in the following examples as two valid key, value pairs:

                    • Missing comma: {"key1":"value1""key2":"value2"}

                    • Missing colon: {"key1":"value1","key2""value2"}

                    • Extra colons: {"key1"::"value1","key2""value2"}

                    Possible values include:
                    • "MATCH"
                    • "NO_MATCH"
                    • "EVALUATE_AS_STRING"
              • TextTransformations — required — (Array<map>)

                Text transformations eliminate some of the unusual formatting that attackers use in web requests in an effort to bypass detection. If you specify one or more transformations in a rule statement, WAF performs all transformations on the content of the request component identified by FieldToMatch, starting from the lowest priority setting, before inspecting the content for a match.

                • Priority — required — (Integer)

                  Sets the relative processing order for multiple transformations that are defined for a rule statement. WAF processes all transformations, from lowest priority to highest, before inspecting the transformed content. The priorities don't need to be consecutive, but they must all be different.

                • Type — required — (String)

                  You can specify the following transformation types:

                  BASE64_DECODE - Decode a Base64-encoded string.

                  BASE64_DECODE_EXT - Decode a Base64-encoded string, but use a forgiving implementation that ignores characters that aren't valid.

                  CMD_LINE - Command-line transformations. These are helpful in reducing effectiveness of attackers who inject an operating system command-line command and use unusual formatting to disguise some or all of the command.

                  • Delete the following characters: \ " ' ^

                  • Delete spaces before the following characters: / (

                  • Replace the following characters with a space: , ;

                  • Replace multiple spaces with one space

                  • Convert uppercase letters (A-Z) to lowercase (a-z)

                  COMPRESS_WHITE_SPACE - Replace these characters with a space character (decimal 32):

                  • \f, formfeed, decimal 12

                  • \t, tab, decimal 9

                  • \n, newline, decimal 10

                  • \r, carriage return, decimal 13

                  • \v, vertical tab, decimal 11

                  • Non-breaking space, decimal 160

                  COMPRESS_WHITE_SPACE also replaces multiple spaces with one space.

                  CSS_DECODE - Decode characters that were encoded using CSS 2.x escape rules syndata.html#characters. This function uses up to two bytes in the decoding process, so it can help to uncover ASCII characters that were encoded using CSS encoding that wouldn’t typically be encoded. It's also useful in countering evasion, which is a combination of a backslash and non-hexadecimal characters. For example, ja\vascript for javascript.

                  ESCAPE_SEQ_DECODE - Decode the following ANSI C escape sequences: \a, \b, \f, \n, \r, \t, \v, \, \?, \', \", \xHH (hexadecimal), \0OOO (octal). Encodings that aren't valid remain in the output.

                  HEX_DECODE - Decode a string of hexadecimal characters into a binary.

                  HTML_ENTITY_DECODE - Replace HTML-encoded characters with unencoded characters. HTML_ENTITY_DECODE performs these operations:

                  • Replaces (ampersand)quot; with "

                  • Replaces (ampersand)nbsp; with a non-breaking space, decimal 160

                  • Replaces (ampersand)lt; with a "less than" symbol

                  • Replaces (ampersand)gt; with >

                  • Replaces characters that are represented in hexadecimal format, (ampersand)#xhhhh;, with the corresponding characters

                  • Replaces characters that are represented in decimal format, (ampersand)#nnnn;, with the corresponding characters

                  JS_DECODE - Decode JavaScript escape sequences. If a \ u HHHH code is in the full-width ASCII code range of FF01-FF5E, then the higher byte is used to detect and adjust the lower byte. If not, only the lower byte is used and the higher byte is zeroed, causing a possible loss of information.

                  LOWERCASE - Convert uppercase letters (A-Z) to lowercase (a-z).

                  MD5 - Calculate an MD5 hash from the data in the input. The computed hash is in a raw binary form.

                  NONE - Specify NONE if you don't want any text transformations.

                  NORMALIZE_PATH - Remove multiple slashes, directory self-references, and directory back-references that are not at the beginning of the input from an input string.

                  NORMALIZE_PATH_WIN - This is the same as NORMALIZE_PATH, but first converts backslash characters to forward slashes.

                  REMOVE_NULLS - Remove all NULL bytes from the input.

                  REPLACE_COMMENTS - Replace each occurrence of a C-style comment (/* ... */) with a single space. Multiple consecutive occurrences are not compressed. Unterminated comments are also replaced with a space (ASCII 0x20). However, a standalone termination of a comment (*/) is not acted upon.

                  REPLACE_NULLS - Replace NULL bytes in the input with space characters (ASCII 0x20).

                  SQL_HEX_DECODE - Decode SQL hex data. Example (0x414243) will be decoded to (ABC).

                  URL_DECODE - Decode a URL-encoded value.

                  URL_DECODE_UNI - Like URL_DECODE, but with support for Microsoft-specific %u encoding. If the code is in the full-width ASCII code range of FF01-FF5E, the higher byte is used to detect and adjust the lower byte. Otherwise, only the lower byte is used and the higher byte is zeroed.

                  UTF8_TO_UNICODE - Convert all UTF-8 character sequences to Unicode. This helps input normalization, and minimizing false-positives and false-negatives for non-English languages.

                  Possible values include:
                  • "NONE"
                  • "COMPRESS_WHITE_SPACE"
                  • "HTML_ENTITY_DECODE"
                  • "LOWERCASE"
                  • "CMD_LINE"
                  • "URL_DECODE"
                  • "BASE64_DECODE"
                  • "HEX_DECODE"
                  • "MD5"
                  • "REPLACE_COMMENTS"
                  • "ESCAPE_SEQ_DECODE"
                  • "SQL_HEX_DECODE"
                  • "CSS_DECODE"
                  • "JS_DECODE"
                  • "NORMALIZE_PATH"
                  • "NORMALIZE_PATH_WIN"
                  • "REMOVE_NULLS"
                  • "REPLACE_NULLS"
                  • "BASE64_DECODE_EXT"
                  • "URL_DECODE_UNI"
                  • "UTF8_TO_UNICODE"
            • RateBasedStatement — (map)

              A rate-based rule tracks the rate of requests for each originating IP address, and triggers the rule action when the rate exceeds a limit that you specify on the number of requests in any 5-minute time span. You can use this to put a temporary block on requests from an IP address that is sending excessive requests.

              WAF tracks and manages web requests separately for each instance of a rate-based rule that you use. For example, if you provide the same rate-based rule settings in two web ACLs, each of the two rule statements represents a separate instance of the rate-based rule and gets its own tracking and management by WAF. If you define a rate-based rule inside a rule group, and then use that rule group in multiple places, each use creates a separate instance of the rate-based rule that gets its own tracking and management by WAF.

              When the rule action triggers, WAF blocks additional requests from the IP address until the request rate falls below the limit.

              You can optionally nest another statement inside the rate-based statement, to narrow the scope of the rule so that it only counts requests that match the nested statement. For example, based on recent requests that you have seen from an attacker, you might create a rate-based rule with a nested AND rule statement that contains the following nested statements:

              • An IP match statement with an IP set that specified the address 192.0.2.44.

              • A string match statement that searches in the User-Agent header for the string BadBot.

              In this rate-based rule, you also define a rate limit. For this example, the rate limit is 1,000. Requests that meet both of the conditions in the statements are counted. If the count exceeds 1,000 requests per five minutes, the rule action triggers. Requests that do not meet both conditions are not counted towards the rate limit and are not affected by this rule.

              You cannot nest a RateBasedStatement inside another statement, for example inside a NotStatement or OrStatement. You can define a RateBasedStatement inside a web ACL and inside a rule group.

              • Limit — required — (Integer)

                The limit on requests per 5-minute period for a single originating IP address. If the statement includes a ScopeDownStatement, this limit is applied only to the requests that match the statement.

              • AggregateKeyType — required — (String)

                Setting that indicates how to aggregate the request counts. The options are the following:

                • IP - Aggregate the request counts on the IP address from the web request origin.

                • FORWARDED_IP - Aggregate the request counts on the first IP address in an HTTP header. If you use this, configure the ForwardedIPConfig, to specify the header to use.

                Possible values include:
                • "IP"
                • "FORWARDED_IP"
              • ForwardedIPConfig — (map)

                The configuration for inspecting IP addresses in an HTTP header that you specify, instead of using the IP address that's reported by the web request origin. Commonly, this is the X-Forwarded-For (XFF) header, but you can specify any header name.

                Note: If the specified header isn't present in the request, WAF doesn't apply the rule to the web request at all.

                This is required if AggregateKeyType is set to FORWARDED_IP.

                • HeaderName — required — (String)

                  The name of the HTTP header to use for the IP address. For example, to use the X-Forwarded-For (XFF) header, set this to X-Forwarded-For.

                  Note: If the specified header isn't present in the request, WAF doesn't apply the rule to the web request at all.
                • FallbackBehavior — required — (String)

                  The match status to assign to the web request if the request doesn't have a valid IP address in the specified position.

                  Note: If the specified header isn't present in the request, WAF doesn't apply the rule to the web request at all.

                  You can specify the following fallback behaviors:

                  • MATCH - Treat the web request as matching the rule statement. WAF applies the rule action to the request.

                  • NO_MATCH - Treat the web request as not matching the rule statement.

                  Possible values include:
                  • "MATCH"
                  • "NO_MATCH"
            • AndStatement — (map)

              A logical rule statement used to combine other rule statements with AND logic. You provide more than one Statement within the AndStatement.

              • Statements — required — (Array<map>)

                The statements to combine with AND logic. You can use any statements that can be nested.

            • OrStatement — (map)

              A logical rule statement used to combine other rule statements with OR logic. You provide more than one Statement within the OrStatement.

              • Statements — required — (Array<map>)

                The statements to combine with OR logic. You can use any statements that can be nested.

            • NotStatement — (map)

              A logical rule statement used to negate the results of another rule statement. You provide one Statement within the NotStatement.

            • ManagedRuleGroupStatement — (map)

              A rule statement used to run the rules that are defined in a managed rule group. To use this, provide the vendor name and the name of the rule group in this statement. You can retrieve the required names by calling ListAvailableManagedRuleGroups.

              You cannot nest a ManagedRuleGroupStatement, for example for use inside a NotStatement or OrStatement. It can only be referenced as a top-level statement within a rule.

              • VendorName — required — (String)

                The name of the managed rule group vendor. You use this, along with the rule group name, to identify the rule group.

              • Name — required — (String)

                The name of the managed rule group. You use this, along with the vendor name, to identify the rule group.

              • Version — (String)

                The version of the managed rule group to use. If you specify this, the version setting is fixed until you change it. If you don't specify this, WAF uses the vendor's default version, and then keeps the version at the vendor's default when the vendor updates the managed rule group settings.

              • ExcludedRules — (Array<map>)

                The rules in the referenced rule group whose actions are set to Count. When you exclude a rule, WAF evaluates it exactly as it would if the rule action setting were Count. This is a useful option for testing the rules in a rule group without modifying how they handle your web traffic.

                • Name — required — (String)

                  The name of the rule whose action you want to override to Count.

            • LabelMatchStatement — (map)

              A rule statement that defines a string match search against labels that have been added to the web request by rules that have already run in the web ACL.

              The label match statement provides the label or namespace string to search for. The label string can represent a part or all of the fully qualified label name that had been added to the web request. Fully qualified labels have a prefix, optional namespaces, and label name. The prefix identifies the rule group or web ACL context of the rule that added the label. If you do not provide the fully qualified name in your label match string, WAF performs the search for labels that were added in the same context as the label match statement.

              • Scope — required — (String)

                Specify whether you want to match using the label name or just the namespace.

                Possible values include:
                • "LABEL"
                • "NAMESPACE"
              • Key — required — (String)

                The string to match against. The setting you provide for this depends on the match statement's Scope setting:

                • If the Scope indicates LABEL, then this specification must include the name and can include any number of preceding namespace specifications and prefix up to providing the fully qualified label name.

                • If the Scope indicates NAMESPACE, then this specification can include any number of contiguous namespace strings, and can include the entire label namespace prefix from the rule group or web ACL where the label originates.

                Labels are case sensitive and components of a label must be separated by colon, for example NS1:NS2:name.

            • RegexMatchStatement — (map)

              A rule statement used to search web request components for a match against a single regular expression.

              • RegexString — required — (String)

                The string representing the regular expression.

              • FieldToMatch — required — (map)

                The part of a web request that you want WAF to inspect. For more information, see FieldToMatch.

                • SingleHeader — (map)

                  Inspect a single header. Provide the name of the header to inspect, for example, User-Agent or Referer. This setting isn't case sensitive.

                  Example JSON: "SingleHeader": { "Name": "haystack" }

                  • Name — required — (String)

                    The name of the query header to inspect.

                • SingleQueryArgument — (map)

                  Inspect a single query argument. Provide the name of the query argument to inspect, such as UserName or SalesRegion. The name can be up to 30 characters long and isn't case sensitive.

                  This is used only to indicate the web request component for WAF to inspect, in the FieldToMatch specification.

                  Example JSON: "SingleQueryArgument": { "Name": "myArgument" }

                  • Name — required — (String)

                    The name of the query argument to inspect.

                • AllQueryArguments — (map)

                  Inspect all query arguments.

                • UriPath — (map)

                  Inspect the request URI path. This is the part of a web request that identifies a resource, for example, /images/daily-ad.jpg.

                • QueryString — (map)

                  Inspect the query string. This is the part of a URL that appears after a ? character, if any.

                • Body — (map)

                  Inspect the request body as plain text. The request body immediately follows the request headers. This is the part of a request that contains any additional data that you want to send to your web server as the HTTP request body, such as data from a form.

                  Note that only the first 8 KB (8192 bytes) of the request body are forwarded to WAF for inspection by the underlying host service. If you don't need to inspect more than 8 KB, you can guarantee that you don't allow additional bytes in by combining a statement that inspects the body of the web request, such as ByteMatchStatement or RegexPatternSetReferenceStatement, with a SizeConstraintStatement that enforces an 8 KB size limit on the body of the request. WAF doesn't support inspecting the entire contents of web requests whose bodies exceed the 8 KB limit.

                • Method — (map)

                  Inspect the HTTP method. The method indicates the type of operation that the request is asking the origin to perform.

                • JsonBody — (map)

                  Inspect the request body as JSON. The request body immediately follows the request headers. This is the part of a request that contains any additional data that you want to send to your web server as the HTTP request body, such as data from a form.

                  Note that only the first 8 KB (8192 bytes) of the request body are forwarded to WAF for inspection by the underlying host service. If you don't need to inspect more than 8 KB, you can guarantee that you don't allow additional bytes in by combining a statement that inspects the body of the web request, such as ByteMatchStatement or RegexPatternSetReferenceStatement, with a SizeConstraintStatement that enforces an 8 KB size limit on the body of the request. WAF doesn't support inspecting the entire contents of web requests whose bodies exceed the 8 KB limit.

                  • MatchPattern — required — (map)

                    The patterns to look for in the JSON body. WAF inspects the results of these pattern matches against the rule inspection criteria.

                    • All — (map)

                      Match all of the elements. See also MatchScope in JsonBody.

                      You must specify either this setting or the IncludedPaths setting, but not both.

                    • IncludedPaths — (Array<String>)

                      Match only the specified include paths. See also MatchScope in JsonBody.

                      Provide the include paths using JSON Pointer syntax. For example, "IncludedPaths": ["/dogs/0/name", "/dogs/1/name"]. For information about this syntax, see the Internet Engineering Task Force (IETF) documentation JavaScript Object Notation (JSON) Pointer.

                      You must specify either this setting or the All setting, but not both.

                      Note: Don't use this option to include all paths. Instead, use the All setting.
                  • MatchScope — required — (String)

                    The parts of the JSON to match against using the MatchPattern. If you specify All, WAF matches against keys and values.

                    Possible values include:
                    • "ALL"
                    • "KEY"
                    • "VALUE"
                  • InvalidFallbackBehavior — (String)

                    What WAF should do if it fails to completely parse the JSON body. The options are the following:

                    • EVALUATE_AS_STRING - Inspect the body as plain text. WAF applies the text transformations and inspection criteria that you defined for the JSON inspection to the body text string.

                    • MATCH - Treat the web request as matching the rule statement. WAF applies the rule action to the request.

                    • NO_MATCH - Treat the web request as not matching the rule statement.

                    If you don't provide this setting, WAF parses and evaluates the content only up to the first parsing failure that it encounters.

                    WAF does its best to parse the entire JSON body, but might be forced to stop for reasons such as invalid characters, duplicate keys, truncation, and any content whose root node isn't an object or an array.

                    WAF parses the JSON in the following examples as two valid key, value pairs:

                    • Missing comma: {"key1":"value1""key2":"value2"}

                    • Missing colon: {"key1":"value1","key2""value2"}

                    • Extra colons: {"key1"::"value1","key2""value2"}

                    Possible values include:
                    • "MATCH"
                    • "NO_MATCH"
                    • "EVALUATE_AS_STRING"
              • TextTransformations — required — (Array<map>)

                Text transformations eliminate some of the unusual formatting that attackers use in web requests in an effort to bypass detection. If you specify one or more transformations in a rule statement, WAF performs all transformations on the content of the request component identified by FieldToMatch, starting from the lowest priority setting, before inspecting the content for a match.

                • Priority — required — (Integer)

                  Sets the relative processing order for multiple transformations that are defined for a rule statement. WAF processes all transformations, from lowest priority to highest, before inspecting the transformed content. The priorities don't need to be consecutive, but they must all be different.

                • Type — required — (String)

                  You can specify the following transformation types:

                  BASE64_DECODE - Decode a Base64-encoded string.

                  BASE64_DECODE_EXT - Decode a Base64-encoded string, but use a forgiving implementation that ignores characters that aren't valid.

                  CMD_LINE - Command-line transformations. These are helpful in reducing effectiveness of attackers who inject an operating system command-line command and use unusual formatting to disguise some or all of the command.

                  • Delete the following characters: \ " ' ^

                  • Delete spaces before the following characters: / (

                  • Replace the following characters with a space: , ;

                  • Replace multiple spaces with one space

                  • Convert uppercase letters (A-Z) to lowercase (a-z)

                  COMPRESS_WHITE_SPACE - Replace these characters with a space character (decimal 32):

                  • \f, formfeed, decimal 12

                  • \t, tab, decimal 9

                  • \n, newline, decimal 10

                  • \r, carriage return, decimal 13

                  • \v, vertical tab, decimal 11

                  • Non-breaking space, decimal 160

                  COMPRESS_WHITE_SPACE also replaces multiple spaces with one space.

                  CSS_DECODE - Decode characters that were encoded using CSS 2.x escape rules syndata.html#characters. This function uses up to two bytes in the decoding process, so it can help to uncover ASCII characters that were encoded using CSS encoding that wouldn’t typically be encoded. It's also useful in countering evasion, which is a combination of a backslash and non-hexadecimal characters. For example, ja\vascript for javascript.

                  ESCAPE_SEQ_DECODE - Decode the following ANSI C escape sequences: \a, \b, \f, \n, \r, \t, \v, \, \?, \', \", \xHH (hexadecimal), \0OOO (octal). Encodings that aren't valid remain in the output.

                  HEX_DECODE - Decode a string of hexadecimal characters into a binary.

                  HTML_ENTITY_DECODE - Replace HTML-encoded characters with unencoded characters. HTML_ENTITY_DECODE performs these operations:

                  • Replaces (ampersand)quot; with "

                  • Replaces (ampersand)nbsp; with a non-breaking space, decimal 160

                  • Replaces (ampersand)lt; with a "less than" symbol

                  • Replaces (ampersand)gt; with >

                  • Replaces characters that are represented in hexadecimal format, (ampersand)#xhhhh;, with the corresponding characters

                  • Replaces characters that are represented in decimal format, (ampersand)#nnnn;, with the corresponding characters

                  JS_DECODE - Decode JavaScript escape sequences. If a \ u HHHH code is in the full-width ASCII code range of FF01-FF5E, then the higher byte is used to detect and adjust the lower byte. If not, only the lower byte is used and the higher byte is zeroed, causing a possible loss of information.

                  LOWERCASE - Convert uppercase letters (A-Z) to lowercase (a-z).

                  MD5 - Calculate an MD5 hash from the data in the input. The computed hash is in a raw binary form.

                  NONE - Specify NONE if you don't want any text transformations.

                  NORMALIZE_PATH - Remove multiple slashes, directory self-references, and directory back-references that are not at the beginning of the input from an input string.

                  NORMALIZE_PATH_WIN - This is the same as NORMALIZE_PATH, but first converts backslash characters to forward slashes.

                  REMOVE_NULLS - Remove all NULL bytes from the input.

                  REPLACE_COMMENTS - Replace each occurrence of a C-style comment (/* ... */) with a single space. Multiple consecutive occurrences are not compressed. Unterminated comments are also replaced with a space (ASCII 0x20). However, a standalone termination of a comment (*/) is not acted upon.

                  REPLACE_NULLS - Replace NULL bytes in the input with space characters (ASCII 0x20).

                  SQL_HEX_DECODE - Decode SQL hex data. Example (0x414243) will be decoded to (ABC).

                  URL_DECODE - Decode a URL-encoded value.

                  URL_DECODE_UNI - Like URL_DECODE, but with support for Microsoft-specific %u encoding. If the code is in the full-width ASCII code range of FF01-FF5E, the higher byte is used to detect and adjust the lower byte. Otherwise, only the lower byte is used and the higher byte is zeroed.

                  UTF8_TO_UNICODE - Convert all UTF-8 character sequences to Unicode. This helps input normalization, and minimizing false-positives and false-negatives for non-English languages.

                  Possible values include:
                  • "NONE"
                  • "COMPRESS_WHITE_SPACE"
                  • "HTML_ENTITY_DECODE"
                  • "LOWERCASE"
                  • "CMD_LINE"
                  • "URL_DECODE"
                  • "BASE64_DECODE"
                  • "HEX_DECODE"
                  • "MD5"
                  • "REPLACE_COMMENTS"
                  • "ESCAPE_SEQ_DECODE"
                  • "SQL_HEX_DECODE"
                  • "CSS_DECODE"
                  • "JS_DECODE"
                  • "NORMALIZE_PATH"
                  • "NORMALIZE_PATH_WIN"
                  • "REMOVE_NULLS"
                  • "REPLACE_NULLS"
                  • "BASE64_DECODE_EXT"
                  • "URL_DECODE_UNI"
                  • "UTF8_TO_UNICODE"
          • Action — (map)

            The action that WAF should take on a web request when it matches the rule statement. Settings at the web ACL level can override the rule action setting.

            This is used only for rules whose statements do not reference a rule group. Rule statements that reference a rule group include RuleGroupReferenceStatement and ManagedRuleGroupStatement.

            You must specify either this Action setting or the rule OverrideAction setting, but not both:

            • If the rule statement does not reference a rule group, use this rule action setting and not the rule override action setting.

            • If the rule statement references a rule group, use the override action setting and not this action setting.

            • Block — (map)

              Instructs WAF to block the web request.

              • CustomResponse — (map)

                Defines a custom response for the web request.

                For information about customizing web requests and responses, see Customizing web requests and responses in WAF in the WAF Developer Guide.

                • ResponseCode — required — (Integer)

                  The HTTP status code to return to the client.

                  For a list of status codes that you can use in your custom reqponses, see Supported status codes for custom response in the WAF Developer Guide.

                • CustomResponseBodyKey — (String)

                  References the response body that you want WAF to return to the web request client. You can define a custom response for a rule action or a default web ACL action that is set to block. To do this, you first define the response body key and value in the CustomResponseBodies setting for the WebACL or RuleGroup where you want to use it. Then, in the rule action or web ACL default action BlockAction setting, you reference the response body using this key.

                • ResponseHeaders — (Array<map>)

                  The HTTP headers to use in the response. Duplicate header names are not allowed.

                  For information about the limits on count and size for custom request and response settings, see WAF quotas in the WAF Developer Guide.

                  • Name — required — (String)

                    The name of the custom header.

                    For custom request header insertion, when WAF inserts the header into the request, it prefixes this name x-amzn-waf-, to avoid confusion with the headers that are already in the request. For example, for the header name sample, WAF inserts the header x-amzn-waf-sample.

                  • Value — required — (String)

                    The value of the custom header.

            • Allow — (map)

              Instructs WAF to allow the web request.

              • CustomRequestHandling — (map)

                Defines custom handling for the web request.

                For information about customizing web requests and responses, see Customizing web requests and responses in WAF in the WAF Developer Guide.

                • InsertHeaders — required — (Array<map>)

                  The HTTP headers to insert into the request. Duplicate header names are not allowed.

                  For information about the limits on count and size for custom request and response settings, see WAF quotas in the WAF Developer Guide.

                  • Name — required — (String)

                    The name of the custom header.

                    For custom request header insertion, when WAF inserts the header into the request, it prefixes this name x-amzn-waf-, to avoid confusion with the headers that are already in the request. For example, for the header name sample, WAF inserts the header x-amzn-waf-sample.

                  • Value — required — (String)

                    The value of the custom header.

            • Count — (map)

              Instructs WAF to count the web request and allow it.

              • CustomRequestHandling — (map)

                Defines custom handling for the web request.

                For information about customizing web requests and responses, see Customizing web requests and responses in WAF in the WAF Developer Guide.

                • InsertHeaders — required — (Array<map>)

                  The HTTP headers to insert into the request. Duplicate header names are not allowed.

                  For information about the limits on count and size for custom request and response settings, see WAF quotas in the WAF Developer Guide.

                  • Name — required — (String)

                    The name of the custom header.

                    For custom request header insertion, when WAF inserts the header into the request, it prefixes this name x-amzn-waf-, to avoid confusion with the headers that are already in the request. For example, for the header name sample, WAF inserts the header x-amzn-waf-sample.

                  • Value — required — (String)

                    The value of the custom header.

            • Captcha — (map)

              Instructs WAF to run a CAPTCHA check against the web request.

              • CustomRequestHandling — (map)

                Defines custom handling for the web request.

                For information about customizing web requests and responses, see Customizing web requests and responses in WAF in the WAF Developer Guide.

                • InsertHeaders — required — (Array<map>)

                  The HTTP headers to insert into the request. Duplicate header names are not allowed.

                  For information about the limits on count and size for custom request and response settings, see WAF quotas in the WAF Developer Guide.

                  • Name — required — (String)

                    The name of the custom header.

                    For custom request header insertion, when WAF inserts the header into the request, it prefixes this name x-amzn-waf-, to avoid confusion with the headers that are already in the request. For example, for the header name sample, WAF inserts the header x-amzn-waf-sample.

                  • Value — required — (String)

                    The value of the custom header.

          • OverrideAction — (map)

            The action to use in the place of the action that results from the rule group evaluation. Set the override action to none to leave the result of the rule group alone. Set it to count to override the result to count only.

            You can only use this for rule statements that reference a rule group, like RuleGroupReferenceStatement and ManagedRuleGroupStatement.

            Note: This option is usually set to none. It does not affect how the rules in the rule group are evaluated. If you want the rules in the rule group to only count matches, do not use this and instead exclude those rules in your rule group reference statement settings.
            • Count — (map)

              Override the rule group evaluation result to count only.

              Note: This option is usually set to none. It does not affect how the rules in the rule group are evaluated. If you want the rules in the rule group to only count matches, do not use this and instead exclude those rules in your rule group reference statement settings.
              • CustomRequestHandling — (map)

                Defines custom handling for the web request.

                For information about customizing web requests and responses, see Customizing web requests and responses in WAF in the WAF Developer Guide.

                • InsertHeaders — required — (Array<map>)

                  The HTTP headers to insert into the request. Duplicate header names are not allowed.

                  For information about the limits on count and size for custom request and response settings, see WAF quotas in the WAF Developer Guide.

                  • Name — required — (String)

                    The name of the custom header.

                    For custom request header insertion, when WAF inserts the header into the request, it prefixes this name x-amzn-waf-, to avoid confusion with the headers that are already in the request. For example, for the header name sample, WAF inserts the header x-amzn-waf-sample.

                  • Value — required — (String)

                    The value of the custom header.

            • None — (map)

              Don't override the rule group evaluation result. This is the most common setting.

          • RuleLabels — (Array<map>)

            Labels to apply to web requests that match the rule match statement. WAF applies fully qualified labels to matching web requests. A fully qualified label is the concatenation of a label namespace and a rule label. The rule's rule group or web ACL defines the label namespace.

            Rules that run after this rule in the web ACL can match against these labels using a LabelMatchStatement.

            For each label, provide a case-sensitive string containing optional namespaces and a label name, according to the following guidelines:

            • Separate each component of the label with a colon.

            • Each namespace or name can have up to 128 characters.

            • You can specify up to 5 namespaces in a label.

            • Don't use the following reserved words in your label specification: aws, waf, managed, rulegroup, webacl, regexpatternset, or ipset.

            For example, myLabelName or nameSpace1:nameSpace2:myLabelName.

            • Name — required — (String)

              The label string.

          • VisibilityConfig — required — (map)

            Defines and enables Amazon CloudWatch metrics and web request sample collection.

            • SampledRequestsEnabled — required — (Boolean)

              A boolean indicating whether WAF should store a sampling of the web requests that match the rules. You can view the sampled requests through the WAF console.

            • CloudWatchMetricsEnabled — required — (Boolean)

              A boolean indicating whether the associated resource sends metrics to Amazon CloudWatch. For the list of available metrics, see WAF Metrics.

            • MetricName — required — (String)

              A name of the Amazon CloudWatch metric. The name can contain only the characters: A-Z, a-z, 0-9, - (hyphen), and _ (underscore). The name can be from one to 128 characters long. It can't contain whitespace or metric names reserved for WAF, for example "All" and "Default_Action."

          • CaptchaConfig — (map)

            Specifies how WAF should handle CAPTCHA evaluations. If you don't specify this, WAF uses the CAPTCHA configuration that's defined for the web ACL.

            • ImmunityTimeProperty — (map)

              Determines how long a CAPTCHA token remains valid after the client successfully solves a CAPTCHA puzzle.

              • ImmunityTime — required — (Integer)

                The amount of time, in seconds, that a CAPTCHA token is valid. The default setting is 300.

        • VisibilityConfig — required — (map)

          Defines and enables Amazon CloudWatch metrics and web request sample collection.

          • SampledRequestsEnabled — required — (Boolean)

            A boolean indicating whether WAF should store a sampling of the web requests that match the rules. You can view the sampled requests through the WAF console.

          • CloudWatchMetricsEnabled — required — (Boolean)

            A boolean indicating whether the associated resource sends metrics to Amazon CloudWatch. For the list of available metrics, see WAF Metrics.

          • MetricName — required — (String)

            A name of the Amazon CloudWatch metric. The name can contain only the characters: A-Z, a-z, 0-9, - (hyphen), and _ (underscore). The name can be from one to 128 characters long. It can't contain whitespace or metric names reserved for WAF, for example "All" and "Default_Action."

        • Capacity — (Integer)

          The web ACL capacity units (WCUs) currently being used by this web ACL.

          WAF uses WCUs to calculate and control the operating resources that are used to run your rules, rule groups, and web ACLs. WAF calculates capacity differently for each rule type, to reflect the relative cost of each rule. Simple rules that cost little to run use fewer WCUs than more complex rules that use more processing power. Rule group capacity is fixed at creation, which helps users plan their web ACL WCU usage when they use a rule group. The WCU limit for web ACLs is 1,500.

        • PreProcessFirewallManagerRuleGroups — (Array<map>)

          The first set of rules for WAF to process in the web ACL. This is defined in an Firewall Manager WAF policy and contains only rule group references. You can't alter these. Any rules and rule groups that you define for the web ACL are prioritized after these.

          In the Firewall Manager WAF policy, the Firewall Manager administrator can define a set of rule groups to run first in the web ACL and a set of rule groups to run last. Within each set, the administrator prioritizes the rule groups, to determine their relative processing order.

          • Name — required — (String)

            The name of the rule group. You cannot change the name of a rule group after you create it.

          • Priority — required — (Integer)

            If you define more than one rule group in the first or last Firewall Manager rule groups, WAF evaluates each request against the rule groups in order, starting from the lowest priority setting. The priorities don't need to be consecutive, but they must all be different.

          • FirewallManagerStatement — required — (map)

            The processing guidance for an Firewall Manager rule. This is like a regular rule Statement, but it can only contain a rule group reference.

            • ManagedRuleGroupStatement — (map)

              A rule statement used to run the rules that are defined in a managed rule group. To use this, provide the vendor name and the name of the rule group in this statement. You can retrieve the required names by calling ListAvailableManagedRuleGroups.

              You cannot nest a ManagedRuleGroupStatement, for example for use inside a NotStatement or OrStatement. It can only be referenced as a top-level statement within a rule.

              • VendorName — required — (String)

                The name of the managed rule group vendor. You use this, along with the rule group name, to identify the rule group.

              • Name — required — (String)

                The name of the managed rule group. You use this, along with the vendor name, to identify the rule group.

              • Version — (String)

                The version of the managed rule group to use. If you specify this, the version setting is fixed until you change it. If you don't specify this, WAF uses the vendor's default version, and then keeps the version at the vendor's default when the vendor updates the managed rule group settings.

              • ExcludedRules — (Array<map>)

                The rules in the referenced rule group whose actions are set to Count. When you exclude a rule, WAF evaluates it exactly as it would if the rule action setting were Count. This is a useful option for testing the rules in a rule group without modifying how they handle your web traffic.

                • Name — required — (String)

                  The name of the rule whose action you want to override to Count.

              • ScopeDownStatement — (map)

                An optional nested statement that narrows the scope of the web requests that are evaluated by the managed rule group. Requests are only evaluated by the rule group if they match the scope-down statement. You can use any nestable Statement in the scope-down statement, and you can nest statements at any level, the same as you can for a rule statement.

                • ByteMatchStatement — (map)

                  A rule statement that defines a string match search for WAF to apply to web requests. The byte match statement provides the bytes to search for, the location in requests that you want WAF to search, and other settings. The bytes to search for are typically a string that corresponds with ASCII characters. In the WAF console and the developer guide, this is refered to as a string match statement.

                  • SearchString — required — (Buffer, Typed Array, Blob, String)

                    A string value that you want WAF to search for. WAF searches only in the part of web requests that you designate for inspection in FieldToMatch. The maximum length of the value is 50 bytes.

                    Valid values depend on the component that you specify for inspection in FieldToMatch:

                    • Method: The HTTP method that you want WAF to search for. This indicates the type of operation specified in the request.

                    • UriPath: The value that you want WAF to search for in the URI path, for example, /images/daily-ad.jpg.

                    If SearchString includes alphabetic characters A-Z and a-z, note that the value is case sensitive.

                    If you're using the WAF API

                    Specify a base64-encoded version of the value. The maximum length of the value before you base64-encode it is 50 bytes.

                    For example, suppose the value of Type is HEADER and the value of Data is User-Agent. If you want to search the User-Agent header for the value BadBot, you base64-encode BadBot using MIME base64-encoding and include the resulting value, QmFkQm90, in the value of SearchString.

                    If you're using the CLI or one of the Amazon Web Services SDKs

                    The value that you want WAF to search for. The SDK automatically base64 encodes the value.

                  • FieldToMatch — required — (map)

                    The part of a web request that you want WAF to inspect. For more information, see FieldToMatch.

                    • SingleHeader — (map)

                      Inspect a single header. Provide the name of the header to inspect, for example, User-Agent or Referer. This setting isn't case sensitive.

                      Example JSON: "SingleHeader": { "Name": "haystack" }

                      • Name — required — (String)

                        The name of the query header to inspect.

                    • SingleQueryArgument — (map)

                      Inspect a single query argument. Provide the name of the query argument to inspect, such as UserName or SalesRegion. The name can be up to 30 characters long and isn't case sensitive.

                      This is used only to indicate the web request component for WAF to inspect, in the FieldToMatch specification.

                      Example JSON: "SingleQueryArgument": { "Name": "myArgument" }

                      • Name — required — (String)

                        The name of the query argument to inspect.

                    • AllQueryArguments — (map)

                      Inspect all query arguments.

                    • UriPath — (map)

                      Inspect the request URI path. This is the part of a web request that identifies a resource, for example, /images/daily-ad.jpg.

                    • QueryString — (map)

                      Inspect the query string. This is the part of a URL that appears after a ? character, if any.

                    • Body — (map)

                      Inspect the request body as plain text. The request body immediately follows the request headers. This is the part of a request that contains any additional data that you want to send to your web server as the HTTP request body, such as data from a form.

                      Note that only the first 8 KB (8192 bytes) of the request body are forwarded to WAF for inspection by the underlying host service. If you don't need to inspect more than 8 KB, you can guarantee that you don't allow additional bytes in by combining a statement that inspects the body of the web request, such as ByteMatchStatement or RegexPatternSetReferenceStatement, with a SizeConstraintStatement that enforces an 8 KB size limit on the body of the request. WAF doesn't support inspecting the entire contents of web requests whose bodies exceed the 8 KB limit.

                    • Method — (map)

                      Inspect the HTTP method. The method indicates the type of operation that the request is asking the origin to perform.

                    • JsonBody — (map)

                      Inspect the request body as JSON. The request body immediately follows the request headers. This is the part of a request that contains any additional data that you want to send to your web server as the HTTP request body, such as data from a form.

                      Note that only the first 8 KB (8192 bytes) of the request body are forwarded to WAF for inspection by the underlying host service. If you don't need to inspect more than 8 KB, you can guarantee that you don't allow additional bytes in by combining a statement that inspects the body of the web request, such as ByteMatchStatement or RegexPatternSetReferenceStatement, with a SizeConstraintStatement that enforces an 8 KB size limit on the body of the request. WAF doesn't support inspecting the entire contents of web requests whose bodies exceed the 8 KB limit.

                      • MatchPattern — required — (map)

                        The patterns to look for in the JSON body. WAF inspects the results of these pattern matches against the rule inspection criteria.

                        • All — (map)

                          Match all of the elements. See also MatchScope in JsonBody.

                          You must specify either this setting or the IncludedPaths setting, but not both.

                        • IncludedPaths — (Array<String>)

                          Match only the specified include paths. See also MatchScope in JsonBody.

                          Provide the include paths using JSON Pointer syntax. For example, "IncludedPaths": ["/dogs/0/name", "/dogs/1/name"]. For information about this syntax, see the Internet Engineering Task Force (IETF) documentation JavaScript Object Notation (JSON) Pointer.

                          You must specify either this setting or the All setting, but not both.

                          Note: Don't use this option to include all paths. Instead, use the All setting.
                      • MatchScope — required — (String)

                        The parts of the JSON to match against using the MatchPattern. If you specify All, WAF matches against keys and values.

                        Possible values include:
                        • "ALL"
                        • "KEY"
                        • "VALUE"
                      • InvalidFallbackBehavior — (String)

                        What WAF should do if it fails to completely parse the JSON body. The options are the following:

                        • EVALUATE_AS_STRING - Inspect the body as plain text. WAF applies the text transformations and inspection criteria that you defined for the JSON inspection to the body text string.

                        • MATCH - Treat the web request as matching the rule statement. WAF applies the rule action to the request.

                        • NO_MATCH - Treat the web request as not matching the rule statement.

                        If you don't provide this setting, WAF parses and evaluates the content only up to the first parsing failure that it encounters.

                        WAF does its best to parse the entire JSON body, but might be forced to stop for reasons such as invalid characters, duplicate keys, truncation, and any content whose root node isn't an object or an array.

                        WAF parses the JSON in the following examples as two valid key, value pairs:

                        • Missing comma: {"key1":"value1""key2":"value2"}

                        • Missing colon: {"key1":"value1","key2""value2"}

                        • Extra colons: {"key1"::"value1","key2""value2"}

                        Possible values include:
                        • "MATCH"
                        • "NO_MATCH"
                        • "EVALUATE_AS_STRING"
                  • TextTransformations — required — (Array<map>)

                    Text transformations eliminate some of the unusual formatting that attackers use in web requests in an effort to bypass detection. If you specify one or more transformations in a rule statement, WAF performs all transformations on the content of the request component identified by FieldToMatch, starting from the lowest priority setting, before inspecting the content for a match.

                    • Priority — required — (Integer)

                      Sets the relative processing order for multiple transformations that are defined for a rule statement. WAF processes all transformations, from lowest priority to highest, before inspecting the transformed content. The priorities don't need to be consecutive, but they must all be different.

                    • Type — required — (String)

                      You can specify the following transformation types:

                      BASE64_DECODE - Decode a Base64-encoded string.

                      BASE64_DECODE_EXT - Decode a Base64-encoded string, but use a forgiving implementation that ignores characters that aren't valid.

                      CMD_LINE - Command-line transformations. These are helpful in reducing effectiveness of attackers who inject an operating system command-line command and use unusual formatting to disguise some or all of the command.

                      • Delete the following characters: \ " ' ^

                      • Delete spaces before the following characters: / (

                      • Replace the following characters with a space: , ;

                      • Replace multiple spaces with one space

                      • Convert uppercase letters (A-Z) to lowercase (a-z)

                      COMPRESS_WHITE_SPACE - Replace these characters with a space character (decimal 32):

                      • \f, formfeed, decimal 12

                      • \t, tab, decimal 9

                      • \n, newline, decimal 10

                      • \r, carriage return, decimal 13

                      • \v, vertical tab, decimal 11

                      • Non-breaking space, decimal 160

                      COMPRESS_WHITE_SPACE also replaces multiple spaces with one space.

                      CSS_DECODE - Decode characters that were encoded using CSS 2.x escape rules syndata.html#characters. This function uses up to two bytes in the decoding process, so it can help to uncover ASCII characters that were encoded using CSS encoding that wouldn’t typically be encoded. It's also useful in countering evasion, which is a combination of a backslash and non-hexadecimal characters. For example, ja\vascript for javascript.

                      ESCAPE_SEQ_DECODE - Decode the following ANSI C escape sequences: \a, \b, \f, \n, \r, \t, \v, \, \?, \', \", \xHH (hexadecimal), \0OOO (octal). Encodings that aren't valid remain in the output.

                      HEX_DECODE - Decode a string of hexadecimal characters into a binary.

                      HTML_ENTITY_DECODE - Replace HTML-encoded characters with unencoded characters. HTML_ENTITY_DECODE performs these operations:

                      • Replaces (ampersand)quot; with "

                      • Replaces (ampersand)nbsp; with a non-breaking space, decimal 160

                      • Replaces (ampersand)lt; with a "less than" symbol

                      • Replaces (ampersand)gt; with >

                      • Replaces characters that are represented in hexadecimal format, (ampersand)#xhhhh;, with the corresponding characters

                      • Replaces characters that are represented in decimal format, (ampersand)#nnnn;, with the corresponding characters

                      JS_DECODE - Decode JavaScript escape sequences. If a \ u HHHH code is in the full-width ASCII code range of FF01-FF5E, then the higher byte is used to detect and adjust the lower byte. If not, only the lower byte is used and the higher byte is zeroed, causing a possible loss of information.

                      LOWERCASE - Convert uppercase letters (A-Z) to lowercase (a-z).

                      MD5 - Calculate an MD5 hash from the data in the input. The computed hash is in a raw binary form.

                      NONE - Specify NONE if you don't want any text transformations.

                      NORMALIZE_PATH - Remove multiple slashes, directory self-references, and directory back-references that are not at the beginning of the input from an input string.

                      NORMALIZE_PATH_WIN - This is the same as NORMALIZE_PATH, but first converts backslash characters to forward slashes.

                      REMOVE_NULLS - Remove all NULL bytes from the input.

                      REPLACE_COMMENTS - Replace each occurrence of a C-style comment (/* ... */) with a single space. Multiple consecutive occurrences are not compressed. Unterminated comments are also replaced with a space (ASCII 0x20). However, a standalone termination of a comment (*/) is not acted upon.

                      REPLACE_NULLS - Replace NULL bytes in the input with space characters (ASCII 0x20).

                      SQL_HEX_DECODE - Decode SQL hex data. Example (0x414243) will be decoded to (ABC).

                      URL_DECODE - Decode a URL-encoded value.

                      URL_DECODE_UNI - Like URL_DECODE, but with support for Microsoft-specific %u encoding. If the code is in the full-width ASCII code range of FF01-FF5E, the higher byte is used to detect and adjust the lower byte. Otherwise, only the lower byte is used and the higher byte is zeroed.

                      UTF8_TO_UNICODE - Convert all UTF-8 character sequences to Unicode. This helps input normalization, and minimizing false-positives and false-negatives for non-English languages.

                      Possible values include:
                      • "NONE"
                      • "COMPRESS_WHITE_SPACE"
                      • "HTML_ENTITY_DECODE"
                      • "LOWERCASE"
                      • "CMD_LINE"
                      • "URL_DECODE"
                      • "BASE64_DECODE"
                      • "HEX_DECODE"
                      • "MD5"
                      • "REPLACE_COMMENTS"
                      • "ESCAPE_SEQ_DECODE"
                      • "SQL_HEX_DECODE"
                      • "CSS_DECODE"
                      • "JS_DECODE"
                      • "NORMALIZE_PATH"
                      • "NORMALIZE_PATH_WIN"
                      • "REMOVE_NULLS"
                      • "REPLACE_NULLS"
                      • "BASE64_DECODE_EXT"
                      • "URL_DECODE_UNI"
                      • "UTF8_TO_UNICODE"
                  • PositionalConstraint — required — (String)

                    The area within the portion of a web request that you want WAF to search for SearchString. Valid values include the following:

                    CONTAINS

                    The specified part of the web request must include the value of SearchString, but the location doesn't matter.

                    CONTAINS_WORD

                    The specified part of the web request must include the value of SearchString, and SearchString must contain only alphanumeric characters or underscore (A-Z, a-z, 0-9, or ). In addition, SearchString must be a word, which means that both of the following are true:

                    • SearchString is at the beginning of the specified part of the web request or is preceded by a character other than an alphanumeric character or underscore (). Examples include the value of a header and ;BadBot.

                    • SearchString is at the end of the specified part of the web request or is followed by a character other than an alphanumeric character or underscore (_), for example, BadBot; and -BadBot;.

                    EXACTLY

                    The value of the specified part of the web request must exactly match the value of SearchString.

                    STARTS_WITH

                    The value of SearchString must appear at the beginning of the specified part of the web request.

                    ENDS_WITH

                    The value of SearchString must appear at the end of the specified part of the web request.

                    Possible values include:
                    • "EXACTLY"
                    • "STARTS_WITH"
                    • "ENDS_WITH"
                    • "CONTAINS"
                    • "CONTAINS_WORD"
                • SqliMatchStatement — (map)

                  Attackers sometimes insert malicious SQL code into web requests in an effort to extract data from your database. To allow or block web requests that appear to contain malicious SQL code, create one or more SQL injection match conditions. An SQL injection match condition identifies the part of web requests, such as the URI or the query string, that you want WAF to inspect. Later in the process, when you create a web ACL, you specify whether to allow or block requests that appear to contain malicious SQL code.

                  • FieldToMatch — required — (map)

                    The part of a web request that you want WAF to inspect. For more information, see FieldToMatch.

                    • SingleHeader — (map)

                      Inspect a single header. Provide the name of the header to inspect, for example, User-Agent or Referer. This setting isn't case sensitive.

                      Example JSON: "SingleHeader": { "Name": "haystack" }

                      • Name — required — (String)

                        The name of the query header to inspect.

                    • SingleQueryArgument — (map)

                      Inspect a single query argument. Provide the name of the query argument to inspect, such as UserName or SalesRegion. The name can be up to 30 characters long and isn't case sensitive.

                      This is used only to indicate the web request component for WAF to inspect, in the FieldToMatch specification.

                      Example JSON: "SingleQueryArgument": { "Name": "myArgument" }

                      • Name — required — (String)

                        The name of the query argument to inspect.

                    • AllQueryArguments — (map)

                      Inspect all query arguments.

                    • UriPath — (map)

                      Inspect the request URI path. This is the part of a web request that identifies a resource, for example, /images/daily-ad.jpg.

                    • QueryString — (map)

                      Inspect the query string. This is the part of a URL that appears after a ? character, if any.

                    • Body — (map)

                      Inspect the request body as plain text. The request body immediately follows the request headers. This is the part of a request that contains any additional data that you want to send to your web server as the HTTP request body, such as data from a form.

                      Note that only the first 8 KB (8192 bytes) of the request body are forwarded to WAF for inspection by the underlying host service. If you don't need to inspect more than 8 KB, you can guarantee that you don't allow additional bytes in by combining a statement that inspects the body of the web request, such as ByteMatchStatement or RegexPatternSetReferenceStatement, with a SizeConstraintStatement that enforces an 8 KB size limit on the body of the request. WAF doesn't support inspecting the entire contents of web requests whose bodies exceed the 8 KB limit.

                    • Method — (map)

                      Inspect the HTTP method. The method indicates the type of operation that the request is asking the origin to perform.

                    • JsonBody — (map)

                      Inspect the request body as JSON. The request body immediately follows the request headers. This is the part of a request that contains any additional data that you want to send to your web server as the HTTP request body, such as data from a form.

                      Note that only the first 8 KB (8192 bytes) of the request body are forwarded to WAF for inspection by the underlying host service. If you don't need to inspect more than 8 KB, you can guarantee that you don't allow additional bytes in by combining a statement that inspects the body of the web request, such as ByteMatchStatement or RegexPatternSetReferenceStatement, with a SizeConstraintStatement that enforces an 8 KB size limit on the body of the request. WAF doesn't support inspecting the entire contents of web requests whose bodies exceed the 8 KB limit.

                      • MatchPattern — required — (map)

                        The patterns to look for in the JSON body. WAF inspects the results of these pattern matches against the rule inspection criteria.

                        • All — (map)

                          Match all of the elements. See also MatchScope in JsonBody.

                          You must specify either this setting or the IncludedPaths setting, but not both.

                        • IncludedPaths — (Array<String>)

                          Match only the specified include paths. See also MatchScope in JsonBody.

                          Provide the include paths using JSON Pointer syntax. For example, "IncludedPaths": ["/dogs/0/name", "/dogs/1/name"]. For information about this syntax, see the Internet Engineering Task Force (IETF) documentation JavaScript Object Notation (JSON) Pointer.

                          You must specify either this setting or the All setting, but not both.

                          Note: Don't use this option to include all paths. Instead, use the All setting.
                      • MatchScope — required — (String)

                        The parts of the JSON to match against using the MatchPattern. If you specify All, WAF matches against keys and values.

                        Possible values include:
                        • "ALL"
                        • "KEY"
                        • "VALUE"
                      • InvalidFallbackBehavior — (String)

                        What WAF should do if it fails to completely parse the JSON body. The options are the following:

                        • EVALUATE_AS_STRING - Inspect the body as plain text. WAF applies the text transformations and inspection criteria that you defined for the JSON inspection to the body text string.

                        • MATCH - Treat the web request as matching the rule statement. WAF applies the rule action to the request.

                        • NO_MATCH - Treat the web request as not matching the rule statement.

                        If you don't provide this setting, WAF parses and evaluates the content only up to the first parsing failure that it encounters.

                        WAF does its best to parse the entire JSON body, but might be forced to stop for reasons such as invalid characters, duplicate keys, truncation, and any content whose root node isn't an object or an array.

                        WAF parses the JSON in the following examples as two valid key, value pairs:

                        • Missing comma: {"key1":"value1""key2":"value2"}

                        • Missing colon: {"key1":"value1","key2""value2"}

                        • Extra colons: {"key1"::"value1","key2""value2"}

                        Possible values include:
                        • "MATCH"
                        • "NO_MATCH"
                        • "EVALUATE_AS_STRING"
                  • TextTransformations — required — (Array<map>)

                    Text transformations eliminate some of the unusual formatting that attackers use in web requests in an effort to bypass detection. If you specify one or more transformations in a rule statement, WAF performs all transformations on the content of the request component identified by FieldToMatch, starting from the lowest priority setting, before inspecting the content for a match.

                    • Priority — required — (Integer)

                      Sets the relative processing order for multiple transformations that are defined for a rule statement. WAF processes all transformations, from lowest priority to highest, before inspecting the transformed content. The priorities don't need to be consecutive, but they must all be different.

                    • Type — required — (String)

                      You can specify the following transformation types:

                      BASE64_DECODE - Decode a Base64-encoded string.

                      BASE64_DECODE_EXT - Decode a Base64-encoded string, but use a forgiving implementation that ignores characters that aren't valid.

                      CMD_LINE - Command-line transformations. These are helpful in reducing effectiveness of attackers who inject an operating system command-line command and use unusual formatting to disguise some or all of the command.

                      • Delete the following characters: \ " ' ^

                      • Delete spaces before the following characters: / (

                      • Replace the following characters with a space: , ;

                      • Replace multiple spaces with one space

                      • Convert uppercase letters (A-Z) to lowercase (a-z)

                      COMPRESS_WHITE_SPACE - Replace these characters with a space character (decimal 32):

                      • \f, formfeed, decimal 12

                      • \t, tab, decimal 9

                      • \n, newline, decimal 10

                      • \r, carriage return, decimal 13

                      • \v, vertical tab, decimal 11

                      • Non-breaking space, decimal 160

                      COMPRESS_WHITE_SPACE also replaces multiple spaces with one space.

                      CSS_DECODE - Decode characters that were encoded using CSS 2.x escape rules syndata.html#characters. This function uses up to two bytes in the decoding process, so it can help to uncover ASCII characters that were encoded using CSS encoding that wouldn’t typically be encoded. It's also useful in countering evasion, which is a combination of a backslash and non-hexadecimal characters. For example, ja\vascript for javascript.

                      ESCAPE_SEQ_DECODE - Decode the following ANSI C escape sequences: \a, \b, \f, \n, \r, \t, \v, \, \?, \', \", \xHH (hexadecimal), \0OOO (octal). Encodings that aren't valid remain in the output.

                      HEX_DECODE - Decode a string of hexadecimal characters into a binary.

                      HTML_ENTITY_DECODE - Replace HTML-encoded characters with unencoded characters. HTML_ENTITY_DECODE performs these operations:

                      • Replaces (ampersand)quot; with "

                      • Replaces (ampersand)nbsp; with a non-breaking space, decimal 160

                      • Replaces (ampersand)lt; with a "less than" symbol

                      • Replaces (ampersand)gt; with >

                      • Replaces characters that are represented in hexadecimal format, (ampersand)#xhhhh;, with the corresponding characters

                      • Replaces characters that are represented in decimal format, (ampersand)#nnnn;, with the corresponding characters

                      JS_DECODE - Decode JavaScript escape sequences. If a \ u HHHH code is in the full-width ASCII code range of FF01-FF5E, then the higher byte is used to detect and adjust the lower byte. If not, only the lower byte is used and the higher byte is zeroed, causing a possible loss of information.

                      LOWERCASE - Convert uppercase letters (A-Z) to lowercase (a-z).

                      MD5 - Calculate an MD5 hash from the data in the input. The computed hash is in a raw binary form.

                      NONE - Specify NONE if you don't want any text transformations.

                      NORMALIZE_PATH - Remove multiple slashes, directory self-references, and directory back-references that are not at the beginning of the input from an input string.

                      NORMALIZE_PATH_WIN - This is the same as NORMALIZE_PATH, but first converts backslash characters to forward slashes.

                      REMOVE_NULLS - Remove all NULL bytes from the input.

                      REPLACE_COMMENTS - Replace each occurrence of a C-style comment (/* ... */) with a single space. Multiple consecutive occurrences are not compressed. Unterminated comments are also replaced with a space (ASCII 0x20). However, a standalone termination of a comment (*/) is not acted upon.

                      REPLACE_NULLS - Replace NULL bytes in the input with space characters (ASCII 0x20).

                      SQL_HEX_DECODE - Decode SQL hex data. Example (0x414243) will be decoded to (ABC).

                      URL_DECODE - Decode a URL-encoded value.

                      URL_DECODE_UNI - Like URL_DECODE, but with support for Microsoft-specific %u encoding. If the code is in the full-width ASCII code range of FF01-FF5E, the higher byte is used to detect and adjust the lower byte. Otherwise, only the lower byte is used and the higher byte is zeroed.

                      UTF8_TO_UNICODE - Convert all UTF-8 character sequences to Unicode. This helps input normalization, and minimizing false-positives and false-negatives for non-English languages.

                      Possible values include:
                      • "NONE"
                      • "COMPRESS_WHITE_SPACE"
                      • "HTML_ENTITY_DECODE"
                      • "LOWERCASE"
                      • "CMD_LINE"
                      • "URL_DECODE"
                      • "BASE64_DECODE"
                      • "HEX_DECODE"
                      • "MD5"
                      • "REPLACE_COMMENTS"
                      • "ESCAPE_SEQ_DECODE"
                      • "SQL_HEX_DECODE"
                      • "CSS_DECODE"
                      • "JS_DECODE"
                      • "NORMALIZE_PATH"
                      • "NORMALIZE_PATH_WIN"
                      • "REMOVE_NULLS"
                      • "REPLACE_NULLS"
                      • "BASE64_DECODE_EXT"
                      • "URL_DECODE_UNI"
                      • "UTF8_TO_UNICODE"
                • XssMatchStatement — (map)

                  A rule statement that defines a cross-site scripting (XSS) match search for WAF to apply to web requests. XSS attacks are those where the attacker uses vulnerabilities in a benign website as a vehicle to inject malicious client-site scripts into other legitimate web browsers. The XSS match statement provides the location in requests that you want WAF to search and text transformations to use on the search area before WAF searches for character sequences that are likely to be malicious strings.

                  • FieldToMatch — required — (map)

                    The part of a web request that you want WAF to inspect. For more information, see FieldToMatch.

                    • SingleHeader — (map)

                      Inspect a single header. Provide the name of the header to inspect, for example, User-Agent or Referer. This setting isn't case sensitive.

                      Example JSON: "SingleHeader": { "Name": "haystack" }

                      • Name — required — (String)

                        The name of the query header to inspect.

                    • SingleQueryArgument — (map)

                      Inspect a single query argument. Provide the name of the query argument to inspect, such as UserName or SalesRegion. The name can be up to 30 characters long and isn't case sensitive.

                      This is used only to indicate the web request component for WAF to inspect, in the FieldToMatch specification.

                      Example JSON: "SingleQueryArgument": { "Name": "myArgument" }

                      • Name — required — (String)

                        The name of the query argument to inspect.

                    • AllQueryArguments — (map)

                      Inspect all query arguments.

                    • UriPath — (map)

                      Inspect the request URI path. This is the part of a web request that identifies a resource, for example, /images/daily-ad.jpg.

                    • QueryString — (map)

                      Inspect the query string. This is the part of a URL that appears after a ? character, if any.

                    • Body — (map)

                      Inspect the request body as plain text. The request body immediately follows the request headers. This is the part of a request that contains any additional data that you want to send to your web server as the HTTP request body, such as data from a form.

                      Note that only the first 8 KB (8192 bytes) of the request body are forwarded to WAF for inspection by the underlying host service. If you don't need to inspect more than 8 KB, you can guarantee that you don't allow additional bytes in by combining a statement that inspects the body of the web request, such as ByteMatchStatement or RegexPatternSetReferenceStatement, with a SizeConstraintStatement that enforces an 8 KB size limit on the body of the request. WAF doesn't support inspecting the entire contents of web requests whose bodies exceed the 8 KB limit.

                    • Method — (map)

                      Inspect the HTTP method. The method indicates the type of operation that the request is asking the origin to perform.

                    • JsonBody — (map)

                      Inspect the request body as JSON. The request body immediately follows the request headers. This is the part of a request that contains any additional data that you want to send to your web server as the HTTP request body, such as data from a form.

                      Note that only the first 8 KB (8192 bytes) of the request body are forwarded to WAF for inspection by the underlying host service. If you don't need to inspect more than 8 KB, you can guarantee that you don't allow additional bytes in by combining a statement that inspects the body of the web request, such as ByteMatchStatement or RegexPatternSetReferenceStatement, with a SizeConstraintStatement that enforces an 8 KB size limit on the body of the request. WAF doesn't support inspecting the entire contents of web requests whose bodies exceed the 8 KB limit.

                      • MatchPattern — required — (map)

                        The patterns to look for in the JSON body. WAF inspects the results of these pattern matches against the rule inspection criteria.

                        • All — (map)

                          Match all of the elements. See also MatchScope in JsonBody.

                          You must specify either this setting or the IncludedPaths setting, but not both.

                        • IncludedPaths — (Array<String>)

                          Match only the specified include paths. See also MatchScope in JsonBody.

                          Provide the include paths using JSON Pointer syntax. For example, "IncludedPaths": ["/dogs/0/name", "/dogs/1/name"]. For information about this syntax, see the Internet Engineering Task Force (IETF) documentation JavaScript Object Notation (JSON) Pointer.

                          You must specify either this setting or the All setting, but not both.

                          Note: Don't use this option to include all paths. Instead, use the All setting.
                      • MatchScope — required — (String)

                        The parts of the JSON to match against using the MatchPattern. If you specify All, WAF matches against keys and values.

                        Possible values include:
                        • "ALL"
                        • "KEY"
                        • "VALUE"
                      • InvalidFallbackBehavior — (String)

                        What WAF should do if it fails to completely parse the JSON body. The options are the following:

                        • EVALUATE_AS_STRING - Inspect the body as plain text. WAF applies the text transformations and inspection criteria that you defined for the JSON inspection to the body text string.

                        • MATCH - Treat the web request as matching the rule statement. WAF applies the rule action to the request.

                        • NO_MATCH - Treat the web request as not matching the rule statement.

                        If you don't provide this setting, WAF parses and evaluates the content only up to the first parsing failure that it encounters.

                        WAF does its best to parse the entire JSON body, but might be forced to stop for reasons such as invalid characters, duplicate keys, truncation, and any content whose root node isn't an object or an array.

                        WAF parses the JSON in the following examples as two valid key, value pairs:

                        • Missing comma: {"key1":"value1""key2":"value2"}

                        • Missing colon: {"key1":"value1","key2""value2"}

                        • Extra colons: {"key1"::"value1","key2""value2"}

                        Possible values include:
                        • "MATCH"
                        • "NO_MATCH"
                        • "EVALUATE_AS_STRING"
                  • TextTransformations — required — (Array<map>)

                    Text transformations eliminate some of the unusual formatting that attackers use in web requests in an effort to bypass detection. If you specify one or more transformations in a rule statement, WAF performs all transformations on the content of the request component identified by FieldToMatch, starting from the lowest priority setting, before inspecting the content for a match.

                    • Priority — required — (Integer)

                      Sets the relative processing order for multiple transformations that are defined for a rule statement. WAF processes all transformations, from lowest priority to highest, before inspecting the transformed content. The priorities don't need to be consecutive, but they must all be different.

                    • Type — required — (String)

                      You can specify the following transformation types:

                      BASE64_DECODE - Decode a Base64-encoded string.

                      BASE64_DECODE_EXT - Decode a Base64-encoded string, but use a forgiving implementation that ignores characters that aren't valid.

                      CMD_LINE - Command-line transformations. These are helpful in reducing effectiveness of attackers who inject an operating system command-line command and use unusual formatting to disguise some or all of the command.

                      • Delete the following characters: \ " ' ^

                      • Delete spaces before the following characters: / (

                      • Replace the following characters with a space: , ;

                      • Replace multiple spaces with one space

                      • Convert uppercase letters (A-Z) to lowercase (a-z)

                      COMPRESS_WHITE_SPACE - Replace these characters with a space character (decimal 32):

                      • \f, formfeed, decimal 12

                      • \t, tab, decimal 9

                      • \n, newline, decimal 10

                      • \r, carriage return, decimal 13

                      • \v, vertical tab, decimal 11

                      • Non-breaking space, decimal 160

                      COMPRESS_WHITE_SPACE also replaces multiple spaces with one space.

                      CSS_DECODE - Decode characters that were encoded using CSS 2.x escape rules syndata.html#characters. This function uses up to two bytes in the decoding process, so it can help to uncover ASCII characters that were encoded using CSS encoding that wouldn’t typically be encoded. It's also useful in countering evasion, which is a combination of a backslash and non-hexadecimal characters. For example, ja\vascript for javascript.

                      ESCAPE_SEQ_DECODE - Decode the following ANSI C escape sequences: \a, \b, \f, \n, \r, \t, \v, \, \?, \', \", \xHH (hexadecimal), \0OOO (octal). Encodings that aren't valid remain in the output.

                      HEX_DECODE - Decode a string of hexadecimal characters into a binary.

                      HTML_ENTITY_DECODE - Replace HTML-encoded characters with unencoded characters. HTML_ENTITY_DECODE performs these operations:

                      • Replaces (ampersand)quot; with "

                      • Replaces (ampersand)nbsp; with a non-breaking space, decimal 160

                      • Replaces (ampersand)lt; with a "less than" symbol

                      • Replaces (ampersand)gt; with >

                      • Replaces characters that are represented in hexadecimal format, (ampersand)#xhhhh;, with the corresponding characters

                      • Replaces characters that are represented in decimal format, (ampersand)#nnnn;, with the corresponding characters

                      JS_DECODE - Decode JavaScript escape sequences. If a \ u HHHH code is in the full-width ASCII code range of FF01-FF5E, then the higher byte is used to detect and adjust the lower byte. If not, only the lower byte is used and the higher byte is zeroed, causing a possible loss of information.

                      LOWERCASE - Convert uppercase letters (A-Z) to lowercase (a-z).

                      MD5 - Calculate an MD5 hash from the data in the input. The computed hash is in a raw binary form.

                      NONE - Specify NONE if you don't want any text transformations.

                      NORMALIZE_PATH - Remove multiple slashes, directory self-references, and directory back-references that are not at the beginning of the input from an input string.

                      NORMALIZE_PATH_WIN - This is the same as NORMALIZE_PATH, but first converts backslash characters to forward slashes.

                      REMOVE_NULLS - Remove all NULL bytes from the input.

                      REPLACE_COMMENTS - Replace each occurrence of a C-style comment (/* ... */) with a single space. Multiple consecutive occurrences are not compressed. Unterminated comments are also replaced with a space (ASCII 0x20). However, a standalone termination of a comment (*/) is not acted upon.

                      REPLACE_NULLS - Replace NULL bytes in the input with space characters (ASCII 0x20).

                      SQL_HEX_DECODE - Decode SQL hex data. Example (0x414243) will be decoded to (ABC).

                      URL_DECODE - Decode a URL-encoded value.

                      URL_DECODE_UNI - Like URL_DECODE, but with support for Microsoft-specific %u encoding. If the code is in the full-width ASCII code range of FF01-FF5E, the higher byte is used to detect and adjust the lower byte. Otherwise, only the lower byte is used and the higher byte is zeroed.

                      UTF8_TO_UNICODE - Convert all UTF-8 character sequences to Unicode. This helps input normalization, and minimizing false-positives and false-negatives for non-English languages.

                      Possible values include:
                      • "NONE"
                      • "COMPRESS_WHITE_SPACE"
                      • "HTML_ENTITY_DECODE"
                      • "LOWERCASE"
                      • "CMD_LINE"
                      • "URL_DECODE"
                      • "BASE64_DECODE"
                      • "HEX_DECODE"
                      • "MD5"
                      • "REPLACE_COMMENTS"
                      • "ESCAPE_SEQ_DECODE"
                      • "SQL_HEX_DECODE"
                      • "CSS_DECODE"
                      • "JS_DECODE"
                      • "NORMALIZE_PATH"
                      • "NORMALIZE_PATH_WIN"
                      • "REMOVE_NULLS"
                      • "REPLACE_NULLS"
                      • "BASE64_DECODE_EXT"
                      • "URL_DECODE_UNI"
                      • "UTF8_TO_UNICODE"
                • SizeConstraintStatement — (map)

                  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 first 8192 bytes (8 KB). If the request body for your web requests never exceeds 8192 bytes, you can create a size constraint condition and block requests that have a request body greater than 8192 bytes.

                  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.

                  • FieldToMatch — required — (map)

                    The part of a web request that you want WAF to inspect. For more information, see FieldToMatch.

                    • SingleHeader — (map)

                      Inspect a single header. Provide the name of the header to inspect, for example, User-Agent or Referer. This setting isn't case sensitive.

                      Example JSON: "SingleHeader": { "Name": "haystack" }

                      • Name — required — (String)

                        The name of the query header to inspect.

                    • SingleQueryArgument — (map)

                      Inspect a single query argument. Provide the name of the query argument to inspect, such as UserName or SalesRegion. The name can be up to 30 characters long and isn't case sensitive.

                      This is used only to indicate the web request component for WAF to inspect, in the FieldToMatch specification.

                      Example JSON: "SingleQueryArgument": { "Name": "myArgument" }

                      • Name — required — (String)

                        The name of the query argument to inspect.

                    • AllQueryArguments — (map)

                      Inspect all query arguments.

                    • UriPath — (map)

                      Inspect the request URI path. This is the part of a web request that identifies a resource, for example, /images/daily-ad.jpg.

                    • QueryString — (map)

                      Inspect the query string. This is the part of a URL that appears after a ? character, if any.

                    • Body — (map)

                      Inspect the request body as plain text. The request body immediately follows the request headers. This is the part of a request that contains any additional data that you want to send to your web server as the HTTP request body, such as data from a form.

                      Note that only the first 8 KB (8192 bytes) of the request body are forwarded to WAF for inspection by the underlying host service. If you don't need to inspect more than 8 KB, you can guarantee that you don't allow additional bytes in by combining a statement that inspects the body of the web request, such as ByteMatchStatement or RegexPatternSetReferenceStatement, with a SizeConstraintStatement that enforces an 8 KB size limit on the body of the request. WAF doesn't support inspecting the entire contents of web requests whose bodies exceed the 8 KB limit.

                    • Method — (map)

                      Inspect the HTTP method. The method indicates the type of operation that the request is asking the origin to perform.

                    • JsonBody — (map)

                      Inspect the request body as JSON. The request body immediately follows the request headers. This is the part of a request that contains any additional data that you want to send to your web server as the HTTP request body, such as data from a form.

                      Note that only the first 8 KB (8192 bytes) of the request body are forwarded to WAF for inspection by the underlying host service. If you don't need to inspect more than 8 KB, you can guarantee that you don't allow additional bytes in by combining a statement that inspects the body of the web request, such as ByteMatchStatement or RegexPatternSetReferenceStatement, with a SizeConstraintStatement that enforces an 8 KB size limit on the body of the request. WAF doesn't support inspecting the entire contents of web requests whose bodies exceed the 8 KB limit.

                      • MatchPattern — required — (map)

                        The patterns to look for in the JSON body. WAF inspects the results of these pattern matches against the rule inspection criteria.

                        • All — (map)

                          Match all of the elements. See also MatchScope in JsonBody.

                          You must specify either this setting or the IncludedPaths setting, but not both.

                        • IncludedPaths — (Array<String>)

                          Match only the specified include paths. See also MatchScope in JsonBody.

                          Provide the include paths using JSON Pointer syntax. For example, "IncludedPaths": ["/dogs/0/name", "/dogs/1/name"]. For information about this syntax, see the Internet Engineering Task Force (IETF) documentation JavaScript Object Notation (JSON) Pointer.

                          You must specify either this setting or the All setting, but not both.

                          Note: Don't use this option to include all paths. Instead, use the All setting.
                      • MatchScope — required — (String)

                        The parts of the JSON to match against using the MatchPattern. If you specify All, WAF matches against keys and values.

                        Possible values include:
                        • "ALL"
                        • "KEY"
                        • "VALUE"
                      • InvalidFallbackBehavior — (String)

                        What WAF should do if it fails to completely parse the JSON body. The options are the following:

                        • EVALUATE_AS_STRING - Inspect the body as plain text. WAF applies the text transformations and inspection criteria that you defined for the JSON inspection to the body text string.

                        • MATCH - Treat the web request as matching the rule statement. WAF applies the rule action to the request.

                        • NO_MATCH - Treat the web request as not matching the rule statement.

                        If you don't provide this setting, WAF parses and evaluates the content only up to the first parsing failure that it encounters.

                        WAF does its best to parse the entire JSON body, but might be forced to stop for reasons such as invalid characters, duplicate keys, truncation, and any content whose root node isn't an object or an array.

                        WAF parses the JSON in the following examples as two valid key, value pairs:

                        • Missing comma: {"key1":"value1""key2":"value2"}

                        • Missing colon: {"key1":"value1","key2""value2"}

                        • Extra colons: {"key1"::"value1","key2""value2"}

                        Possible values include:
                        • "MATCH"
                        • "NO_MATCH"
                        • "EVALUATE_AS_STRING"
                  • ComparisonOperator — required — (String)

                    The operator to use to compare the request part to the size setting.

                    Possible values include:
                    • "EQ"
                    • "NE"
                    • "LE"
                    • "LT"
                    • "GE"
                    • "GT"
                  • Size — required — (Integer)

                    The size, in byte, to compare to the request part, after any transformations.

                  • TextTransformations — required — (Array<map>)

                    Text transformations eliminate some of the unusual formatting that attackers use in web requests in an effort to bypass detection. If you specify one or more transformations in a rule statement, WAF performs all transformations on the content of the request component identified by FieldToMatch, starting from the lowest priority setting, before inspecting the content for a match.

                    • Priority — required — (Integer)

                      Sets the relative processing order for multiple transformations that are defined for a rule statement. WAF processes all transformations, from lowest priority to highest, before inspecting the transformed content. The priorities don't need to be consecutive, but they must all be different.

                    • Type — required — (String)

                      You can specify the following transformation types:

                      BASE64_DECODE - Decode a Base64-encoded string.

                      BASE64_DECODE_EXT - Decode a Base64-encoded string, but use a forgiving implementation that ignores characters that aren't valid.

                      CMD_LINE - Command-line transformations. These are helpful in reducing effectiveness of attackers who inject an operating system command-line command and use unusual formatting to disguise some or all of the command.

                      • Delete the following characters: \ " ' ^

                      • Delete spaces before the following characters: / (

                      • Replace the following characters with a space: , ;

                      • Replace multiple spaces with one space

                      • Convert uppercase letters (A-Z) to lowercase (a-z)

                      COMPRESS_WHITE_SPACE - Replace these characters with a space character (decimal 32):

                      • \f, formfeed, decimal 12

                      • \t, tab, decimal 9

                      • \n, newline, decimal 10

                      • \r, carriage return, decimal 13

                      • \v, vertical tab, decimal 11

                      • Non-breaking space, decimal 160

                      COMPRESS_WHITE_SPACE also replaces multiple spaces with one space.

                      CSS_DECODE - Decode characters that were encoded using CSS 2.x escape rules syndata.html#characters. This function uses up to two bytes in the decoding process, so it can help to uncover ASCII characters that were encoded using CSS encoding that wouldn’t typically be encoded. It's also useful in countering evasion, which is a combination of a backslash and non-hexadecimal characters. For example, ja\vascript for javascript.

                      ESCAPE_SEQ_DECODE - Decode the following ANSI C escape sequences: \a, \b, \f, \n, \r, \t, \v, \, \?, \', \", \xHH (hexadecimal), \0OOO (octal). Encodings that aren't valid remain in the output.

                      HEX_DECODE - Decode a string of hexadecimal characters into a binary.

                      HTML_ENTITY_DECODE - Replace HTML-encoded characters with unencoded characters. HTML_ENTITY_DECODE performs these operations:

                      • Replaces (ampersand)quot; with "

                      • Replaces (ampersand)nbsp; with a non-breaking space, decimal 160

                      • Replaces (ampersand)lt; with a "less than" symbol

                      • Replaces (ampersand)gt; with >

                      • Replaces characters that are represented in hexadecimal format, (ampersand)#xhhhh;, with the corresponding characters

                      • Replaces characters that are represented in decimal format, (ampersand)#nnnn;, with the corresponding characters

                      JS_DECODE - Decode JavaScript escape sequences. If a \ u HHHH code is in the full-width ASCII code range of FF01-FF5E, then the higher byte is used to detect and adjust the lower byte. If not, only the lower byte is used and the higher byte is zeroed, causing a possible loss of information.

                      LOWERCASE - Convert uppercase letters (A-Z) to lowercase (a-z).

                      MD5 - Calculate an MD5 hash from the data in the input. The computed hash is in a raw binary form.

                      NONE - Specify NONE if you don't want any text transformations.

                      NORMALIZE_PATH - Remove multiple slashes, directory self-references, and directory back-references that are not at the beginning of the input from an input string.

                      NORMALIZE_PATH_WIN - This is the same as NORMALIZE_PATH, but first converts backslash characters to forward slashes.

                      REMOVE_NULLS - Remove all NULL bytes from the input.

                      REPLACE_COMMENTS - Replace each occurrence of a C-style comment (/* ... */) with a single space. Multiple consecutive occurrences are not compressed. Unterminated comments are also replaced with a space (ASCII 0x20). However, a standalone termination of a comment (*/) is not acted upon.

                      REPLACE_NULLS - Replace NULL bytes in the input with space characters (ASCII 0x20).

                      SQL_HEX_DECODE - Decode SQL hex data. Example (0x414243) will be decoded to (ABC).

                      URL_DECODE - Decode a URL-encoded value.

                      URL_DECODE_UNI - Like URL_DECODE, but with support for Microsoft-specific %u encoding. If the code is in the full-width ASCII code range of FF01-FF5E, the higher byte is used to detect and adjust the lower byte. Otherwise, only the lower byte is used and the higher byte is zeroed.

                      UTF8_TO_UNICODE - Convert all UTF-8 character sequences to Unicode. This helps input normalization, and minimizing false-positives and false-negatives for non-English languages.

                      Possible values include:
                      • "NONE"
                      • "COMPRESS_WHITE_SPACE"
                      • "HTML_ENTITY_DECODE"
                      • "LOWERCASE"
                      • "CMD_LINE"
                      • "URL_DECODE"
                      • "BASE64_DECODE"
                      • "HEX_DECODE"
                      • "MD5"
                      • "REPLACE_COMMENTS"
                      • "ESCAPE_SEQ_DECODE"
                      • "SQL_HEX_DECODE"
                      • "CSS_DECODE"
                      • "JS_DECODE"
                      • "NORMALIZE_PATH"
                      • "NORMALIZE_PATH_WIN"
                      • "REMOVE_NULLS"
                      • "REPLACE_NULLS"
                      • "BASE64_DECODE_EXT"
                      • "URL_DECODE_UNI"
                      • "UTF8_TO_UNICODE"
                • GeoMatchStatement — (map)

                  A rule statement used to identify web requests based on country of origin.

                  • CountryCodes — (Array<String>)

                    An array of two-character country codes, for example, [ "US", "CN" ], from the alpha-2 country ISO codes of the ISO 3166 international standard.

                  • ForwardedIPConfig — (map)

                    The configuration for inspecting IP addresses in an HTTP header that you specify, instead of using the IP address that's reported by the web request origin. Commonly, this is the X-Forwarded-For (XFF) header, but you can specify any header name.

                    Note: If the specified header isn't present in the request, WAF doesn't apply the rule to the web request at all.
                    • HeaderName — required — (String)

                      The name of the HTTP header to use for the IP address. For example, to use the X-Forwarded-For (XFF) header, set this to X-Forwarded-For.

                      Note: If the specified header isn't present in the request, WAF doesn't apply the rule to the web request at all.
                    • FallbackBehavior — required — (String)

                      The match status to assign to the web request if the request doesn't have a valid IP address in the specified position.

                      Note: If the specified header isn't present in the request, WAF doesn't apply the rule to the web request at all.

                      You can specify the following fallback behaviors:

                      • MATCH - Treat the web request as matching the rule statement. WAF applies the rule action to the request.

                      • NO_MATCH - Treat the web request as not matching the rule statement.

                      Possible values include:
                      • "MATCH"
                      • "NO_MATCH"
                • RuleGroupReferenceStatement — (map)

                  A rule statement used to run the rules that are defined in a RuleGroup. To use this, create a rule group with your rules, then provide the ARN of the rule group in this statement.

                  You cannot nest a RuleGroupReferenceStatement, for example for use inside a NotStatement or OrStatement. You can only use a rule group reference statement at the top level inside a web ACL.

                  • ARN — required — (String)

                    The Amazon Resource Name (ARN) of the entity.

                  • ExcludedRules — (Array<map>)

                    The rules in the referenced rule group whose actions are set to Count. When you exclude a rule, WAF evaluates it exactly as it would if the rule action setting were Count. This is a useful option for testing the rules in a rule group without modifying how they handle your web traffic.

                    • Name — required — (String)

                      The name of the rule whose action you want to override to Count.

                • IPSetReferenceStatement — (map)

                  A rule statement used to detect web requests coming from particular IP addresses or address ranges. To use this, create an IPSet that specifies the addresses you want to detect, then use the ARN of that set in this statement. To create an IP set, see CreateIPSet.

                  Each IP set rule statement references an IP set. You create and maintain the set independent of your rules. This allows you to use the single set in multiple rules. When you update the referenced set, WAF automatically updates all rules that reference it.

                  • ARN — required — (String)

                    The Amazon Resource Name (ARN) of the IPSet that this statement references.

                  • IPSetForwardedIPConfig — (map)

                    The configuration for inspecting IP addresses in an HTTP header that you specify, instead of using the IP address that's reported by the web request origin. Commonly, this is the X-Forwarded-For (XFF) header, but you can specify any header name.

                    Note: If the specified header isn't present in the request, WAF doesn't apply the rule to the web request at all.
                    • HeaderName — required — (String)

                      The name of the HTTP header to use for the IP address. For example, to use the X-Forwarded-For (XFF) header, set this to X-Forwarded-For.

                      Note: If the specified header isn't present in the request, WAF doesn't apply the rule to the web request at all.
                    • FallbackBehavior — required — (String)

                      The match status to assign to the web request if the request doesn't have a valid IP address in the specified position.

                      Note: If the specified header isn't present in the request, WAF doesn't apply the rule to the web request at all.

                      You can specify the following fallback behaviors:

                      • MATCH - Treat the web request as matching the rule statement. WAF applies the rule action to the request.

                      • NO_MATCH - Treat the web request as not matching the rule statement.

                      Possible values include:
                      • "MATCH"
                      • "NO_MATCH"
                    • Position — required — (String)

                      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:

                      • FIRST - Inspect the first IP address in the list of IP addresses in the header. This is usually the client's original IP.

                      • LAST - Inspect the last IP address in the list of IP addresses in the header.

                      • ANY - Inspect all IP addresses in the header for a match. If the header contains more than 10 IP addresses, WAF inspects the last 10.

                      Possible values include:
                      • "FIRST"
                      • "LAST"
                      • "ANY"
                • RegexPatternSetReferenceStatement — (map)

                  A rule statement used to search web request components for matches with regular expressions. To use this, create a RegexPatternSet that specifies the expressions that you want to detect, then use the ARN of that set in this statement. A web request matches the pattern set rule statement if the request component matches any of the patterns in the set. To create a regex pattern set, see CreateRegexPatternSet.

                  Each regex pattern set rule statement references a regex pattern set. You create and maintain the set independent of your rules. This allows you to use the single set in multiple rules. When you update the referenced set, WAF automatically updates all rules that reference it.

                  • ARN — required — (String)

                    The Amazon Resource Name (ARN) of the RegexPatternSet that this statement references.

                  • FieldToMatch — required — (map)

                    The part of a web request that you want WAF to inspect. For more information, see FieldToMatch.

                    • SingleHeader — (map)

                      Inspect a single header. Provide the name of the header to inspect, for example, User-Agent or Referer. This setting isn't case sensitive.

                      Example JSON: "SingleHeader": { "Name": "haystack" }

                      • Name — required — (String)

                        The name of the query header to inspect.

                    • SingleQueryArgument — (map)

                      Inspect a single query argument. Provide the name of the query argument to inspect, such as UserName or SalesRegion. The name can be up to 30 characters long and isn't case sensitive.

                      This is used only to indicate the web request component for WAF to inspect, in the FieldToMatch specification.

                      Example JSON: "SingleQueryArgument": { "Name": "myArgument" }

                      • Name — required — (String)

                        The name of the query argument to inspect.

                    • AllQueryArguments — (map)

                      Inspect all query arguments.

                    • UriPath — (map)

                      Inspect the request URI path. This is the part of a web request that identifies a resource, for example, /images/daily-ad.jpg.

                    • QueryString — (map)

                      Inspect the query string. This is the part of a URL that appears after a ? character, if any.

                    • Body — (map)

                      Inspect the request body as plain text. The request body immediately follows the request headers. This is the part of a request that contains any additional data that you want to send to your web server as the HTTP request body, such as data from a form.

                      Note that only the first 8 KB (8192 bytes) of the request body are forwarded to WAF for inspection by the underlying host service. If you don't need to inspect more than 8 KB, you can guarantee that you don't allow additional bytes in by combining a statement that inspects the body of the web request, such as ByteMatchStatement or RegexPatternSetReferenceStatement, with a SizeConstraintStatement that enforces an 8 KB size limit on the body of the request. WAF doesn't support inspecting the entire contents of web requests whose bodies exceed the 8 KB limit.

                    • Method — (map)

                      Inspect the HTTP method. The method indicates the type of operation that the request is asking the origin to perform.

                    • JsonBody — (map)

                      Inspect the request body as JSON. The request body immediately follows the request headers. This is the part of a request that contains any additional data that you want to send to your web server as the HTTP request body, such as data from a form.

                      Note that only the first 8 KB (8192 bytes) of the request body are forwarded to WAF for inspection by the underlying host service. If you don't need to inspect more than 8 KB, you can guarantee that you don't allow additional bytes in by combining a statement that inspects the body of the web request, such as ByteMatchStatement or RegexPatternSetReferenceStatement, with a SizeConstraintStatement that enforces an 8 KB size limit on the body of the request. WAF doesn't support inspecting the entire contents of web requests whose bodies exceed the 8 KB limit.

                      • MatchPattern — required — (map)

                        The patterns to look for in the JSON body. WAF inspects the results of these pattern matches against the rule inspection criteria.

                        • All — (map)

                          Match all of the elements. See also MatchScope in JsonBody.

                          You must specify either this setting or the IncludedPaths setting, but not both.

                        • IncludedPaths — (Array<String>)

                          Match only the specified include paths. See also MatchScope in JsonBody.

                          Provide the include paths using JSON Pointer syntax. For example, "IncludedPaths": ["/dogs/0/name", "/dogs/1/name"]. For information about this syntax, see the Internet Engineering Task Force (IETF) documentation JavaScript Object Notation (JSON) Pointer.

                          You must specify either this setting or the All setting, but not both.

                          Note: Don't use this option to include all paths. Instead, use the All setting.
                      • MatchScope — required — (String)

                        The parts of the JSON to match against using the MatchPattern. If you specify All, WAF matches against keys and values.

                        Possible values include:
                        • "ALL"
                        • "KEY"
                        • "VALUE"
                      • InvalidFallbackBehavior — (String)

                        What WAF should do if it fails to completely parse the JSON body. The options are the following:

                        • EVALUATE_AS_STRING - Inspect the body as plain text. WAF applies the text transformations and inspection criteria that you defined for the JSON inspection to the body text string.

                        • MATCH - Treat the web request as matching the rule statement. WAF applies the rule action to the request.

                        • NO_MATCH - Treat the web request as not matching the rule statement.

                        If you don't provide this setting, WAF parses and evaluates the content only up to the first parsing failure that it encounters.

                        WAF does its best to parse the entire JSON body, but might be forced to stop for reasons such as invalid characters, duplicate keys, truncation, and any content whose root node isn't an object or an array.

                        WAF parses the JSON in the following examples as two valid key, value pairs:

                        • Missing comma: {"key1":"value1""key2":"value2"}

                        • Missing colon: {"key1":"value1","key2""value2"}

                        • Extra colons: {"key1"::"value1","key2""value2"}

                        Possible values include:
                        • "MATCH"
                        • "NO_MATCH"
                        • "EVALUATE_AS_STRING"
                  • TextTransformations — required — (Array<map>)

                    Text transformations eliminate some of the unusual formatting that attackers use in web requests in an effort to bypass detection. If you specify one or more transformations in a rule statement, WAF performs all transformations on the content of the request component identified by FieldToMatch, starting from the lowest priority setting, before inspecting the content for a match.

                    • Priority — required — (Integer)

                      Sets the relative processing order for multiple transformations that are defined for a rule statement. WAF processes all transformations, from lowest priority to highest, before inspecting the transformed content. The priorities don't need to be consecutive, but they must all be different.

                    • Type — required — (String)

                      You can specify the following transformation types:

                      BASE64_DECODE - Decode a Base64-encoded string.

                      BASE64_DECODE_EXT - Decode a Base64-encoded string, but use a forgiving implementation that ignores characters that aren't valid.

                      CMD_LINE - Command-line transformations. These are helpful in reducing effectiveness of attackers who inject an operating system command-line command and use unusual formatting to disguise some or all of the command.

                      • Delete the following characters: \ " ' ^

                      • Delete spaces before the following characters: / (

                      • Replace the following characters with a space: , ;

                      • Replace multiple spaces with one space

                      • Convert uppercase letters (A-Z) to lowercase (a-z)

                      COMPRESS_WHITE_SPACE - Replace these characters with a space character (decimal 32):

                      • \f, formfeed, decimal 12

                      • \t, tab, decimal 9

                      • \n, newline, decimal 10

                      • \r, carriage return, decimal 13

                      • \v, vertical tab, decimal 11

                      • Non-breaking space, decimal 160

                      COMPRESS_WHITE_SPACE also replaces multiple spaces with one space.

                      CSS_DECODE - Decode characters that were encoded using CSS 2.x escape rules syndata.html#characters. This function uses up to two bytes in the decoding process, so it can help to uncover ASCII characters that were encoded using CSS encoding that wouldn’t typically be encoded. It's also useful in countering evasion, which is a combination of a backslash and non-hexadecimal characters. For example, ja\vascript for javascript.

                      ESCAPE_SEQ_DECODE - Decode the following ANSI C escape sequences: \a, \b, \f, \n, \r, \t, \v, \, \?, \', \", \xHH (hexadecimal), \0OOO (octal). Encodings that aren't valid remain in the output.

                      HEX_DECODE - Decode a string of hexadecimal characters into a binary.

                      HTML_ENTITY_DECODE - Replace HTML-encoded characters with unencoded characters. HTML_ENTITY_DECODE performs these operations:

                      • Replaces (ampersand)quot; with "

                      • Replaces (ampersand)nbsp; with a non-breaking space, decimal 160

                      • Replaces (ampersand)lt; with a "less than" symbol

                      • Replaces (ampersand)gt; with >

                      • Replaces characters that are represented in hexadecimal format, (ampersand)#xhhhh;, with the corresponding characters

                      • Replaces characters that are represented in decimal format, (ampersand)#nnnn;, with the corresponding characters

                      JS_DECODE - Decode JavaScript escape sequences. If a \ u HHHH code is in the full-width ASCII code range of FF01-FF5E, then the higher byte is used to detect and adjust the lower byte. If not, only the lower byte is used and the higher byte is zeroed, causing a possible loss of information.

                      LOWERCASE - Convert uppercase letters (A-Z) to lowercase (a-z).

                      MD5 - Calculate an MD5 hash from the data in the input. The computed hash is in a raw binary form.

                      NONE - Specify NONE if you don't want any text transformations.

                      NORMALIZE_PATH - Remove multiple slashes, directory self-references, and directory back-references that are not at the beginning of the input from an input string.

                      NORMALIZE_PATH_WIN - This is the same as NORMALIZE_PATH, but first converts backslash characters to forward slashes.

                      REMOVE_NULLS - Remove all NULL bytes from the input.

                      REPLACE_COMMENTS - Replace each occurrence of a C-style comment (/* ... */) with a single space. Multiple consecutive occurrences are not compressed. Unterminated comments are also replaced with a space (ASCII 0x20). However, a standalone termination of a comment (*/) is not acted upon.

                      REPLACE_NULLS - Replace NULL bytes in the input with space characters (ASCII 0x20).

                      SQL_HEX_DECODE - Decode SQL hex data. Example (0x414243) will be decoded to (ABC).

                      URL_DECODE - Decode a URL-encoded value.

                      URL_DECODE_UNI - Like URL_DECODE, but with support for Microsoft-specific %u encoding. If the code is in the full-width ASCII code range of FF01-FF5E, the higher byte is used to detect and adjust the lower byte. Otherwise, only the lower byte is used and the higher byte is zeroed.

                      UTF8_TO_UNICODE - Convert all UTF-8 character sequences to Unicode. This helps input normalization, and minimizing false-positives and false-negatives for non-English languages.

                      Possible values include:
                      • "NONE"
                      • "COMPRESS_WHITE_SPACE"
                      • "HTML_ENTITY_DECODE"
                      • "LOWERCASE"
                      • "CMD_LINE"
                      • "URL_DECODE"
                      • "BASE64_DECODE"
                      • "HEX_DECODE"
                      • "MD5"
                      • "REPLACE_COMMENTS"
                      • "ESCAPE_SEQ_DECODE"
                      • "SQL_HEX_DECODE"
                      • "CSS_DECODE"
                      • "JS_DECODE"
                      • "NORMALIZE_PATH"
                      • "NORMALIZE_PATH_WIN"
                      • "REMOVE_NULLS"
                      • "REPLACE_NULLS"
                      • "BASE64_DECODE_EXT"
                      • "URL_DECODE_UNI"
                      • "UTF8_TO_UNICODE"
                • RateBasedStatement — (map)

                  A rate-based rule tracks the rate of requests for each originating IP address, and triggers the rule action when the rate exceeds a limit that you specify on the number of requests in any 5-minute time span. You can use this to put a temporary block on requests from an IP address that is sending excessive requests.

                  WAF tracks and manages web requests separately for each instance of a rate-based rule that you use. For example, if you provide the same rate-based rule settings in two web ACLs, each of the two rule statements represents a separate instance of the rate-based rule and gets its own tracking and management by WAF. If you define a rate-based rule inside a rule group, and then use that rule group in multiple places, each use creates a separate instance of the rate-based rule that gets its own tracking and management by WAF.

                  When the rule action triggers, WAF blocks additional requests from the IP address until the request rate falls below the limit.

                  You can optionally nest another statement inside the rate-based statement, to narrow the scope of the rule so that it only counts requests that match the nested statement. For example, based on recent requests that you have seen from an attacker, you might create a rate-based rule with a nested AND rule statement that contains the following nested statements:

                  • An IP match statement with an IP set that specified the address 192.0.2.44.

                  • A string match statement that searches in the User-Agent header for the string BadBot.

                  In this rate-based rule, you also define a rate limit. For this example, the rate limit is 1,000. Requests that meet both of the conditions in the statements are counted. If the count exceeds 1,000 requests per five minutes, the rule action triggers. Requests that do not meet both conditions are not counted towards the rate limit and are not affected by this rule.

                  You cannot nest a RateBasedStatement inside another statement, for example inside a NotStatement or OrStatement. You can define a RateBasedStatement inside a web ACL and inside a rule group.

                  • Limit — required — (Integer)

                    The limit on requests per 5-minute period for a single originating IP address. If the statement includes a ScopeDownStatement, this limit is applied only to the requests that match the statement.

                  • AggregateKeyType — required — (String)

                    Setting that indicates how to aggregate the request counts. The options are the following:

                    • IP - Aggregate the request counts on the IP address from the web request origin.

                    • FORWARDED_IP - Aggregate the request counts on the first IP address in an HTTP header. If you use this, configure the ForwardedIPConfig, to specify the header to use.

                    Possible values include:
                    • "IP"
                    • "FORWARDED_IP"
                  • ForwardedIPConfig — (map)

                    The configuration for inspecting IP addresses in an HTTP header that you specify, instead of using the IP address that's reported by the web request origin. Commonly, this is the X-Forwarded-For (XFF) header, but you can specify any header name.

                    Note: If the specified header isn't present in the request, WAF doesn't apply the rule to the web request at all.

                    This is required if AggregateKeyType is set to FORWARDED_IP.

                    • HeaderName — required — (String)

                      The name of the HTTP header to use for the IP address. For example, to use the X-Forwarded-For (XFF) header, set this to X-Forwarded-For.

                      Note: If the specified header isn't present in the request, WAF doesn't apply the rule to the web request at all.
                    • FallbackBehavior — required — (String)

                      The match status to assign to the web request if the request doesn't have a valid IP address in the specified position.

                      Note: If the specified header isn't present in the request, WAF doesn't apply the rule to the web request at all.

                      You can specify the following fallback behaviors:

                      • MATCH - Treat the web request as matching the rule statement. WAF applies the rule action to the request.

                      • NO_MATCH - Treat the web request as not matching the rule statement.

                      Possible values include:
                      • "MATCH"
                      • "NO_MATCH"
                • AndStatement — (map)

                  A logical rule statement used to combine other rule statements with AND logic. You provide more than one Statement within the AndStatement.

                  • Statements — required — (Array<map>)

                    The statements to combine with AND logic. You can use any statements that can be nested.

                • OrStatement — (map)

                  A logical rule statement used to combine other rule statements with OR logic. You provide more than one Statement within the OrStatement.

                  • Statements — required — (Array<map>)

                    The statements to combine with OR logic. You can use any statements that can be nested.

                • NotStatement — (map)

                  A logical rule statement used to negate the results of another rule statement. You provide one Statement within the NotStatement.

                • LabelMatchStatement — (map)

                  A rule statement that defines a string match search against labels that have been added to the web request by rules that have already run in the web ACL.

                  The label match statement provides the label or namespace string to search for. The label string can represent a part or all of the fully qualified label name that had been added to the web request. Fully qualified labels have a prefix, optional namespaces, and label name. The prefix identifies the rule group or web ACL context of the rule that added the label. If you do not provide the fully qualified name in your label match string, WAF performs the search for labels that were added in the same context as the label match statement.

                  • Scope — required — (String)

                    Specify whether you want to match using the label name or just the namespace.

                    Possible values include:
                    • "LABEL"
                    • "NAMESPACE"
                  • Key — required — (String)

                    The string to match against. The setting you provide for this depends on the match statement's Scope setting:

                    • If the Scope indicates LABEL, then this specification must include the name and can include any number of preceding namespace specifications and prefix up to providing the fully qualified label name.

                    • If the Scope indicates NAMESPACE, then this specification can include any number of contiguous namespace strings, and can include the entire label namespace prefix from the rule group or web ACL where the label originates.

                    Labels are case sensitive and components of a label must be separated by colon, for example NS1:NS2:name.

                • RegexMatchStatement — (map)

                  A rule statement used to search web request components for a match against a single regular expression.

                  • RegexString — required — (String)

                    The string representing the regular expression.

                  • FieldToMatch — required — (map)

                    The part of a web request that you want WAF to inspect. For more information, see FieldToMatch.

                    • SingleHeader — (map)

                      Inspect a single header. Provide the name of the header to inspect, for example, User-Agent or Referer. This setting isn't case sensitive.

                      Example JSON: "SingleHeader": { "Name": "haystack" }

                      • Name — required — (String)

                        The name of the query header to inspect.

                    • SingleQueryArgument — (map)

                      Inspect a single query argument. Provide the name of the query argument to inspect, such as UserName or SalesRegion. The name can be up to 30 characters long and isn't case sensitive.

                      This is used only to indicate the web request component for WAF to inspect, in the FieldToMatch specification.

                      Example JSON: "SingleQueryArgument": { "Name": "myArgument" }

                      • Name — required — (String)

                        The name of the query argument to inspect.

                    • AllQueryArguments — (map)

                      Inspect all query arguments.

                    • UriPath — (map)

                      Inspect the request URI path. This is the part of a web request that identifies a resource, for example, /images/daily-ad.jpg.

                    • QueryString — (map)

                      Inspect the query string. This is the part of a URL that appears after a ? character, if any.

                    • Body — (map)

                      Inspect the request body as plain text. The request body immediately follows the request headers. This is the part of a request that contains any additional data that you want to send to your web server as the HTTP request body, such as data from a form.

                      Note that only the first 8 KB (8192 bytes) of the request body are forwarded to WAF for inspection by the underlying host service. If you don't need to inspect more than 8 KB, you can guarantee that you don't allow additional bytes in by combining a statement that inspects the body of the web request, such as ByteMatchStatement or RegexPatternSetReferenceStatement, with a SizeConstraintStatement that enforces an 8 KB size limit on the body of the request. WAF doesn't support inspecting the entire contents of web requests whose bodies exceed the 8 KB limit.

                    • Method — (map)

                      Inspect the HTTP method. The method indicates the type of operation that the request is asking the origin to perform.

                    • JsonBody — (map)

                      Inspect the request body as JSON. The request body immediately follows the request headers. This is the part of a request that contains any additional data that you want to send to your web server as the HTTP request body, such as data from a form.

                      Note that only the first 8 KB (8192 bytes) of the request body are forwarded to WAF for inspection by the underlying host service. If you don't need to inspect more than 8 KB, you can guarantee that you don't allow additional bytes in by combining a statement that inspects the body of the web request, such as ByteMatchStatement or RegexPatternSetReferenceStatement, with a SizeConstraintStatement that enforces an 8 KB size limit on the body of the request. WAF doesn't support inspecting the entire contents of web requests whose bodies exceed the 8 KB limit.

                      • MatchPattern — required — (map)

                        The patterns to look for in the JSON body. WAF inspects the results of these pattern matches against the rule inspection criteria.

                        • All — (map)

                          Match all of the elements. See also MatchScope in JsonBody.

                          You must specify either this setting or the IncludedPaths setting, but not both.

                        • IncludedPaths — (Array<String>)

                          Match only the specified include paths. See also MatchScope in JsonBody.

                          Provide the include paths using JSON Pointer syntax. For example, "IncludedPaths": ["/dogs/0/name", "/dogs/1/name"]. For information about this syntax, see the Internet Engineering Task Force (IETF) documentation JavaScript Object Notation (JSON) Pointer.

                          You must specify either this setting or the All setting, but not both.

                          Note: Don't use this option to include all paths. Instead, use the All setting.
                      • MatchScope — required — (String)

                        The parts of the JSON to match against using the MatchPattern. If you specify All, WAF matches against keys and values.

                        Possible values include:
                        • "ALL"
                        • "KEY"
                        • "VALUE"
                      • InvalidFallbackBehavior — (String)

                        What WAF should do if it fails to completely parse the JSON body. The options are the following:

                        • EVALUATE_AS_STRING - Inspect the body as plain text. WAF applies the text transformations and inspection criteria that you defined for the JSON inspection to the body text string.

                        • MATCH - Treat the web request as matching the rule statement. WAF applies the rule action to the request.

                        • NO_MATCH - Treat the web request as not matching the rule statement.

                        If you don't provide this setting, WAF parses and evaluates the content only up to the first parsing failure that it encounters.

                        WAF does its best to parse the entire JSON body, but might be forced to stop for reasons such as invalid characters, duplicate keys, truncation, and any content whose root node isn't an object or an array.

                        WAF parses the JSON in the following examples as two valid key, value pairs:

                        • Missing comma: {"key1":"value1""key2":"value2"}

                        • Missing colon: {"key1":"value1","key2""value2"}

                        • Extra colons: {"key1"::"value1","key2""value2"}

                        Possible values include:
                        • "MATCH"
                        • "NO_MATCH"
                        • "EVALUATE_AS_STRING"
                  • TextTransformations — required — (Array<map>)

                    Text transformations eliminate some of the unusual formatting that attackers use in web requests in an effort to bypass detection. If you specify one or more transformations in a rule statement, WAF performs all transformations on the content of the request component identified by FieldToMatch, starting from the lowest priority setting, before inspecting the content for a match.

                    • Priority — required — (Integer)

                      Sets the relative processing order for multiple transformations that are defined for a rule statement. WAF processes all transformations, from lowest priority to highest, before inspecting the transformed content. The priorities don't need to be consecutive, but they must all be different.

                    • Type — required — (String)

                      You can specify the following transformation types:

                      BASE64_DECODE - Decode a Base64-encoded string.

                      BASE64_DECODE_EXT - Decode a Base64-encoded string, but use a forgiving implementation that ignores characters that aren't valid.

                      CMD_LINE - Command-line transformations. These are helpful in reducing effectiveness of attackers who inject an operating system command-line command and use unusual formatting to disguise some or all of the command.

                      • Delete the following characters: \ " ' ^

                      • Delete spaces before the following characters: / (

                      • Replace the following characters with a space: , ;

                      • Replace multiple spaces with one space

                      • Convert uppercase letters (A-Z) to lowercase (a-z)

                      COMPRESS_WHITE_SPACE - Replace these characters with a space character (decimal 32):

                      • \f, formfeed, decimal 12

                      • \t, tab, decimal 9

                      • \n, newline, decimal 10

                      • \r, carriage return, decimal 13

                      • \v, vertical tab, decimal 11

                      • Non-breaking space, decimal 160

                      COMPRESS_WHITE_SPACE also replaces multiple spaces with one space.

                      CSS_DECODE - Decode characters that were encoded using CSS 2.x escape rules syndata.html#characters. This function uses up to two bytes in the decoding process, so it can help to uncover ASCII characters that were encoded using CSS encoding that wouldn’t typically be encoded. It's also useful in countering evasion, which is a combination of a backslash and non-hexadecimal characters. For example, ja\vascript for javascript.

                      ESCAPE_SEQ_DECODE - Decode the following ANSI C escape sequences: \a, \b, \f, \n, \r, \t, \v, \, \?, \', \", \xHH (hexadecimal), \0OOO (octal). Encodings that aren't valid remain in the output.

                      HEX_DECODE - Decode a string of hexadecimal characters into a binary.

                      HTML_ENTITY_DECODE - Replace HTML-encoded characters with unencoded characters. HTML_ENTITY_DECODE performs these operations:

                      • Replaces (ampersand)quot; with "

                      • Replaces (ampersand)nbsp; with a non-breaking space, decimal 160

                      • Replaces (ampersand)lt; with a "less than" symbol

                      • Replaces (ampersand)gt; with >

                      • Replaces characters that are represented in hexadecimal format, (ampersand)#xhhhh;, with the corresponding characters

                      • Replaces characters that are represented in decimal format, (ampersand)#nnnn;, with the corresponding characters

                      JS_DECODE - Decode JavaScript escape sequences. If a \ u HHHH code is in the full-width ASCII code range of FF01-FF5E, then the higher byte is used to detect and adjust the lower byte. If not, only the lower byte is used and the higher byte is zeroed, causing a possible loss of information.

                      LOWERCASE - Convert uppercase letters (A-Z) to lowercase (a-z).

                      MD5 - Calculate an MD5 hash from the data in the input. The computed hash is in a raw binary form.

                      NONE - Specify NONE if you don't want any text transformations.

                      NORMALIZE_PATH - Remove multiple slashes, directory self-references, and directory back-references that are not at the beginning of the input from an input string.

                      NORMALIZE_PATH_WIN - This is the same as NORMALIZE_PATH, but first converts backslash characters to forward slashes.

                      REMOVE_NULLS - Remove all NULL bytes from the input.

                      REPLACE_COMMENTS - Replace each occurrence of a C-style comment (/* ... */) with a single space. Multiple consecutive occurrences are not compressed. Unterminated comments are also replaced with a space (ASCII 0x20). However, a standalone termination of a comment (*/) is not acted upon.

                      REPLACE_NULLS - Replace NULL bytes in the input with space characters (ASCII 0x20).

                      SQL_HEX_DECODE - Decode SQL hex data. Example (0x414243) will be decoded to (ABC).

                      URL_DECODE - Decode a URL-encoded value.

                      URL_DECODE_UNI - Like URL_DECODE, but with support for Microsoft-specific %u encoding. If the code is in the full-width ASCII code range of FF01-FF5E, the higher byte is used to detect and adjust the lower byte. Otherwise, only the lower byte is used and the higher byte is zeroed.

                      UTF8_TO_UNICODE - Convert all UTF-8 character sequences to Unicode. This helps input normalization, and minimizing false-positives and false-negatives for non-English languages.

                      Possible values include:
                      • "NONE"
                      • "COMPRESS_WHITE_SPACE"
                      • "HTML_ENTITY_DECODE"
                      • "LOWERCASE"
                      • "CMD_LINE"
                      • "URL_DECODE"
                      • "BASE64_DECODE"
                      • "HEX_DECODE"
                      • "MD5"
                      • "REPLACE_COMMENTS"
                      • "ESCAPE_SEQ_DECODE"
                      • "SQL_HEX_DECODE"
                      • "CSS_DECODE"
                      • "JS_DECODE"
                      • "NORMALIZE_PATH"
                      • "NORMALIZE_PATH_WIN"
                      • "REMOVE_NULLS"
                      • "REPLACE_NULLS"
                      • "BASE64_DECODE_EXT"
                      • "URL_DECODE_UNI"
                      • "UTF8_TO_UNICODE"
            • RuleGroupReferenceStatement — (map)

              A rule statement used to run the rules that are defined in a RuleGroup. To use this, create a rule group with your rules, then provide the ARN of the rule group in this statement.

              You cannot nest a RuleGroupReferenceStatement, for example for use inside a NotStatement or OrStatement. You can only use a rule group reference statement at the top level inside a web ACL.

              • ARN — required — (String)

                The Amazon Resource Name (ARN) of the entity.

              • ExcludedRules — (Array<map>)

                The rules in the referenced rule group whose actions are set to Count. When you exclude a rule, WAF evaluates it exactly as it would if the rule action setting were Count. This is a useful option for testing the rules in a rule group without modifying how they handle your web traffic.

                • Name — required — (String)

                  The name of the rule whose action you want to override to Count.

          • OverrideAction — required — (map)

            The action to use in the place of the action that results from the rule group evaluation. Set the override action to none to leave the result of the rule group alone. Set it to count to override the result to count only.

            You can only use this for rule statements that reference a rule group, like RuleGroupReferenceStatement and ManagedRuleGroupStatement.

            Note: This option is usually set to none. It does not affect how the rules in the rule group are evaluated. If you want the rules in the rule group to only count matches, do not use this and instead exclude those rules in your rule group reference statement settings.
            • Count — (map)

              Override the rule group evaluation result to count only.

              Note: This option is usually set to none. It does not affect how the rules in the rule group are evaluated. If you want the rules in the rule group to only count matches, do not use this and instead exclude those rules in your rule group reference statement settings.
              • CustomRequestHandling — (map)

                Defines custom handling for the web request.

                For information about customizing web requests and responses, see Customizing web requests and responses in WAF in the WAF Developer Guide.

                • InsertHeaders — required — (Array<map>)

                  The HTTP headers to insert into the request. Duplicate header names are not allowed.

                  For information about the limits on count and size for custom request and response settings, see WAF quotas in the WAF Developer Guide.

                  • Name — required — (String)

                    The name of the custom header.

                    For custom request header insertion, when WAF inserts the header into the request, it prefixes this name x-amzn-waf-, to avoid confusion with the headers that are already in the request. For example, for the header name sample, WAF inserts the header x-amzn-waf-sample.

                  • Value — required — (String)

                    The value of the custom header.

            • None — (map)

              Don't override the rule group evaluation result. This is the most common setting.

          • VisibilityConfig — required — (map)

            Defines and enables Amazon CloudWatch metrics and web request sample collection.

            • SampledRequestsEnabled — required — (Boolean)

              A boolean indicating whether WAF should store a sampling of the web requests that match the rules. You can view the sampled requests through the WAF console.

            • CloudWatchMetricsEnabled — required — (Boolean)

              A boolean indicating whether the associated resource sends metrics to Amazon CloudWatch. For the list of available metrics, see WAF Metrics.

            • MetricName — required — (String)

              A name of the Amazon CloudWatch metric. The name can contain only the characters: A-Z, a-z, 0-9, - (hyphen), and _ (underscore). The name can be from one to 128 characters long. It can't contain whitespace or metric names reserved for WAF, for example "All" and "Default_Action."

        • PostProcessFirewallManagerRuleGroups — (Array<map>)

          The last set of rules for WAF to process in the web ACL. This is defined in an Firewall Manager WAF policy and contains only rule group references. You can't alter these. Any rules and rule groups that you define for the web ACL are prioritized before these.

          In the Firewall Manager WAF policy, the Firewall Manager administrator can define a set of rule groups to run first in the web ACL and a set of rule groups to run last. Within each set, the administrator prioritizes the rule groups, to determine their relative processing order.

          • Name — required — (String)

            The name of the rule group. You cannot change the name of a rule group after you create it.

          • Priority — required — (Integer)

            If you define more than one rule group in the first or last Firewall Manager rule groups, WAF evaluates each request against the rule groups in order, starting from the lowest priority setting. The priorities don't need to be consecutive, but they must all be different.

          • FirewallManagerStatement — required — (map)

            The processing guidance for an Firewall Manager rule. This is like a regular rule Statement, but it can only contain a rule group reference.

            • ManagedRuleGroupStatement — (map)

              A rule statement used to run the rules that are defined in a managed rule group. To use this, provide the vendor name and the name of the rule group in this statement. You can retrieve the required names by calling ListAvailableManagedRuleGroups.

              You cannot nest a ManagedRuleGroupStatement, for example for use inside a NotStatement or OrStatement. It can only be referenced as a top-level statement within a rule.

              • VendorName — required — (String)

                The name of the managed rule group vendor. You use this, along with the rule group name, to identify the rule group.

              • Name — required — (String)

                The name of the managed rule group. You use this, along with the vendor name, to identify the rule group.

              • Version — (String)

                The version of the managed rule group to use. If you specify this, the version setting is fixed until you change it. If you don't specify this, WAF uses the vendor's default version, and then keeps the version at the vendor's default when the vendor updates the managed rule group settings.

              • ExcludedRules — (Array<map>)

                The rules in the referenced rule group whose actions are set to Count. When you exclude a rule, WAF evaluates it exactly as it would if the rule action setting were Count. This is a useful option for testing the rules in a rule group without modifying how they handle your web traffic.

                • Name — required — (String)

                  The name of the rule whose action you want to override to Count.

              • ScopeDownStatement — (map)

                An optional nested statement that narrows the scope of the web requests that are evaluated by the managed rule group. Requests are only evaluated by the rule group if they match the scope-down statement. You can use any nestable Statement in the scope-down statement, and you can nest statements at any level, the same as you can for a rule statement.

                • ByteMatchStatement — (map)

                  A rule statement that defines a string match search for WAF to apply to web requests. The byte match statement provides the bytes to search for, the location in requests that you want WAF to search, and other settings. The bytes to search for are typically a string that corresponds with ASCII characters. In the WAF console and the developer guide, this is refered to as a string match statement.

                  • SearchString — required — (Buffer, Typed Array, Blob, String)

                    A string value that you want WAF to search for. WAF searches only in the part of web requests that you designate for inspection in FieldToMatch. The maximum length of the value is 50 bytes.

                    Valid values depend on the component that you specify for inspection in FieldToMatch:

                    • Method: The HTTP method that you want WAF to search for. This indicates the type of operation specified in the request.

                    • UriPath: The value that you want WAF to search for in the URI path, for example, /images/daily-ad.jpg.

                    If SearchString includes alphabetic characters A-Z and a-z, note that the value is case sensitive.

                    If you're using the WAF API

                    Specify a base64-encoded version of the value. The maximum length of the value before you base64-encode it is 50 bytes.

                    For example, suppose the value of Type is HEADER and the value of Data is User-Agent. If you want to search the User-Agent header for the value BadBot, you base64-encode BadBot using MIME base64-encoding and include the resulting value, QmFkQm90, in the value of SearchString.

                    If you're using the CLI or one of the Amazon Web Services SDKs

                    The value that you want WAF to search for. The SDK automatically base64 encodes the value.

                  • FieldToMatch — required — (map)

                    The part of a web request that you want WAF to inspect. For more information, see FieldToMatch.

                    • SingleHeader — (map)

                      Inspect a single header. Provide the name of the header to inspect, for example, User-Agent or Referer. This setting isn't case sensitive.

                      Example JSON: "SingleHeader": { "Name": "haystack" }

                      • Name — required — (String)

                        The name of the query header to inspect.

                    • SingleQueryArgument — (map)

                      Inspect a single query argument. Provide the name of the query argument to inspect, such as UserName or SalesRegion. The name can be up to 30 characters long and isn't case sensitive.

                      This is used only to indicate the web request component for WAF to inspect, in the FieldToMatch specification.

                      Example JSON: "SingleQueryArgument": { "Name": "myArgument" }

                      • Name — required — (String)

                        The name of the query argument to inspect.

                    • AllQueryArguments — (map)

                      Inspect all query arguments.

                    • UriPath — (map)

                      Inspect the request URI path. This is the part of a web request that identifies a resource, for example, /images/daily-ad.jpg.

                    • QueryString — (map)

                      Inspect the query string. This is the part of a URL that appears after a ? character, if any.

                    • Body — (map)

                      Inspect the request body as plain text. The request body immediately follows the request headers. This is the part of a request that contains any additional data that you want to send to your web server as the HTTP request body, such as data from a form.

                      Note that only the first 8 KB (8192 bytes) of the request body are forwarded to WAF for inspection by the underlying host service. If you don't need to inspect more than 8 KB, you can guarantee that you don't allow additional bytes in by combining a statement that inspects the body of the web request, such as ByteMatchStatement or RegexPatternSetReferenceStatement, with a SizeConstraintStatement that enforces an 8 KB size limit on the body of the request. WAF doesn't support inspecting the entire contents of web requests whose bodies exceed the 8 KB limit.

                    • Method — (map)

                      Inspect the HTTP method. The method indicates the type of operation that the request is asking the origin to perform.

                    • JsonBody — (map)

                      Inspect the request body as JSON. The request body immediately follows the request headers. This is the part of a request that contains any additional data that you want to send to your web server as the HTTP request body, such as data from a form.

                      Note that only the first 8 KB (8192 bytes) of the request body are forwarded to WAF for inspection by the underlying host service. If you don't need to inspect more than 8 KB, you can guarantee that you don't allow additional bytes in by combining a statement that inspects the body of the web request, such as ByteMatchStatement or RegexPatternSetReferenceStatement, with a SizeConstraintStatement that enforces an 8 KB size limit on the body of the request. WAF doesn't support inspecting the entire contents of web requests whose bodies exceed the 8 KB limit.

                      • MatchPattern — required — (map)

                        The patterns to look for in the JSON body. WAF inspects the results of these pattern matches against the rule inspection criteria.

                        • All — (map)

                          Match all of the elements. See also MatchScope in JsonBody.

                          You must specify either this setting or the IncludedPaths setting, but not both.

                        • IncludedPaths — (Array<String>)

                          Match only the specified include paths. See also MatchScope in JsonBody.

                          Provide the include paths using JSON Pointer syntax. For example, "IncludedPaths": ["/dogs/0/name", "/dogs/1/name"]. For information about this syntax, see the Internet Engineering Task Force (IETF) documentation JavaScript Object Notation (JSON) Pointer.

                          You must specify either this setting or the All setting, but not both.

                          Note: Don't use this option to include all paths. Instead, use the All setting.
                      • MatchScope — required — (String)

                        The parts of the JSON to match against using the MatchPattern. If you specify All, WAF matches against keys and values.

                        Possible values include:
                        • "ALL"
                        • "KEY"
                        • "VALUE"
                      • InvalidFallbackBehavior — (String)

                        What WAF should do if it fails to completely parse the JSON body. The options are the following:

                        • EVALUATE_AS_STRING - Inspect the body as plain text. WAF applies the text transformations and inspection criteria that you defined for the JSON inspection to the body text string.

                        • MATCH - Treat the web request as matching the rule statement. WAF applies the rule action to the request.

                        • NO_MATCH - Treat the web request as not matching the rule statement.

                        If you don't provide this setting, WAF parses and evaluates the content only up to the first parsing failure that it encounters.

                        WAF does its best to parse the entire JSON body, but might be forced to stop for reasons such as invalid characters, duplicate keys, truncation, and any content whose root node isn't an object or an array.

                        WAF parses the JSON in the following examples as two valid key, value pairs:

                        • Missing comma: {"key1":"value1""key2":"value2"}

                        • Missing colon: {"key1":"value1","key2""value2"}

                        • Extra colons: {"key1"::"value1","key2""value2"}

                        Possible values include:
                        • "MATCH"
                        • "NO_MATCH"
                        • "EVALUATE_AS_STRING"
                  • TextTransformations — required — (Array<map>)

                    Text transformations eliminate some of the unusual formatting that attackers use in web requests in an effort to bypass detection. If you specify one or more transformations in a rule statement, WAF performs all transformations on the content of the request component identified by FieldToMatch, starting from the lowest priority setting, before inspecting the content for a match.

                    • Priority — required — (Integer)

                      Sets the relative processing order for multiple transformations that are defined for a rule statement. WAF processes all transformations, from lowest priority to highest, before inspecting the transformed content. The priorities don't need to be consecutive, but they must all be different.

                    • Type — required — (String)

                      You can specify the following transformation types:

                      BASE64_DECODE - Decode a Base64-encoded string.

                      BASE64_DECODE_EXT - Decode a Base64-encoded string, but use a forgiving implementation that ignores characters that aren't valid.

                      CMD_LINE - Command-line transformations. These are helpful in reducing effectiveness of attackers who inject an operating system command-line command and use unusual formatting to disguise some or all of the command.

                      • Delete the following characters: \ " ' ^

                      • Delete spaces before the following characters: / (

                      • Replace the following characters with a space: , ;

                      • Replace multiple spaces with one space

                      • Convert uppercase letters (A-Z) to lowercase (a-z)

                      COMPRESS_WHITE_SPACE - Replace these characters with a space character (decimal 32):

                      • \f, formfeed, decimal 12

                      • \t, tab, decimal 9

                      • \n, newline, decimal 10

                      • \r, carriage return, decimal 13

                      • \v, vertical tab, decimal 11

                      • Non-breaking space, decimal 160

                      COMPRESS_WHITE_SPACE also replaces multiple spaces with one space.

                      CSS_DECODE - Decode characters that were encoded using CSS 2.x escape rules syndata.html#characters. This function uses up to two bytes in the decoding process, so it can help to uncover ASCII characters that were encoded using CSS encoding that wouldn’t typically be encoded. It's also useful in countering evasion, which is a combination of a backslash and non-hexadecimal characters. For example, ja\vascript for javascript.

                      ESCAPE_SEQ_DECODE - Decode the following ANSI C escape sequences: \a, \b, \f, \n, \r, \t, \v, \, \?, \', \", \xHH (hexadecimal), \0OOO (octal). Encodings that aren't valid remain in the output.

                      HEX_DECODE - Decode a string of hexadecimal characters into a binary.

                      HTML_ENTITY_DECODE - Replace HTML-encoded characters with unencoded characters. HTML_ENTITY_DECODE performs these operations:

                      • Replaces (ampersand)quot; with "

                      • Replaces (ampersand)nbsp; with a non-breaking space, decimal 160

                      • Replaces (ampersand)lt; with a "less than" symbol

                      • Replaces (ampersand)gt; with >

                      • Replaces characters that are represented in hexadecimal format, (ampersand)#xhhhh;, with the corresponding characters

                      • Replaces characters that are represented in decimal format, (ampersand)#nnnn;, with the corresponding characters

                      JS_DECODE - Decode JavaScript escape sequences. If a \ u HHHH code is in the full-width ASCII code range of FF01-FF5E, then the higher byte is used to detect and adjust the lower byte. If not, only the lower byte is used and the higher byte is zeroed, causing a possible loss of information.

                      LOWERCASE - Convert uppercase letters (A-Z) to lowercase (a-z).

                      MD5 - Calculate an MD5 hash from the data in the input. The computed hash is in a raw binary form.

                      NONE - Specify NONE if you don't want any text transformations.

                      NORMALIZE_PATH - Remove multiple slashes, directory self-references, and directory back-references that are not at the beginning of the input from an input string.

                      NORMALIZE_PATH_WIN - This is the same as NORMALIZE_PATH, but first converts backslash characters to forward slashes.

                      REMOVE_NULLS - Remove all NULL bytes from the input.

                      REPLACE_COMMENTS - Replace each occurrence of a C-style comment (/* ... */) with a single space. Multiple consecutive occurrences are not compressed. Unterminated comments are also replaced with a space (ASCII 0x20). However, a standalone termination of a comment (*/) is not acted upon.

                      REPLACE_NULLS - Replace NULL bytes in the input with space characters (ASCII 0x20).

                      SQL_HEX_DECODE - Decode SQL hex data. Example (0x414243) will be decoded to (ABC).

                      URL_DECODE - Decode a URL-encoded value.

                      URL_DECODE_UNI - Like URL_DECODE, but with support for Microsoft-specific %u encoding. If the code is in the full-width ASCII code range of FF01-FF5E, the higher byte is used to detect and adjust the lower byte. Otherwise, only the lower byte is used and the higher byte is zeroed.

                      UTF8_TO_UNICODE - Convert all UTF-8 character sequences to Unicode. This helps input normalization, and minimizing false-positives and false-negatives for non-English languages.

                      Possible values include:
                      • "NONE"
                      • "COMPRESS_WHITE_SPACE"
                      • "HTML_ENTITY_DECODE"
                      • "LOWERCASE"
                      • "CMD_LINE"
                      • "URL_DECODE"
                      • "BASE64_DECODE"
                      • "HEX_DECODE"
                      • "MD5"
                      • "REPLACE_COMMENTS"
                      • "ESCAPE_SEQ_DECODE"
                      • "SQL_HEX_DECODE"
                      • "CSS_DECODE"
                      • "JS_DECODE"
                      • "NORMALIZE_PATH"
                      • "NORMALIZE_PATH_WIN"
                      • "REMOVE_NULLS"
                      • "REPLACE_NULLS"
                      • "BASE64_DECODE_EXT"
                      • "URL_DECODE_UNI"
                      • "UTF8_TO_UNICODE"
                  • PositionalConstraint — required — (String)

                    The area within the portion of a web request that you want WAF to search for SearchString. Valid values include the following:

                    CONTAINS

                    The specified part of the web request must include the value of SearchString, but the location doesn't matter.

                    CONTAINS_WORD

                    The specified part of the web request must include the value of SearchString, and SearchString must contain only alphanumeric characters or underscore (A-Z, a-z, 0-9, or ). In addition, SearchString must be a word, which means that both of the following are true:

                    • SearchString is at the beginning of the specified part of the web request or is preceded by a character other than an alphanumeric character or underscore (). Examples include the value of a header and ;BadBot.

                    • SearchString is at the end of the specified part of the web request or is followed by a character other than an alphanumeric character or underscore (_), for example, BadBot; and -BadBot;.

                    EXACTLY

                    The value of the specified part of the web request must exactly match the value of SearchString.

                    STARTS_WITH

                    The value of SearchString must appear at the beginning of the specified part of the web request.

                    ENDS_WITH

                    The value of SearchString must appear at the end of the specified part of the web request.

                    Possible values include:
                    • "EXACTLY"
                    • "STARTS_WITH"
                    • "ENDS_WITH"
                    • "CONTAINS"
                    • "CONTAINS_WORD"
                • SqliMatchStatement — (map)

                  Attackers sometimes insert malicious SQL code into web requests in an effort to extract data from your database. To allow or block web requests that appear to contain malicious SQL code, create one or more SQL injection match conditions. An SQL injection match condition identifies the part of web requests, such as the URI or the query string, that you want WAF to inspect. Later in the process, when you create a web ACL, you specify whether to allow or block requests that appear to contain malicious SQL code.

                  • FieldToMatch — required — (map)

                    The part of a web request that you want WAF to inspect. For more information, see FieldToMatch.

                    • SingleHeader — (map)

                      Inspect a single header. Provide the name of the header to inspect, for example, User-Agent or Referer. This setting isn't case sensitive.

                      Example JSON: "SingleHeader": { "Name": "haystack" }

                      • Name — required — (String)

                        The name of the query header to inspect.

                    • SingleQueryArgument — (map)

                      Inspect a single query argument. Provide the name of the query argument to inspect, such as UserName or SalesRegion. The name can be up to 30 characters long and isn't case sensitive.

                      This is used only to indicate the web request component for WAF to inspect, in the FieldToMatch specification.

                      Example JSON: "SingleQueryArgument": { "Name": "myArgument" }

                      • Name — required — (String)

                        The name of the query argument to inspect.

                    • AllQueryArguments — (map)

                      Inspect all query arguments.

                    • UriPath — (map)

                      Inspect the request URI path. This is the part of a web request that identifies a resource, for example, /images/daily-ad.jpg.

                    • QueryString — (map)

                      Inspect the query string. This is the part of a URL that appears after a ? character, if any.

                    • Body — (map)

                      Inspect the request body as plain text. The request body immediately follows the request headers. This is the part of a request that contains any additional data that you want to send to your web server as the HTTP request body, such as data from a form.

                      Note that only the first 8 KB (8192 bytes) of the request body are forwarded to WAF for inspection by the underlying host service. If you don't need to inspect more than 8 KB, you can guarantee that you don't allow additional bytes in by combining a statement that inspects the body of the web request, such as ByteMatchStatement or RegexPatternSetReferenceStatement, with a SizeConstraintStatement that enforces an 8 KB size limit on the body of the request. WAF doesn't support inspecting the entire contents of web requests whose bodies exceed the 8 KB limit.

                    • Method — (map)

                      Inspect the HTTP method. The method indicates the type of operation that the request is asking the origin to perform.

                    • JsonBody — (map)

                      Inspect the request body as JSON. The request body immediately follows the request headers. This is the part of a request that contains any additional data that you want to send to your web server as the HTTP request body, such as data from a form.

                      Note that only the first 8 KB (8192 bytes) of the request body are forwarded to WAF for inspection by the underlying host service. If you don't need to inspect more than 8 KB, you can guarantee that you don't allow additional bytes in by combining a statement that inspects the body of the web request, such as ByteMatchStatement or RegexPatternSetReferenceStatement, with a SizeConstraintStatement that enforces an 8 KB size limit on the body of the request. WAF doesn't support inspecting the entire contents of web requests whose bodies exceed the 8 KB limit.

                      • MatchPattern — required — (map)

                        The patterns to look for in the JSON body. WAF inspects the results of these pattern matches against the rule inspection criteria.

                        • All — (map)

                          Match all of the elements. See also MatchScope in JsonBody.

                          You must specify either this setting or the IncludedPaths setting, but not both.

                        • IncludedPaths — (Array<String>)

                          Match only the specified include paths. See also MatchScope in JsonBody.

                          Provide the include paths using JSON Pointer syntax. For example, "IncludedPaths": ["/dogs/0/name", "/dogs/1/name"]. For information about this syntax, see the Internet Engineering Task Force (IETF) documentation JavaScript Object Notation (JSON) Pointer.

                          You must specify either this setting or the All setting, but not both.

                          Note: Don't use this option to include all paths. Instead, use the All setting.
                      • MatchScope — required — (String)

                        The parts of the JSON to match against using the MatchPattern. If you specify All, WAF matches against keys and values.

                        Possible values include:
                        • "ALL"
                        • "KEY"
                        • "VALUE"
                      • InvalidFallbackBehavior — (String)

                        What WAF should do if it fails to completely parse the JSON body. The options are the following:

                        • EVALUATE_AS_STRING - Inspect the body as plain text. WAF applies the text transformations and inspection criteria that you defined for the JSON inspection to the body text string.

                        • MATCH - Treat the web request as matching the rule statement. WAF applies the rule action to the request.

                        • NO_MATCH - Treat the web request as not matching the rule statement.

                        If you don't provide this setting, WAF parses and evaluates the content only up to the first parsing failure that it encounters.

                        WAF does its best to parse the entire JSON body, but might be forced to stop for reasons such as invalid characters, duplicate keys, truncation, and any content whose root node isn't an object or an array.

                        WAF parses the JSON in the following examples as two valid key, value pairs:

                        • Missing comma: {"key1":"value1""key2":"value2"}

                        • Missing colon: {"key1":"value1","key2""value2"}

                        • Extra colons: {"key1"::"value1","key2""value2"}

                        Possible values include:
                        • "MATCH"
                        • "NO_MATCH"
                        • "EVALUATE_AS_STRING"
                  • TextTransformations — required — (Array<map>)

                    Text transformations eliminate some of the unusual formatting that attackers use in web requests in an effort to bypass detection. If you specify one or more transformations in a rule statement, WAF performs all transformations on the content of the request component identified by FieldToMatch, starting from the lowest priority setting, before inspecting the content for a match.

                    • Priority — required — (Integer)

                      Sets the relative processing order for multiple transformations that are defined for a rule statement. WAF processes all transformations, from lowest priority to highest, before inspecting the transformed content. The priorities don't need to be consecutive, but they must all be different.

                    • Type — required — (String)

                      You can specify the following transformation types:

                      BASE64_DECODE - Decode a Base64-encoded string.

                      BASE64_DECODE_EXT - Decode a Base64-encoded string, but use a forgiving implementation that ignores characters that aren't valid.

                      CMD_LINE - Command-line transformations. These are helpful in reducing effectiveness of attackers who inject an operating system command-line command and use unusual formatting to disguise some or all of the command.

                      • Delete the following characters: \ " ' ^

                      • Delete spaces before the following characters: / (

                      • Replace the following characters with a space: , ;

                      • Replace multiple spaces with one space

                      • Convert uppercase letters (A-Z) to lowercase (a-z)

                      COMPRESS_WHITE_SPACE - Replace these characters with a space character (decimal 32):

                      • \f, formfeed, decimal 12

                      • \t, tab, decimal 9

                      • \n, newline, decimal 10

                      • \r, carriage return, decimal 13

                      • \v, vertical tab, decimal 11

                      • Non-breaking space, decimal 160

                      COMPRESS_WHITE_SPACE also replaces multiple spaces with one space.

                      CSS_DECODE - Decode characters that were encoded using CSS 2.x escape rules syndata.html#characters. This function uses up to two bytes in the decoding process, so it can help to uncover ASCII characters that were encoded using CSS encoding that wouldn’t typically be encoded. It's also useful in countering evasion, which is a combination of a backslash and non-hexadecimal characters. For example, ja\vascript for javascript.

                      ESCAPE_SEQ_DECODE - Decode the following ANSI C escape sequences: \a, \b, \f, \n, \r, \t, \v, \, \?, \', \", \xHH (hexadecimal), \0OOO (octal). Encodings that aren't valid remain in the output.

                      HEX_DECODE - Decode a string of hexadecimal characters into a binary.

                      HTML_ENTITY_DECODE - Replace HTML-encoded characters with unencoded characters. HTML_ENTITY_DECODE performs these operations:

                      • Replaces (ampersand)quot; with "

                      • Replaces (ampersand)nbsp; with a non-breaking space, decimal 160

                      • Replaces (ampersand)lt; with a "less than" symbol

                      • Replaces (ampersand)gt; with >

                      • Replaces characters that are represented in hexadecimal format, (ampersand)#xhhhh;, with the corresponding characters

                      • Replaces characters that are represented in decimal format, (ampersand)#nnnn;, with the corresponding characters

                      JS_DECODE - Decode JavaScript escape sequences. If a \ u HHHH code is in the full-width ASCII code range of FF01-FF5E, then the higher byte is used to detect and adjust the lower byte. If not, only the lower byte is used and the higher byte is zeroed, causing a possible loss of information.

                      LOWERCASE - Convert uppercase letters (A-Z) to lowercase (a-z).

                      MD5 - Calculate an MD5 hash from the data in the input. The computed hash is in a raw binary form.

                      NONE - Specify NONE if you don't want any text transformations.

                      NORMALIZE_PATH - Remove multiple slashes, directory self-references, and directory back-references that are not at the beginning of the input from an input string.

                      NORMALIZE_PATH_WIN - This is the same as NORMALIZE_PATH, but first converts backslash characters to forward slashes.

                      REMOVE_NULLS - Remove all NULL bytes from the input.

                      REPLACE_COMMENTS - Replace each occurrence of a C-style comment (/* ... */) with a single space. Multiple consecutive occurrences are not compressed. Unterminated comments are also replaced with a space (ASCII 0x20). However, a standalone termination of a comment (*/) is not acted upon.

                      REPLACE_NULLS - Replace NULL bytes in the input with space characters (ASCII 0x20).

                      SQL_HEX_DECODE - Decode SQL hex data. Example (0x414243) will be decoded to (ABC).

                      URL_DECODE - Decode a URL-encoded value.

                      URL_DECODE_UNI - Like URL_DECODE, but with support for Microsoft-specific %u encoding. If the code is in the full-width ASCII code range of FF01-FF5E, the higher byte is used to detect and adjust the lower byte. Otherwise, only the lower byte is used and the higher byte is zeroed.

                      UTF8_TO_UNICODE - Convert all UTF-8 character sequences to Unicode. This helps input normalization, and minimizing false-positives and false-negatives for non-English languages.

                      Possible values include:
                      • "NONE"
                      • "COMPRESS_WHITE_SPACE"
                      • "HTML_ENTITY_DECODE"
                      • "LOWERCASE"
                      • "CMD_LINE"
                      • "URL_DECODE"
                      • "BASE64_DECODE"
                      • "HEX_DECODE"
                      • "MD5"
                      • "REPLACE_COMMENTS"
                      • "ESCAPE_SEQ_DECODE"
                      • "SQL_HEX_DECODE"
                      • "CSS_DECODE"
                      • "JS_DECODE"
                      • "NORMALIZE_PATH"
                      • "NORMALIZE_PATH_WIN"
                      • "REMOVE_NULLS"
                      • "REPLACE_NULLS"
                      • "BASE64_DECODE_EXT"
                      • "URL_DECODE_UNI"
                      • "UTF8_TO_UNICODE"
                • XssMatchStatement — (map)

                  A rule statement that defines a cross-site scripting (XSS) match search for WAF to apply to web requests. XSS attacks are those where the attacker uses vulnerabilities in a benign website as a vehicle to inject malicious client-site scripts into other legitimate web browsers. The XSS match statement provides the location in requests that you want WAF to search and text transformations to use on the search area before WAF searches for character sequences that are likely to be malicious strings.

                  • FieldToMatch — required — (map)

                    The part of a web request that you want WAF to inspect. For more information, see FieldToMatch.

                    • SingleHeader — (map)

                      Inspect a single header. Provide the name of the header to inspect, for example, User-Agent or Referer. This setting isn't case sensitive.

                      Example JSON: "SingleHeader": { "Name": "haystack" }

                      • Name — required — (String)

                        The name of the query header to inspect.

                    • SingleQueryArgument — (map)

                      Inspect a single query argument. Provide the name of the query argument to inspect, such as UserName or SalesRegion. The name can be up to 30 characters long and isn't case sensitive.

                      This is used only to indicate the web request component for WAF to inspect, in the FieldToMatch specification.

                      Example JSON: "SingleQueryArgument": { "Name": "myArgument" }

                      • Name — required — (String)

                        The name of the query argument to inspect.

                    • AllQueryArguments — (map)

                      Inspect all query arguments.

                    • UriPath — (map)

                      Inspect the request URI path. This is the part of a web request that identifies a resource, for example, /images/daily-ad.jpg.

                    • QueryString — (map)

                      Inspect the query string. This is the part of a URL that appears after a ? character, if any.

                    • Body — (map)

                      Inspect the request body as plain text. The request body immediately follows the request headers. This is the part of a request that contains any additional data that you want to send to your web server as the HTTP request body, such as data from a form.

                      Note that only the first 8 KB (8192 bytes) of the request body are forwarded to WAF for inspection by the underlying host service. If you don't need to inspect more than 8 KB, you can guarantee that you don't allow additional bytes in by combining a statement that inspects the body of the web request, such as ByteMatchStatement or RegexPatternSetReferenceStatement, with a SizeConstraintStatement that enforces an 8 KB size limit on the body of the request. WAF doesn't support inspecting the entire contents of web requests whose bodies exceed the 8 KB limit.

                    • Method — (map)

                      Inspect the HTTP method. The method indicates the type of operation that the request is asking the origin to perform.

                    • JsonBody — (map)

                      Inspect the request body as JSON. The request body immediately follows the request headers. This is the part of a request that contains any additional data that you want to send to your web server as the HTTP request body, such as data from a form.

                      Note that only the first 8 KB (8192 bytes) of the request body are forwarded to WAF for inspection by the underlying host service. If you don't need to inspect more than 8 KB, you can guarantee that you don't allow additional bytes in by combining a statement that inspects the body of the web request, such as ByteMatchStatement or RegexPatternSetReferenceStatement, with a SizeConstraintStatement that enforces an 8 KB size limit on the body of the request. WAF doesn't support inspecting the entire contents of web requests whose bodies exceed the 8 KB limit.

                      • MatchPattern — required — (map)

                        The patterns to look for in the JSON body. WAF inspects the results of these pattern matches against the rule inspection criteria.

                        • All — (map)

                          Match all of the elements. See also MatchScope in JsonBody.

                          You must specify either this setting or the IncludedPaths setting, but not both.

                        • IncludedPaths — (Array<String>)

                          Match only the specified include paths. See also MatchScope in JsonBody.

                          Provide the include paths using JSON Pointer syntax. For example, "IncludedPaths": ["/dogs/0/name", "/dogs/1/name"]. For information about this syntax, see the Internet Engineering Task Force (IETF) documentation JavaScript Object Notation (JSON) Pointer.

                          You must specify either this setting or the All setting, but not both.

                          Note: Don't use this option to include all paths. Instead, use the All setting.
                      • MatchScope — required — (String)

                        The parts of the JSON to match against using the MatchPattern. If you specify All, WAF matches against keys and values.

                        Possible values include:
                        • "ALL"
                        • "KEY"
                        • "VALUE"
                      • InvalidFallbackBehavior — (String)

                        What WAF should do if it fails to completely parse the JSON body. The options are the following:

                        • EVALUATE_AS_STRING - Inspect the body as plain text. WAF applies the text transformations and inspection criteria that you defined for the JSON inspection to the body text string.

                        • MATCH - Treat the web request as matching the rule statement. WAF applies the rule action to the request.

                        • NO_MATCH - Treat the web request as not matching the rule statement.

                        If you don't provide this setting, WAF parses and evaluates the content only up to the first parsing failure that it encounters.

                        WAF does its best to parse the entire JSON body, but might be forced to stop for reasons such as invalid characters, duplicate keys, truncation, and any content whose root node isn't an object or an array.

                        WAF parses the JSON in the following examples as two valid key, value pairs:

                        • Missing comma: {"key1":"value1""key2":"value2"}

                        • Missing colon: {"key1":"value1","key2""value2"}

                        • Extra colons: {"key1"::"value1","key2""value2"}

                        Possible values include:
                        • "MATCH"
                        • "NO_MATCH"
                        • "EVALUATE_AS_STRING"
                  • TextTransformations — required — (Array<map>)

                    Text transformations eliminate some of the unusual formatting that attackers use in web requests in an effort to bypass detection. If you specify one or more transformations in a rule statement, WAF performs all transformations on the content of the request component identified by FieldToMatch, starting from the lowest priority setting, before inspecting the content for a match.

                    • Priority — required — (Integer)

                      Sets the relative processing order for multiple transformations that are defined for a rule statement. WAF processes all transformations, from lowest priority to highest, before inspecting the transformed content. The priorities don't need to be consecutive, but they must all be different.

                    • Type — required — (String)

                      You can specify the following transformation types:

                      BASE64_DECODE - Decode a Base64-encoded string.

                      BASE64_DECODE_EXT - Decode a Base64-encoded string, but use a forgiving implementation that ignores characters that aren't valid.

                      CMD_LINE - Command-line transformations. These are helpful in reducing effectiveness of attackers who inject an operating system command-line command and use unusual formatting to disguise some or all of the command.

                      • Delete the following characters: \ " ' ^

                      • Delete spaces before the following characters: / (

                      • Replace the following characters with a space: , ;

                      • Replace multiple spaces with one space

                      • Convert uppercase letters (A-Z) to lowercase (a-z)

                      COMPRESS_WHITE_SPACE - Replace these characters with a space character (decimal 32):

                      • \f, formfeed, decimal 12

                      • \t, tab, decimal 9

                      • \n, newline, decimal 10

                      • \r, carriage return, decimal 13

                      • \v, vertical tab, decimal 11

                      • Non-breaking space, decimal 160

                      COMPRESS_WHITE_SPACE also replaces multiple spaces with one space.

                      CSS_DECODE - Decode characters that were encoded using CSS 2.x escape rules syndata.html#characters. This function uses up to two bytes in the decoding process, so it can help to uncover ASCII characters that were encoded using CSS encoding that wouldn’t typically be encoded. It's also useful in countering evasion, which is a combination of a backslash and non-hexadecimal characters. For example, ja\vascript for javascript.

                      ESCAPE_SEQ_DECODE - Decode the following ANSI C escape sequences: \a, \b, \f, \n, \r, \t, \v, \, \?, \', \", \xHH (hexadecimal), \0OOO (octal). Encodings that aren't valid remain in the output.

                      HEX_DECODE - Decode a string of hexadecimal characters into a binary.

                      HTML_ENTITY_DECODE - Replace HTML-encoded characters with unencoded characters. HTML_ENTITY_DECODE performs these operations:

                      • Replaces (ampersand)quot; with "

                      • Replaces (ampersand)nbsp; with a non-breaking space, decimal 160

                      • Replaces (ampersand)lt; with a "less than" symbol

                      • Replaces (ampersand)gt; with >

                      • Replaces characters that are represented in hexadecimal format, (ampersand)#xhhhh;, with the corresponding characters

                      • Replaces characters that are represented in decimal format, (ampersand)#nnnn;, with the corresponding characters

                      JS_DECODE - Decode JavaScript escape sequences. If a \ u HHHH code is in the full-width ASCII code range of FF01-FF5E, then the higher byte is used to detect and adjust the lower byte. If not, only the lower byte is used and the higher byte is zeroed, causing a possible loss of information.

                      LOWERCASE - Convert uppercase letters (A-Z) to lowercase (a-z).

                      MD5 - Calculate an MD5 hash from the data in the input. The computed hash is in a raw binary form.

                      NONE - Specify NONE if you don't want any text transformations.

                      NORMALIZE_PATH - Remove multiple slashes, directory self-references, and directory back-references that are not at the beginning of the input from an input string.

                      NORMALIZE_PATH_WIN - This is the same as NORMALIZE_PATH, but first converts backslash characters to forward slashes.

                      REMOVE_NULLS - Remove all NULL bytes from the input.

                      REPLACE_COMMENTS - Replace each occurrence of a C-style comment (/* ... */) with a single space. Multiple consecutive occurrences are not compressed. Unterminated comments are also replaced with a space (ASCII 0x20). However, a standalone termination of a comment (*/) is not acted upon.

                      REPLACE_NULLS - Replace NULL bytes in the input with space characters (ASCII 0x20).

                      SQL_HEX_DECODE - Decode SQL hex data. Example (0x414243) will be decoded to (ABC).

                      URL_DECODE - Decode a URL-encoded value.

                      URL_DECODE_UNI - Like URL_DECODE, but with support for Microsoft-specific %u encoding. If the code is in the full-width ASCII code range of FF01-FF5E, the higher byte is used to detect and adjust the lower byte. Otherwise, only the lower byte is used and the higher byte is zeroed.

                      UTF8_TO_UNICODE - Convert all UTF-8 character sequences to Unicode. This helps input normalization, and minimizing false-positives and false-negatives for non-English languages.

                      Possible values include:
                      • "NONE"
                      • "COMPRESS_WHITE_SPACE"
                      • "HTML_ENTITY_DECODE"
                      • "LOWERCASE"
                      • "CMD_LINE"
                      • "URL_DECODE"
                      • "BASE64_DECODE"
                      • "HEX_DECODE"
                      • "MD5"
                      • "REPLACE_COMMENTS"
                      • "ESCAPE_SEQ_DECODE"
                      • "SQL_HEX_DECODE"
                      • "CSS_DECODE"
                      • "JS_DECODE"
                      • "NORMALIZE_PATH"
                      • "NORMALIZE_PATH_WIN"
                      • "REMOVE_NULLS"
                      • "REPLACE_NULLS"
                      • "BASE64_DECODE_EXT"
                      • "URL_DECODE_UNI"
                      • "UTF8_TO_UNICODE"
                • SizeConstraintStatement — (map)

                  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 first 8192 bytes (8 KB). If the request body for your web requests never exceeds 8192 bytes, you can create a size constraint condition and block requests that have a request body greater than 8192 bytes.

                  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.

                  • FieldToMatch — required — (map)

                    The part of a web request that you want WAF to inspect. For more information, see FieldToMatch.

                    • SingleHeader — (map)

                      Inspect a single header. Provide the name of the header to inspect, for example, User-Agent or Referer. This setting isn't case sensitive.

                      Example JSON: "SingleHeader": { "Name": "haystack" }

                      • Name — required — (String)

                        The name of the query header to inspect.

                    • SingleQueryArgument — (map)

                      Inspect a single query argument. Provide the name of the query argument to inspect, such as UserName or SalesRegion. The name can be up to 30 characters long and isn't case sensitive.

                      This is used only to indicate the web request component for WAF to inspect, in the FieldToMatch specification.

                      Example JSON: "SingleQueryArgument": { "Name": "myArgument" }

                      • Name — required — (String)

                        The name of the query argument to inspect.

                    • AllQueryArguments — (map)

                      Inspect all query arguments.

                    • UriPath — (map)

                      Inspect the request URI path. This is the part of a web request that identifies a resource, for example, /images/daily-ad.jpg.

                    • QueryString — (map)

                      Inspect the query string. This is the part of a URL that appears after a ? character, if any.

                    • Body — (map)

                      Inspect the request body as plain text. The request body immediately follows the request headers. This is the part of a request that contains any additional data that you want to send to your web server as the HTTP request body, such as data from a form.

                      Note that only the first 8 KB (8192 bytes) of the request body are forwarded to WAF for inspection by the underlying host service. If you don't need to inspect more than 8 KB, you can guarantee that you don't allow additional bytes in by combining a statement that inspects the body of the web request, such as ByteMatchStatement or RegexPatternSetReferenceStatement, with a SizeConstraintStatement that enforces an 8 KB size limit on the body of the request. WAF doesn't support inspecting the entire contents of web requests whose bodies exceed the 8 KB limit.

                    • Method — (map)

                      Inspect the HTTP method. The method indicates the type of operation that the request is asking the origin to perform.

                    • JsonBody — (map)

                      Inspect the request body as JSON. The request body immediately follows the request headers. This is the part of a request that contains any additional data that you want to send to your web server as the HTTP request body, such as data from a form.

                      Note that only the first 8 KB (8192 bytes) of the request body are forwarded to WAF for inspection by the underlying host service. If you don't need to inspect more than 8 KB, you can guarantee that you don't allow additional bytes in by combining a statement that inspects the body of the web request, such as ByteMatchStatement or RegexPatternSetReferenceStatement, with a SizeConstraintStatement that enforces an 8 KB size limit on the body of the request. WAF doesn't support inspecting the entire contents of web requests whose bodies exceed the 8 KB limit.

                      • MatchPattern — required — (map)

                        The patterns to look for in the JSON body. WAF inspects the results of these pattern matches against the rule inspection criteria.

                        • All — (map)

                          Match all of the elements. See also MatchScope in JsonBody.

                          You must specify either this setting or the IncludedPaths setting, but not both.

                        • IncludedPaths — (Array<String>)

                          Match only the specified include paths. See also MatchScope in JsonBody.

                          Provide the include paths using JSON Pointer syntax. For example, "IncludedPaths": ["/dogs/0/name", "/dogs/1/name"]. For information about this syntax, see the Internet Engineering Task Force (IETF) documentation JavaScript Object Notation (JSON) Pointer.

                          You must specify either this setting or the All setting, but not both.

                          Note: Don't use this option to include all paths. Instead, use the All setting.
                      • MatchScope — required — (String)

                        The parts of the JSON to match against using the MatchPattern. If you specify All, WAF matches against keys and values.

                        Possible values include:
                        • "ALL"
                        • "KEY"
                        • "VALUE"
                      • InvalidFallbackBehavior — (String)

                        What WAF should do if it fails to completely parse the JSON body. The options are the following:

                        • EVALUATE_AS_STRING - Inspect the body as plain text. WAF applies the text transformations and inspection criteria that you defined for the JSON inspection to the body text string.

                        • MATCH - Treat the web request as matching the rule statement. WAF applies the rule action to the request.

                        • NO_MATCH - Treat the web request as not matching the rule statement.

                        If you don't provide this setting, WAF parses and evaluates the content only up to the first parsing failure that it encounters.

                        WAF does its best to parse the entire JSON body, but might be forced to stop for reasons such as invalid characters, duplicate keys, truncation, and any content whose root node isn't an object or an array.

                        WAF parses the JSON in the following examples as two valid key, value pairs:

                        • Missing comma: {"key1":"value1""key2":"value2"}

                        • Missing colon: {"key1":"value1","key2""value2"}

                        • Extra colons: {"key1"::"value1","key2""value2"}

                        Possible values include:
                        • "MATCH"
                        • "NO_MATCH"
                        • "EVALUATE_AS_STRING"
                  • ComparisonOperator — required — (String)

                    The operator to use to compare the request part to the size setting.

                    Possible values include:
                    • "EQ"
                    • "NE"
                    • "LE"
                    • "LT"
                    • "GE"
                    • "GT"
                  • Size — required — (Integer)

                    The size, in byte, to compare to the request part, after any transformations.

                  • TextTransformations — required — (Array<map>)

                    Text transformations eliminate some of the unusual formatting that attackers use in web requests in an effort to bypass detection. If you specify one or more transformations in a rule statement, WAF performs all transformations on the content of the request component identified by FieldToMatch, starting from the lowest priority setting, before inspecting the content for a match.

                    • Priority — required — (Integer)

                      Sets the relative processing order for multiple transformations that are defined for a rule statement. WAF processes all transformations, from lowest priority to highest, before inspecting the transformed content. The priorities don't need to be consecutive, but they must all be different.

                    • Type — required — (String)

                      You can specify the following transformation types:

                      BASE64_DECODE - Decode a Base64-encoded string.

                      BASE64_DECODE_EXT - Decode a Base64-encoded string, but use a forgiving implementation that ignores characters that aren't valid.

                      CMD_LINE - Command-line transformations. These are helpful in reducing effectiveness of attackers who inject an operating system command-line command and use unusual formatting to disguise some or all of the command.

                      • Delete the following characters: \ " ' ^

                      • Delete spaces before the following characters: / (

                      • Replace the following characters with a space: , ;

                      • Replace multiple spaces with one space

                      • Convert uppercase letters (A-Z) to lowercase (a-z)

                      COMPRESS_WHITE_SPACE - Replace these characters with a space character (decimal 32):

                      • \f, formfeed, decimal 12

                      • \t, tab, decimal 9

                      • \n, newline, decimal 10

                      • \r, carriage return, decimal 13

                      • \v, vertical tab, decimal 11

                      • Non-breaking space, decimal 160

                      COMPRESS_WHITE_SPACE also replaces multiple spaces with one space.

                      CSS_DECODE - Decode characters that were encoded using CSS 2.x escape rules syndata.html#characters. This function uses up to two bytes in the decoding process, so it can help to uncover ASCII characters that were encoded using CSS encoding that wouldn’t typically be encoded. It's also useful in countering evasion, which is a combination of a backslash and non-hexadecimal characters. For example, ja\vascript for javascript.

                      ESCAPE_SEQ_DECODE - Decode the following ANSI C escape sequences: \a, \b, \f, \n, \r, \t, \v, \, \?, \', \", \xHH (hexadecimal), \0OOO (octal). Encodings that aren't valid remain in the output.

                      HEX_DECODE - Decode a string of hexadecimal characters into a binary.

                      HTML_ENTITY_DECODE - Replace HTML-encoded characters with unencoded characters. HTML_ENTITY_DECODE performs these operations:

                      • Replaces (ampersand)quot; with "

                      • Replaces (ampersand)nbsp; with a non-breaking space, decimal 160

                      • Replaces (ampersand)lt; with a "less than" symbol

                      • Replaces (ampersand)gt; with >

                      • Replaces characters that are represented in hexadecimal format, (ampersand)#xhhhh;, with the corresponding characters

                      • Replaces characters that are represented in decimal format, (ampersand)#nnnn;, with the corresponding characters

                      JS_DECODE - Decode JavaScript escape sequences. If a \ u HHHH code is in the full-width ASCII code range of FF01-FF5E, then the higher byte is used to detect and adjust the lower byte. If not, only the lower byte is used and the higher byte is zeroed, causing a possible loss of information.

                      LOWERCASE - Convert uppercase letters (A-Z) to lowercase (a-z).

                      MD5 - Calculate an MD5 hash from the data in the input. The computed hash is in a raw binary form.

                      NONE - Specify NONE if you don't want any text transformations.

                      NORMALIZE_PATH - Remove multiple slashes, directory self-references, and directory back-references that are not at the beginning of the input from an input string.

                      NORMALIZE_PATH_WIN - This is the same as NORMALIZE_PATH, but first converts backslash characters to forward slashes.

                      REMOVE_NULLS - Remove all NULL bytes from the input.

                      REPLACE_COMMENTS - Replace each occurrence of a C-style comment (/* ... */) with a single space. Multiple consecutive occurrences are not compressed. Unterminated comments are also replaced with a space (ASCII 0x20). However, a standalone termination of a comment (*/) is not acted upon.

                      REPLACE_NULLS - Replace NULL bytes in the input with space characters (ASCII 0x20).

                      SQL_HEX_DECODE - Decode SQL hex data. Example (0x414243) will be decoded to (ABC).

                      URL_DECODE - Decode a URL-encoded value.

                      URL_DECODE_UNI - Like URL_DECODE, but with support for Microsoft-specific %u encoding. If the code is in the full-width ASCII code range of FF01-FF5E, the higher byte is used to detect and adjust the lower byte. Otherwise, only the lower byte is used and the higher byte is zeroed.

                      UTF8_TO_UNICODE - Convert all UTF-8 character sequences to Unicode. This helps input normalization, and minimizing false-positives and false-negatives for non-English languages.

                      Possible values include:
                      • "NONE"
                      • "COMPRESS_WHITE_SPACE"
                      • "HTML_ENTITY_DECODE"
                      • "LOWERCASE"
                      • "CMD_LINE"
                      • "URL_DECODE"
                      • "BASE64_DECODE"
                      • "HEX_DECODE"
                      • "MD5"
                      • "REPLACE_COMMENTS"
                      • "ESCAPE_SEQ_DECODE"
                      • "SQL_HEX_DECODE"
                      • "CSS_DECODE"
                      • "JS_DECODE"
                      • "NORMALIZE_PATH"
                      • "NORMALIZE_PATH_WIN"
                      • "REMOVE_NULLS"
                      • "REPLACE_NULLS"
                      • "BASE64_DECODE_EXT"
                      • "URL_DECODE_UNI"
                      • "UTF8_TO_UNICODE"
                • GeoMatchStatement — (map)

                  A rule statement used to identify web requests based on country of origin.

                  • CountryCodes — (Array<String>)

                    An array of two-character country codes, for example, [ "US", "CN" ], from the alpha-2 country ISO codes of the ISO 3166 international standard.

                  • ForwardedIPConfig — (map)

                    The configuration for inspecting IP addresses in an HTTP header that you specify, instead of using the IP address that's reported by the web request origin. Commonly, this is the X-Forwarded-For (XFF) header, but you can specify any header name.

                    Note: If the specified header isn't present in the request, WAF doesn't apply the rule to the web request at all.
                    • HeaderName — required — (String)

                      The name of the HTTP header to use for the IP address. For example, to use the X-Forwarded-For (XFF) header, set this to X-Forwarded-For.

                      Note: If the specified header isn't present in the request, WAF doesn't apply the rule to the web request at all.
                    • FallbackBehavior — required — (String)

                      The match status to assign to the web request if the request doesn't have a valid IP address in the specified position.

                      Note: If the specified header isn't present in the request, WAF doesn't apply the rule to the web request at all.

                      You can specify the following fallback behaviors:

                      • MATCH - Treat the web request as matching the rule statement. WAF applies the rule action to the request.

                      • NO_MATCH - Treat the web request as not matching the rule statement.

                      Possible values include:
                      • "MATCH"
                      • "NO_MATCH"
                • RuleGroupReferenceStatement — (map)

                  A rule statement used to run the rules that are defined in a RuleGroup. To use this, create a rule group with your rules, then provide the ARN of the rule group in this statement.

                  You cannot nest a RuleGroupReferenceStatement, for example for use inside a NotStatement or OrStatement. You can only use a rule group reference statement at the top level inside a web ACL.

                  • ARN — required — (String)

                    The Amazon Resource Name (ARN) of the entity.

                  • ExcludedRules — (Array<map>)

                    The rules in the referenced rule group whose actions are set to Count. When you exclude a rule, WAF evaluates it exactly as it would if the rule action setting were Count. This is a useful option for testing the rules in a rule group without modifying how they handle your web traffic.

                    • Name — required — (String)

                      The name of the rule whose action you want to override to Count.

                • IPSetReferenceStatement — (map)

                  A rule statement used to detect web requests coming from particular IP addresses or address ranges. To use this, create an IPSet that specifies the addresses you want to detect, then use the ARN of that set in this statement. To create an IP set, see CreateIPSet.

                  Each IP set rule statement references an IP set. You create and maintain the set independent of your rules. This allows you to use the single set in multiple rules. When you update the referenced set, WAF automatically updates all rules that reference it.

                  • ARN — required — (String)

                    The Amazon Resource Name (ARN) of the IPSet that this statement references.

                  • IPSetForwardedIPConfig — (map)

                    The configuration for inspecting IP addresses in an HTTP header that you specify, instead of using the IP address that's reported by the web request origin. Commonly, this is the X-Forwarded-For (XFF) header, but you can specify any header name.

                    Note: If the specified header isn't present in the request, WAF doesn't apply the rule to the web request at all.
                    • HeaderName — required — (String)

                      The name of the HTTP header to use for the IP address. For example, to use the X-Forwarded-For (XFF) header, set this to X-Forwarded-For.

                      Note: If the specified header isn't present in the request, WAF doesn't apply the rule to the web request at all.
                    • FallbackBehavior — required — (String)

                      The match status to assign to the web request if the request doesn't have a valid IP address in the specified position.

                      Note: If the specified header isn't present in the request, WAF doesn't apply the rule to the web request at all.

                      You can specify the following fallback behaviors:

                      • MATCH - Treat the web request as matching the rule statement. WAF applies the rule action to the request.

                      • NO_MATCH - Treat the web request as not matching the rule statement.

                      Possible values include:
                      • "MATCH"
                      • "NO_MATCH"
                    • Position — required — (String)

                      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:

                      • FIRST - Inspect the first IP address in the list of IP addresses in the header. This is usually the client's original IP.

                      • LAST - Inspect the last IP address in the list of IP addresses in the header.

                      • ANY - Inspect all IP addresses in the header for a match. If the header contains more than 10 IP addresses, WAF inspects the last 10.

                      Possible values include:
                      • "FIRST"
                      • "LAST"
                      • "ANY"
                • RegexPatternSetReferenceStatement — (map)

                  A rule statement used to search web request components for matches with regular expressions. To use this, create a RegexPatternSet that specifies the expressions that you want to detect, then use the ARN of that set in this statement. A web request matches the pattern set rule statement if the request component matches any of the patterns in the set. To create a regex pattern set, see CreateRegexPatternSet.

                  Each regex pattern set rule statement references a regex pattern set. You create and maintain the set independent of your rules. This allows you to use the single set in multiple rules. When you update the referenced set, WAF automatically updates all rules that reference it.

                  • ARN — required — (String)

                    The Amazon Resource Name (ARN) of the RegexPatternSet that this statement references.

                  • FieldToMatch — required — (map)

                    The part of a web request that you want WAF to inspect. For more information, see FieldToMatch.

                    • SingleHeader — (map)

                      Inspect a single header. Provide the name of the header to inspect, for example, User-Agent or Referer. This setting isn't case sensitive.

                      Example JSON: "SingleHeader": { "Name": "haystack" }

                      • Name — required — (String)

                        The name of the query header to inspect.

                    • SingleQueryArgument — (map)

                      Inspect a single query argument. Provide the name of the query argument to inspect, such as UserName or SalesRegion. The name can be up to 30 characters long and isn't case sensitive.

                      This is used only to indicate the web request component for WAF to inspect, in the FieldToMatch specification.

                      Example JSON: "SingleQueryArgument": { "Name": "myArgument" }

                      • Name — required — (String)

                        The name of the query argument to inspect.

                    • AllQueryArguments — (map)

                      Inspect all query arguments.

                    • UriPath — (map)

                      Inspect the request URI path. This is the part of a web request that identifies a resource, for example, /images/daily-ad.jpg.

                    • QueryString — (map)

                      Inspect the query string. This is the part of a URL that appears after a ? character, if any.

                    • Body — (map)

                      Inspect the request body as plain text. The request body immediately follows the request headers. This is the part of a request that contains any additional data that you want to send to your web server as the HTTP request body, such as data from a form.

                      Note that only the first 8 KB (8192 bytes) of the request body are forwarded to WAF for inspection by the underlying host service. If you don't need to inspect more than 8 KB, you can guarantee that you don't allow additional bytes in by combining a statement that inspects the body of the web request, such as ByteMatchStatement or RegexPatternSetReferenceStatement, with a SizeConstraintStatement that enforces an 8 KB size limit on the body of the request. WAF doesn't support inspecting the entire contents of web requests whose bodies exceed the 8 KB limit.

                    • Method — (map)

                      Inspect the HTTP method. The method indicates the type of operation that the request is asking the origin to perform.

                    • JsonBody — (map)

                      Inspect the request body as JSON. The request body immediately follows the request headers. This is the part of a request that contains any additional data that you want to send to your web server as the HTTP request body, such as data from a form.

                      Note that only the first 8 KB (8192 bytes) of the request body are forwarded to WAF for inspection by the underlying host service. If you don't need to inspect more than 8 KB, you can guarantee that you don't allow additional bytes in by combining a statement that inspects the body of the web request, such as ByteMatchStatement or RegexPatternSetReferenceStatement, with a SizeConstraintStatement that enforces an 8 KB size limit on the body of the request. WAF doesn't support inspecting the entire contents of web requests whose bodies exceed the 8 KB limit.

                      • MatchPattern — required — (map)

                        The patterns to look for in the JSON body. WAF inspects the results of these pattern matches against the rule inspection criteria.

                        • All — (map)

                          Match all of the elements. See also MatchScope in JsonBody.

                          You must specify either this setting or the IncludedPaths setting, but not both.

                        • IncludedPaths — (Array<String>)

                          Match only the specified include paths. See also MatchScope in JsonBody.

                          Provide the include paths using JSON Pointer syntax. For example, "IncludedPaths": ["/dogs/0/name", "/dogs/1/name"]. For information about this syntax, see the Internet Engineering Task Force (IETF) documentation JavaScript Object Notation (JSON) Pointer.

                          You must specify either this setting or the All setting, but not both.

                          Note: Don't use this option to include all paths. Instead, use the All setting.
                      • MatchScope — required — (String)

                        The parts of the JSON to match against using the MatchPattern. If you specify All, WAF matches against keys and values.

                        Possible values include:
                        • "ALL"
                        • "KEY"
                        • "VALUE"
                      • InvalidFallbackBehavior — (String)

                        What WAF should do if it fails to completely parse the JSON body. The options are the following:

                        • EVALUATE_AS_STRING - Inspect the body as plain text. WAF applies the text transformations and inspection criteria that you defined for the JSON inspection to the body text string.

                        • MATCH - Treat the web request as matching the rule statement. WAF applies the rule action to the request.

                        • NO_MATCH - Treat the web request as not matching the rule statement.

                        If you don't provide this setting, WAF parses and evaluates the content only up to the first parsing failure that it encounters.

                        WAF does its best to parse the entire JSON body, but might be forced to stop for reasons such as invalid characters, duplicate keys, truncation, and any content whose root node isn't an object or an array.

                        WAF parses the JSON in the following examples as two valid key, value pairs:

                        • Missing comma: {"key1":"value1""key2":"value2"}

                        • Missing colon: {"key1":"value1","key2""value2"}

                        • Extra colons: {"key1"::"value1","key2""value2"}

                        Possible values include:
                        • "MATCH"
                        • "NO_MATCH"
                        • "EVALUATE_AS_STRING"
                  • TextTransformations — required — (Array<map>)

                    Text transformations eliminate some of the unusual formatting that attackers use in web requests in an effort to bypass detection. If you specify one or more transformations in a rule statement, WAF performs all transformations on the content of the request component identified by FieldToMatch, starting from the lowest priority setting, before inspecting the content for a match.

                    • Priority — required — (Integer)

                      Sets the relative processing order for multiple transformations that are defined for a rule statement. WAF processes all transformations, from lowest priority to highest, before inspecting the transformed content. The priorities don't need to be consecutive, but they must all be different.

                    • Type — required — (String)

                      You can specify the following transformation types:

                      BASE64_DECODE - Decode a Base64-encoded string.

                      BASE64_DECODE_EXT - Decode a Base64-encoded string, but use a forgiving implementation that ignores characters that aren't valid.

                      CMD_LINE - Command-line transformations. These are helpful in reducing effectiveness of attackers who inject an operating system command-line command and use unusual formatting to disguise some or all of the command.

                      • Delete the following characters: \ " ' ^

                      • Delete spaces before the following characters: / (

                      • Replace the following characters with a space: , ;

                      • Replace multiple spaces with one space

                      • Convert uppercase letters (A-Z) to lowercase (a-z)

                      COMPRESS_WHITE_SPACE - Replace these characters with a space character (decimal 32):

                      • \f, formfeed, decimal 12

                      • \t, tab, decimal 9

                      • \n, newline, decimal 10

                      • \r, carriage return, decimal 13

                      • \v, vertical tab, decimal 11

                      • Non-breaking space, decimal 160

                      COMPRESS_WHITE_SPACE also replaces multiple spaces with one space.

                      CSS_DECODE - Decode characters that were encoded using CSS 2.x escape rules syndata.html#characters. This function uses up to two bytes in the decoding process, so it can help to uncover ASCII characters that were encoded using CSS encoding that wouldn’t typically be encoded. It's also useful in countering evasion, which is a combination of a backslash and non-hexadecimal characters. For example, ja\vascript for javascript.

                      ESCAPE_SEQ_DECODE - Decode the following ANSI C escape sequences: \a, \b, \f, \n, \r, \t, \v, \, \?, \', \", \xHH (hexadecimal), \0OOO (octal). Encodings that aren't valid remain in the output.

                      HEX_DECODE - Decode a string of hexadecimal characters into a binary.

                      HTML_ENTITY_DECODE - Replace HTML-encoded characters with unencoded characters. HTML_ENTITY_DECODE performs these operations:

                      • Replaces (ampersand)quot; with "

                      • Replaces (ampersand)nbsp; with a non-breaking space, decimal 160

                      • Replaces (ampersand)lt; with a "less than" symbol

                      • Replaces (ampersand)gt; with >

                      • Replaces characters that are represented in hexadecimal format, (ampersand)#xhhhh;, with the corresponding characters

                      • Replaces characters that are represented in decimal format, (ampersand)#nnnn;, with the corresponding characters

                      JS_DECODE - Decode JavaScript escape sequences. If a \ u HHHH code is in the full-width ASCII code range of FF01-FF5E, then the higher byte is used to detect and adjust the lower byte. If not, only the lower byte is used and the higher byte is zeroed, causing a possible loss of information.

                      LOWERCASE - Convert uppercase letters (A-Z) to lowercase (a-z).

                      MD5 - Calculate an MD5 hash from the data in the input. The computed hash is in a raw binary form.

                      NONE - Specify NONE if you don't want any text transformations.

                      NORMALIZE_PATH - Remove multiple slashes, directory self-references, and directory back-references that are not at the beginning of the input from an input string.

                      NORMALIZE_PATH_WIN - This is the same as NORMALIZE_PATH, but first converts backslash characters to forward slashes.

                      REMOVE_NULLS - Remove all NULL bytes from the input.

                      REPLACE_COMMENTS - Replace each occurrence of a C-style comment (/* ... */) with a single space. Multiple consecutive occurrences are not compressed. Unterminated comments are also replaced with a space (ASCII 0x20). However, a standalone termination of a comment (*/) is not acted upon.

                      REPLACE_NULLS - Replace NULL bytes in the input with space characters (ASCII 0x20).

                      SQL_HEX_DECODE - Decode SQL hex data. Example (0x414243) will be decoded to (ABC).

                      URL_DECODE - Decode a URL-encoded value.

                      URL_DECODE_UNI - Like URL_DECODE, but with support for Microsoft-specific %u encoding. If the code is in the full-width ASCII code range of FF01-FF5E, the higher byte is used to detect and adjust the lower byte. Otherwise, only the lower byte is used and the higher byte is zeroed.

                      UTF8_TO_UNICODE - Convert all UTF-8 character sequences to Unicode. This helps input normalization, and minimizing false-positives and false-negatives for non-English languages.

                      Possible values include:
                      • "NONE"
                      • "COMPRESS_WHITE_SPACE"
                      • "HTML_ENTITY_DECODE"
                      • "LOWERCASE"
                      • "CMD_LINE"
                      • "URL_DECODE"
                      • "BASE64_DECODE"
                      • "HEX_DECODE"
                      • "MD5"
                      • "REPLACE_COMMENTS"
                      • "ESCAPE_SEQ_DECODE"
                      • "SQL_HEX_DECODE"
                      • "CSS_DECODE"
                      • "JS_DECODE"
                      • "NORMALIZE_PATH"
                      • "NORMALIZE_PATH_WIN"
                      • "REMOVE_NULLS"
                      • "REPLACE_NULLS"
                      • "BASE64_DECODE_EXT"
                      • "URL_DECODE_UNI"
                      • "UTF8_TO_UNICODE"
                • RateBasedStatement — (map)

                  A rate-based rule tracks the rate of requests for each originating IP address, and triggers the rule action when the rate exceeds a limit that you specify on the number of requests in any 5-minute time span. You can use this to put a temporary block on requests from an IP address that is sending excessive requests.

                  WAF tracks and manages web requests separately for each instance of a rate-based rule that you use. For example, if you provide the same rate-based rule settings in two web ACLs, each of the two rule statements represents a separate instance of the rate-based rule and gets its own tracking and management by WAF. If you define a rate-based rule inside a rule group, and then use that rule group in multiple places, each use creates a separate instance of the rate-based rule that gets its own tracking and management by WAF.

                  When the rule action triggers, WAF blocks additional requests from the IP address until the request rate falls below the limit.

                  You can optionally nest another statement inside the rate-based statement, to narrow the scope of the rule so that it only counts requests that match the nested statement. For example, based on recent requests that you have seen from an attacker, you might create a rate-based rule with a nested AND rule statement that contains the following nested statements:

                  • An IP match statement with an IP set that specified the address 192.0.2.44.

                  • A string match statement that searches in the User-Agent header for the string BadBot.

                  In this rate-based rule, you also define a rate limit. For this example, the rate limit is 1,000. Requests that meet both of the conditions in the statements are counted. If the count exceeds 1,000 requests per five minutes, the rule action triggers. Requests that do not meet both conditions are not counted towards the rate limit and are not affected by this rule.

                  You cannot nest a RateBasedStatement inside another statement, for example inside a NotStatement or OrStatement. You can define a RateBasedStatement inside a web ACL and inside a rule group.

                  • Limit — required — (Integer)

                    The limit on requests per 5-minute period for a single originating IP address. If the statement includes a ScopeDownStatement, this limit is applied only to the requests that match the statement.

                  • AggregateKeyType — required — (String)

                    Setting that indicates how to aggregate the request counts. The options are the following:

                    • IP - Aggregate the request counts on the IP address from the web request origin.

                    • FORWARDED_IP - Aggregate the request counts on the first IP address in an HTTP header. If you use this, configure the ForwardedIPConfig, to specify the header to use.

                    Possible values include:
                    • "IP"
                    • "FORWARDED_IP"
                  • ForwardedIPConfig — (map)

                    The configuration for inspecting IP addresses in an HTTP header that you specify, instead of using the IP address that's reported by the web request origin. Commonly, this is the X-Forwarded-For (XFF) header, but you can specify any header name.

                    Note: If the specified header isn't present in the request, WAF doesn't apply the rule to the web request at all.

                    This is required if AggregateKeyType is set to FORWARDED_IP.

                    • HeaderName — required — (String)

                      The name of the HTTP header to use for the IP address. For example, to use the X-Forwarded-For (XFF) header, set this to X-Forwarded-For.

                      Note: If the specified header isn't present in the request, WAF doesn't apply the rule to the web request at all.
                    • FallbackBehavior — required — (String)

                      The match status to assign to the web request if the request doesn't have a valid IP address in the specified position.

                      Note: If the specified header isn't present in the request, WAF doesn't apply the rule to the web request at all.

                      You can specify the following fallback behaviors:

                      • MATCH - Treat the web request as matching the rule statement. WAF applies the rule action to the request.

                      • NO_MATCH - Treat the web request as not matching the rule statement.

                      Possible values include:
                      • "MATCH"
                      • "NO_MATCH"
                • AndStatement — (map)

                  A logical rule statement used to combine other rule statements with AND logic. You provide more than one Statement within the AndStatement.

                  • Statements — required — (Array<map>)

                    The statements to combine with AND logic. You can use any statements that can be nested.

                • OrStatement — (map)

                  A logical rule statement used to combine other rule statements with OR logic. You provide more than one Statement within the OrStatement.

                  • Statements — required — (Array<map>)

                    The statements to combine with OR logic. You can use any statements that can be nested.

                • NotStatement — (map)

                  A logical rule statement used to negate the results of another rule statement. You provide one Statement within the NotStatement.

                • LabelMatchStatement — (map)

                  A rule statement that defines a string match search against labels that have been added to the web request by rules that have already run in the web ACL.

                  The label match statement provides the label or namespace string to search for. The label string can represent a part or all of the fully qualified label name that had been added to the web request. Fully qualified labels have a prefix, optional namespaces, and label name. The prefix identifies the rule group or web ACL context of the rule that added the label. If you do not provide the fully qualified name in your label match string, WAF performs the search for labels that were added in the same context as the label match statement.

                  • Scope — required — (String)

                    Specify whether you want to match using the label name or just the namespace.

                    Possible values include:
                    • "LABEL"
                    • "NAMESPACE"
                  • Key — required — (String)

                    The string to match against. The setting you provide for this depends on the match statement's Scope setting:

                    • If the Scope indicates LABEL, then this specification must include the name and can include any number of preceding namespace specifications and prefix up to providing the fully qualified label name.

                    • If the Scope indicates NAMESPACE, then this specification can include any number of contiguous namespace strings, and can include the entire label namespace prefix from the rule group or web ACL where the label originates.

                    Labels are case sensitive and components of a label must be separated by colon, for example NS1:NS2:name.

                • RegexMatchStatement — (map)

                  A rule statement used to search web request components for a match against a single regular expression.

                  • RegexString — required — (String)

                    The string representing the regular expression.

                  • FieldToMatch — required — (map)

                    The part of a web request that you want WAF to inspect. For more information, see FieldToMatch.

                    • SingleHeader — (map)

                      Inspect a single header. Provide the name of the header to inspect, for example, User-Agent or Referer. This setting isn't case sensitive.

                      Example JSON: "SingleHeader": { "Name": "haystack" }

                      • Name — required — (String)

                        The name of the query header to inspect.

                    • SingleQueryArgument — (map)

                      Inspect a single query argument. Provide the name of the query argument to inspect, such as UserName or SalesRegion. The name can be up to 30 characters long and isn't case sensitive.

                      This is used only to indicate the web request component for WAF to inspect, in the FieldToMatch specification.

                      Example JSON: "SingleQueryArgument": { "Name": "myArgument" }

                      • Name — required — (String)

                        The name of the query argument to inspect.

                    • AllQueryArguments — (map)

                      Inspect all query arguments.

                    • UriPath — (map)

                      Inspect the request URI path. This is the part of a web request that identifies a resource, for example, /images/daily-ad.jpg.

                    • QueryString — (map)

                      Inspect the query string. This is the part of a URL that appears after a ? character, if any.

                    • Body — (map)

                      Inspect the request body as plain text. The request body immediately follows the request headers. This is the part of a request that contains any additional data that you want to send to your web server as the HTTP request body, such as data from a form.

                      Note that only the first 8 KB (8192 bytes) of the request body are forwarded to WAF for inspection by the underlying host service. If you don't need to inspect more than 8 KB, you can guarantee that you don't allow additional bytes in by combining a statement that inspects the body of the web request, such as ByteMatchStatement or RegexPatternSetReferenceStatement, with a SizeConstraintStatement that enforces an 8 KB size limit on the body of the request. WAF doesn't support inspecting the entire contents of web requests whose bodies exceed the 8 KB limit.

                    • Method — (map)

                      Inspect the HTTP method. The method indicates the type of operation that the request is asking the origin to perform.

                    • JsonBody — (map)

                      Inspect the request body as JSON. The request body immediately follows the request headers. This is the part of a request that contains any additional data that you want to send to your web server as the HTTP request body, such as data from a form.

                      Note that only the first 8 KB (8192 bytes) of the request body are forwarded to WAF for inspection by the underlying host service. If you don't need to inspect more than 8 KB, you can guarantee that you don't allow additional bytes in by combining a statement that inspects the body of the web request, such as ByteMatchStatement or RegexPatternSetReferenceStatement, with a SizeConstraintStatement that enforces an 8 KB size limit on the body of the request. WAF doesn't support inspecting the entire contents of web requests whose bodies exceed the 8 KB limit.

                      • MatchPattern — required — (map)

                        The patterns to look for in the JSON body. WAF inspects the results of these pattern matches against the rule inspection criteria.

                        • All — (map)

                          Match all of the elements. See also MatchScope in JsonBody.

                          You must specify either this setting or the IncludedPaths setting, but not both.

                        • IncludedPaths — (Array<String>)

                          Match only the specified include paths. See also MatchScope in JsonBody.

                          Provide the include paths using JSON Pointer syntax. For example, "IncludedPaths": ["/dogs/0/name", "/dogs/1/name"]. For information about this syntax, see the Internet Engineering Task Force (IETF) documentation JavaScript Object Notation (JSON) Pointer.

                          You must specify either this setting or the All setting, but not both.

                          Note: Don't use this option to include all paths. Instead, use the All setting.
                      • MatchScope — required — (String)

                        The parts of the JSON to match against using the MatchPattern. If you specify All, WAF matches against keys and values.

                        Possible values include:
                        • "ALL"
                        • "KEY"
                        • "VALUE"
                      • InvalidFallbackBehavior — (String)

                        What WAF should do if it fails to completely parse the JSON body. The options are the following:

                        • EVALUATE_AS_STRING - Inspect the body as plain text. WAF applies the text transformations and inspection criteria that you defined for the JSON inspection to the body text string.

                        • MATCH - Treat the web request as matching the rule statement. WAF applies the rule action to the request.

                        • NO_MATCH - Treat the web request as not matching the rule statement.

                        If you don't provide this setting, WAF parses and evaluates the content only up to the first parsing failure that it encounters.

                        WAF does its best to parse the entire JSON body, but might be forced to stop for reasons such as invalid characters, duplicate keys, truncation, and any content whose root node isn't an object or an array.

                        WAF parses the JSON in the following examples as two valid key, value pairs:

                        • Missing comma: {"key1":"value1""key2":"value2"}

                        • Missing colon: {"key1":"value1","key2""value2"}

                        • Extra colons: {"key1"::"value1","key2""value2"}

                        Possible values include:
                        • "MATCH"
                        • "NO_MATCH"
                        • "EVALUATE_AS_STRING"
                  • TextTransformations — required — (Array<map>)

                    Text transformations eliminate some of the unusual formatting that attackers use in web requests in an effort to bypass detection. If you specify one or more transformations in a rule statement, WAF performs all transformations on the content of the request component identified by FieldToMatch, starting from the lowest priority setting, before inspecting the content for a match.

                    • Priority — required — (Integer)

                      Sets the relative processing order for multiple transformations that are defined for a rule statement. WAF processes all transformations, from lowest priority to highest, before inspecting the transformed content. The priorities don't need to be consecutive, but they must all be different.

                    • Type — required — (String)

                      You can specify the following transformation types:

                      BASE64_DECODE - Decode a Base64-encoded string.

                      BASE64_DECODE_EXT - Decode a Base64-encoded string, but use a forgiving implementation that ignores characters that aren't valid.

                      CMD_LINE - Command-line transformations. These are helpful in reducing effectiveness of attackers who inject an operating system command-line command and use unusual formatting to disguise some or all of the command.

                      • Delete the following characters: \ " ' ^

                      • Delete spaces before the following characters: / (

                      • Replace the following characters with a space: , ;

                      • Replace multiple spaces with one space

                      • Convert uppercase letters (A-Z) to lowercase (a-z)

                      COMPRESS_WHITE_SPACE - Replace these characters with a space character (decimal 32):

                      • \f, formfeed, decimal 12

                      • \t, tab, decimal 9

                      • \n, newline, decimal 10

                      • \r, carriage return, decimal 13

                      • \v, vertical tab, decimal 11

                      • Non-breaking space, decimal 160

                      COMPRESS_WHITE_SPACE also replaces multiple spaces with one space.

                      CSS_DECODE - Decode characters that were encoded using CSS 2.x escape rules syndata.html#characters. This function uses up to two bytes in the decoding process, so it can help to uncover ASCII characters that were encoded using CSS encoding that wouldn’t typically be encoded. It's also useful in countering evasion, which is a combination of a backslash and non-hexadecimal characters. For example, ja\vascript for javascript.

                      ESCAPE_SEQ_DECODE - Decode the following ANSI C escape sequences: \a, \b, \f, \n, \r, \t, \v, \, \?, \', \", \xHH (hexadecimal), \0OOO (octal). Encodings that aren't valid remain in the output.

                      HEX_DECODE - Decode a string of hexadecimal characters into a binary.

                      HTML_ENTITY_DECODE - Replace HTML-encoded characters with unencoded characters. HTML_ENTITY_DECODE performs these operations:

                      • Replaces (ampersand)quot; with "

                      • Replaces (ampersand)nbsp; with a non-breaking space, decimal 160

                      • Replaces (ampersand)lt; with a "less than" symbol

                      • Replaces (ampersand)gt; with >

                      • Replaces characters that are represented in hexadecimal format, (ampersand)#xhhhh;, with the corresponding characters

                      • Replaces characters that are represented in decimal format, (ampersand)#nnnn;, with the corresponding characters

                      JS_DECODE - Decode JavaScript escape sequences. If a \ u HHHH code is in the full-width ASCII code range of FF01-FF5E, then the higher byte is used to detect and adjust the lower byte. If not, only the lower byte is used and the higher byte is zeroed, causing a possible loss of information.

                      LOWERCASE - Convert uppercase letters (A-Z) to lowercase (a-z).

                      MD5 - Calculate an MD5 hash from the data in the input. The computed hash is in a raw binary form.

                      NONE - Specify NONE if you don't want any text transformations.

                      NORMALIZE_PATH - Remove multiple slashes, directory self-references, and directory back-references that are not at the beginning of the input from an input string.

                      NORMALIZE_PATH_WIN - This is the same as NORMALIZE_PATH, but first converts backslash characters to forward slashes.

                      REMOVE_NULLS - Remove all NULL bytes from the input.

                      REPLACE_COMMENTS - Replace each occurrence of a C-style comment (/* ... */) with a single space. Multiple consecutive occurrences are not compressed. Unterminated comments are also replaced with a space (ASCII 0x20). However, a standalone termination of a comment (*/) is not acted upon.

                      REPLACE_NULLS - Replace NULL bytes in the input with space characters (ASCII 0x20).

                      SQL_HEX_DECODE - Decode SQL hex data. Example (0x414243) will be decoded to (ABC).

                      URL_DECODE - Decode a URL-encoded value.

                      URL_DECODE_UNI - Like URL_DECODE, but with support for Microsoft-specific %u encoding. If the code is in the full-width ASCII code range of FF01-FF5E, the higher byte is used to detect and adjust the lower byte. Otherwise, only the lower byte is used and the higher byte is zeroed.

                      UTF8_TO_UNICODE - Convert all UTF-8 character sequences to Unicode. This helps input normalization, and minimizing false-positives and false-negatives for non-English languages.

                      Possible values include:
                      • "NONE"
                      • "COMPRESS_WHITE_SPACE"
                      • "HTML_ENTITY_DECODE"
                      • "LOWERCASE"
                      • "CMD_LINE"
                      • "URL_DECODE"
                      • "BASE64_DECODE"
                      • "HEX_DECODE"
                      • "MD5"
                      • "REPLACE_COMMENTS"
                      • "ESCAPE_SEQ_DECODE"
                      • "SQL_HEX_DECODE"
                      • "CSS_DECODE"
                      • "JS_DECODE"
                      • "NORMALIZE_PATH"
                      • "NORMALIZE_PATH_WIN"
                      • "REMOVE_NULLS"
                      • "REPLACE_NULLS"
                      • "BASE64_DECODE_EXT"
                      • "URL_DECODE_UNI"
                      • "UTF8_TO_UNICODE"
            • RuleGroupReferenceStatement — (map)

              A rule statement used to run the rules that are defined in a RuleGroup. To use this, create a rule group with your rules, then provide the ARN of the rule group in this statement.

              You cannot nest a RuleGroupReferenceStatement, for example for use inside a NotStatement or OrStatement. You can only use a rule group reference statement at the top level inside a web ACL.

              • ARN — required — (String)

                The Amazon Resource Name (ARN) of the entity.

              • ExcludedRules — (Array<map>)

                The rules in the referenced rule group whose actions are set to Count. When you exclude a rule, WAF evaluates it exactly as it would if the rule action setting were Count. This is a useful option for testing the rules in a rule group without modifying how they handle your web traffic.

                • Name — required — (String)

                  The name of the rule whose action you want to override to Count.

          • OverrideAction — required — (map)

            The action to use in the place of the action that results from the rule group evaluation. Set the override action to none to leave the result of the rule group alone. Set it to count to override the result to count only.

            You can only use this for rule statements that reference a rule group, like RuleGroupReferenceStatement and ManagedRuleGroupStatement.

            Note: This option is usually set to none. It does not affect how the rules in the rule group are evaluated. If you want the rules in the rule group to only count matches, do not use this and instead exclude those rules in your rule group reference statement settings.
            • Count — (map)

              Override the rule group evaluation result to count only.

              Note: This option is usually set to none. It does not affect how the rules in the rule group are evaluated. If you want the rules in the rule group to only count matches, do not use this and instead exclude those rules in your rule group reference statement settings.
              • CustomRequestHandling — (map)

                Defines custom handling for the web request.

                For information about customizing web requests and responses, see Customizing web requests and responses in WAF in the WAF Developer Guide.

                • InsertHeaders — required — (Array<map>)

                  The HTTP headers to insert into the request. Duplicate header names are not allowed.

                  For information about the limits on count and size for custom request and response settings, see WAF quotas in the WAF Developer Guide.

                  • Name — required — (String)

                    The name of the custom header.

                    For custom request header insertion, when WAF inserts the header into the request, it prefixes this name x-amzn-waf-, to avoid confusion with the headers that are already in the request. For example, for the header name sample, WAF inserts the header x-amzn-waf-sample.

                  • Value — required — (String)

                    The value of the custom header.

            • None — (map)

              Don't override the rule group evaluation result. This is the most common setting.

          • VisibilityConfig — required — (map)

            Defines and enables Amazon CloudWatch metrics and web request sample collection.

            • SampledRequestsEnabled — required — (Boolean)

              A boolean indicating whether WAF should store a sampling of the web requests that match the rules. You can view the sampled requests through the WAF console.

            • CloudWatchMetricsEnabled — required — (Boolean)

              A boolean indicating whether the associated resource sends metrics to Amazon CloudWatch. For the list of available metrics, see WAF Metrics.

            • MetricName — required — (String)

              A name of the Amazon CloudWatch metric. The name can contain only the characters: A-Z, a-z, 0-9, - (hyphen), and _ (underscore). The name can be from one to 128 characters long. It can't contain whitespace or metric names reserved for WAF, for example "All" and "Default_Action."

        • ManagedByFirewallManager — (Boolean)

          Indicates whether this web ACL is managed by Firewall Manager. If true, then only Firewall Manager can delete the web ACL or any Firewall Manager rule groups in the web ACL.

        • LabelNamespace — (String)

          The label namespace prefix for this web ACL. All labels added by rules in this web ACL have this prefix.

          • The syntax for the label namespace prefix for a web ACL is the following:

            awswaf:<account ID>:webacl:<web ACL name>:

          • When a rule with a label matches a web request, WAF adds the fully qualified label to the request. A fully qualified label is made up of the label namespace from the rule group or web ACL where the rule is defined and the label from the rule, separated by a colon:

            <label namespace>:<label from rule>

        • CustomResponseBodies — (map<map>)

          A map of custom response keys and content bodies. When you create a rule with a block action, you can send a custom response to the web request. You define these for the web ACL, and then use them in the rules and default actions that you define in the web ACL.

          For information about customizing web requests and responses, see Customizing web requests and responses in WAF in the WAF Developer Guide.

          For information about the limits on count and size for custom request and response settings, see WAF quotas in the WAF Developer Guide.

          • ContentType — required — (String)

            The type of content in the payload that you are defining in the Content string.

            Possible values include:
            • "TEXT_PLAIN"
            • "TEXT_HTML"
            • "APPLICATION_JSON"
          • Content — required — (String)

            The payload of the custom response.

            You can use JSON escape strings in JSON content. To do this, you must specify JSON content in the ContentType setting.

            For information about the limits on count and size for custom request and response settings, see WAF quotas in the WAF Developer Guide.

        • CaptchaConfig — (map)

          Specifies how WAF should handle CAPTCHA evaluations for rules that don't have their own CaptchaConfig settings. If you don't specify this, WAF uses its default settings for CaptchaConfig.

          • ImmunityTimeProperty — (map)

            Determines how long a CAPTCHA token remains valid after the client successfully solves a CAPTCHA puzzle.

            • ImmunityTime — required — (Integer)

              The amount of time, in seconds, that a CAPTCHA token is valid. The default setting is 300.

      • LockToken — (String)

        A token used for optimistic locking. WAF returns a token to your get and list requests, to mark the state of the entity at the time of the request. To make changes to the entity associated with the token, you provide the token to operations like update and delete. WAF uses the token to ensure that no changes have been made to the entity since you last retrieved it. If a change has been made, the update fails with a WAFOptimisticLockException. If this happens, perform another get, and use the new token returned by that operation.

Returns:

  • (AWS.Request) —

    a handle to the operation request for subsequent event callback registration.

getWebACLForResource(params = {}, callback) ⇒ AWS.Request

Retrieves the WebACL for the specified resource.

Service Reference:

Examples:

Calling the getWebACLForResource operation

var params = {
  ResourceArn: 'STRING_VALUE' /* required */
};
wafv2.getWebACLForResource(params, function(err, data) {
  if (err) console.log(err, err.stack); // an error occurred
  else     console.log(data);           // successful response
});

Parameters:

  • params (Object) (defaults to: {}) —
    • ResourceArn — (String)

      The ARN (Amazon Resource Name) of the resource.

Callback (callback):

  • function(err, data) { ... }

    Called when a response from the service is returned. If a callback is not supplied, you must call AWS.Request.send() on the returned request object to initiate the request.

    Context (this):

    • (AWS.Response) —

      the response object containing error, data properties, and the original request object.

    Parameters:

    • err (Error) —

      the error object returned from the request. Set to null if the request is successful.

    • data (Object) —

      the de-serialized data returned from the request. Set to null if a request error occurs. The data object has the following properties:

      • WebACL — (map)

        The web ACL that is associated with the resource. If there is no associated resource, WAF returns a null web ACL.

        • Name — required — (String)

          The name of the web ACL. You cannot change the name of a web ACL after you create it.

        • Id — required — (String)

          A unique identifier for the WebACL. This ID is returned in the responses to create and list commands. You use this ID to do things like get, update, and delete a WebACL.

        • ARN — required — (String)

          The Amazon Resource Name (ARN) of the web ACL that you want to associate with the resource.

        • DefaultAction — required — (map)

          The action to perform if none of the Rules contained in the WebACL match.

          • Block — (map)

            Specifies that WAF should block requests by default.

            • CustomResponse — (map)

              Defines a custom response for the web request.

              For information about customizing web requests and responses, see Customizing web requests and responses in WAF in the WAF Developer Guide.

              • ResponseCode — required — (Integer)

                The HTTP status code to return to the client.

                For a list of status codes that you can use in your custom reqponses, see Supported status codes for custom response in the WAF Developer Guide.

              • CustomResponseBodyKey — (String)

                References the response body that you want WAF to return to the web request client. You can define a custom response for a rule action or a default web ACL action that is set to block. To do this, you first define the response body key and value in the CustomResponseBodies setting for the WebACL or RuleGroup where you want to use it. Then, in the rule action or web ACL default action BlockAction setting, you reference the response body using this key.

              • ResponseHeaders — (Array<map>)

                The HTTP headers to use in the response. Duplicate header names are not allowed.

                For information about the limits on count and size for custom request and response settings, see WAF quotas in the WAF Developer Guide.

                • Name — required — (String)

                  The name of the custom header.

                  For custom request header insertion, when WAF inserts the header into the request, it prefixes this name x-amzn-waf-, to avoid confusion with the headers that are already in the request. For example, for the header name sample, WAF inserts the header x-amzn-waf-sample.

                • Value — required — (String)

                  The value of the custom header.

          • Allow — (map)

            Specifies that WAF should allow requests by default.

            • CustomRequestHandling — (map)

              Defines custom handling for the web request.

              For information about customizing web requests and responses, see Customizing web requests and responses in WAF in the WAF Developer Guide.

              • InsertHeaders — required — (Array<map>)

                The HTTP headers to insert into the request. Duplicate header names are not allowed.

                For information about the limits on count and size for custom request and response settings, see WAF quotas in the WAF Developer Guide.

                • Name — required — (String)

                  The name of the custom header.

                  For custom request header insertion, when WAF inserts the header into the request, it prefixes this name x-amzn-waf-, to avoid confusion with the headers that are already in the request. For example, for the header name sample, WAF inserts the header x-amzn-waf-sample.

                • Value — required — (String)

                  The value of the custom header.

        • Description — (String)

          A description of the web ACL that helps with identification.

        • Rules — (Array<map>)

          The Rule statements used to identify the web requests that you want to allow, block, or count. Each rule includes one top-level statement that WAF uses to identify matching web requests, and parameters that govern how WAF handles them.

          • Name — required — (String)

            The name of the rule. You can't change the name of a Rule after you create it.

          • Priority — required — (Integer)

            If you define more than one Rule in a WebACL, WAF evaluates each request against the Rules in order based on the value of Priority. WAF processes rules with lower priority first. The priorities don't need to be consecutive, but they must all be different.

          • Statement — required — (map)

            The WAF processing statement for the rule, for example ByteMatchStatement or SizeConstraintStatement.

            • ByteMatchStatement — (map)

              A rule statement that defines a string match search for WAF to apply to web requests. The byte match statement provides the bytes to search for, the location in requests that you want WAF to search, and other settings. The bytes to search for are typically a string that corresponds with ASCII characters. In the WAF console and the developer guide, this is refered to as a string match statement.

              • SearchString — required — (Buffer, Typed Array, Blob, String)

                A string value that you want WAF to search for. WAF searches only in the part of web requests that you designate for inspection in FieldToMatch. The maximum length of the value is 50 bytes.

                Valid values depend on the component that you specify for inspection in FieldToMatch:

                • Method: The HTTP method that you want WAF to search for. This indicates the type of operation specified in the request.

                • UriPath: The value that you want WAF to search for in the URI path, for example, /images/daily-ad.jpg.

                If SearchString includes alphabetic characters A-Z and a-z, note that the value is case sensitive.

                If you're using the WAF API

                Specify a base64-encoded version of the value. The maximum length of the value before you base64-encode it is 50 bytes.

                For example, suppose the value of Type is HEADER and the value of Data is User-Agent. If you want to search the User-Agent header for the value BadBot, you base64-encode BadBot using MIME base64-encoding and include the resulting value, QmFkQm90, in the value of SearchString.

                If you're using the CLI or one of the Amazon Web Services SDKs

                The value that you want WAF to search for. The SDK automatically base64 encodes the value.

              • FieldToMatch — required — (map)

                The part of a web request that you want WAF to inspect. For more information, see FieldToMatch.

                • SingleHeader — (map)

                  Inspect a single header. Provide the name of the header to inspect, for example, User-Agent or Referer. This setting isn't case sensitive.

                  Example JSON: "SingleHeader": { "Name": "haystack" }

                  • Name — required — (String)

                    The name of the query header to inspect.

                • SingleQueryArgument — (map)

                  Inspect a single query argument. Provide the name of the query argument to inspect, such as UserName or SalesRegion. The name can be up to 30 characters long and isn't case sensitive.

                  This is used only to indicate the web request component for WAF to inspect, in the FieldToMatch specification.

                  Example JSON: "SingleQueryArgument": { "Name": "myArgument" }

                  • Name — required — (String)

                    The name of the query argument to inspect.

                • AllQueryArguments — (map)

                  Inspect all query arguments.

                • UriPath — (map)

                  Inspect the request URI path. This is the part of a web request that identifies a resource, for example, /images/daily-ad.jpg.

                • QueryString — (map)

                  Inspect the query string. This is the part of a URL that appears after a ? character, if any.

                • Body — (map)

                  Inspect the request body as plain text. The request body immediately follows the request headers. This is the part of a request that contains any additional data that you want to send to your web server as the HTTP request body, such as data from a form.

                  Note that only the first 8 KB (8192 bytes) of the request body are forwarded to WAF for inspection by the underlying host service. If you don't need to inspect more than 8 KB, you can guarantee that you don't allow additional bytes in by combining a statement that inspects the body of the web request, such as ByteMatchStatement or RegexPatternSetReferenceStatement, with a SizeConstraintStatement that enforces an 8 KB size limit on the body of the request. WAF doesn't support inspecting the entire contents of web requests whose bodies exceed the 8 KB limit.

                • Method — (map)

                  Inspect the HTTP method. The method indicates the type of operation that the request is asking the origin to perform.

                • JsonBody — (map)

                  Inspect the request body as JSON. The request body immediately follows the request headers. This is the part of a request that contains any additional data that you want to send to your web server as the HTTP request body, such as data from a form.

                  Note that only the first 8 KB (8192 bytes) of the request body are forwarded to WAF for inspection by the underlying host service. If you don't need to inspect more than 8 KB, you can guarantee that you don't allow additional bytes in by combining a statement that inspects the body of the web request, such as ByteMatchStatement or RegexPatternSetReferenceStatement, with a SizeConstraintStatement that enforces an 8 KB size limit on the body of the request. WAF doesn't support inspecting the entire contents of web requests whose bodies exceed the 8 KB limit.

                  • MatchPattern — required — (map)

                    The patterns to look for in the JSON body. WAF inspects the results of these pattern matches against the rule inspection criteria.

                    • All — (map)

                      Match all of the elements. See also MatchScope in JsonBody.

                      You must specify either this setting or the IncludedPaths setting, but not both.

                    • IncludedPaths — (Array<String>)

                      Match only the specified include paths. See also MatchScope in JsonBody.

                      Provide the include paths using JSON Pointer syntax. For example, "IncludedPaths": ["/dogs/0/name", "/dogs/1/name"]. For information about this syntax, see the Internet Engineering Task Force (IETF) documentation JavaScript Object Notation (JSON) Pointer.

                      You must specify either this setting or the All setting, but not both.

                      Note: Don't use this option to include all paths. Instead, use the All setting.
                  • MatchScope — required — (String)

                    The parts of the JSON to match against using the MatchPattern. If you specify All, WAF matches against keys and values.

                    Possible values include:
                    • "ALL"
                    • "KEY"
                    • "VALUE"
                  • InvalidFallbackBehavior — (String)

                    What WAF should do if it fails to completely parse the JSON body. The options are the following:

                    • EVALUATE_AS_STRING - Inspect the body as plain text. WAF applies the text transformations and inspection criteria that you defined for the JSON inspection to the body text string.

                    • MATCH - Treat the web request as matching the rule statement. WAF applies the rule action to the request.

                    • NO_MATCH - Treat the web request as not matching the rule statement.

                    If you don't provide this setting, WAF parses and evaluates the content only up to the first parsing failure that it encounters.

                    WAF does its best to parse the entire JSON body, but might be forced to stop for reasons such as invalid characters, duplicate keys, truncation, and any content whose root node isn't an object or an array.

                    WAF parses the JSON in the following examples as two valid key, value pairs:

                    • Missing comma: {"key1":"value1""key2":"value2"}

                    • Missing colon: {"key1":"value1","key2""value2"}

                    • Extra colons: {"key1"::"value1","key2""value2"}

                    Possible values include:
                    • "MATCH"
                    • "NO_MATCH"
                    • "EVALUATE_AS_STRING"
              • TextTransformations — required — (Array<map>)

                Text transformations eliminate some of the unusual formatting that attackers use in web requests in an effort to bypass detection. If you specify one or more transformations in a rule statement, WAF performs all transformations on the content of the request component identified by FieldToMatch, starting from the lowest priority setting, before inspecting the content for a match.

                • Priority — required — (Integer)

                  Sets the relative processing order for multiple transformations that are defined for a rule statement. WAF processes all transformations, from lowest priority to highest, before inspecting the transformed content. The priorities don't need to be consecutive, but they must all be different.

                • Type — required — (String)

                  You can specify the following transformation types:

                  BASE64_DECODE - Decode a Base64-encoded string.

                  BASE64_DECODE_EXT - Decode a Base64-encoded string, but use a forgiving implementation that ignores characters that aren't valid.

                  CMD_LINE - Command-line transformations. These are helpful in reducing effectiveness of attackers who inject an operating system command-line command and use unusual formatting to disguise some or all of the command.

                  • Delete the following characters: \ " ' ^

                  • Delete spaces before the following characters: / (

                  • Replace the following characters with a space: , ;

                  • Replace multiple spaces with one space

                  • Convert uppercase letters (A-Z) to lowercase (a-z)

                  COMPRESS_WHITE_SPACE - Replace these characters with a space character (decimal 32):

                  • \f, formfeed, decimal 12

                  • \t, tab, decimal 9

                  • \n, newline, decimal 10

                  • \r, carriage return, decimal 13

                  • \v, vertical tab, decimal 11

                  • Non-breaking space, decimal 160

                  COMPRESS_WHITE_SPACE also replaces multiple spaces with one space.

                  CSS_DECODE - Decode characters that were encoded using CSS 2.x escape rules syndata.html#characters. This function uses up to two bytes in the decoding process, so it can help to uncover ASCII characters that were encoded using CSS encoding that wouldn’t typically be encoded. It's also useful in countering evasion, which is a combination of a backslash and non-hexadecimal characters. For example, ja\vascript for javascript.

                  ESCAPE_SEQ_DECODE - Decode the following ANSI C escape sequences: \a, \b, \f, \n, \r, \t, \v, \, \?, \', \", \xHH (hexadecimal), \0OOO (octal). Encodings that aren't valid remain in the output.

                  HEX_DECODE - Decode a string of hexadecimal characters into a binary.

                  HTML_ENTITY_DECODE - Replace HTML-encoded characters with unencoded characters. HTML_ENTITY_DECODE performs these operations:

                  • Replaces (ampersand)quot; with "

                  • Replaces (ampersand)nbsp; with a non-breaking space, decimal 160

                  • Replaces (ampersand)lt; with a "less than" symbol

                  • Replaces (ampersand)gt; with >

                  • Replaces characters that are represented in hexadecimal format, (ampersand)#xhhhh;, with the corresponding characters

                  • Replaces characters that are represented in decimal format, (ampersand)#nnnn;, with the corresponding characters

                  JS_DECODE - Decode JavaScript escape sequences. If a \ u HHHH code is in the full-width ASCII code range of FF01-FF5E, then the higher byte is used to detect and adjust the lower byte. If not, only the lower byte is used and the higher byte is zeroed, causing a possible loss of information.

                  LOWERCASE - Convert uppercase letters (A-Z) to lowercase (a-z).

                  MD5 - Calculate an MD5 hash from the data in the input. The computed hash is in a raw binary form.

                  NONE - Specify NONE if you don't want any text transformations.

                  NORMALIZE_PATH - Remove multiple slashes, directory self-references, and directory back-references that are not at the beginning of the input from an input string.

                  NORMALIZE_PATH_WIN - This is the same as NORMALIZE_PATH, but first converts backslash characters to forward slashes.

                  REMOVE_NULLS - Remove all NULL bytes from the input.

                  REPLACE_COMMENTS - Replace each occurrence of a C-style comment (/* ... */) with a single space. Multiple consecutive occurrences are not compressed. Unterminated comments are also replaced with a space (ASCII 0x20). However, a standalone termination of a comment (*/) is not acted upon.

                  REPLACE_NULLS - Replace NULL bytes in the input with space characters (ASCII 0x20).

                  SQL_HEX_DECODE - Decode SQL hex data. Example (0x414243) will be decoded to (ABC).

                  URL_DECODE - Decode a URL-encoded value.

                  URL_DECODE_UNI - Like URL_DECODE, but with support for Microsoft-specific %u encoding. If the code is in the full-width ASCII code range of FF01-FF5E, the higher byte is used to detect and adjust the lower byte. Otherwise, only the lower byte is used and the higher byte is zeroed.

                  UTF8_TO_UNICODE - Convert all UTF-8 character sequences to Unicode. This helps input normalization, and minimizing false-positives and false-negatives for non-English languages.

                  Possible values include:
                  • "NONE"
                  • "COMPRESS_WHITE_SPACE"
                  • "HTML_ENTITY_DECODE"
                  • "LOWERCASE"
                  • "CMD_LINE"
                  • "URL_DECODE"
                  • "BASE64_DECODE"
                  • "HEX_DECODE"
                  • "MD5"
                  • "REPLACE_COMMENTS"
                  • "ESCAPE_SEQ_DECODE"
                  • "SQL_HEX_DECODE"
                  • "CSS_DECODE"
                  • "JS_DECODE"
                  • "NORMALIZE_PATH"
                  • "NORMALIZE_PATH_WIN"
                  • "REMOVE_NULLS"
                  • "REPLACE_NULLS"
                  • "BASE64_DECODE_EXT"
                  • "URL_DECODE_UNI"
                  • "UTF8_TO_UNICODE"
              • PositionalConstraint — required — (String)

                The area within the portion of a web request that you want WAF to search for SearchString. Valid values include the following:

                CONTAINS

                The specified part of the web request must include the value of SearchString, but the location doesn't matter.

                CONTAINS_WORD

                The specified part of the web request must include the value of SearchString, and SearchString must contain only alphanumeric characters or underscore (A-Z, a-z, 0-9, or ). In addition, SearchString must be a word, which means that both of the following are true:

                • SearchString is at the beginning of the specified part of the web request or is preceded by a character other than an alphanumeric character or underscore (). Examples include the value of a header and ;BadBot.

                • SearchString is at the end of the specified part of the web request or is followed by a character other than an alphanumeric character or underscore (_), for example, BadBot; and -BadBot;.

                EXACTLY

                The value of the specified part of the web request must exactly match the value of SearchString.

                STARTS_WITH

                The value of SearchString must appear at the beginning of the specified part of the web request.

                ENDS_WITH

                The value of SearchString must appear at the end of the specified part of the web request.

                Possible values include:
                • "EXACTLY"
                • "STARTS_WITH"
                • "ENDS_WITH"
                • "CONTAINS"
                • "CONTAINS_WORD"
            • SqliMatchStatement — (map)

              Attackers sometimes insert malicious SQL code into web requests in an effort to extract data from your database. To allow or block web requests that appear to contain malicious SQL code, create one or more SQL injection match conditions. An SQL injection match condition identifies the part of web requests, such as the URI or the query string, that you want WAF to inspect. Later in the process, when you create a web ACL, you specify whether to allow or block requests that appear to contain malicious SQL code.

              • FieldToMatch — required — (map)

                The part of a web request that you want WAF to inspect. For more information, see FieldToMatch.

                • SingleHeader — (map)

                  Inspect a single header. Provide the name of the header to inspect, for example, User-Agent or Referer. This setting isn't case sensitive.

                  Example JSON: "SingleHeader": { "Name": "haystack" }

                  • Name — required — (String)

                    The name of the query header to inspect.

                • SingleQueryArgument — (map)

                  Inspect a single query argument. Provide the name of the query argument to inspect, such as UserName or SalesRegion. The name can be up to 30 characters long and isn't case sensitive.

                  This is used only to indicate the web request component for WAF to inspect, in the FieldToMatch specification.

                  Example JSON: "SingleQueryArgument": { "Name": "myArgument" }

                  • Name — required — (String)

                    The name of the query argument to inspect.

                • AllQueryArguments — (map)

                  Inspect all query arguments.

                • UriPath — (map)

                  Inspect the request URI path. This is the part of a web request that identifies a resource, for example, /images/daily-ad.jpg.

                • QueryString — (map)

                  Inspect the query string. This is the part of a URL that appears after a ? character, if any.

                • Body — (map)

                  Inspect the request body as plain text. The request body immediately follows the request headers. This is the part of a request that contains any additional data that you want to send to your web server as the HTTP request body, such as data from a form.

                  Note that only the first 8 KB (8192 bytes) of the request body are forwarded to WAF for inspection by the underlying host service. If you don't need to inspect more than 8 KB, you can guarantee that you don't allow additional bytes in by combining a statement that inspects the body of the web request, such as ByteMatchStatement or RegexPatternSetReferenceStatement, with a SizeConstraintStatement that enforces an 8 KB size limit on the body of the request. WAF doesn't support inspecting the entire contents of web requests whose bodies exceed the 8 KB limit.

                • Method — (map)

                  Inspect the HTTP method. The method indicates the type of operation that the request is asking the origin to perform.

                • JsonBody — (map)

                  Inspect the request body as JSON. The request body immediately follows the request headers. This is the part of a request that contains any additional data that you want to send to your web server as the HTTP request body, such as data from a form.

                  Note that only the first 8 KB (8192 bytes) of the request body are forwarded to WAF for inspection by the underlying host service. If you don't need to inspect more than 8 KB, you can guarantee that you don't allow additional bytes in by combining a statement that inspects the body of the web request, such as ByteMatchStatement or RegexPatternSetReferenceStatement, with a SizeConstraintStatement that enforces an 8 KB size limit on the body of the request. WAF doesn't support inspecting the entire contents of web requests whose bodies exceed the 8 KB limit.

                  • MatchPattern — required — (map)

                    The patterns to look for in the JSON body. WAF inspects the results of these pattern matches against the rule inspection criteria.

                    • All — (map)

                      Match all of the elements. See also MatchScope in JsonBody.

                      You must specify either this setting or the IncludedPaths setting, but not both.

                    • IncludedPaths — (Array<String>)

                      Match only the specified include paths. See also MatchScope in JsonBody.

                      Provide the include paths using JSON Pointer syntax. For example, "IncludedPaths": ["/dogs/0/name", "/dogs/1/name"]. For information about this syntax, see the Internet Engineering Task Force (IETF) documentation JavaScript Object Notation (JSON) Pointer.

                      You must specify either this setting or the All setting, but not both.

                      Note: Don't use this option to include all paths. Instead, use the All setting.
                  • MatchScope — required — (String)

                    The parts of the JSON to match against using the MatchPattern. If you specify All, WAF matches against keys and values.

                    Possible values include:
                    • "ALL"
                    • "KEY"
                    • "VALUE"
                  • InvalidFallbackBehavior — (String)

                    What WAF should do if it fails to completely parse the JSON body. The options are the following:

                    • EVALUATE_AS_STRING - Inspect the body as plain text. WAF applies the text transformations and inspection criteria that you defined for the JSON inspection to the body text string.

                    • MATCH - Treat the web request as matching the rule statement. WAF applies the rule action to the request.

                    • NO_MATCH - Treat the web request as not matching the rule statement.

                    If you don't provide this setting, WAF parses and evaluates the content only up to the first parsing failure that it encounters.

                    WAF does its best to parse the entire JSON body, but might be forced to stop for reasons such as invalid characters, duplicate keys, truncation, and any content whose root node isn't an object or an array.

                    WAF parses the JSON in the following examples as two valid key, value pairs:

                    • Missing comma: {"key1":"value1""key2":"value2"}

                    • Missing colon: {"key1":"value1","key2""value2"}

                    • Extra colons: {"key1"::"value1","key2""value2"}

                    Possible values include:
                    • "MATCH"
                    • "NO_MATCH"
                    • "EVALUATE_AS_STRING"
              • TextTransformations — required — (Array<map>)

                Text transformations eliminate some of the unusual formatting that attackers use in web requests in an effort to bypass detection. If you specify one or more transformations in a rule statement, WAF performs all transformations on the content of the request component identified by FieldToMatch, starting from the lowest priority setting, before inspecting the content for a match.

                • Priority — required — (Integer)

                  Sets the relative processing order for multiple transformations that are defined for a rule statement. WAF processes all transformations, from lowest priority to highest, before inspecting the transformed content. The priorities don't need to be consecutive, but they must all be different.

                • Type — required — (String)

                  You can specify the following transformation types:

                  BASE64_DECODE - Decode a Base64-encoded string.

                  BASE64_DECODE_EXT - Decode a Base64-encoded string, but use a forgiving implementation that ignores characters that aren't valid.

                  CMD_LINE - Command-line transformations. These are helpful in reducing effectiveness of attackers who inject an operating system command-line command and use unusual formatting to disguise some or all of the command.

                  • Delete the following characters: \ " ' ^

                  • Delete spaces before the following characters: / (

                  • Replace the following characters with a space: , ;

                  • Replace multiple spaces with one space

                  • Convert uppercase letters (A-Z) to lowercase (a-z)

                  COMPRESS_WHITE_SPACE - Replace these characters with a space character (decimal 32):

                  • \f, formfeed, decimal 12

                  • \t, tab, decimal 9

                  • \n, newline, decimal 10

                  • \r, carriage return, decimal 13

                  • \v, vertical tab, decimal 11

                  • Non-breaking space, decimal 160

                  COMPRESS_WHITE_SPACE also replaces multiple spaces with one space.

                  CSS_DECODE - Decode characters that were encoded using CSS 2.x escape rules syndata.html#characters. This function uses up to two bytes in the decoding process, so it can help to uncover ASCII characters that were encoded using CSS encoding that wouldn’t typically be encoded. It's also useful in countering evasion, which is a combination of a backslash and non-hexadecimal characters. For example, ja\vascript for javascript.

                  ESCAPE_SEQ_DECODE - Decode the following ANSI C escape sequences: \a, \b, \f, \n, \r, \t, \v, \, \?, \', \", \xHH (hexadecimal), \0OOO (octal). Encodings that aren't valid remain in the output.

                  HEX_DECODE - Decode a string of hexadecimal characters into a binary.

                  HTML_ENTITY_DECODE - Replace HTML-encoded characters with unencoded characters. HTML_ENTITY_DECODE performs these operations:

                  • Replaces (ampersand)quot; with "

                  • Replaces (ampersand)nbsp; with a non-breaking space, decimal 160

                  • Replaces (ampersand)lt; with a "less than" symbol

                  • Replaces (ampersand)gt; with >

                  • Replaces characters that are represented in hexadecimal format, (ampersand)#xhhhh;, with the corresponding characters

                  • Replaces characters that are represented in decimal format, (ampersand)#nnnn;, with the corresponding characters

                  JS_DECODE - Decode JavaScript escape sequences. If a \ u HHHH code is in the full-width ASCII code range of FF01-FF5E, then the higher byte is used to detect and adjust the lower byte. If not, only the lower byte is used and the higher byte is zeroed, causing a possible loss of information.

                  LOWERCASE - Convert uppercase letters (A-Z) to lowercase (a-z).

                  MD5 - Calculate an MD5 hash from the data in the input. The computed hash is in a raw binary form.

                  NONE - Specify NONE if you don't want any text transformations.

                  NORMALIZE_PATH - Remove multiple slashes, directory self-references, and directory back-references that are not at the beginning of the input from an input string.

                  NORMALIZE_PATH_WIN - This is the same as NORMALIZE_PATH, but first converts backslash characters to forward slashes.

                  REMOVE_NULLS - Remove all NULL bytes from the input.

                  REPLACE_COMMENTS - Replace each occurrence of a C-style comment (/* ... */) with a single space. Multiple consecutive occurrences are not compressed. Unterminated comments are also replaced with a space (ASCII 0x20). However, a standalone termination of a comment (*/) is not acted upon.

                  REPLACE_NULLS - Replace NULL bytes in the input with space characters (ASCII 0x20).

                  SQL_HEX_DECODE - Decode SQL hex data. Example (0x414243) will be decoded to (ABC).

                  URL_DECODE - Decode a URL-encoded value.

                  URL_DECODE_UNI - Like URL_DECODE, but with support for Microsoft-specific %u encoding. If the code is in the full-width ASCII code range of FF01-FF5E, the higher byte is used to detect and adjust the lower byte. Otherwise, only the lower byte is used and the higher byte is zeroed.

                  UTF8_TO_UNICODE - Convert all UTF-8 character sequences to Unicode. This helps input normalization, and minimizing false-positives and false-negatives for non-English languages.

                  Possible values include:
                  • "NONE"
                  • "COMPRESS_WHITE_SPACE"
                  • "HTML_ENTITY_DECODE"
                  • "LOWERCASE"
                  • "CMD_LINE"
                  • "URL_DECODE"
                  • "BASE64_DECODE"
                  • "HEX_DECODE"
                  • "MD5"
                  • "REPLACE_COMMENTS"
                  • "ESCAPE_SEQ_DECODE"
                  • "SQL_HEX_DECODE"
                  • "CSS_DECODE"
                  • "JS_DECODE"
                  • "NORMALIZE_PATH"
                  • "NORMALIZE_PATH_WIN"
                  • "REMOVE_NULLS"
                  • "REPLACE_NULLS"
                  • "BASE64_DECODE_EXT"
                  • "URL_DECODE_UNI"
                  • "UTF8_TO_UNICODE"
            • XssMatchStatement — (map)

              A rule statement that defines a cross-site scripting (XSS) match search for WAF to apply to web requests. XSS attacks are those where the attacker uses vulnerabilities in a benign website as a vehicle to inject malicious client-site scripts into other legitimate web browsers. The XSS match statement provides the location in requests that you want WAF to search and text transformations to use on the search area before WAF searches for character sequences that are likely to be malicious strings.

              • FieldToMatch — required — (map)

                The part of a web request that you want WAF to inspect. For more information, see FieldToMatch.

                • SingleHeader — (map)

                  Inspect a single header. Provide the name of the header to inspect, for example, User-Agent or Referer. This setting isn't case sensitive.

                  Example JSON: "SingleHeader": { "Name": "haystack" }

                  • Name — required — (String)

                    The name of the query header to inspect.

                • SingleQueryArgument — (map)

                  Inspect a single query argument. Provide the name of the query argument to inspect, such as UserName or SalesRegion. The name can be up to 30 characters long and isn't case sensitive.

                  This is used only to indicate the web request component for WAF to inspect, in the FieldToMatch specification.

                  Example JSON: "SingleQueryArgument": { "Name": "myArgument" }

                  • Name — required — (String)

                    The name of the query argument to inspect.

                • AllQueryArguments — (map)

                  Inspect all query arguments.

                • UriPath — (map)

                  Inspect the request URI path. This is the part of a web request that identifies a resource, for example, /images/daily-ad.jpg.

                • QueryString — (map)

                  Inspect the query string. This is the part of a URL that appears after a ? character, if any.

                • Body — (map)

                  Inspect the request body as plain text. The request body immediately follows the request headers. This is the part of a request that contains any additional data that you want to send to your web server as the HTTP request body, such as data from a form.

                  Note that only the first 8 KB (8192 bytes) of the request body are forwarded to WAF for inspection by the underlying host service. If you don't need to inspect more than 8 KB, you can guarantee that you don't allow additional bytes in by combining a statement that inspects the body of the web request, such as ByteMatchStatement or RegexPatternSetReferenceStatement, with a SizeConstraintStatement that enforces an 8 KB size limit on the body of the request. WAF doesn't support inspecting the entire contents of web requests whose bodies exceed the 8 KB limit.

                • Method — (map)

                  Inspect the HTTP method. The method indicates the type of operation that the request is asking the origin to perform.

                • JsonBody — (map)

                  Inspect the request body as JSON. The request body immediately follows the request headers. This is the part of a request that contains any additional data that you want to send to your web server as the HTTP request body, such as data from a form.

                  Note that only the first 8 KB (8192 bytes) of the request body are forwarded to WAF for inspection by the underlying host service. If you don't need to inspect more than 8 KB, you can guarantee that you don't allow additional bytes in by combining a statement that inspects the body of the web request, such as ByteMatchStatement or RegexPatternSetReferenceStatement, with a SizeConstraintStatement that enforces an 8 KB size limit on the body of the request. WAF doesn't support inspecting the entire contents of web requests whose bodies exceed the 8 KB limit.

                  • MatchPattern — required — (map)

                    The patterns to look for in the JSON body. WAF inspects the results of these pattern matches against the rule inspection criteria.

                    • All — (map)

                      Match all of the elements. See also MatchScope in JsonBody.

                      You must specify either this setting or the IncludedPaths setting, but not both.

                    • IncludedPaths — (Array<String>)

                      Match only the specified include paths. See also MatchScope in JsonBody.

                      Provide the include paths using JSON Pointer syntax. For example, "IncludedPaths": ["/dogs/0/name", "/dogs/1/name"]. For information about this syntax, see the Internet Engineering Task Force (IETF) documentation JavaScript Object Notation (JSON) Pointer.

                      You must specify either this setting or the All setting, but not both.

                      Note: Don't use this option to include all paths. Instead, use the All setting.
                  • MatchScope — required — (String)

                    The parts of the JSON to match against using the MatchPattern. If you specify All, WAF matches against keys and values.

                    Possible values include:
                    • "ALL"
                    • "KEY"
                    • "VALUE"
                  • InvalidFallbackBehavior — (String)

                    What WAF should do if it fails to completely parse the JSON body. The options are the following:

                    • EVALUATE_AS_STRING - Inspect the body as plain text. WAF applies the text transformations and inspection criteria that you defined for the JSON inspection to the body text string.

                    • MATCH - Treat the web request as matching the rule statement. WAF applies the rule action to the request.

                    • NO_MATCH - Treat the web request as not matching the rule statement.

                    If you don't provide this setting, WAF parses and evaluates the content only up to the first parsing failure that it encounters.

                    WAF does its best to parse the entire JSON body, but might be forced to stop for reasons such as invalid characters, duplicate keys, truncation, and any content whose root node isn't an object or an array.

                    WAF parses the JSON in the following examples as two valid key, value pairs:

                    • Missing comma: {"key1":"value1""key2":"value2"}

                    • Missing colon: {"key1":"value1","key2""value2"}

                    • Extra colons: {"key1"::"value1","key2""value2"}

                    Possible values include:
                    • "MATCH"
                    • "NO_MATCH"
                    • "EVALUATE_AS_STRING"
              • TextTransformations — required — (Array<map>)

                Text transformations eliminate some of the unusual formatting that attackers use in web requests in an effort to bypass detection. If you specify one or more transformations in a rule statement, WAF performs all transformations on the content of the request component identified by FieldToMatch, starting from the lowest priority setting, before inspecting the content for a match.

                • Priority — required — (Integer)

                  Sets the relative processing order for multiple transformations that are defined for a rule statement. WAF processes all transformations, from lowest priority to highest, before inspecting the transformed content. The priorities don't need to be consecutive, but they must all be different.

                • Type — required — (String)

                  You can specify the following transformation types:

                  BASE64_DECODE - Decode a Base64-encoded string.

                  BASE64_DECODE_EXT - Decode a Base64-encoded string, but use a forgiving implementation that ignores characters that aren't valid.

                  CMD_LINE - Command-line transformations. These are helpful in reducing effectiveness of attackers who inject an operating system command-line command and use unusual formatting to disguise some or all of the command.

                  • Delete the following characters: \ " ' ^

                  • Delete spaces before the following characters: / (

                  • Replace the following characters with a space: , ;

                  • Replace multiple spaces with one space

                  • Convert uppercase letters (A-Z) to lowercase (a-z)

                  COMPRESS_WHITE_SPACE - Replace these characters with a space character (decimal 32):

                  • \f, formfeed, decimal 12

                  • \t, tab, decimal 9

                  • \n, newline, decimal 10

                  • \r, carriage return, decimal 13

                  • \v, vertical tab, decimal 11

                  • Non-breaking space, decimal 160

                  COMPRESS_WHITE_SPACE also replaces multiple spaces with one space.

                  CSS_DECODE - Decode characters that were encoded using CSS 2.x escape rules syndata.html#characters. This function uses up to two bytes in the decoding process, so it can help to uncover ASCII characters that were encoded using CSS encoding that wouldn’t typically be encoded. It's also useful in countering evasion, which is a combination of a backslash and non-hexadecimal characters. For example, ja\vascript for javascript.

                  ESCAPE_SEQ_DECODE - Decode the following ANSI C escape sequences: \a, \b, \f, \n, \r, \t, \v, \, \?, \', \", \xHH (hexadecimal), \0OOO (octal). Encodings that aren't valid remain in the output.

                  HEX_DECODE - Decode a string of hexadecimal characters into a binary.

                  HTML_ENTITY_DECODE - Replace HTML-encoded characters with unencoded characters. HTML_ENTITY_DECODE performs these operations:

                  • Replaces (ampersand)quot; with "

                  • Replaces (ampersand)nbsp; with a non-breaking space, decimal 160

                  • Replaces (ampersand)lt; with a "less than" symbol

                  • Replaces (ampersand)gt; with >

                  • Replaces characters that are represented in hexadecimal format, (ampersand)#xhhhh;, with the corresponding characters

                  • Replaces characters that are represented in decimal format, (ampersand)#nnnn;, with the corresponding characters

                  JS_DECODE - Decode JavaScript escape sequences. If a \ u HHHH code is in the full-width ASCII code range of FF01-FF5E, then the higher byte is used to detect and adjust the lower byte. If not, only the lower byte is used and the higher byte is zeroed, causing a possible loss of information.

                  LOWERCASE - Convert uppercase letters (A-Z) to lowercase (a-z).

                  MD5 - Calculate an MD5 hash from the data in the input. The computed hash is in a raw binary form.

                  NONE - Specify NONE if you don't want any text transformations.

                  NORMALIZE_PATH - Remove multiple slashes, directory self-references, and directory back-references that are not at the beginning of the input from an input string.

                  NORMALIZE_PATH_WIN - This is the same as NORMALIZE_PATH, but first converts backslash characters to forward slashes.

                  REMOVE_NULLS - Remove all NULL bytes from the input.

                  REPLACE_COMMENTS - Replace each occurrence of a C-style comment (/* ... */) with a single space. Multiple consecutive occurrences are not compressed. Unterminated comments are also replaced with a space (ASCII 0x20). However, a standalone termination of a comment (*/) is not acted upon.

                  REPLACE_NULLS - Replace NULL bytes in the input with space characters (ASCII 0x20).

                  SQL_HEX_DECODE - Decode SQL hex data. Example (0x414243) will be decoded to (ABC).

                  URL_DECODE - Decode a URL-encoded value.

                  URL_DECODE_UNI - Like URL_DECODE, but with support for Microsoft-specific %u encoding. If the code is in the full-width ASCII code range of FF01-FF5E, the higher byte is used to detect and adjust the lower byte. Otherwise, only the lower byte is used and the higher byte is zeroed.

                  UTF8_TO_UNICODE - Convert all UTF-8 character sequences to Unicode. This helps input normalization, and minimizing false-positives and false-negatives for non-English languages.

                  Possible values include:
                  • "NONE"
                  • "COMPRESS_WHITE_SPACE"
                  • "HTML_ENTITY_DECODE"
                  • "LOWERCASE"
                  • "CMD_LINE"
                  • "URL_DECODE"
                  • "BASE64_DECODE"
                  • "HEX_DECODE"
                  • "MD5"
                  • "REPLACE_COMMENTS"
                  • "ESCAPE_SEQ_DECODE"
                  • "SQL_HEX_DECODE"
                  • "CSS_DECODE"
                  • "JS_DECODE"
                  • "NORMALIZE_PATH"
                  • "NORMALIZE_PATH_WIN"
                  • "REMOVE_NULLS"
                  • "REPLACE_NULLS"
                  • "BASE64_DECODE_EXT"
                  • "URL_DECODE_UNI"
                  • "UTF8_TO_UNICODE"
            • SizeConstraintStatement — (map)

              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 first 8192 bytes (8 KB). If the request body for your web requests never exceeds 8192 bytes, you can create a size constraint condition and block requests that have a request body greater than 8192 bytes.

              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.

              • FieldToMatch — required — (map)

                The part of a web request that you want WAF to inspect. For more information, see FieldToMatch.

                • SingleHeader — (map)

                  Inspect a single header. Provide the name of the header to inspect, for example, User-Agent or Referer. This setting isn't case sensitive.

                  Example JSON: "SingleHeader": { "Name": "haystack" }

                  • Name — required — (String)

                    The name of the query header to inspect.

                • SingleQueryArgument — (map)

                  Inspect a single query argument. Provide the name of the query argument to inspect, such as UserName or SalesRegion. The name can be up to 30 characters long and isn't case sensitive.

                  This is used only to indicate the web request component for WAF to inspect, in the FieldToMatch specification.

                  Example JSON: "SingleQueryArgument": { "Name": "myArgument" }

                  • Name — required — (String)

                    The name of the query argument to inspect.

                • AllQueryArguments — (map)

                  Inspect all query arguments.

                • UriPath — (map)

                  Inspect the request URI path. This is the part of a web request that identifies a resource, for example, /images/daily-ad.jpg.

                • QueryString — (map)

                  Inspect the query string. This is the part of a URL that appears after a ? character, if any.

                • Body — (map)

                  Inspect the request body as plain text. The request body immediately follows the request headers. This is the part of a request that contains any additional data that you want to send to your web server as the HTTP request body, such as data from a form.

                  Note that only the first 8 KB (8192 bytes) of the request body are forwarded to WAF for inspection by the underlying host service. If you don't need to inspect more than 8 KB, you can guarantee that you don't allow additional bytes in by combining a statement that inspects the body of the web request, such as ByteMatchStatement or RegexPatternSetReferenceStatement, with a SizeConstraintStatement that enforces an 8 KB size limit on the body of the request. WAF doesn't support inspecting the entire contents of web requests whose bodies exceed the 8 KB limit.

                • Method — (map)

                  Inspect the HTTP method. The method indicates the type of operation that the request is asking the origin to perform.

                • JsonBody — (map)

                  Inspect the request body as JSON. The request body immediately follows the request headers. This is the part of a request that contains any additional data that you want to send to your web server as the HTTP request body, such as data from a form.

                  Note that only the first 8 KB (8192 bytes) of the request body are forwarded to WAF for inspection by the underlying host service. If you don't need to inspect more than 8 KB, you can guarantee that you don't allow additional bytes in by combining a statement that inspects the body of the web request, such as ByteMatchStatement or RegexPatternSetReferenceStatement, with a SizeConstraintStatement that enforces an 8 KB size limit on the body of the request. WAF doesn't support inspecting the entire contents of web requests whose bodies exceed the 8 KB limit.

                  • MatchPattern — required — (map)

                    The patterns to look for in the JSON body. WAF inspects the results of these pattern matches against the rule inspection criteria.

                    • All — (map)

                      Match all of the elements. See also MatchScope in JsonBody.

                      You must specify either this setting or the IncludedPaths setting, but not both.

                    • IncludedPaths — (Array<String>)

                      Match only the specified include paths. See also MatchScope in JsonBody.

                      Provide the include paths using JSON Pointer syntax. For example, "IncludedPaths": ["/dogs/0/name", "/dogs/1/name"]. For information about this syntax, see the Internet Engineering Task Force (IETF) documentation JavaScript Object Notation (JSON) Pointer.

                      You must specify either this setting or the All setting, but not both.

                      Note: Don't use this option to include all paths. Instead, use the All setting.
                  • MatchScope — required — (String)

                    The parts of the JSON to match against using the MatchPattern. If you specify All, WAF matches against keys and values.

                    Possible values include:
                    • "ALL"
                    • "KEY"
                    • "VALUE"
                  • InvalidFallbackBehavior — (String)

                    What WAF should do if it fails to completely parse the JSON body. The options are the following:

                    • EVALUATE_AS_STRING - Inspect the body as plain text. WAF applies the text transformations and inspection criteria that you defined for the JSON inspection to the body text string.

                    • MATCH - Treat the web request as matching the rule statement. WAF applies the rule action to the request.

                    • NO_MATCH - Treat the web request as not matching the rule statement.

                    If you don't provide this setting, WAF parses and evaluates the content only up to the first parsing failure that it encounters.

                    WAF does its best to parse the entire JSON body, but might be forced to stop for reasons such as invalid characters, duplicate keys, truncation, and any content whose root node isn't an object or an array.

                    WAF parses the JSON in the following examples as two valid key, value pairs:

                    • Missing comma: {"key1":"value1""key2":"value2"}

                    • Missing colon: {"key1":"value1","key2""value2"}

                    • Extra colons: {"key1"::"value1","key2""value2"}

                    Possible values include:
                    • "MATCH"
                    • "NO_MATCH"
                    • "EVALUATE_AS_STRING"
              • ComparisonOperator — required — (String)

                The operator to use to compare the request part to the size setting.

                Possible values include:
                • "EQ"
                • "NE"
                • "LE"
                • "LT"
                • "GE"
                • "GT"
              • Size — required — (Integer)

                The size, in byte, to compare to the request part, after any transformations.

              • TextTransformations — required — (Array<map>)

                Text transformations eliminate some of the unusual formatting that attackers use in web requests in an effort to bypass detection. If you specify one or more transformations in a rule statement, WAF performs all transformations on the content of the request component identified by FieldToMatch, starting from the lowest priority setting, before inspecting the content for a match.

                • Priority — required — (Integer)

                  Sets the relative processing order for multiple transformations that are defined for a rule statement. WAF processes all transformations, from lowest priority to highest, before inspecting the transformed content. The priorities don't need to be consecutive, but they must all be different.

                • Type — required — (String)

                  You can specify the following transformation types:

                  BASE64_DECODE - Decode a Base64-encoded string.

                  BASE64_DECODE_EXT - Decode a Base64-encoded string, but use a forgiving implementation that ignores characters that aren't valid.

                  CMD_LINE - Command-line transformations. These are helpful in reducing effectiveness of attackers who inject an operating system command-line command and use unusual formatting to disguise some or all of the command.

                  • Delete the following characters: \ " ' ^

                  • Delete spaces before the following characters: / (

                  • Replace the following characters with a space: , ;

                  • Replace multiple spaces with one space

                  • Convert uppercase letters (A-Z) to lowercase (a-z)

                  COMPRESS_WHITE_SPACE - Replace these characters with a space character (decimal 32):

                  • \f, formfeed, decimal 12

                  • \t, tab, decimal 9

                  • \n, newline, decimal 10

                  • \r, carriage return, decimal 13

                  • \v, vertical tab, decimal 11

                  • Non-breaking space, decimal 160

                  COMPRESS_WHITE_SPACE also replaces multiple spaces with one space.

                  CSS_DECODE - Decode characters that were encoded using CSS 2.x escape rules syndata.html#characters. This function uses up to two bytes in the decoding process, so it can help to uncover ASCII characters that were encoded using CSS encoding that wouldn’t typically be encoded. It's also useful in countering evasion, which is a combination of a backslash and non-hexadecimal characters. For example, ja\vascript for javascript.

                  ESCAPE_SEQ_DECODE - Decode the following ANSI C escape sequences: \a, \b, \f, \n, \r, \t, \v, \, \?, \', \", \xHH (hexadecimal), \0OOO (octal). Encodings that aren't valid remain in the output.

                  HEX_DECODE - Decode a string of hexadecimal characters into a binary.

                  HTML_ENTITY_DECODE - Replace HTML-encoded characters with unencoded characters. HTML_ENTITY_DECODE performs these operations:

                  • Replaces (ampersand)quot; with "

                  • Replaces (ampersand)nbsp; with a non-breaking space, decimal 160

                  • Replaces (ampersand)lt; with a "less than" symbol

                  • Replaces (ampersand)gt; with >

                  • Replaces characters that are represented in hexadecimal format, (ampersand)#xhhhh;, with the corresponding characters

                  • Replaces characters that are represented in decimal format, (ampersand)#nnnn;, with the corresponding characters

                  JS_DECODE - Decode JavaScript escape sequences. If a \ u HHHH code is in the full-width ASCII code range of FF01-FF5E, then the higher byte is used to detect and adjust the lower byte. If not, only the lower byte is used and the higher byte is zeroed, causing a possible loss of information.

                  LOWERCASE - Convert uppercase letters (A-Z) to lowercase (a-z).

                  MD5 - Calculate an MD5 hash from the data in the input. The computed hash is in a raw binary form.

                  NONE - Specify NONE if you don't want any text transformations.

                  NORMALIZE_PATH - Remove multiple slashes, directory self-references, and directory back-references that are not at the beginning of the input from an input string.

                  NORMALIZE_PATH_WIN - This is the same as NORMALIZE_PATH, but first converts backslash characters to forward slashes.

                  REMOVE_NULLS - Remove all NULL bytes from the input.

                  REPLACE_COMMENTS - Replace each occurrence of a C-style comment (/* ... */) with a single space. Multiple consecutive occurrences are not compressed. Unterminated comments are also replaced with a space (ASCII 0x20). However, a standalone termination of a comment (*/) is not acted upon.

                  REPLACE_NULLS - Replace NULL bytes in the input with space characters (ASCII 0x20).

                  SQL_HEX_DECODE - Decode SQL hex data. Example (0x414243) will be decoded to (ABC).

                  URL_DECODE - Decode a URL-encoded value.

                  URL_DECODE_UNI - Like URL_DECODE, but with support for Microsoft-specific %u encoding. If the code is in the full-width ASCII code range of FF01-FF5E, the higher byte is used to detect and adjust the lower byte. Otherwise, only the lower byte is used and the higher byte is zeroed.

                  UTF8_TO_UNICODE - Convert all UTF-8 character sequences to Unicode. This helps input normalization, and minimizing false-positives and false-negatives for non-English languages.

                  Possible values include:
                  • "NONE"
                  • "COMPRESS_WHITE_SPACE"
                  • "HTML_ENTITY_DECODE"
                  • "LOWERCASE"
                  • "CMD_LINE"
                  • "URL_DECODE"
                  • "BASE64_DECODE"
                  • "HEX_DECODE"
                  • "MD5"
                  • "REPLACE_COMMENTS"
                  • "ESCAPE_SEQ_DECODE"
                  • "SQL_HEX_DECODE"
                  • "CSS_DECODE"
                  • "JS_DECODE"
                  • "NORMALIZE_PATH"
                  • "NORMALIZE_PATH_WIN"
                  • "REMOVE_NULLS"
                  • "REPLACE_NULLS"
                  • "BASE64_DECODE_EXT"
                  • "URL_DECODE_UNI"
                  • "UTF8_TO_UNICODE"
            • GeoMatchStatement — (map)

              A rule statement used to identify web requests based on country of origin.

              • CountryCodes — (Array<String>)

                An array of two-character country codes, for example, [ "US", "CN" ], from the alpha-2 country ISO codes of the ISO 3166 international standard.

              • ForwardedIPConfig — (map)

                The configuration for inspecting IP addresses in an HTTP header that you specify, instead of using the IP address that's reported by the web request origin. Commonly, this is the X-Forwarded-For (XFF) header, but you can specify any header name.

                Note: If the specified header isn't present in the request, WAF doesn't apply the rule to the web request at all.
                • HeaderName — required — (String)

                  The name of the HTTP header to use for the IP address. For example, to use the X-Forwarded-For (XFF) header, set this to X-Forwarded-For.

                  Note: If the specified header isn't present in the request, WAF doesn't apply the rule to the web request at all.
                • FallbackBehavior — required — (String)

                  The match status to assign to the web request if the request doesn't have a valid IP address in the specified position.

                  Note: If the specified header isn't present in the request, WAF doesn't apply the rule to the web request at all.

                  You can specify the following fallback behaviors:

                  • MATCH - Treat the web request as matching the rule statement. WAF applies the rule action to the request.

                  • NO_MATCH - Treat the web request as not matching the rule statement.

                  Possible values include:
                  • "MATCH"
                  • "NO_MATCH"
            • RuleGroupReferenceStatement — (map)

              A rule statement used to run the rules that are defined in a RuleGroup. To use this, create a rule group with your rules, then provide the ARN of the rule group in this statement.

              You cannot nest a RuleGroupReferenceStatement, for example for use inside a NotStatement or OrStatement. You can only use a rule group reference statement at the top level inside a web ACL.

              • ARN — required — (String)

                The Amazon Resource Name (ARN) of the entity.

              • ExcludedRules — (Array<map>)

                The rules in the referenced rule group whose actions are set to Count. When you exclude a rule, WAF evaluates it exactly as it would if the rule action setting were Count. This is a useful option for testing the rules in a rule group without modifying how they handle your web traffic.

                • Name — required — (String)

                  The name of the rule whose action you want to override to Count.

            • IPSetReferenceStatement — (map)

              A rule statement used to detect web requests coming from particular IP addresses or address ranges. To use this, create an IPSet that specifies the addresses you want to detect, then use the ARN of that set in this statement. To create an IP set, see CreateIPSet.

              Each IP set rule statement references an IP set. You create and maintain the set independent of your rules. This allows you to use the single set in multiple rules. When you update the referenced set, WAF automatically updates all rules that reference it.

              • ARN — required — (String)

                The Amazon Resource Name (ARN) of the IPSet that this statement references.

              • IPSetForwardedIPConfig — (map)

                The configuration for inspecting IP addresses in an HTTP header that you specify, instead of using the IP address that's reported by the web request origin. Commonly, this is the X-Forwarded-For (XFF) header, but you can specify any header name.

                Note: If the specified header isn't present in the request, WAF doesn't apply the rule to the web request at all.
                • HeaderName — required — (String)

                  The name of the HTTP header to use for the IP address. For example, to use the X-Forwarded-For (XFF) header, set this to X-Forwarded-For.

                  Note: If the specified header isn't present in the request, WAF doesn't apply the rule to the web request at all.
                • FallbackBehavior — required — (String)

                  The match status to assign to the web request if the request doesn't have a valid IP address in the specified position.

                  Note: If the specified header isn't present in the request, WAF doesn't apply the rule to the web request at all.

                  You can specify the following fallback behaviors:

                  • MATCH - Treat the web request as matching the rule statement. WAF applies the rule action to the request.

                  • NO_MATCH - Treat the web request as not matching the rule statement.

                  Possible values include:
                  • "MATCH"
                  • "NO_MATCH"
                • Position — required — (String)

                  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:

                  • FIRST - Inspect the first IP address in the list of IP addresses in the header. This is usually the client's original IP.

                  • LAST - Inspect the last IP address in the list of IP addresses in the header.

                  • ANY - Inspect all IP addresses in the header for a match. If the header contains more than 10 IP addresses, WAF inspects the last 10.

                  Possible values include:
                  • "FIRST"
                  • "LAST"
                  • "ANY"
            • RegexPatternSetReferenceStatement — (map)

              A rule statement used to search web request components for matches with regular expressions. To use this, create a RegexPatternSet that specifies the expressions that you want to detect, then use the ARN of that set in this statement. A web request matches the pattern set rule statement if the request component matches any of the patterns in the set. To create a regex pattern set, see CreateRegexPatternSet.

              Each regex pattern set rule statement references a regex pattern set. You create and maintain the set independent of your rules. This allows you to use the single set in multiple rules. When you update the referenced set, WAF automatically updates all rules that reference it.

              • ARN — required — (String)

                The Amazon Resource Name (ARN) of the RegexPatternSet that this statement references.

              • FieldToMatch — required — (map)

                The part of a web request that you want WAF to inspect. For more information, see FieldToMatch.

                • SingleHeader — (map)

                  Inspect a single header. Provide the name of the header to inspect, for example, User-Agent or Referer. This setting isn't case sensitive.

                  Example JSON: "SingleHeader": { "Name": "haystack" }

                  • Name — required — (String)

                    The name of the query header to inspect.

                • SingleQueryArgument — (map)

                  Inspect a single query argument. Provide the name of the query argument to inspect, such as UserName or SalesRegion. The name can be up to 30 characters long and isn't case sensitive.

                  This is used only to indicate the web request component for WAF to inspect, in the FieldToMatch specification.

                  Example JSON: "SingleQueryArgument": { "Name": "myArgument" }

                  • Name — required — (String)

                    The name of the query argument to inspect.

                • AllQueryArguments — (map)

                  Inspect all query arguments.

                • UriPath — (map)

                  Inspect the request URI path. This is the part of a web request that identifies a resource, for example, /images/daily-ad.jpg.

                • QueryString — (map)

                  Inspect the query string. This is the part of a URL that appears after a ? character, if any.

                • Body — (map)

                  Inspect the request body as plain text. The request body immediately follows the request headers. This is the part of a request that contains any additional data that you want to send to your web server as the HTTP request body, such as data from a form.

                  Note that only the first 8 KB (8192 bytes) of the request body are forwarded to WAF for inspection by the underlying host service. If you don't need to inspect more than 8 KB, you can guarantee that you don't allow additional bytes in by combining a statement that inspects the body of the web request, such as ByteMatchStatement or RegexPatternSetReferenceStatement, with a SizeConstraintStatement that enforces an 8 KB size limit on the body of the request. WAF doesn't support inspecting the entire contents of web requests whose bodies exceed the 8 KB limit.

                • Method — (map)

                  Inspect the HTTP method. The method indicates the type of operation that the request is asking the origin to perform.

                • JsonBody — (map)

                  Inspect the request body as JSON. The request body immediately follows the request headers. This is the part of a request that contains any additional data that you want to send to your web server as the HTTP request body, such as data from a form.

                  Note that only the first 8 KB (8192 bytes) of the request body are forwarded to WAF for inspection by the underlying host service. If you don't need to inspect more than 8 KB, you can guarantee that you don't allow additional bytes in by combining a statement that inspects the body of the web request, such as ByteMatchStatement or RegexPatternSetReferenceStatement, with a SizeConstraintStatement that enforces an 8 KB size limit on the body of the request. WAF doesn't support inspecting the entire contents of web requests whose bodies exceed the 8 KB limit.

                  • MatchPattern — required — (map)

                    The patterns to look for in the JSON body. WAF inspects the results of these pattern matches against the rule inspection criteria.

                    • All — (map)

                      Match all of the elements. See also MatchScope in JsonBody.

                      You must specify either this setting or the IncludedPaths setting, but not both.

                    • IncludedPaths — (Array<String>)

                      Match only the specified include paths. See also MatchScope in JsonBody.

                      Provide the include paths using JSON Pointer syntax. For example, "IncludedPaths": ["/dogs/0/name", "/dogs/1/name"]. For information about this syntax, see the Internet Engineering Task Force (IETF) documentation JavaScript Object Notation (JSON) Pointer.

                      You must specify either this setting or the All setting, but not both.

                      Note: Don't use this option to include all paths. Instead, use the All setting.
                  • MatchScope — required — (String)

                    The parts of the JSON to match against using the MatchPattern. If you specify All, WAF matches against keys and values.

                    Possible values include:
                    • "ALL"
                    • "KEY"
                    • "VALUE"
                  • InvalidFallbackBehavior — (String)

                    What WAF should do if it fails to completely parse the JSON body. The options are the following:

                    • EVALUATE_AS_STRING - Inspect the body as plain text. WAF applies the text transformations and inspection criteria that you defined for the JSON inspection to the body text string.

                    • MATCH - Treat the web request as matching the rule statement. WAF applies the rule action to the request.

                    • NO_MATCH - Treat the web request as not matching the rule statement.

                    If you don't provide this setting, WAF parses and evaluates the content only up to the first parsing failure that it encounters.

                    WAF does its best to parse the entire JSON body, but might be forced to stop for reasons such as invalid characters, duplicate keys, truncation, and any content whose root node isn't an object or an array.

                    WAF parses the JSON in the following examples as two valid key, value pairs:

                    • Missing comma: {"key1":"value1""key2":"value2"}

                    • Missing colon: {"key1":"value1","key2""value2"}

                    • Extra colons: {"key1"::"value1","key2""value2"}

                    Possible values include:
                    • "MATCH"
                    • "NO_MATCH"
                    • "EVALUATE_AS_STRING"
              • TextTransformations — required — (Array<map>)

                Text transformations eliminate some of the unusual formatting that attackers use in web requests in an effort to bypass detection. If you specify one or more transformations in a rule statement, WAF performs all transformations on the content of the request component identified by FieldToMatch, starting from the lowest priority setting, before inspecting the content for a match.

                • Priority — required — (Integer)

                  Sets the relative processing order for multiple transformations that are defined for a rule statement. WAF processes all transformations, from lowest priority to highest, before inspecting the transformed content. The priorities don't need to be consecutive, but they must all be different.

                • Type — required — (String)

                  You can specify the following transformation types:

                  BASE64_DECODE - Decode a Base64-encoded string.

                  BASE64_DECODE_EXT - Decode a Base64-encoded string, but use a forgiving implementation that ignores characters that aren't valid.

                  CMD_LINE - Command-line transformations. These are helpful in reducing effectiveness of attackers who inject an operating system command-line command and use unusual formatting to disguise some or all of the command.

                  • Delete the following characters: \ " ' ^

                  • Delete spaces before the following characters: / (

                  • Replace the following characters with a space: , ;

                  • Replace multiple spaces with one space

                  • Convert uppercase letters (A-Z) to lowercase (a-z)

                  COMPRESS_WHITE_SPACE - Replace these characters with a space character (decimal 32):

                  • \f, formfeed, decimal 12

                  • \t, tab, decimal 9

                  • \n, newline, decimal 10

                  • \r, carriage return, decimal 13

                  • \v, vertical tab, decimal 11

                  • Non-breaking space, decimal 160

                  COMPRESS_WHITE_SPACE also replaces multiple spaces with one space.

                  CSS_DECODE - Decode characters that were encoded using CSS 2.x escape rules syndata.html#characters. This function uses up to two bytes in the decoding process, so it can help to uncover ASCII characters that were encoded using CSS encoding that wouldn’t typically be encoded. It's also useful in countering evasion, which is a combination of a backslash and non-hexadecimal characters. For example, ja\vascript for javascript.

                  ESCAPE_SEQ_DECODE - Decode the following ANSI C escape sequences: \a, \b, \f, \n, \r, \t, \v, \, \?, \', \", \xHH (hexadecimal), \0OOO (octal). Encodings that aren't valid remain in the output.

                  HEX_DECODE - Decode a string of hexadecimal characters into a binary.

                  HTML_ENTITY_DECODE - Replace HTML-encoded characters with unencoded characters. HTML_ENTITY_DECODE performs these operations:

                  • Replaces (ampersand)quot; with "

                  • Replaces (ampersand)nbsp; with a non-breaking space, decimal 160

                  • Replaces (ampersand)lt; with a "less than" symbol

                  • Replaces (ampersand)gt; with >

                  • Replaces characters that are represented in hexadecimal format, (ampersand)#xhhhh;, with the corresponding characters

                  • Replaces characters that are represented in decimal format, (ampersand)#nnnn;, with the corresponding characters

                  JS_DECODE - Decode JavaScript escape sequences. If a \ u HHHH code is in the full-width ASCII code range of FF01-FF5E, then the higher byte is used to detect and adjust the lower byte. If not, only the lower byte is used and the higher byte is zeroed, causing a possible loss of information.

                  LOWERCASE - Convert uppercase letters (A-Z) to lowercase (a-z).

                  MD5 - Calculate an MD5 hash from the data in the input. The computed hash is in a raw binary form.

                  NONE - Specify NONE if you don't want any text transformations.

                  NORMALIZE_PATH - Remove multiple slashes, directory self-references, and directory back-references that are not at the beginning of the input from an input string.

                  NORMALIZE_PATH_WIN - This is the same as NORMALIZE_PATH, but first converts backslash characters to forward slashes.

                  REMOVE_NULLS - Remove all NULL bytes from the input.

                  REPLACE_COMMENTS - Replace each occurrence of a C-style comment (/* ... */) with a single space. Multiple consecutive occurrences are not compressed. Unterminated comments are also replaced with a space (ASCII 0x20). However, a standalone termination of a comment (*/) is not acted upon.

                  REPLACE_NULLS - Replace NULL bytes in the input with space characters (ASCII 0x20).

                  SQL_HEX_DECODE - Decode SQL hex data. Example (0x414243) will be decoded to (ABC).

                  URL_DECODE - Decode a URL-encoded value.

                  URL_DECODE_UNI - Like URL_DECODE, but with support for Microsoft-specific %u encoding. If the code is in the full-width ASCII code range of FF01-FF5E, the higher byte is used to detect and adjust the lower byte. Otherwise, only the lower byte is used and the higher byte is zeroed.

                  UTF8_TO_UNICODE - Convert all UTF-8 character sequences to Unicode. This helps input normalization, and minimizing false-positives and false-negatives for non-English languages.

                  Possible values include:
                  • "NONE"
                  • "COMPRESS_WHITE_SPACE"
                  • "HTML_ENTITY_DECODE"
                  • "LOWERCASE"
                  • "CMD_LINE"
                  • "URL_DECODE"
                  • "BASE64_DECODE"
                  • "HEX_DECODE"
                  • "MD5"
                  • "REPLACE_COMMENTS"
                  • "ESCAPE_SEQ_DECODE"
                  • "SQL_HEX_DECODE"
                  • "CSS_DECODE"
                  • "JS_DECODE"
                  • "NORMALIZE_PATH"
                  • "NORMALIZE_PATH_WIN"
                  • "REMOVE_NULLS"
                  • "REPLACE_NULLS"
                  • "BASE64_DECODE_EXT"
                  • "URL_DECODE_UNI"
                  • "UTF8_TO_UNICODE"
            • RateBasedStatement — (map)

              A rate-based rule tracks the rate of requests for each originating IP address, and triggers the rule action when the rate exceeds a limit that you specify on the number of requests in any 5-minute time span. You can use this to put a temporary block on requests from an IP address that is sending excessive requests.

              WAF tracks and manages web requests separately for each instance of a rate-based rule that you use. For example, if you provide the same rate-based rule settings in two web ACLs, each of the two rule statements represents a separate instance of the rate-based rule and gets its own tracking and management by WAF. If you define a rate-based rule inside a rule group, and then use that rule group in multiple places, each use creates a separate instance of the rate-based rule that gets its own tracking and management by WAF.

              When the rule action triggers, WAF blocks additional requests from the IP address until the request rate falls below the limit.

              You can optionally nest another statement inside the rate-based statement, to narrow the scope of the rule so that it only counts requests that match the nested statement. For example, based on recent requests that you have seen from an attacker, you might create a rate-based rule with a nested AND rule statement that contains the following nested statements:

              • An IP match statement with an IP set that specified the address 192.0.2.44.

              • A string match statement that searches in the User-Agent header for the string BadBot.

              In this rate-based rule, you also define a rate limit. For this example, the rate limit is 1,000. Requests that meet both of the conditions in the statements are counted. If the count exceeds 1,000 requests per five minutes, the rule action triggers. Requests that do not meet both conditions are not counted towards the rate limit and are not affected by this rule.

              You cannot nest a RateBasedStatement inside another statement, for example inside a NotStatement or OrStatement. You can define a RateBasedStatement inside a web ACL and inside a rule group.

              • Limit — required — (Integer)

                The limit on requests per 5-minute period for a single originating IP address. If the statement includes a ScopeDownStatement, this limit is applied only to the requests that match the statement.

              • AggregateKeyType — required — (String)

                Setting that indicates how to aggregate the request counts. The options are the following:

                • IP - Aggregate the request counts on the IP address from the web request origin.

                • FORWARDED_IP - Aggregate the request counts on the first IP address in an HTTP header. If you use this, configure the ForwardedIPConfig, to specify the header to use.

                Possible values include:
                • "IP"
                • "FORWARDED_IP"
              • ForwardedIPConfig — (map)

                The configuration for inspecting IP addresses in an HTTP header that you specify, instead of using the IP address that's reported by the web request origin. Commonly, this is the X-Forwarded-For (XFF) header, but you can specify any header name.

                Note: If the specified header isn't present in the request, WAF doesn't apply the rule to the web request at all.

                This is required if AggregateKeyType is set to FORWARDED_IP.

                • HeaderName — required — (String)

                  The name of the HTTP header to use for the IP address. For example, to use the X-Forwarded-For (XFF) header, set this to X-Forwarded-For.

                  Note: If the specified header isn't present in the request, WAF doesn't apply the rule to the web request at all.
                • FallbackBehavior — required — (String)

                  The match status to assign to the web request if the request doesn't have a valid IP address in the specified position.

                  Note: If the specified header isn't present in the request, WAF doesn't apply the rule to the web request at all.

                  You can specify the following fallback behaviors:

                  • MATCH - Treat the web request as matching the rule statement. WAF applies the rule action to the request.

                  • NO_MATCH - Treat the web request as not matching the rule statement.

                  Possible values include:
                  • "MATCH"
                  • "NO_MATCH"
            • AndStatement — (map)

              A logical rule statement used to combine other rule statements with AND logic. You provide more than one Statement within the AndStatement.

              • Statements — required — (Array<map>)

                The statements to combine with AND logic. You can use any statements that can be nested.

            • OrStatement — (map)

              A logical rule statement used to combine other rule statements with OR logic. You provide more than one Statement within the OrStatement.

              • Statements — required — (Array<map>)

                The statements to combine with OR logic. You can use any statements that can be nested.

            • NotStatement — (map)

              A logical rule statement used to negate the results of another rule statement. You provide one Statement within the NotStatement.

            • ManagedRuleGroupStatement — (map)

              A rule statement used to run the rules that are defined in a managed rule group. To use this, provide the vendor name and the name of the rule group in this statement. You can retrieve the required names by calling ListAvailableManagedRuleGroups.

              You cannot nest a ManagedRuleGroupStatement, for example for use inside a NotStatement or OrStatement. It can only be referenced as a top-level statement within a rule.

              • VendorName — required — (String)

                The name of the managed rule group vendor. You use this, along with the rule group name, to identify the rule group.

              • Name — required — (String)

                The name of the managed rule group. You use this, along with the vendor name, to identify the rule group.

              • Version — (String)

                The version of the managed rule group to use. If you specify this, the version setting is fixed until you change it. If you don't specify this, WAF uses the vendor's default version, and then keeps the version at the vendor's default when the vendor updates the managed rule group settings.

              • ExcludedRules — (Array<map>)

                The rules in the referenced rule group whose actions are set to Count. When you exclude a rule, WAF evaluates it exactly as it would if the rule action setting were Count. This is a useful option for testing the rules in a rule group without modifying how they handle your web traffic.

                • Name — required — (String)

                  The name of the rule whose action you want to override to Count.

            • LabelMatchStatement — (map)

              A rule statement that defines a string match search against labels that have been added to the web request by rules that have already run in the web ACL.

              The label match statement provides the label or namespace string to search for. The label string can represent a part or all of the fully qualified label name that had been added to the web request. Fully qualified labels have a prefix, optional namespaces, and label name. The prefix identifies the rule group or web ACL context of the rule that added the label. If you do not provide the fully qualified name in your label match string, WAF performs the search for labels that were added in the same context as the label match statement.

              • Scope — required — (String)

                Specify whether you want to match using the label name or just the namespace.

                Possible values include:
                • "LABEL"
                • "NAMESPACE"
              • Key — required — (String)

                The string to match against. The setting you provide for this depends on the match statement's Scope setting:

                • If the Scope indicates LABEL, then this specification must include the name and can include any number of preceding namespace specifications and prefix up to providing the fully qualified label name.

                • If the Scope indicates NAMESPACE, then this specification can include any number of contiguous namespace strings, and can include the entire label namespace prefix from the rule group or web ACL where the label originates.

                Labels are case sensitive and components of a label must be separated by colon, for example NS1:NS2:name.

            • RegexMatchStatement — (map)

              A rule statement used to search web request components for a match against a single regular expression.

              • RegexString — required — (String)

                The string representing the regular expression.

              • FieldToMatch — required — (map)

                The part of a web request that you want WAF to inspect. For more information, see FieldToMatch.

                • SingleHeader — (map)

                  Inspect a single header. Provide the name of the header to inspect, for example, User-Agent or Referer. This setting isn't case sensitive.

                  Example JSON: "SingleHeader": { "Name": "haystack" }

                  • Name — required — (String)

                    The name of the query header to inspect.

                • SingleQueryArgument — (map)

                  Inspect a single query argument. Provide the name of the query argument to inspect, such as UserName or SalesRegion. The name can be up to 30 characters long and isn't case sensitive.

                  This is used only to indicate the web request component for WAF to inspect, in the FieldToMatch specification.

                  Example JSON: "SingleQueryArgument": { "Name": "myArgument" }

                  • Name — required — (String)

                    The name of the query argument to inspect.

                • AllQueryArguments — (map)

                  Inspect all query arguments.

                • UriPath — (map)

                  Inspect the request URI path. This is the part of a web request that identifies a resource, for example, /images/daily-ad.jpg.

                • QueryString — (map)

                  Inspect the query string. This is the part of a URL that appears after a ? character, if any.

                • Body — (map)

                  Inspect the request body as plain text. The request body immediately follows the request headers. This is the part of a request that contains any additional data that you want to send to your web server as the HTTP request body, such as data from a form.

                  Note that only the first 8 KB (8192 bytes) of the request body are forwarded to WAF for inspection by the underlying host service. If you don't need to inspect more than 8 KB, you can guarantee that you don't allow additional bytes in by combining a statement that inspects the body of the web request, such as ByteMatchStatement or RegexPatternSetReferenceStatement, with a SizeConstraintStatement that enforces an 8 KB size limit on the body of the request. WAF doesn't support inspecting the entire contents of web requests whose bodies exceed the 8 KB limit.

                • Method — (map)

                  Inspect the HTTP method. The method indicates the type of operation that the request is asking the origin to perform.

                • JsonBody — (map)

                  Inspect the request body as JSON. The request body immediately follows the request headers. This is the part of a request that contains any additional data that you want to send to your web server as the HTTP request body, such as data from a form.

                  Note that only the first 8 KB (8192 bytes) of the request body are forwarded to WAF for inspection by the underlying host service. If you don't need to inspect more than 8 KB, you can guarantee that you don't allow additional bytes in by combining a statement that inspects the body of the web request, such as ByteMatchStatement or RegexPatternSetReferenceStatement, with a SizeConstraintStatement that enforces an 8 KB size limit on the body of the request. WAF doesn't support inspecting the entire contents of web requests whose bodies exceed the 8 KB limit.

                  • MatchPattern — required — (map)

                    The patterns to look for in the JSON body. WAF inspects the results of these pattern matches against the rule inspection criteria.

                    • All — (map)

                      Match all of the elements. See also MatchScope in JsonBody.

                      You must specify either this setting or the IncludedPaths setting, but not both.

                    • IncludedPaths — (Array<String>)

                      Match only the specified include paths. See also MatchScope in JsonBody.

                      Provide the include paths using JSON Pointer syntax. For example, "IncludedPaths": ["/dogs/0/name", "/dogs/1/name"]. For information about this syntax, see the Internet Engineering Task Force (IETF) documentation JavaScript Object Notation (JSON) Pointer.

                      You must specify either this setting or the All setting, but not both.

                      Note: Don't use this option to include all paths. Instead, use the All setting.
                  • MatchScope — required — (String)

                    The parts of the JSON to match against using the MatchPattern. If you specify All, WAF matches against keys and values.

                    Possible values include:
                    • "ALL"
                    • "KEY"
                    • "VALUE"
                  • InvalidFallbackBehavior — (String)

                    What WAF should do if it fails to completely parse the JSON body. The options are the following:

                    • EVALUATE_AS_STRING - Inspect the body as plain text. WAF applies the text transformations and inspection criteria that you defined for the JSON inspection to the body text string.

                    • MATCH - Treat the web request as matching the rule statement. WAF applies the rule action to the request.

                    • NO_MATCH - Treat the web request as not matching the rule statement.

                    If you don't provide this setting, WAF parses and evaluates the content only up to the first parsing failure that it encounters.

                    WAF does its best to parse the entire JSON body, but might be forced to stop for reasons such as invalid characters, duplicate keys, truncation, and any content whose root node isn't an object or an array.

                    WAF parses the JSON in the following examples as two valid key, value pairs:

                    • Missing comma: {"key1":"value1""key2":"value2"}

                    • Missing colon: {"key1":"value1","key2""value2"}

                    • Extra colons: {"key1"::"value1","key2""value2"}

                    Possible values include:
                    • "MATCH"
                    • "NO_MATCH"
                    • "EVALUATE_AS_STRING"
              • TextTransformations — required — (Array<map>)

                Text transformations eliminate some of the unusual formatting that attackers use in web requests in an effort to bypass detection. If you specify one or more transformations in a rule statement, WAF performs all transformations on the content of the request component identified by FieldToMatch, starting from the lowest priority setting, before inspecting the content for a match.

                • Priority — required — (Integer)

                  Sets the relative processing order for multiple transformations that are defined for a rule statement. WAF processes all transformations, from lowest priority to highest, before inspecting the transformed content. The priorities don't need to be consecutive, but they must all be different.

                • Type — required — (String)

                  You can specify the following transformation types:

                  BASE64_DECODE - Decode a Base64-encoded string.

                  BASE64_DECODE_EXT - Decode a Base64-encoded string, but use a forgiving implementation that ignores characters that aren't valid.

                  CMD_LINE - Command-line transformations. These are helpful in reducing effectiveness of attackers who inject an operating system command-line command and use unusual formatting to disguise some or all of the command.

                  • Delete the following characters: \ " ' ^

                  • Delete spaces before the following characters: / (

                  • Replace the following characters with a space: , ;

                  • Replace multiple spaces with one space

                  • Convert uppercase letters (A-Z) to lowercase (a-z)

                  COMPRESS_WHITE_SPACE - Replace these characters with a space character (decimal 32):

                  • \f, formfeed, decimal 12

                  • \t, tab, decimal 9

                  • \n, newline, decimal 10

                  • \r, carriage return, decimal 13

                  • \v, vertical tab, decimal 11

                  • Non-breaking space, decimal 160

                  COMPRESS_WHITE_SPACE also replaces multiple spaces with one space.

                  CSS_DECODE - Decode characters that were encoded using CSS 2.x escape rules syndata.html#characters. This function uses up to two bytes in the decoding process, so it can help to uncover ASCII characters that were encoded using CSS encoding that wouldn’t typically be encoded. It's also useful in countering evasion, which is a combination of a backslash and non-hexadecimal characters. For example, ja\vascript for javascript.

                  ESCAPE_SEQ_DECODE - Decode the following ANSI C escape sequences: \a, \b, \f, \n, \r, \t, \v, \, \?, \', \", \xHH (hexadecimal), \0OOO (octal). Encodings that aren't valid remain in the output.

                  HEX_DECODE - Decode a string of hexadecimal characters into a binary.

                  HTML_ENTITY_DECODE - Replace HTML-encoded characters with unencoded characters. HTML_ENTITY_DECODE performs these operations:

                  • Replaces (ampersand)quot; with "

                  • Replaces (ampersand)nbsp; with a non-breaking space, decimal 160

                  • Replaces (ampersand)lt; with a "less than" symbol

                  • Replaces (ampersand)gt; with >

                  • Replaces characters that are represented in hexadecimal format, (ampersand)#xhhhh;, with the corresponding characters

                  • Replaces characters that are represented in decimal format, (ampersand)#nnnn;, with the corresponding characters

                  JS_DECODE - Decode JavaScript escape sequences. If a \ u HHHH code is in the full-width ASCII code range of FF01-FF5E, then the higher byte is used to detect and adjust the lower byte. If not, only the lower byte is used and the higher byte is zeroed, causing a possible loss of information.

                  LOWERCASE - Convert uppercase letters (A-Z) to lowercase (a-z).

                  MD5 - Calculate an MD5 hash from the data in the input. The computed hash is in a raw binary form.

                  NONE - Specify NONE if you don't want any text transformations.

                  NORMALIZE_PATH - Remove multiple slashes, directory self-references, and directory back-references that are not at the beginning of the input from an input string.

                  NORMALIZE_PATH_WIN - This is the same as NORMALIZE_PATH, but first converts backslash characters to forward slashes.

                  REMOVE_NULLS - Remove all NULL bytes from the input.

                  REPLACE_COMMENTS - Replace each occurrence of a C-style comment (/* ... */) with a single space. Multiple consecutive occurrences are not compressed. Unterminated comments are also replaced with a space (ASCII 0x20). However, a standalone termination of a comment (*/) is not acted upon.

                  REPLACE_NULLS - Replace NULL bytes in the input with space characters (ASCII 0x20).

                  SQL_HEX_DECODE - Decode SQL hex data. Example (0x414243) will be decoded to (ABC).

                  URL_DECODE - Decode a URL-encoded value.

                  URL_DECODE_UNI - Like URL_DECODE, but with support for Microsoft-specific %u encoding. If the code is in the full-width ASCII code range of FF01-FF5E, the higher byte is used to detect and adjust the lower byte. Otherwise, only the lower byte is used and the higher byte is zeroed.

                  UTF8_TO_UNICODE - Convert all UTF-8 character sequences to Unicode. This helps input normalization, and minimizing false-positives and false-negatives for non-English languages.

                  Possible values include:
                  • "NONE"
                  • "COMPRESS_WHITE_SPACE"
                  • "HTML_ENTITY_DECODE"
                  • "LOWERCASE"
                  • "CMD_LINE"
                  • "URL_DECODE"
                  • "BASE64_DECODE"
                  • "HEX_DECODE"
                  • "MD5"
                  • "REPLACE_COMMENTS"
                  • "ESCAPE_SEQ_DECODE"
                  • "SQL_HEX_DECODE"
                  • "CSS_DECODE"
                  • "JS_DECODE"
                  • "NORMALIZE_PATH"
                  • "NORMALIZE_PATH_WIN"
                  • "REMOVE_NULLS"
                  • "REPLACE_NULLS"
                  • "BASE64_DECODE_EXT"
                  • "URL_DECODE_UNI"
                  • "UTF8_TO_UNICODE"
          • Action — (map)

            The action that WAF should take on a web request when it matches the rule statement. Settings at the web ACL level can override the rule action setting.

            This is used only for rules whose statements do not reference a rule group. Rule statements that reference a rule group include RuleGroupReferenceStatement and ManagedRuleGroupStatement.

            You must specify either this Action setting or the rule OverrideAction setting, but not both:

            • If the rule statement does not reference a rule group, use this rule action setting and not the rule override action setting.

            • If the rule statement references a rule group, use the override action setting and not this action setting.

            • Block — (map)

              Instructs WAF to block the web request.

              • CustomResponse — (map)

                Defines a custom response for the web request.

                For information about customizing web requests and responses, see Customizing web requests and responses in WAF in the WAF Developer Guide.

                • ResponseCode — required — (Integer)

                  The HTTP status code to return to the client.

                  For a list of status codes that you can use in your custom reqponses, see Supported status codes for custom response in the WAF Developer Guide.

                • CustomResponseBodyKey — (String)

                  References the response body that you want WAF to return to the web request client. You can define a custom response for a rule action or a default web ACL action that is set to block. To do this, you first define the response body key and value in the CustomResponseBodies setting for the WebACL or RuleGroup where you want to use it. Then, in the rule action or web ACL default action BlockAction setting, you reference the response body using this key.

                • ResponseHeaders — (Array<map>)

                  The HTTP headers to use in the response. Duplicate header names are not allowed.

                  For information about the limits on count and size for custom request and response settings, see WAF quotas in the WAF Developer Guide.

                  • Name — required — (String)

                    The name of the custom header.

                    For custom request header insertion, when WAF inserts the header into the request, it prefixes this name x-amzn-waf-, to avoid confusion with the headers that are already in the request. For example, for the header name sample, WAF inserts the header x-amzn-waf-sample.

                  • Value — required — (String)

                    The value of the custom header.

            • Allow — (map)

              Instructs WAF to allow the web request.

              • CustomRequestHandling — (map)

                Defines custom handling for the web request.

                For information about customizing web requests and responses, see Customizing web requests and responses in WAF in the WAF Developer Guide.

                • InsertHeaders — required — (Array<map>)

                  The HTTP headers to insert into the request. Duplicate header names are not allowed.

                  For information about the limits on count and size for custom request and response settings, see WAF quotas in the WAF Developer Guide.

                  • Name — required — (String)

                    The name of the custom header.

                    For custom request header insertion, when WAF inserts the header into the request, it prefixes this name x-amzn-waf-, to avoid confusion with the headers that are already in the request. For example, for the header name sample, WAF inserts the header x-amzn-waf-sample.

                  • Value — required — (String)

                    The value of the custom header.

            • Count — (map)

              Instructs WAF to count the web request and allow it.

              • CustomRequestHandling — (map)

                Defines custom handling for the web request.

                For information about customizing web requests and responses, see Customizing web requests and responses in WAF in the WAF Developer Guide.

                • InsertHeaders — required — (Array<map>)

                  The HTTP headers to insert into the request. Duplicate header names are not allowed.

                  For information about the limits on count and size for custom request and response settings, see WAF quotas in the WAF Developer Guide.

                  • Name — required — (String)

                    The name of the custom header.

                    For custom request header insertion, when WAF inserts the header into the request, it prefixes this name x-amzn-waf-, to avoid confusion with the headers that are already in the request. For example, for the header name sample, WAF inserts the header x-amzn-waf-sample.

                  • Value — required — (String)

                    The value of the custom header.

            • Captcha — (map)

              Instructs WAF to run a CAPTCHA check against the web request.

              • CustomRequestHandling — (map)

                Defines custom handling for the web request.

                For information about customizing web requests and responses, see Customizing web requests and responses in WAF in the WAF Developer Guide.

                • InsertHeaders — required — (Array<map>)

                  The HTTP headers to insert into the request. Duplicate header names are not allowed.

                  For information about the limits on count and size for custom request and response settings, see WAF quotas in the WAF Developer Guide.

                  • Name — required — (String)

                    The name of the custom header.

                    For custom request header insertion, when WAF inserts the header into the request, it prefixes this name x-amzn-waf-, to avoid confusion with the headers that are already in the request. For example, for the header name sample, WAF inserts the header x-amzn-waf-sample.

                  • Value — required — (String)

                    The value of the custom header.

          • OverrideAction — (map)

            The action to use in the place of the action that results from the rule group evaluation. Set the override action to none to leave the result of the rule group alone. Set it to count to override the result to count only.

            You can only use this for rule statements that reference a rule group, like RuleGroupReferenceStatement and ManagedRuleGroupStatement.

            Note: This option is usually set to none. It does not affect how the rules in the rule group are evaluated. If you want the rules in the rule group to only count matches, do not use this and instead exclude those rules in your rule group reference statement settings.
            • Count — (map)

              Override the rule group evaluation result to count only.

              Note: This option is usually set to none. It does not affect how the rules in the rule group are evaluated. If you want the rules in the rule group to only count matches, do not use this and instead exclude those rules in your rule group reference statement settings.
              • CustomRequestHandling — (map)

                Defines custom handling for the web request.

                For information about customizing web requests and responses, see Customizing web requests and responses in WAF in the WAF Developer Guide.

                • InsertHeaders — required — (Array<map>)

                  The HTTP headers to insert into the request. Duplicate header names are not allowed.

                  For information about the limits on count and size for custom request and response settings, see WAF quotas in the WAF Developer Guide.

                  • Name — required — (String)

                    The name of the custom header.

                    For custom request header insertion, when WAF inserts the header into the request, it prefixes this name x-amzn-waf-, to avoid confusion with the headers that are already in the request. For example, for the header name sample, WAF inserts the header x-amzn-waf-sample.

                  • Value — required — (String)

                    The value of the custom header.

            • None — (map)

              Don't override the rule group evaluation result. This is the most common setting.

          • RuleLabels — (Array<map>)

            Labels to apply to web requests that match the rule match statement. WAF applies fully qualified labels to matching web requests. A fully qualified label is the concatenation of a label namespace and a rule label. The rule's rule group or web ACL defines the label namespace.

            Rules that run after this rule in the web ACL can match against these labels using a LabelMatchStatement.

            For each label, provide a case-sensitive string containing optional namespaces and a label name, according to the following guidelines:

            • Separate each component of the label with a colon.

            • Each namespace or name can have up to 128 characters.

            • You can specify up to 5 namespaces in a label.

            • Don't use the following reserved words in your label specification: aws, waf, managed, rulegroup, webacl, regexpatternset, or ipset.

            For example, myLabelName or nameSpace1:nameSpace2:myLabelName.

            • Name — required — (String)

              The label string.

          • VisibilityConfig — required — (map)

            Defines and enables Amazon CloudWatch metrics and web request sample collection.

            • SampledRequestsEnabled — required — (Boolean)

              A boolean indicating whether WAF should store a sampling of the web requests that match the rules. You can view the sampled requests through the WAF console.

            • CloudWatchMetricsEnabled — required — (Boolean)

              A boolean indicating whether the associated resource sends metrics to Amazon CloudWatch. For the list of available metrics, see WAF Metrics.

            • MetricName — required — (String)

              A name of the Amazon CloudWatch metric. The name can contain only the characters: A-Z, a-z, 0-9, - (hyphen), and _ (underscore). The name can be from one to 128 characters long. It can't contain whitespace or metric names reserved for WAF, for example "All" and "Default_Action."

          • CaptchaConfig — (map)

            Specifies how WAF should handle CAPTCHA evaluations. If you don't specify this, WAF uses the CAPTCHA configuration that's defined for the web ACL.

            • ImmunityTimeProperty — (map)

              Determines how long a CAPTCHA token remains valid after the client successfully solves a CAPTCHA puzzle.

              • ImmunityTime — required — (Integer)

                The amount of time, in seconds, that a CAPTCHA token is valid. The default setting is 300.

        • VisibilityConfig — required — (map)

          Defines and enables Amazon CloudWatch metrics and web request sample collection.

          • SampledRequestsEnabled — required — (Boolean)

            A boolean indicating whether WAF should store a sampling of the web requests that match the rules. You can view the sampled requests through the WAF console.

          • CloudWatchMetricsEnabled — required — (Boolean)

            A boolean indicating whether the associated resource sends metrics to Amazon CloudWatch. For the list of available metrics, see WAF Metrics.

          • MetricName — required — (String)

            A name of the Amazon CloudWatch metric. The name can contain only the characters: A-Z, a-z, 0-9, - (hyphen), and _ (underscore). The name can be from one to 128 characters long. It can't contain whitespace or metric names reserved for WAF, for example "All" and "Default_Action."

        • Capacity — (Integer)

          The web ACL capacity units (WCUs) currently being used by this web ACL.

          WAF uses WCUs to calculate and control the operating resources that are used to run your rules, rule groups, and web ACLs. WAF calculates capacity differently for each rule type, to reflect the relative cost of each rule. Simple rules that cost little to run use fewer WCUs than more complex rules that use more processing power. Rule group capacity is fixed at creation, which helps users plan their web ACL WCU usage when they use a rule group. The WCU limit for web ACLs is 1,500.

        • PreProcessFirewallManagerRuleGroups — (Array<map>)

          The first set of rules for WAF to process in the web ACL. This is defined in an Firewall Manager WAF policy and contains only rule group references. You can't alter these. Any rules and rule groups that you define for the web ACL are prioritized after these.

          In the Firewall Manager WAF policy, the Firewall Manager administrator can define a set of rule groups to run first in the web ACL and a set of rule groups to run last. Within each set, the administrator prioritizes the rule groups, to determine their relative processing order.

          • Name — required — (String)

            The name of the rule group. You cannot change the name of a rule group after you create it.

          • Priority — required — (Integer)

            If you define more than one rule group in the first or last Firewall Manager rule groups, WAF evaluates each request against the rule groups in order, starting from the lowest priority setting. The priorities don't need to be consecutive, but they must all be different.

          • FirewallManagerStatement — required — (map)

            The processing guidance for an Firewall Manager rule. This is like a regular rule Statement, but it can only contain a rule group reference.

            • ManagedRuleGroupStatement — (map)

              A rule statement used to run the rules that are defined in a managed rule group. To use this, provide the vendor name and the name of the rule group in this statement. You can retrieve the required names by calling ListAvailableManagedRuleGroups.

              You cannot nest a ManagedRuleGroupStatement, for example for use inside a NotStatement or OrStatement. It can only be referenced as a top-level statement within a rule.

              • VendorName — required — (String)

                The name of the managed rule group vendor. You use this, along with the rule group name, to identify the rule group.

              • Name — required — (String)

                The name of the managed rule group. You use this, along with the vendor name, to identify the rule group.

              • Version — (String)

                The version of the managed rule group to use. If you specify this, the version setting is fixed until you change it. If you don't specify this, WAF uses the vendor's default version, and then keeps the version at the vendor's default when the vendor updates the managed rule group settings.

              • ExcludedRules — (Array<map>)

                The rules in the referenced rule group whose actions are set to Count. When you exclude a rule, WAF evaluates it exactly as it would if the rule action setting were Count. This is a useful option for testing the rules in a rule group without modifying how they handle your web traffic.

                • Name — required — (String)

                  The name of the rule whose action you want to override to Count.

              • ScopeDownStatement — (map)

                An optional nested statement that narrows the scope of the web requests that are evaluated by the managed rule group. Requests are only evaluated by the rule group if they match the scope-down statement. You can use any nestable Statement in the scope-down statement, and you can nest statements at any level, the same as you can for a rule statement.

                • ByteMatchStatement — (map)

                  A rule statement that defines a string match search for WAF to apply to web requests. The byte match statement provides the bytes to search for, the location in requests that you want WAF to search, and other settings. The bytes to search for are typically a string that corresponds with ASCII characters. In the WAF console and the developer guide, this is refered to as a string match statement.

                  • SearchString — required — (Buffer, Typed Array, Blob, String)

                    A string value that you want WAF to search for. WAF searches only in the part of web requests that you designate for inspection in FieldToMatch. The maximum length of the value is 50 bytes.

                    Valid values depend on the component that you specify for inspection in FieldToMatch:

                    • Method: The HTTP method that you want WAF to search for. This indicates the type of operation specified in the request.

                    • UriPath: The value that you want WAF to search for in the URI path, for example, /images/daily-ad.jpg.

                    If SearchString includes alphabetic characters A-Z and a-z, note that the value is case sensitive.

                    If you're using the WAF API

                    Specify a base64-encoded version of the value. The maximum length of the value before you base64-encode it is 50 bytes.

                    For example, suppose the value of Type is HEADER and the value of Data is User-Agent. If you want to search the User-Agent header for the value BadBot, you base64-encode BadBot using MIME base64-encoding and include the resulting value, QmFkQm90, in the value of SearchString.

                    If you're using the CLI or one of the Amazon Web Services SDKs

                    The value that you want WAF to search for. The SDK automatically base64 encodes the value.

                  • FieldToMatch — required — (map)

                    The part of a web request that you want WAF to inspect. For more information, see FieldToMatch.

                    • SingleHeader — (map)

                      Inspect a single header. Provide the name of the header to inspect, for example, User-Agent or Referer. This setting isn't case sensitive.

                      Example JSON: "SingleHeader": { "Name": "haystack" }

                      • Name — required — (String)

                        The name of the query header to inspect.

                    • SingleQueryArgument — (map)

                      Inspect a single query argument. Provide the name of the query argument to inspect, such as UserName or SalesRegion. The name can be up to 30 characters long and isn't case sensitive.

                      This is used only to indicate the web request component for WAF to inspect, in the FieldToMatch specification.

                      Example JSON: "SingleQueryArgument": { "Name": "myArgument" }

                      • Name — required — (String)

                        The name of the query argument to inspect.

                    • AllQueryArguments — (map)

                      Inspect all query arguments.

                    • UriPath — (map)

                      Inspect the request URI path. This is the part of a web request that identifies a resource, for example, /images/daily-ad.jpg.

                    • QueryString — (map)

                      Inspect the query string. This is the part of a URL that appears after a ? character, if any.

                    • Body — (map)

                      Inspect the request body as plain text. The request body immediately follows the request headers. This is the part of a request that contains any additional data that you want to send to your web server as the HTTP request body, such as data from a form.

                      Note that only the first 8 KB (8192 bytes) of the request body are forwarded to WAF for inspection by the underlying host service. If you don't need to inspect more than 8 KB, you can guarantee that you don't allow additional bytes in by combining a statement that inspects the body of the web request, such as ByteMatchStatement or RegexPatternSetReferenceStatement, with a SizeConstraintStatement that enforces an 8 KB size limit on the body of the request. WAF doesn't support inspecting the entire contents of web requests whose bodies exceed the 8 KB limit.

                    • Method — (map)

                      Inspect the HTTP method. The method indicates the type of operation that the request is asking the origin to perform.

                    • JsonBody — (map)

                      Inspect the request body as JSON. The request body immediately follows the request headers. This is the part of a request that contains any additional data that you want to send to your web server as the HTTP request body, such as data from a form.

                      Note that only the first 8 KB (8192 bytes) of the request body are forwarded to WAF for inspection by the underlying host service. If you don't need to inspect more than 8 KB, you can guarantee that you don't allow additional bytes in by combining a statement that inspects the body of the web request, such as ByteMatchStatement or RegexPatternSetReferenceStatement, with a SizeConstraintStatement that enforces an 8 KB size limit on the body of the request. WAF doesn't support inspecting the entire contents of web requests whose bodies exceed the 8 KB limit.

                      • MatchPattern — required — (map)

                        The patterns to look for in the JSON body. WAF inspects the results of these pattern matches against the rule inspection criteria.

                        • All — (map)

                          Match all of the elements. See also MatchScope in JsonBody.

                          You must specify either this setting or the IncludedPaths setting, but not both.

                        • IncludedPaths — (Array<String>)

                          Match only the specified include paths. See also MatchScope in JsonBody.

                          Provide the include paths using JSON Pointer syntax. For example, "IncludedPaths": ["/dogs/0/name", "/dogs/1/name"]. For information about this syntax, see the Internet Engineering Task Force (IETF) documentation JavaScript Object Notation (JSON) Pointer.

                          You must specify either this setting or the All setting, but not both.

                          Note: Don't use this option to include all paths. Instead, use the All setting.
                      • MatchScope — required — (String)

                        The parts of the JSON to match against using the MatchPattern. If you specify All, WAF matches against keys and values.

                        Possible values include:
                        • "ALL"
                        • "KEY"
                        • "VALUE"
                      • InvalidFallbackBehavior — (String)

                        What WAF should do if it fails to completely parse the JSON body. The options are the following:

                        • EVALUATE_AS_STRING - Inspect the body as plain text. WAF applies the text transformations and inspection criteria that you defined for the JSON inspection to the body text string.

                        • MATCH - Treat the web request as matching the rule statement. WAF applies the rule action to the request.

                        • NO_MATCH - Treat the web request as not matching the rule statement.

                        If you don't provide this setting, WAF parses and evaluates the content only up to the first parsing failure that it encounters.

                        WAF does its best to parse the entire JSON body, but might be forced to stop for reasons such as invalid characters, duplicate keys, truncation, and any content whose root node isn't an object or an array.

                        WAF parses the JSON in the following examples as two valid key, value pairs:

                        • Missing comma: {"key1":"value1""key2":"value2"}

                        • Missing colon: {"key1":"value1","key2""value2"}

                        • Extra colons: {"key1"::"value1","key2""value2"}

                        Possible values include:
                        • "MATCH"
                        • "NO_MATCH"
                        • "EVALUATE_AS_STRING"
                  • TextTransformations — required — (Array<map>)

                    Text transformations eliminate some of the unusual formatting that attackers use in web requests in an effort to bypass detection. If you specify one or more transformations in a rule statement, WAF performs all transformations on the content of the request component identified by FieldToMatch, starting from the lowest priority setting, before inspecting the content for a match.

                    • Priority — required — (Integer)

                      Sets the relative processing order for multiple transformations that are defined for a rule statement. WAF processes all transformations, from lowest priority to highest, before inspecting the transformed content. The priorities don't need to be consecutive, but they must all be different.

                    • Type — required — (String)

                      You can specify the following transformation types:

                      BASE64_DECODE - Decode a Base64-encoded string.

                      BASE64_DECODE_EXT - Decode a Base64-encoded string, but use a forgiving implementation that ignores characters that aren't valid.

                      CMD_LINE - Command-line transformations. These are helpful in reducing effectiveness of attackers who inject an operating system command-line command and use unusual formatting to disguise some or all of the command.

                      • Delete the following characters: \ " ' ^

                      • Delete spaces before the following characters: / (

                      • Replace the following characters with a space: , ;

                      • Replace multiple spaces with one space

                      • Convert uppercase letters (A-Z) to lowercase (a-z)

                      COMPRESS_WHITE_SPACE - Replace these characters with a space character (decimal 32):

                      • \f, formfeed, decimal 12

                      • \t, tab, decimal 9

                      • \n, newline, decimal 10

                      • \r, carriage return, decimal 13

                      • \v, vertical tab, decimal 11

                      • Non-breaking space, decimal 160

                      COMPRESS_WHITE_SPACE also replaces multiple spaces with one space.

                      CSS_DECODE - Decode characters that were encoded using CSS 2.x escape rules syndata.html#characters. This function uses up to two bytes in the decoding process, so it can help to uncover ASCII characters that were encoded using CSS encoding that wouldn’t typically be encoded. It's also useful in countering evasion, which is a combination of a backslash and non-hexadecimal characters. For example, ja\vascript for javascript.

                      ESCAPE_SEQ_DECODE - Decode the following ANSI C escape sequences: \a, \b, \f, \n, \r, \t, \v, \, \?, \', \", \xHH (hexadecimal), \0OOO (octal). Encodings that aren't valid remain in the output.

                      HEX_DECODE - Decode a string of hexadecimal characters into a binary.

                      HTML_ENTITY_DECODE - Replace HTML-encoded characters with unencoded characters. HTML_ENTITY_DECODE performs these operations:

                      • Replaces (ampersand)quot; with "

                      • Replaces (ampersand)nbsp; with a non-breaking space, decimal 160

                      • Replaces (ampersand)lt; with a "less than" symbol

                      • Replaces (ampersand)gt; with >

                      • Replaces characters that are represented in hexadecimal format, (ampersand)#xhhhh;, with the corresponding characters

                      • Replaces characters that are represented in decimal format, (ampersand)#nnnn;, with the corresponding characters

                      JS_DECODE - Decode JavaScript escape sequences. If a \ u HHHH code is in the full-width ASCII code range of FF01-FF5E, then the higher byte is used to detect and adjust the lower byte. If not, only the lower byte is used and the higher byte is zeroed, causing a possible loss of information.

                      LOWERCASE - Convert uppercase letters (A-Z) to lowercase (a-z).

                      MD5 - Calculate an MD5 hash from the data in the input. The computed hash is in a raw binary form.

                      NONE - Specify NONE if you don't want any text transformations.

                      NORMALIZE_PATH - Remove multiple slashes, directory self-references, and directory back-references that are not at the beginning of the input from an input string.

                      NORMALIZE_PATH_WIN - This is the same as NORMALIZE_PATH, but first converts backslash characters to forward slashes.

                      REMOVE_NULLS - Remove all NULL bytes from the input.

                      REPLACE_COMMENTS - Replace each occurrence of a C-style comment (/* ... */) with a single space. Multiple consecutive occurrences are not compressed. Unterminated comments are also replaced with a space (ASCII 0x20). However, a standalone termination of a comment (*/) is not acted upon.

                      REPLACE_NULLS - Replace NULL bytes in the input with space characters (ASCII 0x20).

                      SQL_HEX_DECODE - Decode SQL hex data. Example (0x414243) will be decoded to (ABC).

                      URL_DECODE - Decode a URL-encoded value.

                      URL_DECODE_UNI - Like URL_DECODE, but with support for Microsoft-specific %u encoding. If the code is in the full-width ASCII code range of FF01-FF5E, the higher byte is used to detect and adjust the lower byte. Otherwise, only the lower byte is used and the higher byte is zeroed.

                      UTF8_TO_UNICODE - Convert all UTF-8 character sequences to Unicode. This helps input normalization, and minimizing false-positives and false-negatives for non-English languages.

                      Possible values include:
                      • "NONE"
                      • "COMPRESS_WHITE_SPACE"
                      • "HTML_ENTITY_DECODE"
                      • "LOWERCASE"
                      • "CMD_LINE"
                      • "URL_DECODE"
                      • "BASE64_DECODE"
                      • "HEX_DECODE"
                      • "MD5"
                      • "REPLACE_COMMENTS"
                      • "ESCAPE_SEQ_DECODE"
                      • "SQL_HEX_DECODE"
                      • "CSS_DECODE"
                      • "JS_DECODE"
                      • "NORMALIZE_PATH"
                      • "NORMALIZE_PATH_WIN"
                      • "REMOVE_NULLS"
                      • "REPLACE_NULLS"
                      • "BASE64_DECODE_EXT"
                      • "URL_DECODE_UNI"
                      • "UTF8_TO_UNICODE"
                  • PositionalConstraint — required — (String)

                    The area within the portion of a web request that you want WAF to search for SearchString. Valid values include the following:

                    CONTAINS

                    The specified part of the web request must include the value of SearchString, but the location doesn't matter.

                    CONTAINS_WORD

                    The specified part of the web request must include the value of SearchString, and SearchString must contain only alphanumeric characters or underscore (A-Z, a-z, 0-9, or ). In addition, SearchString must be a word, which means that both of the following are true:

                    • SearchString is at the beginning of the specified part of the web request or is preceded by a character other than an alphanumeric character or underscore (). Examples include the value of a header and ;BadBot.

                    • SearchString is at the end of the specified part of the web request or is followed by a character other than an alphanumeric character or underscore (_), for example, BadBot; and -BadBot;.

                    EXACTLY

                    The value of the specified part of the web request must exactly match the value of SearchString.

                    STARTS_WITH

                    The value of SearchString must appear at the beginning of the specified part of the web request.

                    ENDS_WITH

                    The value of SearchString must appear at the end of the specified part of the web request.

                    Possible values include:
                    • "EXACTLY"
                    • "STARTS_WITH"
                    • "ENDS_WITH"
                    • "CONTAINS"
                    • "CONTAINS_WORD"
                • SqliMatchStatement — (map)

                  Attackers sometimes insert malicious SQL code into web requests in an effort to extract data from your database. To allow or block web requests that appear to contain malicious SQL code, create one or more SQL injection match conditions. An SQL injection match condition identifies the part of web requests, such as the URI or the query string, that you want WAF to inspect. Later in the process, when you create a web ACL, you specify whether to allow or block requests that appear to contain malicious SQL code.

                  • FieldToMatch — required — (map)

                    The part of a web request that you want WAF to inspect. For more information, see FieldToMatch.

                    • SingleHeader — (map)

                      Inspect a single header. Provide the name of the header to inspect, for example, User-Agent or Referer. This setting isn't case sensitive.

                      Example JSON: "SingleHeader": { "Name": "haystack" }

                      • Name — required — (String)

                        The name of the query header to inspect.

                    • SingleQueryArgument — (map)

                      Inspect a single query argument. Provide the name of the query argument to inspect, such as UserName or SalesRegion. The name can be up to 30 characters long and isn't case sensitive.

                      This is used only to indicate the web request component for WAF to inspect, in the FieldToMatch specification.

                      Example JSON: "SingleQueryArgument": { "Name": "myArgument" }

                      • Name — required — (String)

                        The name of the query argument to inspect.

                    • AllQueryArguments — (map)

                      Inspect all query arguments.

                    • UriPath — (map)

                      Inspect the request URI path. This is the part of a web request that identifies a resource, for example, /images/daily-ad.jpg.

                    • QueryString — (map)

                      Inspect the query string. This is the part of a URL that appears after a ? character, if any.

                    • Body — (map)

                      Inspect the request body as plain text. The request body immediately follows the request headers. This is the part of a request that contains any additional data that you want to send to your web server as the HTTP request body, such as data from a form.

                      Note that only the first 8 KB (8192 bytes) of the request body are forwarded to WAF for inspection by the underlying host service. If you don't need to inspect more than 8 KB, you can guarantee that you don't allow additional bytes in by combining a statement that inspects the body of the web request, such as ByteMatchStatement or RegexPatternSetReferenceStatement, with a SizeConstraintStatement that enforces an 8 KB size limit on the body of the request. WAF doesn't support inspecting the entire contents of web requests whose bodies exceed the 8 KB limit.

                    • Method — (map)

                      Inspect the HTTP method. The method indicates the type of operation that the request is asking the origin to perform.

                    • JsonBody — (map)

                      Inspect the request body as JSON. The request body immediately follows the request headers. This is the part of a request that contains any additional data that you want to send to your web server as the HTTP request body, such as data from a form.

                      Note that only the first 8 KB (8192 bytes) of the request body are forwarded to WAF for inspection by the underlying host service. If you don't need to inspect more than 8 KB, you can guarantee that you don't allow additional bytes in by combining a statement that inspects the body of the web request, such as ByteMatchStatement or RegexPatternSetReferenceStatement, with a SizeConstraintStatement that enforces an 8 KB size limit on the body of the request. WAF doesn't support inspecting the entire contents of web requests whose bodies exceed the 8 KB limit.

                      • MatchPattern — required — (map)

                        The patterns to look for in the JSON body. WAF inspects the results of these pattern matches against the rule inspection criteria.

                        • All — (map)

                          Match all of the elements. See also MatchScope in JsonBody.

                          You must specify either this setting or the IncludedPaths setting, but not both.

                        • IncludedPaths — (Array<String>)

                          Match only the specified include paths. See also MatchScope in JsonBody.

                          Provide the include paths using JSON Pointer syntax. For example, "IncludedPaths": ["/dogs/0/name", "/dogs/1/name"]. For information about this syntax, see the Internet Engineering Task Force (IETF) documentation JavaScript Object Notation (JSON) Pointer.

                          You must specify either this setting or the All setting, but not both.

                          Note: Don't use this option to include all paths. Instead, use the All setting.
                      • MatchScope — required — (String)

                        The parts of the JSON to match against using the MatchPattern. If you specify All, WAF matches against keys and values.

                        Possible values include:
                        • "ALL"
                        • "KEY"
                        • "VALUE"
                      • InvalidFallbackBehavior — (String)

                        What WAF should do if it fails to completely parse the JSON body. The options are the following:

                        • EVALUATE_AS_STRING - Inspect the body as plain text. WAF applies the text transformations and inspection criteria that you defined for the JSON inspection to the body text string.

                        • MATCH - Treat the web request as matching the rule statement. WAF applies the rule action to the request.

                        • NO_MATCH - Treat the web request as not matching the rule statement.

                        If you don't provide this setting, WAF parses and evaluates the content only up to the first parsing failure that it encounters.

                        WAF does its best to parse the entire JSON body, but might be forced to stop for reasons such as invalid characters, duplicate keys, truncation, and any content whose root node isn't an object or an array.

                        WAF parses the JSON in the following examples as two valid key, value pairs:

                        • Missing comma: {"key1":"value1""key2":"value2"}

                        • Missing colon: {"key1":"value1","key2""value2"}

                        • Extra colons: {"key1"::"value1","key2""value2"}

                        Possible values include:
                        • "MATCH"
                        • "NO_MATCH"
                        • "EVALUATE_AS_STRING"
                  • TextTransformations — required — (Array<map>)

                    Text transformations eliminate some of the unusual formatting that attackers use in web requests in an effort to bypass detection. If you specify one or more transformations in a rule statement, WAF performs all transformations on the content of the request component identified by FieldToMatch, starting from the lowest priority setting, before inspecting the content for a match.

                    • Priority — required — (Integer)

                      Sets the relative processing order for multiple transformations that are defined for a rule statement. WAF processes all transformations, from lowest priority to highest, before inspecting the transformed content. The priorities don't need to be consecutive, but they must all be different.

                    • Type — required — (String)

                      You can specify the following transformation types:

                      BASE64_DECODE - Decode a Base64-encoded string.

                      BASE64_DECODE_EXT - Decode a Base64-encoded string, but use a forgiving implementation that ignores characters that aren't valid.

                      CMD_LINE - Command-line transformations. These are helpful in reducing effectiveness of attackers who inject an operating system command-line command and use unusual formatting to disguise some or all of the command.

                      • Delete the following characters: \ " ' ^

                      • Delete spaces before the following characters: / (

                      • Replace the following characters with a space: , ;

                      • Replace multiple spaces with one space

                      • Convert uppercase letters (A-Z) to lowercase (a-z)

                      COMPRESS_WHITE_SPACE - Replace these characters with a space character (decimal 32):

                      • \f, formfeed, decimal 12

                      • \t, tab, decimal 9

                      • \n, newline, decimal 10

                      • \r, carriage return, decimal 13

                      • \v, vertical tab, decimal 11

                      • Non-breaking space, decimal 160

                      COMPRESS_WHITE_SPACE also replaces multiple spaces with one space.

                      CSS_DECODE - Decode characters that were encoded using CSS 2.x escape rules syndata.html#characters. This function uses up to two bytes in the decoding process, so it can help to uncover ASCII characters that were encoded using CSS encoding that wouldn’t typically be encoded. It's also useful in countering evasion, which is a combination of a backslash and non-hexadecimal characters. For example, ja\vascript for javascript.

                      ESCAPE_SEQ_DECODE - Decode the following ANSI C escape sequences: \a, \b, \f, \n, \r, \t, \v, \, \?, \', \", \xHH (hexadecimal), \0OOO (octal). Encodings that aren't valid remain in the output.

                      HEX_DECODE - Decode a string of hexadecimal characters into a binary.

                      HTML_ENTITY_DECODE - Replace HTML-encoded characters with unencoded characters. HTML_ENTITY_DECODE performs these operations:

                      • Replaces (ampersand)quot; with "

                      • Replaces (ampersand)nbsp; with a non-breaking space, decimal 160

                      • Replaces (ampersand)lt; with a "less than" symbol

                      • Replaces (ampersand)gt; with >

                      • Replaces characters that are represented in hexadecimal format, (ampersand)#xhhhh;, with the corresponding characters

                      • Replaces characters that are represented in decimal format, (ampersand)#nnnn;, with the corresponding characters

                      JS_DECODE - Decode JavaScript escape sequences. If a \ u HHHH code is in the full-width ASCII code range of FF01-FF5E, then the higher byte is used to detect and adjust the lower byte. If not, only the lower byte is used and the higher byte is zeroed, causing a possible loss of information.

                      LOWERCASE - Convert uppercase letters (A-Z) to lowercase (a-z).

                      MD5 - Calculate an MD5 hash from the data in the input. The computed hash is in a raw binary form.

                      NONE - Specify NONE if you don't want any text transformations.

                      NORMALIZE_PATH - Remove multiple slashes, directory self-references, and directory back-references that are not at the beginning of the input from an input string.

                      NORMALIZE_PATH_WIN - This is the same as NORMALIZE_PATH, but first converts backslash characters to forward slashes.

                      REMOVE_NULLS - Remove all NULL bytes from the input.

                      REPLACE_COMMENTS - Replace each occurrence of a C-style comment (/* ... */) with a single space. Multiple consecutive occurrences are not compressed. Unterminated comments are also replaced with a space (ASCII 0x20). However, a standalone termination of a comment (*/) is not acted upon.

                      REPLACE_NULLS - Replace NULL bytes in the input with space characters (ASCII 0x20).

                      SQL_HEX_DECODE - Decode SQL hex data. Example (0x414243) will be decoded to (ABC).

                      URL_DECODE - Decode a URL-encoded value.

                      URL_DECODE_UNI - Like URL_DECODE, but with support for Microsoft-specific %u encoding. If the code is in the full-width ASCII code range of FF01-FF5E, the higher byte is used to detect and adjust the lower byte. Otherwise, only the lower byte is used and the higher byte is zeroed.

                      UTF8_TO_UNICODE - Convert all UTF-8 character sequences to Unicode. This helps input normalization, and minimizing false-positives and false-negatives for non-English languages.

                      Possible values include:
                      • "NONE"
                      • "COMPRESS_WHITE_SPACE"
                      • "HTML_ENTITY_DECODE"
                      • "LOWERCASE"
                      • "CMD_LINE"
                      • "URL_DECODE"
                      • "BASE64_DECODE"
                      • "HEX_DECODE"
                      • "MD5"
                      • "REPLACE_COMMENTS"
                      • "ESCAPE_SEQ_DECODE"
                      • "SQL_HEX_DECODE"
                      • "CSS_DECODE"
                      • "JS_DECODE"
                      • "NORMALIZE_PATH"
                      • "NORMALIZE_PATH_WIN"
                      • "REMOVE_NULLS"
                      • "REPLACE_NULLS"
                      • "BASE64_DECODE_EXT"
                      • "URL_DECODE_UNI"
                      • "UTF8_TO_UNICODE"
                • XssMatchStatement — (map)

                  A rule statement that defines a cross-site scripting (XSS) match search for WAF to apply to web requests. XSS attacks are those where the attacker uses vulnerabilities in a benign website as a vehicle to inject malicious client-site scripts into other legitimate web browsers. The XSS match statement provides the location in requests that you want WAF to search and text transformations to use on the search area before WAF searches for character sequences that are likely to be malicious strings.

                  • FieldToMatch — required — (map)

                    The part of a web request that you want WAF to inspect. For more information, see FieldToMatch.

                    • SingleHeader — (map)

                      Inspect a single header. Provide the name of the header to inspect, for example, User-Agent or Referer. This setting isn't case sensitive.

                      Example JSON: "SingleHeader": { "Name": "haystack" }

                      • Name — required — (String)

                        The name of the query header to inspect.

                    • SingleQueryArgument — (map)

                      Inspect a single query argument. Provide the name of the query argument to inspect, such as UserName or SalesRegion. The name can be up to 30 characters long and isn't case sensitive.

                      This is used only to indicate the web request component for WAF to inspect, in the FieldToMatch specification.

                      Example JSON: "SingleQueryArgument": { "Name": "myArgument" }

                      • Name — required — (String)

                        The name of the query argument to inspect.

                    • AllQueryArguments — (map)

                      Inspect all query arguments.

                    • UriPath — (map)

                      Inspect the request URI path. This is the part of a web request that identifies a resource, for example, /images/daily-ad.jpg.

                    • QueryString — (map)

                      Inspect the query string. This is the part of a URL that appears after a ? character, if any.

                    • Body — (map)

                      Inspect the request body as plain text. The request body immediately follows the request headers. This is the part of a request that contains any additional data that you want to send to your web server as the HTTP request body, such as data from a form.

                      Note that only the first 8 KB (8192 bytes) of the request body are forwarded to WAF for inspection by the underlying host service. If you don't need to inspect more than 8 KB, you can guarantee that you don't allow additional bytes in by combining a statement that inspects the body of the web request, such as ByteMatchStatement or RegexPatternSetReferenceStatement, with a SizeConstraintStatement that enforces an 8 KB size limit on the body of the request. WAF doesn't support inspecting the entire contents of web requests whose bodies exceed the 8 KB limit.

                    • Method — (map)

                      Inspect the HTTP method. The method indicates the type of operation that the request is asking the origin to perform.

                    • JsonBody — (map)

                      Inspect the request body as JSON. The request body immediately follows the request headers. This is the part of a request that contains any additional data that you want to send to your web server as the HTTP request body, such as data from a form.

                      Note that only the first 8 KB (8192 bytes) of the request body are forwarded to WAF for inspection by the underlying host service. If you don't need to inspect more than 8 KB, you can guarantee that you don't allow additional bytes in by combining a statement that inspects the body of the web request, such as ByteMatchStatement or RegexPatternSetReferenceStatement, with a SizeConstraintStatement that enforces an 8 KB size limit on the body of the request. WAF doesn't support inspecting the entire contents of web requests whose bodies exceed the 8 KB limit.

                      • MatchPattern — required — (map)

                        The patterns to look for in the JSON body. WAF inspects the results of these pattern matches against the rule inspection criteria.

                        • All — (map)

                          Match all of the elements. See also MatchScope in JsonBody.

                          You must specify either this setting or the IncludedPaths setting, but not both.

                        • IncludedPaths — (Array<String>)

                          Match only the specified include paths. See also MatchScope in JsonBody.

                          Provide the include paths using JSON Pointer syntax. For example, "IncludedPaths": ["/dogs/0/name", "/dogs/1/name"]. For information about this syntax, see the Internet Engineering Task Force (IETF) documentation JavaScript Object Notation (JSON) Pointer.

                          You must specify either this setting or the All setting, but not both.

                          Note: Don't use this option to include all paths. Instead, use the All setting.
                      • MatchScope — required — (String)

                        The parts of the JSON to match against using the MatchPattern. If you specify All, WAF matches against keys and values.

                        Possible values include:
                        • "ALL"
                        • "KEY"
                        • "VALUE"
                      • InvalidFallbackBehavior — (String)

                        What WAF should do if it fails to completely parse the JSON body. The options are the following:

                        • EVALUATE_AS_STRING - Inspect the body as plain text. WAF applies the text transformations and inspection criteria that you defined for the JSON inspection to the body text string.

                        • MATCH - Treat the web request as matching the rule statement. WAF applies the rule action to the request.

                        • NO_MATCH - Treat the web request as not matching the rule statement.

                        If you don't provide this setting, WAF parses and evaluates the content only up to the first parsing failure that it encounters.

                        WAF does its best to parse the entire JSON body, but might be forced to stop for reasons such as invalid characters, duplicate keys, truncation, and any content whose root node isn't an object or an array.

                        WAF parses the JSON in the following examples as two valid key, value pairs:

                        • Missing comma: {"key1":"value1""key2":"value2"}

                        • Missing colon: {"key1":"value1","key2""value2"}

                        • Extra colons: {"key1"::"value1","key2""value2"}

                        Possible values include:
                        • "MATCH"
                        • "NO_MATCH"
                        • "EVALUATE_AS_STRING"
                  • TextTransformations — required — (Array<map>)

                    Text transformations eliminate some of the unusual formatting that attackers use in web requests in an effort to bypass detection. If you specify one or more transformations in a rule statement, WAF performs all transformations on the content of the request component identified by FieldToMatch, starting from the lowest priority setting, before inspecting the content for a match.

                    • Priority — required — (Integer)

                      Sets the relative processing order for multiple transformations that are defined for a rule statement. WAF processes all transformations, from lowest priority to highest, before inspecting the transformed content. The priorities don't need to be consecutive, but they must all be different.

                    • Type — required — (String)

                      You can specify the following transformation types:

                      BASE64_DECODE - Decode a Base64-encoded string.

                      BASE64_DECODE_EXT - Decode a Base64-encoded string, but use a forgiving implementation that ignores characters that aren't valid.

                      CMD_LINE - Command-line transformations. These are helpful in reducing effectiveness of attackers who inject an operating system command-line command and use unusual formatting to disguise some or all of the command.

                      • Delete the following characters: \ " ' ^

                      • Delete spaces before the following characters: / (

                      • Replace the following characters with a space: , ;

                      • Replace multiple spaces with one space

                      • Convert uppercase letters (A-Z) to lowercase (a-z)

                      COMPRESS_WHITE_SPACE - Replace these characters with a space character (decimal 32):

                      • \f, formfeed, decimal 12

                      • \t, tab, decimal 9

                      • \n, newline, decimal 10

                      • \r, carriage return, decimal 13

                      • \v, vertical tab, decimal 11

                      • Non-breaking space, decimal 160

                      COMPRESS_WHITE_SPACE also replaces multiple spaces with one space.

                      CSS_DECODE - Decode characters that were encoded using CSS 2.x escape rules syndata.html#characters. This function uses up to two bytes in the decoding process, so it can help to uncover ASCII characters that were encoded using CSS encoding that wouldn’t typically be encoded. It's also useful in countering evasion, which is a combination of a backslash and non-hexadecimal characters. For example, ja\vascript for javascript.

                      ESCAPE_SEQ_DECODE - Decode the following ANSI C escape sequences: \a, \b, \f, \n, \r, \t, \v, \, \?, \', \", \xHH (hexadecimal), \0OOO (octal). Encodings that aren't valid remain in the output.

                      HEX_DECODE - Decode a string of hexadecimal characters into a binary.

                      HTML_ENTITY_DECODE - Replace HTML-encoded characters with unencoded characters. HTML_ENTITY_DECODE performs these operations:

                      • Replaces (ampersand)quot; with "

                      • Replaces (ampersand)nbsp; with a non-breaking space, decimal 160

                      • Replaces (ampersand)lt; with a "less than" symbol

                      • Replaces (ampersand)gt; with >

                      • Replaces characters that are represented in hexadecimal format, (ampersand)#xhhhh;, with the corresponding characters

                      • Replaces characters that are represented in decimal format, (ampersand)#nnnn;, with the corresponding characters

                      JS_DECODE - Decode JavaScript escape sequences. If a \ u HHHH code is in the full-width ASCII code range of FF01-FF5E, then the higher byte is used to detect and adjust the lower byte. If not, only the lower byte is used and the higher byte is zeroed, causing a possible loss of information.

                      LOWERCASE - Convert uppercase letters (A-Z) to lowercase (a-z).

                      MD5 - Calculate an MD5 hash from the data in the input. The computed hash is in a raw binary form.

                      NONE - Specify NONE if you don't want any text transformations.

                      NORMALIZE_PATH - Remove multiple slashes, directory self-references, and directory back-references that are not at the beginning of the input from an input string.

                      NORMALIZE_PATH_WIN - This is the same as NORMALIZE_PATH, but first converts backslash characters to forward slashes.

                      REMOVE_NULLS - Remove all NULL bytes from the input.

                      REPLACE_COMMENTS - Replace each occurrence of a C-style comment (/* ... */) with a single space. Multiple consecutive occurrences are not compressed. Unterminated comments are also replaced with a space (ASCII 0x20). However, a standalone termination of a comment (*/) is not acted upon.

                      REPLACE_NULLS - Replace NULL bytes in the input with space characters (ASCII 0x20).

                      SQL_HEX_DECODE - Decode SQL hex data. Example (0x414243) will be decoded to (ABC).

                      URL_DECODE - Decode a URL-encoded value.

                      URL_DECODE_UNI - Like URL_DECODE, but with support for Microsoft-specific %u encoding. If the code is in the full-width ASCII code range of FF01-FF5E, the higher byte is used to detect and adjust the lower byte. Otherwise, only the lower byte is used and the higher byte is zeroed.

                      UTF8_TO_UNICODE - Convert all UTF-8 character sequences to Unicode. This helps input normalization, and minimizing false-positives and false-negatives for non-English languages.

                      Possible values include:
                      • "NONE"
                      • "COMPRESS_WHITE_SPACE"
                      • "HTML_ENTITY_DECODE"
                      • "LOWERCASE"
                      • "CMD_LINE"
                      • "URL_DECODE"
                      • "BASE64_DECODE"
                      • "HEX_DECODE"
                      • "MD5"
                      • "REPLACE_COMMENTS"
                      • "ESCAPE_SEQ_DECODE"
                      • "SQL_HEX_DECODE"
                      • "CSS_DECODE"
                      • "JS_DECODE"
                      • "NORMALIZE_PATH"
                      • "NORMALIZE_PATH_WIN"
                      • "REMOVE_NULLS"
                      • "REPLACE_NULLS"
                      • "BASE64_DECODE_EXT"
                      • "URL_DECODE_UNI"
                      • "UTF8_TO_UNICODE"
                • SizeConstraintStatement — (map)

                  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 first 8192 bytes (8 KB). If the request body for your web requests never exceeds 8192 bytes, you can create a size constraint condition and block requests that have a request body greater than 8192 bytes.

                  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.

                  • FieldToMatch — required — (map)

                    The part of a web request that you want WAF to inspect. For more information, see FieldToMatch.

                    • SingleHeader — (map)

                      Inspect a single header. Provide the name of the header to inspect, for example, User-Agent or Referer. This setting isn't case sensitive.

                      Example JSON: "SingleHeader": { "Name": "haystack" }

                      • Name — required — (String)

                        The name of the query header to inspect.

                    • SingleQueryArgument — (map)

                      Inspect a single query argument. Provide the name of the query argument to inspect, such as UserName or SalesRegion. The name can be up to 30 characters long and isn't case sensitive.

                      This is used only to indicate the web request component for WAF to inspect, in the FieldToMatch specification.

                      Example JSON: "SingleQueryArgument": { "Name": "myArgument" }

                      • Name — required — (String)

                        The name of the query argument to inspect.

                    • AllQueryArguments — (map)

                      Inspect all query arguments.

                    • UriPath — (map)

                      Inspect the request URI path. This is the part of a web request that identifies a resource, for example, /images/daily-ad.jpg.

                    • QueryString — (map)

                      Inspect the query string. This is the part of a URL that appears after a ? character, if any.

                    • Body — (map)

                      Inspect the request body as plain text. The request body immediately follows the request headers. This is the part of a request that contains any additional data that you want to send to your web server as the HTTP request body, such as data from a form.

                      Note that only the first 8 KB (8192 bytes) of the request body are forwarded to WAF for inspection by the underlying host service. If you don't need to inspect more than 8 KB, you can guarantee that you don't allow additional bytes in by combining a statement that inspects the body of the web request, such as ByteMatchStatement or RegexPatternSetReferenceStatement, with a SizeConstraintStatement that enforces an 8 KB size limit on the body of the request. WAF doesn't support inspecting the entire contents of web requests whose bodies exceed the 8 KB limit.

                    • Method — (map)

                      Inspect the HTTP method. The method indicates the type of operation that the request is asking the origin to perform.

                    • JsonBody — (map)

                      Inspect the request body as JSON. The request body immediately follows the request headers. This is the part of a request that contains any additional data that you want to send to your web server as the HTTP request body, such as data from a form.

                      Note that only the first 8 KB (8192 bytes) of the request body are forwarded to WAF for inspection by the underlying host service. If you don't need to inspect more than 8 KB, you can guarantee that you don't allow additional bytes in by combining a statement that inspects the body of the web request, such as ByteMatchStatement or RegexPatternSetReferenceStatement, with a SizeConstraintStatement that enforces an 8 KB size limit on the body of the request. WAF doesn't support inspecting the entire contents of web requests whose bodies exceed the 8 KB limit.

                      • MatchPattern — required — (map)

                        The patterns to look for in the JSON body. WAF inspects the results of these pattern matches against the rule inspection criteria.

                        • All — (map)

                          Match all of the elements. See also MatchScope in JsonBody.

                          You must specify either this setting or the IncludedPaths setting, but not both.

                        • IncludedPaths — (Array<String>)

                          Match only the specified include paths. See also MatchScope in JsonBody.

                          Provide the include paths using JSON Pointer syntax. For example, "IncludedPaths": ["/dogs/0/name", "/dogs/1/name"]. For information about this syntax, see the Internet Engineering Task Force (IETF) documentation JavaScript Object Notation (JSON) Pointer.

                          You must specify either this setting or the All setting, but not both.

                          Note: Don't use this option to include all paths. Instead, use the All setting.
                      • MatchScope — required — (String)

                        The parts of the JSON to match against using the MatchPattern. If you specify All, WAF matches against keys and values.

                        Possible values include:
                        • "ALL"
                        • "KEY"
                        • "VALUE"
                      • InvalidFallbackBehavior — (String)

                        What WAF should do if it fails to completely parse the JSON body. The options are the following:

                        • EVALUATE_AS_STRING - Inspect the body as plain text. WAF applies the text transformations and inspection criteria that you defined for the JSON inspection to the body text string.

                        • MATCH - Treat the web request as matching the rule statement. WAF applies the rule action to the request.

                        • NO_MATCH - Treat the web request as not matching the rule statement.

                        If you don't provide this setting, WAF parses and evaluates the content only up to the first parsing failure that it encounters.

                        WAF does its best to parse the entire JSON body, but might be forced to stop for reasons such as invalid characters, duplicate keys, truncation, and any content whose root node isn't an object or an array.

                        WAF parses the JSON in the following examples as two valid key, value pairs:

                        • Missing comma: {"key1":"value1""key2":"value2"}

                        • Missing colon: {"key1":"value1","key2""value2"}

                        • Extra colons: {"key1"::"value1","key2""value2"}

                        Possible values include:
                        • "MATCH"
                        • "NO_MATCH"
                        • "EVALUATE_AS_STRING"
                  • ComparisonOperator — required — (String)

                    The operator to use to compare the request part to the size setting.

                    Possible values include:
                    • "EQ"
                    • "NE"
                    • "LE"
                    • "LT"
                    • "GE"
                    • "GT"
                  • Size — required — (Integer)

                    The size, in byte, to compare to the request part, after any transformations.

                  • TextTransformations — required — (Array<map>)

                    Text transformations eliminate some of the unusual formatting that attackers use in web requests in an effort to bypass detection. If you specify one or more transformations in a rule statement, WAF performs all transformations on the content of the request component identified by FieldToMatch, starting from the lowest priority setting, before inspecting the content for a match.

                    • Priority — required — (Integer)

                      Sets the relative processing order for multiple transformations that are defined for a rule statement. WAF processes all transformations, from lowest priority to highest, before inspecting the transformed content. The priorities don't need to be consecutive, but they must all be different.

                    • Type — required — (String)

                      You can specify the following transformation types:

                      BASE64_DECODE - Decode a Base64-encoded string.

                      BASE64_DECODE_EXT - Decode a Base64-encoded string, but use a forgiving implementation that ignores characters that aren't valid.

                      CMD_LINE - Command-line transformations. These are helpful in reducing effectiveness of attackers who inject an operating system command-line command and use unusual formatting to disguise some or all of the command.

                      • Delete the following characters: \ " ' ^

                      • Delete spaces before the following characters: / (

                      • Replace the following characters with a space: , ;

                      • Replace multiple spaces with one space

                      • Convert uppercase letters (A-Z) to lowercase (a-z)

                      COMPRESS_WHITE_SPACE - Replace these characters with a space character (decimal 32):

                      • \f, formfeed, decimal 12

                      • \t, tab, decimal 9

                      • \n, newline, decimal 10

                      • \r, carriage return, decimal 13

                      • \v, vertical tab, decimal 11

                      • Non-breaking space, decimal 160

                      COMPRESS_WHITE_SPACE also replaces multiple spaces with one space.

                      CSS_DECODE - Decode characters that were encoded using CSS 2.x escape rules syndata.html#characters. This function uses up to two bytes in the decoding process, so it can help to uncover ASCII characters that were encoded using CSS encoding that wouldn’t typically be encoded. It's also useful in countering evasion, which is a combination of a backslash and non-hexadecimal characters. For example, ja\vascript for javascript.

                      ESCAPE_SEQ_DECODE - Decode the following ANSI C escape sequences: \a, \b, \f, \n, \r, \t, \v, \, \?, \', \", \xHH (hexadecimal), \0OOO (octal). Encodings that aren't valid remain in the output.

                      HEX_DECODE - Decode a string of hexadecimal characters into a binary.

                      HTML_ENTITY_DECODE - Replace HTML-encoded characters with unencoded characters. HTML_ENTITY_DECODE performs these operations:

                      • Replaces (ampersand)quot; with "

                      • Replaces (ampersand)nbsp; with a non-breaking space, decimal 160

                      • Replaces (ampersand)lt; with a "less than" symbol

                      • Replaces (ampersand)gt; with >

                      • Replaces characters that are represented in hexadecimal format, (ampersand)#xhhhh;, with the corresponding characters

                      • Replaces characters that are represented in decimal format, (ampersand)#nnnn;, with the corresponding characters

                      JS_DECODE - Decode JavaScript escape sequences. If a \ u HHHH code is in the full-width ASCII code range of FF01-FF5E, then the higher byte is used to detect and adjust the lower byte. If not, only the lower byte is used and the higher byte is zeroed, causing a possible loss of information.

                      LOWERCASE - Convert uppercase letters (A-Z) to lowercase (a-z).

                      MD5 - Calculate an MD5 hash from the data in the input. The computed hash is in a raw binary form.

                      NONE - Specify NONE if you don't want any text transformations.

                      NORMALIZE_PATH - Remove multiple slashes, directory self-references, and directory back-references that are not at the beginning of the input from an input string.

                      NORMALIZE_PATH_WIN - This is the same as NORMALIZE_PATH, but first converts backslash characters to forward slashes.

                      REMOVE_NULLS - Remove all NULL bytes from the input.

                      REPLACE_COMMENTS - Replace each occurrence of a C-style comment (/* ... */) with a single space. Multiple consecutive occurrences are not compressed. Unterminated comments are also replaced with a space (ASCII 0x20). However, a standalone termination of a comment (*/) is not acted upon.

                      REPLACE_NULLS - Replace NULL bytes in the input with space characters (ASCII 0x20).

                      SQL_HEX_DECODE - Decode SQL hex data. Example (0x414243) will be decoded to (ABC).

                      URL_DECODE - Decode a URL-encoded value.

                      URL_DECODE_UNI - Like URL_DECODE, but with support for Microsoft-specific %u encoding. If the code is in the full-width ASCII code range of FF01-FF5E, the higher byte is used to detect and adjust the lower byte. Otherwise, only the lower byte is used and the higher byte is zeroed.

                      UTF8_TO_UNICODE - Convert all UTF-8 character sequences to Unicode. This helps input normalization, and minimizing false-positives and false-negatives for non-English languages.

                      Possible values include:
                      • "NONE"
                      • "COMPRESS_WHITE_SPACE"
                      • "HTML_ENTITY_DECODE"
                      • "LOWERCASE"
                      • "CMD_LINE"
                      • "URL_DECODE"
                      • "BASE64_DECODE"
                      • "HEX_DECODE"
                      • "MD5"
                      • "REPLACE_COMMENTS"
                      • "ESCAPE_SEQ_DECODE"
                      • "SQL_HEX_DECODE"
                      • "CSS_DECODE"
                      • "JS_DECODE"
                      • "NORMALIZE_PATH"
                      • "NORMALIZE_PATH_WIN"
                      • "REMOVE_NULLS"
                      • "REPLACE_NULLS"
                      • "BASE64_DECODE_EXT"
                      • "URL_DECODE_UNI"
                      • "UTF8_TO_UNICODE"
                • GeoMatchStatement — (map)

                  A rule statement used to identify web requests based on country of origin.

                  • CountryCodes — (Array<String>)

                    An array of two-character country codes, for example, [ "US", "CN" ], from the alpha-2 country ISO codes of the ISO 3166 international standard.

                  • ForwardedIPConfig — (map)

                    The configuration for inspecting IP addresses in an HTTP header that you specify, instead of using the IP address that's reported by the web request origin. Commonly, this is the X-Forwarded-For (XFF) header, but you can specify any header name.

                    Note: If the specified header isn't present in the request, WAF doesn't apply the rule to the web request at all.
                    • HeaderName — required — (String)

                      The name of the HTTP header to use for the IP address. For example, to use the X-Forwarded-For (XFF) header, set this to X-Forwarded-For.

                      Note: If the specified header isn't present in the request, WAF doesn't apply the rule to the web request at all.
                    • FallbackBehavior — required — (String)

                      The match status to assign to the web request if the request doesn't have a valid IP address in the specified position.

                      Note: If the specified header isn't present in the request, WAF doesn't apply the rule to the web request at all.

                      You can specify the following fallback behaviors:

                      • MATCH - Treat the web request as matching the rule statement. WAF applies the rule action to the request.

                      • NO_MATCH - Treat the web request as not matching the rule statement.

                      Possible values include:
                      • "MATCH"
                      • "NO_MATCH"
                • RuleGroupReferenceStatement — (map)

                  A rule statement used to run the rules that are defined in a RuleGroup. To use this, create a rule group with your rules, then provide the ARN of the rule group in this statement.

                  You cannot nest a RuleGroupReferenceStatement, for example for use inside a NotStatement or OrStatement. You can only use a rule group reference statement at the top level inside a web ACL.

                  • ARN — required — (String)

                    The Amazon Resource Name (ARN) of the entity.

                  • ExcludedRules — (Array<map>)

                    The rules in the referenced rule group whose actions are set to Count. When you exclude a rule, WAF evaluates it exactly as it would if the rule action setting were Count. This is a useful option for testing the rules in a rule group without modifying how they handle your web traffic.

                    • Name — required — (String)

                      The name of the rule whose action you want to override to Count.

                • IPSetReferenceStatement — (map)

                  A rule statement used to detect web requests coming from particular IP addresses or address ranges. To use this, create an IPSet that specifies the addresses you want to detect, then use the ARN of that set in this statement. To create an IP set, see CreateIPSet.

                  Each IP set rule statement references an IP set. You create and maintain the set independent of your rules. This allows you to use the single set in multiple rules. When you update the referenced set, WAF automatically updates all rules that reference it.

                  • ARN — required — (String)

                    The Amazon Resource Name (ARN) of the IPSet that this statement references.

                  • IPSetForwardedIPConfig — (map)

                    The configuration for inspecting IP addresses in an HTTP header that you specify, instead of using the IP address that's reported by the web request origin. Commonly, this is the X-Forwarded-For (XFF) header, but you can specify any header name.

                    Note: If the specified header isn't present in the request, WAF doesn't apply the rule to the web request at all.
                    • HeaderName — required — (String)

                      The name of the HTTP header to use for the IP address. For example, to use the X-Forwarded-For (XFF) header, set this to X-Forwarded-For.

                      Note: If the specified header isn't present in the request, WAF doesn't apply the rule to the web request at all.
                    • FallbackBehavior — required — (String)

                      The match status to assign to the web request if the request doesn't have a valid IP address in the specified position.

                      Note: If the specified header isn't present in the request, WAF doesn't apply the rule to the web request at all.

                      You can specify the following fallback behaviors:

                      • MATCH - Treat the web request as matching the rule statement. WAF applies the rule action to the request.

                      • NO_MATCH - Treat the web request as not matching the rule statement.

                      Possible values include:
                      • "MATCH"
                      • "NO_MATCH"
                    • Position — required — (String)

                      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:

                      • FIRST - Inspect the first IP address in the list of IP addresses in the header. This is usually the client's original IP.

                      • LAST - Inspect the last IP address in the list of IP addresses in the header.

                      • ANY - Inspect all IP addresses in the header for a match. If the header contains more than 10 IP addresses, WAF inspects the last 10.

                      Possible values include:
                      • "FIRST"
                      • "LAST"
                      • "ANY"
                • RegexPatternSetReferenceStatement — (map)

                  A rule statement used to search web request components for matches with regular expressions. To use this, create a RegexPatternSet that specifies the expressions that you want to detect, then use the ARN of that set in this statement. A web request matches the pattern set rule statement if the request component matches any of the patterns in the set. To create a regex pattern set, see CreateRegexPatternSet.

                  Each regex pattern set rule statement references a regex pattern set. You create and maintain the set independent of your rules. This allows you to use the single set in multiple rules. When you update the referenced set, WAF automatically updates all rules that reference it.

                  • ARN — required — (String)

                    The Amazon Resource Name (ARN) of the RegexPatternSet that this statement references.

                  • FieldToMatch — required — (map)

                    The part of a web request that you want WAF to inspect. For more information, see FieldToMatch.

                    • SingleHeader — (map)

                      Inspect a single header. Provide the name of the header to inspect, for example, User-Agent or Referer. This setting isn't case sensitive.

                      Example JSON: "SingleHeader": { "Name": "haystack" }

                      • Name — required — (String)

                        The name of the query header to inspect.

                    • SingleQueryArgument — (map)

                      Inspect a single query argument. Provide the name of the query argument to inspect, such as UserName or SalesRegion. The name can be up to 30 characters long and isn't case sensitive.

                      This is used only to indicate the web request component for WAF to inspect, in the FieldToMatch specification.

                      Example JSON: "SingleQueryArgument": { "Name": "myArgument" }

                      • Name — required — (String)

                        The name of the query argument to inspect.

                    • AllQueryArguments — (map)

                      Inspect all query arguments.

                    • UriPath — (map)

                      Inspect the request URI path. This is the part of a web request that identifies a resource, for example, /images/daily-ad.jpg.

                    • QueryString — (map)

                      Inspect the query string. This is the part of a URL that appears after a ? character, if any.

                    • Body — (map)

                      Inspect the request body as plain text. The request body immediately follows the request headers. This is the part of a request that contains any additional data that you want to send to your web server as the HTTP request body, such as data from a form.

                      Note that only the first 8 KB (8192 bytes) of the request body are forwarded to WAF for inspection by the underlying host service. If you don't need to inspect more than 8 KB, you can guarantee that you don't allow additional bytes in by combining a statement that inspects the body of the web request, such as ByteMatchStatement or RegexPatternSetReferenceStatement, with a SizeConstraintStatement that enforces an 8 KB size limit on the body of the request. WAF doesn't support inspecting the entire contents of web requests whose bodies exceed the 8 KB limit.

                    • Method — (map)

                      Inspect the HTTP method. The method indicates the type of operation that the request is asking the origin to perform.

                    • JsonBody — (map)

                      Inspect the request body as JSON. The request body immediately follows the request headers. This is the part of a request that contains any additional data that you want to send to your web server as the HTTP request body, such as data from a form.

                      Note that only the first 8 KB (8192 bytes) of the request body are forwarded to WAF for inspection by the underlying host service. If you don't need to inspect more than 8 KB, you can guarantee that you don't allow additional bytes in by combining a statement that inspects the body of the web request, such as ByteMatchStatement or RegexPatternSetReferenceStatement, with a SizeConstraintStatement that enforces an 8 KB size limit on the body of the request. WAF doesn't support inspecting the entire contents of web requests whose bodies exceed the 8 KB limit.

                      • MatchPattern — required — (map)

                        The patterns to look for in the JSON body. WAF inspects the results of these pattern matches against the rule inspection criteria.

                        • All — (map)

                          Match all of the elements. See also MatchScope in JsonBody.

                          You must specify either this setting or the IncludedPaths setting, but not both.

                        • IncludedPaths — (Array<String>)

                          Match only the specified include paths. See also MatchScope in JsonBody.

                          Provide the include paths using JSON Pointer syntax. For example, "IncludedPaths": ["/dogs/0/name", "/dogs/1/name"]. For information about this syntax, see the Internet Engineering Task Force (IETF) documentation JavaScript Object Notation (JSON) Pointer.

                          You must specify either this setting or the All setting, but not both.

                          Note: Don't use this option to include all paths. Instead, use the All setting.
                      • MatchScope — required — (String)

                        The parts of the JSON to match against using the MatchPattern. If you specify All, WAF matches against keys and values.

                        Possible values include:
                        • "ALL"
                        • "KEY"
                        • "VALUE"
                      • InvalidFallbackBehavior — (String)

                        What WAF should do if it fails to completely parse the JSON body. The options are the following:

                        • EVALUATE_AS_STRING - Inspect the body as plain text. WAF applies the text transformations and inspection criteria that you defined for the JSON inspection to the body text string.

                        • MATCH - Treat the web request as matching the rule statement. WAF applies the rule action to the request.

                        • NO_MATCH - Treat the web request as not matching the rule statement.

                        If you don't provide this setting, WAF parses and evaluates the content only up to the first parsing failure that it encounters.

                        WAF does its best to parse the entire JSON body, but might be forced to stop for reasons such as invalid characters, duplicate keys, truncation, and any content whose root node isn't an object or an array.

                        WAF parses the JSON in the following examples as two valid key, value pairs:

                        • Missing comma: {"key1":"value1""key2":"value2"}

                        • Missing colon: {"key1":"value1","key2""value2"}

                        • Extra colons: {"key1"::"value1","key2""value2"}

                        Possible values include:
                        • "MATCH"
                        • "NO_MATCH"
                        • "EVALUATE_AS_STRING"
                  • TextTransformations — required — (Array<map>)

                    Text transformations eliminate some of the unusual formatting that attackers use in web requests in an effort to bypass detection. If you specify one or more transformations in a rule statement, WAF performs all transformations on the content of the request component identified by FieldToMatch, starting from the lowest priority setting, before inspecting the content for a match.

                    • Priority — required — (Integer)

                      Sets the relative processing order for multiple transformations that are defined for a rule statement. WAF processes all transformations, from lowest priority to highest, before inspecting the transformed content. The priorities don't need to be consecutive, but they must all be different.

                    • Type — required — (String)

                      You can specify the following transformation types:

                      BASE64_DECODE - Decode a Base64-encoded string.

                      BASE64_DECODE_EXT - Decode a Base64-encoded string, but use a forgiving implementation that ignores characters that aren't valid.

                      CMD_LINE - Command-line transformations. These are helpful in reducing effectiveness of attackers who inject an operating system command-line command and use unusual formatting to disguise some or all of the command.

                      • Delete the following characters: \ " ' ^

                      • Delete spaces before the following characters: / (

                      • Replace the following characters with a space: , ;

                      • Replace multiple spaces with one space

                      • Convert uppercase letters (A-Z) to lowercase (a-z)

                      COMPRESS_WHITE_SPACE - Replace these characters with a space character (decimal 32):

                      • \f, formfeed, decimal 12

                      • \t, tab, decimal 9

                      • \n, newline, decimal 10

                      • \r, carriage return, decimal 13

                      • \v, vertical tab, decimal 11

                      • Non-breaking space, decimal 160

                      COMPRESS_WHITE_SPACE also replaces multiple spaces with one space.

                      CSS_DECODE - Decode characters that were encoded using CSS 2.x escape rules syndata.html#characters. This function uses up to two bytes in the decoding process, so it can help to uncover ASCII characters that were encoded using CSS encoding that wouldn’t typically be encoded. It's also useful in countering evasion, which is a combination of a backslash and non-hexadecimal characters. For example, ja\vascript for javascript.

                      ESCAPE_SEQ_DECODE - Decode the following ANSI C escape sequences: \a, \b, \f, \n, \r, \t, \v, \, \?, \', \", \xHH (hexadecimal), \0OOO (octal). Encodings that aren't valid remain in the output.

                      HEX_DECODE - Decode a string of hexadecimal characters into a binary.

                      HTML_ENTITY_DECODE - Replace HTML-encoded characters with unencoded characters. HTML_ENTITY_DECODE performs these operations:

                      • Replaces (ampersand)quot; with "

                      • Replaces (ampersand)nbsp; with a non-breaking space, decimal 160

                      • Replaces (ampersand)lt; with a "less than" symbol

                      • Replaces (ampersand)gt; with >

                      • Replaces characters that are represented in hexadecimal format, (ampersand)#xhhhh;, with the corresponding characters

                      • Replaces characters that are represented in decimal format, (ampersand)#nnnn;, with the corresponding characters

                      JS_DECODE - Decode JavaScript escape sequences. If a \ u HHHH code is in the full-width ASCII code range of FF01-FF5E, then the higher byte is used to detect and adjust the lower byte. If not, only the lower byte is used and the higher byte is zeroed, causing a possible loss of information.

                      LOWERCASE - Convert uppercase letters (A-Z) to lowercase (a-z).

                      MD5 - Calculate an MD5 hash from the data in the input. The computed hash is in a raw binary form.

                      NONE - Specify NONE if you don't want any text transformations.

                      NORMALIZE_PATH - Remove multiple slashes, directory self-references, and directory back-references that are not at the beginning of the input from an input string.

                      NORMALIZE_PATH_WIN - This is the same as NORMALIZE_PATH, but first converts backslash characters to forward slashes.

                      REMOVE_NULLS - Remove all NULL bytes from the input.

                      REPLACE_COMMENTS - Replace each occurrence of a C-style comment (/* ... */) with a single space. Multiple consecutive occurrences are not compressed. Unterminated comments are also replaced with a space (ASCII 0x20). However, a standalone termination of a comment (*/) is not acted upon.

                      REPLACE_NULLS - Replace NULL bytes in the input with space characters (ASCII 0x20).

                      SQL_HEX_DECODE - Decode SQL hex data. Example (0x414243) will be decoded to (ABC).

                      URL_DECODE - Decode a URL-encoded value.

                      URL_DECODE_UNI - Like URL_DECODE, but with support for Microsoft-specific %u encoding. If the code is in the full-width ASCII code range of FF01-FF5E, the higher byte is used to detect and adjust the lower byte. Otherwise, only the lower byte is used and the higher byte is zeroed.

                      UTF8_TO_UNICODE - Convert all UTF-8 character sequences to Unicode. This helps input normalization, and minimizing false-positives and false-negatives for non-English languages.

                      Possible values include:
                      • "NONE"
                      • "COMPRESS_WHITE_SPACE"
                      • "HTML_ENTITY_DECODE"
                      • "LOWERCASE"
                      • "CMD_LINE"
                      • "URL_DECODE"
                      • "BASE64_DECODE"
                      • "HEX_DECODE"
                      • "MD5"
                      • "REPLACE_COMMENTS"
                      • "ESCAPE_SEQ_DECODE"
                      • "SQL_HEX_DECODE"
                      • "CSS_DECODE"
                      • "JS_DECODE"
                      • "NORMALIZE_PATH"
                      • "NORMALIZE_PATH_WIN"
                      • "REMOVE_NULLS"
                      • "REPLACE_NULLS"
                      • "BASE64_DECODE_EXT"
                      • "URL_DECODE_UNI"
                      • "UTF8_TO_UNICODE"
                • RateBasedStatement — (map)

                  A rate-based rule tracks the rate of requests for each originating IP address, and triggers the rule action when the rate exceeds a limit that you specify on the number of requests in any 5-minute time span. You can use this to put a temporary block on requests from an IP address that is sending excessive requests.

                  WAF tracks and manages web requests separately for each instance of a rate-based rule that you use. For example, if you provide the same rate-based rule settings in two web ACLs, each of the two rule statements represents a separate instance of the rate-based rule and gets its own tracking and management by WAF. If you define a rate-based rule inside a rule group, and then use that rule group in multiple places, each use creates a separate instance of the rate-based rule that gets its own tracking and management by WAF.

                  When the rule action triggers, WAF blocks additional requests from the IP address until the request rate falls below the limit.

                  You can optionally nest another statement inside the rate-based statement, to narrow the scope of the rule so that it only counts requests that match the nested statement. For example, based on recent requests that you have seen from an attacker, you might create a rate-based rule with a nested AND rule statement that contains the following nested statements:

                  • An IP match statement with an IP set that specified the address 192.0.2.44.

                  • A string match statement that searches in the User-Agent header for the string BadBot.

                  In this rate-based rule, you also define a rate limit. For this example, the rate limit is 1,000. Requests that meet both of the conditions in the statements are counted. If the count exceeds 1,000 requests per five minutes, the rule action triggers. Requests that do not meet both conditions are not counted towards the rate limit and are not affected by this rule.

                  You cannot nest a RateBasedStatement inside another statement, for example inside a NotStatement or OrStatement. You can define a RateBasedStatement inside a web ACL and inside a rule group.

                  • Limit — required — (Integer)

                    The limit on requests per 5-minute period for a single originating IP address. If the statement includes a ScopeDownStatement, this limit is applied only to the requests that match the statement.

                  • AggregateKeyType — required — (String)

                    Setting that indicates how to aggregate the request counts. The options are the following:

                    • IP - Aggregate the request counts on the IP address from the web request origin.

                    • FORWARDED_IP - Aggregate the request counts on the first IP address in an HTTP header. If you use this, configure the ForwardedIPConfig, to specify the header to use.

                    Possible values include:
                    • "IP"
                    • "FORWARDED_IP"
                  • ForwardedIPConfig — (map)

                    The configuration for inspecting IP addresses in an HTTP header that you specify, instead of using the IP address that's reported by the web request origin. Commonly, this is the X-Forwarded-For (XFF) header, but you can specify any header name.

                    Note: If the specified header isn't present in the request, WAF doesn't apply the rule to the web request at all.

                    This is required if AggregateKeyType is set to FORWARDED_IP.

                    • HeaderName — required — (String)

                      The name of the HTTP header to use for the IP address. For example, to use the X-Forwarded-For (XFF) header, set this to X-Forwarded-For.

                      Note: If the specified header isn't present in the request, WAF doesn't apply the rule to the web request at all.
                    • FallbackBehavior — required — (String)

                      The match status to assign to the web request if the request doesn't have a valid IP address in the specified position.

                      Note: If the specified header isn't present in the request, WAF doesn't apply the rule to the web request at all.

                      You can specify the following fallback behaviors:

                      • MATCH - Treat the web request as matching the rule statement. WAF applies the rule action to the request.

                      • NO_MATCH - Treat the web request as not matching the rule statement.

                      Possible values include:
                      • "MATCH"
                      • "NO_MATCH"
                • AndStatement — (map)

                  A logical rule statement used to combine other rule statements with AND logic. You provide more than one Statement within the AndStatement.

                  • Statements — required — (Array<map>)

                    The statements to combine with AND logic. You can use any statements that can be nested.

                • OrStatement — (map)

                  A logical rule statement used to combine other rule statements with OR logic. You provide more than one Statement within the OrStatement.

                  • Statements — required — (Array<map>)

                    The statements to combine with OR logic. You can use any statements that can be nested.

                • NotStatement — (map)

                  A logical rule statement used to negate the results of another rule statement. You provide one Statement within the NotStatement.

                • LabelMatchStatement — (map)

                  A rule statement that defines a string match search against labels that have been added to the web request by rules that have already run in the web ACL.

                  The label match statement provides the label or namespace string to search for. The label string can represent a part or all of the fully qualified label name that had been added to the web request. Fully qualified labels have a prefix, optional namespaces, and label name. The prefix identifies the rule group or web ACL context of the rule that added the label. If you do not provide the fully qualified name in your label match string, WAF performs the search for labels that were added in the same context as the label match statement.

                  • Scope — required — (String)

                    Specify whether you want to match using the label name or just the namespace.

                    Possible values include:
                    • "LABEL"
                    • "NAMESPACE"
                  • Key — required — (String)

                    The string to match against. The setting you provide for this depends on the match statement's Scope setting:

                    • If the Scope indicates LABEL, then this specification must include the name and can include any number of preceding namespace specifications and prefix up to providing the fully qualified label name.

                    • If the Scope indicates NAMESPACE, then this specification can include any number of contiguous namespace strings, and can include the entire label namespace prefix from the rule group or web ACL where the label originates.

                    Labels are case sensitive and components of a label must be separated by colon, for example NS1:NS2:name.

                • RegexMatchStatement — (map)

                  A rule statement used to search web request components for a match against a single regular expression.

                  • RegexString — required — (String)

                    The string representing the regular expression.

                  • FieldToMatch — required — (map)

                    The part of a web request that you want WAF to inspect. For more information, see FieldToMatch.

                    • SingleHeader — (map)

                      Inspect a single header. Provide the name of the header to inspect, for example, User-Agent or Referer. This setting isn't case sensitive.

                      Example JSON: "SingleHeader": { "Name": "haystack" }

                      • Name — required — (String)

                        The name of the query header to inspect.

                    • SingleQueryArgument — (map)

                      Inspect a single query argument. Provide the name of the query argument to inspect, such as UserName or SalesRegion. The name can be up to 30 characters long and isn't case sensitive.

                      This is used only to indicate the web request component for WAF to inspect, in the FieldToMatch specification.

                      Example JSON: "SingleQueryArgument": { "Name": "myArgument" }

                      • Name — required — (String)

                        The name of the query argument to inspect.

                    • AllQueryArguments — (map)

                      Inspect all query arguments.

                    • UriPath — (map)

                      Inspect the request URI path. This is the part of a web request that identifies a resource, for example, /images/daily-ad.jpg.

                    • QueryString — (map)

                      Inspect the query string. This is the part of a URL that appears after a ? character, if any.

                    • Body — (map)

                      Inspect the request body as plain text. The request body immediately follows the request headers. This is the part of a request that contains any additional data that you want to send to your web server as the HTTP request body, such as data from a form.

                      Note that only the first 8 KB (8192 bytes) of the request body are forwarded to WAF for inspection by the underlying host service. If you don't need to inspect more than 8 KB, you can guarantee that you don't allow additional bytes in by combining a statement that inspects the body of the web request, such as ByteMatchStatement or RegexPatternSetReferenceStatement, with a SizeConstraintStatement that enforces an 8 KB size limit on the body of the request. WAF doesn't support inspecting the entire contents of web requests whose bodies exceed the 8 KB limit.

                    • Method — (map)

                      Inspect the HTTP method. The method indicates the type of operation that the request is asking the origin to perform.

                    • JsonBody — (map)

                      Inspect the request body as JSON. The request body immediately follows the request headers. This is the part of a request that contains any additional data that you want to send to your web server as the HTTP request body, such as data from a form.

                      Note that only the first 8 KB (8192 bytes) of the request body are forwarded to WAF for inspection by the underlying host service. If you don't need to inspect more than 8 KB, you can guarantee that you don't allow additional bytes in by combining a statement that inspects the body of the web request, such as ByteMatchStatement or RegexPatternSetReferenceStatement, with a SizeConstraintStatement that enforces an 8 KB size limit on the body of the request. WAF doesn't support inspecting the entire contents of web requests whose bodies exceed the 8 KB limit.

                      • MatchPattern — required — (map)

                        The patterns to look for in the JSON body. WAF inspects the results of these pattern matches against the rule inspection criteria.

                        • All — (map)

                          Match all of the elements. See also MatchScope in JsonBody.

                          You must specify either this setting or the IncludedPaths setting, but not both.

                        • IncludedPaths — (Array<String>)

                          Match only the specified include paths. See also MatchScope in JsonBody.

                          Provide the include paths using JSON Pointer syntax. For example, "IncludedPaths": ["/dogs/0/name", "/dogs/1/name"]. For information about this syntax, see the Internet Engineering Task Force (IETF) documentation JavaScript Object Notation (JSON) Pointer.

                          You must specify either this setting or the All setting, but not both.

                          Note: Don't use this option to include all paths. Instead, use the All setting.
                      • MatchScope — required — (String)

                        The parts of the JSON to match against using the MatchPattern. If you specify All, WAF matches against keys and values.

                        Possible values include:
                        • "ALL"
                        • "KEY"
                        • "VALUE"
                      • InvalidFallbackBehavior — (String)

                        What WAF should do if it fails to completely parse the JSON body. The options are the following:

                        • EVALUATE_AS_STRING - Inspect the body as plain text. WAF applies the text transformations and inspection criteria that you defined for the JSON inspection to the body text string.

                        • MATCH - Treat the web request as matching the rule statement. WAF applies the rule action to the request.

                        • NO_MATCH - Treat the web request as not matching the rule statement.

                        If you don't provide this setting, WAF parses and evaluates the content only up to the first parsing failure that it encounters.

                        WAF does its best to parse the entire JSON body, but might be forced to stop for reasons such as invalid characters, duplicate keys, truncation, and any content whose root node isn't an object or an array.

                        WAF parses the JSON in the following examples as two valid key, value pairs:

                        • Missing comma: {"key1":"value1""key2":"value2"}

                        • Missing colon: {"key1":"value1","key2""value2"}

                        • Extra colons: {"key1"::"value1","key2""value2"}

                        Possible values include:
                        • "MATCH"
                        • "NO_MATCH"
                        • "EVALUATE_AS_STRING"
                  • TextTransformations — required — (Array<map>)

                    Text transformations eliminate some of the unusual formatting that attackers use in web requests in an effort to bypass detection. If you specify one or more transformations in a rule statement, WAF performs all transformations on the content of the request component identified by FieldToMatch, starting from the lowest priority setting, before inspecting the content for a match.

                    • Priority — required — (Integer)

                      Sets the relative processing order for multiple transformations that are defined for a rule statement. WAF processes all transformations, from lowest priority to highest, before inspecting the transformed content. The priorities don't need to be consecutive, but they must all be different.

                    • Type — required — (String)

                      You can specify the following transformation types:

                      BASE64_DECODE - Decode a Base64-encoded string.

                      BASE64_DECODE_EXT - Decode a Base64-encoded string, but use a forgiving implementation that ignores characters that aren't valid.

                      CMD_LINE - Command-line transformations. These are helpful in reducing effectiveness of attackers who inject an operating system command-line command and use unusual formatting to disguise some or all of the command.

                      • Delete the following characters: \ " ' ^

                      • Delete spaces before the following characters: / (

                      • Replace the following characters with a space: , ;

                      • Replace multiple spaces with one space

                      • Convert uppercase letters (A-Z) to lowercase (a-z)

                      COMPRESS_WHITE_SPACE - Replace these characters with a space character (decimal 32):

                      • \f, formfeed, decimal 12

                      • \t, tab, decimal 9

                      • \n, newline, decimal 10

                      • \r, carriage return, decimal 13

                      • \v, vertical tab, decimal 11

                      • Non-breaking space, decimal 160

                      COMPRESS_WHITE_SPACE also replaces multiple spaces with one space.

                      CSS_DECODE - Decode characters that were encoded using CSS 2.x escape rules syndata.html#characters. This function uses up to two bytes in the decoding process, so it can help to uncover ASCII characters that were encoded using CSS encoding that wouldn’t typically be encoded. It's also useful in countering evasion, which is a combination of a backslash and non-hexadecimal characters. For example, ja\vascript for javascript.

                      ESCAPE_SEQ_DECODE - Decode the following ANSI C escape sequences: \a, \b, \f, \n, \r, \t, \v, \, \?, \', \", \xHH (hexadecimal), \0OOO (octal). Encodings that aren't valid remain in the output.

                      HEX_DECODE - Decode a string of hexadecimal characters into a binary.

                      HTML_ENTITY_DECODE - Replace HTML-encoded characters with unencoded characters. HTML_ENTITY_DECODE performs these operations:

                      • Replaces (ampersand)quot; with "

                      • Replaces (ampersand)nbsp; with a non-breaking space, decimal 160

                      • Replaces (ampersand)lt; with a "less than" symbol

                      • Replaces (ampersand)gt; with >

                      • Replaces characters that are represented in hexadecimal format, (ampersand)#xhhhh;, with the corresponding characters

                      • Replaces characters that are represented in decimal format, (ampersand)#nnnn;, with the corresponding characters

                      JS_DECODE - Decode JavaScript escape sequences. If a \ u HHHH code is in the full-width ASCII code range of FF01-FF5E, then the higher byte is used to detect and adjust the lower byte. If not, only the lower byte is used and the higher byte is zeroed, causing a possible loss of information.

                      LOWERCASE - Convert uppercase letters (A-Z) to lowercase (a-z).

                      MD5 - Calculate an MD5 hash from the data in the input. The computed hash is in a raw binary form.

                      NONE - Specify NONE if you don't want any text transformations.

                      NORMALIZE_PATH - Remove multiple slashes, directory self-references, and directory back-references that are not at the beginning of the input from an input string.

                      NORMALIZE_PATH_WIN - This is the same as NORMALIZE_PATH, but first converts backslash characters to forward slashes.

                      REMOVE_NULLS - Remove all NULL bytes from the input.

                      REPLACE_COMMENTS - Replace each occurrence of a C-style comment (/* ... */) with a single space. Multiple consecutive occurrences are not compressed. Unterminated comments are also replaced with a space (ASCII 0x20). However, a standalone termination of a comment (*/) is not acted upon.

                      REPLACE_NULLS - Replace NULL bytes in the input with space characters (ASCII 0x20).

                      SQL_HEX_DECODE - Decode SQL hex data. Example (0x414243) will be decoded to (ABC).

                      URL_DECODE - Decode a URL-encoded value.

                      URL_DECODE_UNI - Like URL_DECODE, but with support for Microsoft-specific %u encoding. If the code is in the full-width ASCII code range of FF01-FF5E, the higher byte is used to detect and adjust the lower byte. Otherwise, only the lower byte is used and the higher byte is zeroed.

                      UTF8_TO_UNICODE - Convert all UTF-8 character sequences to Unicode. This helps input normalization, and minimizing false-positives and false-negatives for non-English languages.

                      Possible values include:
                      • "NONE"
                      • "COMPRESS_WHITE_SPACE"
                      • "HTML_ENTITY_DECODE"
                      • "LOWERCASE"
                      • "CMD_LINE"
                      • "URL_DECODE"
                      • "BASE64_DECODE"
                      • "HEX_DECODE"
                      • "MD5"
                      • "REPLACE_COMMENTS"
                      • "ESCAPE_SEQ_DECODE"
                      • "SQL_HEX_DECODE"
                      • "CSS_DECODE"
                      • "JS_DECODE"
                      • "NORMALIZE_PATH"
                      • "NORMALIZE_PATH_WIN"
                      • "REMOVE_NULLS"
                      • "REPLACE_NULLS"
                      • "BASE64_DECODE_EXT"
                      • "URL_DECODE_UNI"
                      • "UTF8_TO_UNICODE"
            • RuleGroupReferenceStatement — (map)

              A rule statement used to run the rules that are defined in a RuleGroup. To use this, create a rule group with your rules, then provide the ARN of the rule group in this statement.

              You cannot nest a RuleGroupReferenceStatement, for example for use inside a NotStatement or OrStatement. You can only use a rule group reference statement at the top level inside a web ACL.

              • ARN — required — (String)

                The Amazon Resource Name (ARN) of the entity.

              • ExcludedRules — (Array<map>)

                The rules in the referenced rule group whose actions are set to Count. When you exclude a rule, WAF evaluates it exactly as it would if the rule action setting were Count. This is a useful option for testing the rules in a rule group without modifying how they handle your web traffic.

                • Name — required — (String)

                  The name of the rule whose action you want to override to Count.

          • OverrideAction — required — (map)

            The action to use in the place of the action that results from the rule group evaluation. Set the override action to none to leave the result of the rule group alone. Set it to count to override the result to count only.

            You can only use this for rule statements that reference a rule group, like RuleGroupReferenceStatement and ManagedRuleGroupStatement.

            Note: This option is usually set to none. It does not affect how the rules in the rule group are evaluated. If you want the rules in the rule group to only count matches, do not use this and instead exclude those rules in your rule group reference statement settings.
            • Count — (map)

              Override the rule group evaluation result to count only.

              Note: This option is usually set to none. It does not affect how the rules in the rule group are evaluated. If you want the rules in the rule group to only count matches, do not use this and instead exclude those rules in your rule group reference statement settings.
              • CustomRequestHandling — (map)

                Defines custom handling for the web request.

                For information about customizing web requests and responses, see Customizing web requests and responses in WAF in the WAF Developer Guide.

                • InsertHeaders — required — (Array<map>)

                  The HTTP headers to insert into the request. Duplicate header names are not allowed.

                  For information about the limits on count and size for custom request and response settings, see WAF quotas in the WAF Developer Guide.

                  • Name — required — (String)

                    The name of the custom header.

                    For custom request header insertion, when WAF inserts the header into the request, it prefixes this name x-amzn-waf-, to avoid confusion with the headers that are already in the request. For example, for the header name sample, WAF inserts the header x-amzn-waf-sample.

                  • Value — required — (String)

                    The value of the custom header.

            • None — (map)

              Don't override the rule group evaluation result. This is the most common setting.

          • VisibilityConfig — required — (map)

            Defines and enables Amazon CloudWatch metrics and web request sample collection.

            • SampledRequestsEnabled — required — (Boolean)

              A boolean indicating whether WAF should store a sampling of the web requests that match the rules. You can view the sampled requests through the WAF console.

            • CloudWatchMetricsEnabled — required — (Boolean)

              A boolean indicating whether the associated resource sends metrics to Amazon CloudWatch. For the list of available metrics, see WAF Metrics.

            • MetricName — required — (String)

              A name of the Amazon CloudWatch metric. The name can contain only the characters: A-Z, a-z, 0-9, - (hyphen), and _ (underscore). The name can be from one to 128 characters long. It can't contain whitespace or metric names reserved for WAF, for example "All" and "Default_Action."

        • PostProcessFirewallManagerRuleGroups — (Array<map>)

          The last set of rules for WAF to process in the web ACL. This is defined in an Firewall Manager WAF policy and contains only rule group references. You can't alter these. Any rules and rule groups that you define for the web ACL are prioritized before these.

          In the Firewall Manager WAF policy, the Firewall Manager administrator can define a set of rule groups to run first in the web ACL and a set of rule groups to run last. Within each set, the administrator prioritizes the rule groups, to determine their relative processing order.

          • Name — required — (String)

            The name of the rule group. You cannot change the name of a rule group after you create it.

          • Priority — required — (Integer)

            If you define more than one rule group in the first or last Firewall Manager rule groups, WAF evaluates each request against the rule groups in order, starting from the lowest priority setting. The priorities don't need to be consecutive, but they must all be different.

          • FirewallManagerStatement — required — (map)

            The processing guidance for an Firewall Manager rule. This is like a regular rule Statement, but it can only contain a rule group reference.

            • ManagedRuleGroupStatement — (map)

              A rule statement used to run the rules that are defined in a managed rule group. To use this, provide the vendor name and the name of the rule group in this statement. You can retrieve the required names by calling ListAvailableManagedRuleGroups.

              You cannot nest a ManagedRuleGroupStatement, for example for use inside a NotStatement or OrStatement. It can only be referenced as a top-level statement within a rule.

              • VendorName — required — (String)

                The name of the managed rule group vendor. You use this, along with the rule group name, to identify the rule group.

              • Name — required — (String)

                The name of the managed rule group. You use this, along with the vendor name, to identify the rule group.

              • Version — (String)

                The version of the managed rule group to use. If you specify this, the version setting is fixed until you change it. If you don't specify this, WAF uses the vendor's default version, and then keeps the version at the vendor's default when the vendor updates the managed rule group settings.

              • ExcludedRules — (Array<map>)

                The rules in the referenced rule group whose actions are set to Count. When you exclude a rule, WAF evaluates it exactly as it would if the rule action setting were Count. This is a useful option for testing the rules in a rule group without modifying how they handle your web traffic.

                • Name — required — (String)

                  The name of the rule whose action you want to override to Count.

              • ScopeDownStatement — (map)

                An optional nested statement that narrows the scope of the web requests that are evaluated by the managed rule group. Requests are only evaluated by the rule group if they match the scope-down statement. You can use any nestable Statement in the scope-down statement, and you can nest statements at any level, the same as you can for a rule statement.

                • ByteMatchStatement — (map)

                  A rule statement that defines a string match search for WAF to apply to web requests. The byte match statement provides the bytes to search for, the location in requests that you want WAF to search, and other settings. The bytes to search for are typically a string that corresponds with ASCII characters. In the WAF console and the developer guide, this is refered to as a string match statement.

                  • SearchString — required — (Buffer, Typed Array, Blob, String)

                    A string value that you want WAF to search for. WAF searches only in the part of web requests that you designate for inspection in FieldToMatch. The maximum length of the value is 50 bytes.

                    Valid values depend on the component that you specify for inspection in FieldToMatch:

                    • Method: The HTTP method that you want WAF to search for. This indicates the type of operation specified in the request.

                    • UriPath: The value that you want WAF to search for in the URI path, for example, /images/daily-ad.jpg.

                    If SearchString includes alphabetic characters A-Z and a-z, note that the value is case sensitive.

                    If you're using the WAF API

                    Specify a base64-encoded version of the value. The maximum length of the value before you base64-encode it is 50 bytes.

                    For example, suppose the value of Type is HEADER and the value of Data is User-Agent. If you want to search the User-Agent header for the value BadBot, you base64-encode BadBot using MIME base64-encoding and include the resulting value, QmFkQm90, in the value of SearchString.

                    If you're using the CLI or one of the Amazon Web Services SDKs

                    The value that you want WAF to search for. The SDK automatically base64 encodes the value.

                  • FieldToMatch — required — (map)

                    The part of a web request that you want WAF to inspect. For more information, see FieldToMatch.

                    • SingleHeader — (map)

                      Inspect a single header. Provide the name of the header to inspect, for example, User-Agent or Referer. This setting isn't case sensitive.

                      Example JSON: "SingleHeader": { "Name": "haystack" }

                      • Name — required — (String)

                        The name of the query header to inspect.

                    • SingleQueryArgument — (map)

                      Inspect a single query argument. Provide the name of the query argument to inspect, such as UserName or SalesRegion. The name can be up to 30 characters long and isn't case sensitive.

                      This is used only to indicate the web request component for WAF to inspect, in the FieldToMatch specification.

                      Example JSON: "SingleQueryArgument": { "Name": "myArgument" }

                      • Name — required — (String)

                        The name of the query argument to inspect.

                    • AllQueryArguments — (map)

                      Inspect all query arguments.

                    • UriPath — (map)

                      Inspect the request URI path. This is the part of a web request that identifies a resource, for example, /images/daily-ad.jpg.

                    • QueryString — (map)

                      Inspect the query string. This is the part of a URL that appears after a ? character, if any.

                    • Body — (map)

                      Inspect the request body as plain text. The request body immediately follows the request headers. This is the part of a request that contains any additional data that you want to send to your web server as the HTTP request body, such as data from a form.

                      Note that only the first 8 KB (8192 bytes) of the request body are forwarded to WAF for inspection by the underlying host service. If you don't need to inspect more than 8 KB, you can guarantee that you don't allow additional bytes in by combining a statement that inspects the body of the web request, such as ByteMatchStatement or RegexPatternSetReferenceStatement, with a SizeConstraintStatement that enforces an 8 KB size limit on the body of the request. WAF doesn't support inspecting the entire contents of web requests whose bodies exceed the 8 KB limit.

                    • Method — (map)

                      Inspect the HTTP method. The method indicates the type of operation that the request is asking the origin to perform.

                    • JsonBody — (map)

                      Inspect the request body as JSON. The request body immediately follows the request headers. This is the part of a request that contains any additional data that you want to send to your web server as the HTTP request body, such as data from a form.

                      Note that only the first 8 KB (8192 bytes) of the request body are forwarded to WAF for inspection by the underlying host service. If you don't need to inspect more than 8 KB, you can guarantee that you don't allow additional bytes in by combining a statement that inspects the body of the web request, such as ByteMatchStatement or RegexPatternSetReferenceStatement, with a SizeConstraintStatement that enforces an 8 KB size limit on the body of the request. WAF doesn't support inspecting the entire contents of web requests whose bodies exceed the 8 KB limit.

                      • MatchPattern — required — (map)

                        The patterns to look for in the JSON body. WAF inspects the results of these pattern matches against the rule inspection criteria.

                        • All — (map)

                          Match all of the elements. See also MatchScope in JsonBody.

                          You must specify either this setting or the IncludedPaths setting, but not both.

                        • IncludedPaths — (Array<String>)

                          Match only the specified include paths. See also MatchScope in JsonBody.

                          Provide the include paths using JSON Pointer syntax. For example, "IncludedPaths": ["/dogs/0/name", "/dogs/1/name"]. For information about this syntax, see the Internet Engineering Task Force (IETF) documentation JavaScript Object Notation (JSON) Pointer.

                          You must specify either this setting or the All setting, but not both.

                          Note: Don't use this option to include all paths. Instead, use the All setting.
                      • MatchScope — required — (String)

                        The parts of the JSON to match against using the MatchPattern. If you specify All, WAF matches against keys and values.

                        Possible values include:
                        • "ALL"
                        • "KEY"
                        • "VALUE"
                      • InvalidFallbackBehavior — (String)

                        What WAF should do if it fails to completely parse the JSON body. The options are the following:

                        • EVALUATE_AS_STRING - Inspect the body as plain text. WAF applies the text transformations and inspection criteria that you defined for the JSON inspection to the body text string.

                        • MATCH - Treat the web request as matching the rule statement. WAF applies the rule action to the request.

                        • NO_MATCH - Treat the web request as not matching the rule statement.

                        If you don't provide this setting, WAF parses and evaluates the content only up to the first parsing failure that it encounters.

                        WAF does its best to parse the entire JSON body, but might be forced to stop for reasons such as invalid characters, duplicate keys, truncation, and any content whose root node isn't an object or an array.

                        WAF parses the JSON in the following examples as two valid key, value pairs:

                        • Missing comma: {"key1":"value1""key2":"value2"}

                        • Missing colon: {"key1":"value1","key2""value2"}

                        • Extra colons: {"key1"::"value1","key2""value2"}

                        Possible values include:
                        • "MATCH"
                        • "NO_MATCH"
                        • "EVALUATE_AS_STRING"
                  • TextTransformations — required — (Array<map>)

                    Text transformations eliminate some of the unusual formatting that attackers use in web requests in an effort to bypass detection. If you specify one or more transformations in a rule statement, WAF performs all transformations on the content of the request component identified by FieldToMatch, starting from the lowest priority setting, before inspecting the content for a match.

                    • Priority — required — (Integer)

                      Sets the relative processing order for multiple transformations that are defined for a rule statement. WAF processes all transformations, from lowest priority to highest, before inspecting the transformed content. The priorities don't need to be consecutive, but they must all be different.

                    • Type — required — (String)

                      You can specify the following transformation types:

                      BASE64_DECODE - Decode a Base64-encoded string.

                      BASE64_DECODE_EXT - Decode a Base64-encoded string, but use a forgiving implementation that ignores characters that aren't valid.

                      CMD_LINE - Command-line transformations. These are helpful in reducing effectiveness of attackers who inject an operating system command-line command and use unusual formatting to disguise some or all of the command.

                      • Delete the following characters: \ " ' ^

                      • Delete spaces before the following characters: / (

                      • Replace the following characters with a space: , ;

                      • Replace multiple spaces with one space

                      • Convert uppercase letters (A-Z) to lowercase (a-z)

                      COMPRESS_WHITE_SPACE - Replace these characters with a space character (decimal 32):

                      • \f, formfeed, decimal 12

                      • \t, tab, decimal 9

                      • \n, newline, decimal 10

                      • \r, carriage return, decimal 13

                      • \v, vertical tab, decimal 11

                      • Non-breaking space, decimal 160

                      COMPRESS_WHITE_SPACE also replaces multiple spaces with one space.

                      CSS_DECODE - Decode characters that were encoded using CSS 2.x escape rules syndata.html#characters. This function uses up to two bytes in the decoding process, so it can help to uncover ASCII characters that were encoded using CSS encoding that wouldn’t typically be encoded. It's also useful in countering evasion, which is a combination of a backslash and non-hexadecimal characters. For example, ja\vascript for javascript.

                      ESCAPE_SEQ_DECODE - Decode the following ANSI C escape sequences: \a, \b, \f, \n, \r, \t, \v, \, \?, \', \", \xHH (hexadecimal), \0OOO (octal). Encodings that aren't valid remain in the output.

                      HEX_DECODE - Decode a string of hexadecimal characters into a binary.

                      HTML_ENTITY_DECODE - Replace HTML-encoded characters with unencoded characters. HTML_ENTITY_DECODE performs these operations:

                      • Replaces (ampersand)quot; with "

                      • Replaces (ampersand)nbsp; with a non-breaking space, decimal 160

                      • Replaces (ampersand)lt; with a "less than" symbol

                      • Replaces (ampersand)gt; with >

                      • Replaces characters that are represented in hexadecimal format, (ampersand)#xhhhh;, with the corresponding characters

                      • Replaces characters that are represented in decimal format, (ampersand)#nnnn;, with the corresponding characters

                      JS_DECODE - Decode JavaScript escape sequences. If a \ u HHHH code is in the full-width ASCII code range of FF01-FF5E, then the higher byte is used to detect and adjust the lower byte. If not, only the lower byte is used and the higher byte is zeroed, causing a possible loss of information.

                      LOWERCASE - Convert uppercase letters (A-Z) to lowercase (a-z).

                      MD5 - Calculate an MD5 hash from the data in the input. The computed hash is in a raw binary form.

                      NONE - Specify NONE if you don't want any text transformations.

                      NORMALIZE_PATH - Remove multiple slashes, directory self-references, and directory back-references that are not at the beginning of the input from an input string.

                      NORMALIZE_PATH_WIN - This is the same as NORMALIZE_PATH, but first converts backslash characters to forward slashes.

                      REMOVE_NULLS - Remove all NULL bytes from the input.

                      REPLACE_COMMENTS - Replace each occurrence of a C-style comment (/* ... */) with a single space. Multiple consecutive occurrences are not compressed. Unterminated comments are also replaced with a space (ASCII 0x20). However, a standalone termination of a comment (*/) is not acted upon.

                      REPLACE_NULLS - Replace NULL bytes in the input with space characters (ASCII 0x20).

                      SQL_HEX_DECODE - Decode SQL hex data. Example (0x414243) will be decoded to (ABC).

                      URL_DECODE - Decode a URL-encoded value.

                      URL_DECODE_UNI - Like URL_DECODE, but with support for Microsoft-specific %u encoding. If the code is in the full-width ASCII code range of FF01-FF5E, the higher byte is used to detect and adjust the lower byte. Otherwise, only the lower byte is used and the higher byte is zeroed.

                      UTF8_TO_UNICODE - Convert all UTF-8 character sequences to Unicode. This helps input normalization, and minimizing false-positives and false-negatives for non-English languages.

                      Possible values include:
                      • "NONE"
                      • "COMPRESS_WHITE_SPACE"
                      • "HTML_ENTITY_DECODE"
                      • "LOWERCASE"
                      • "CMD_LINE"
                      • "URL_DECODE"
                      • "BASE64_DECODE"
                      • "HEX_DECODE"
                      • "MD5"
                      • "REPLACE_COMMENTS"
                      • "ESCAPE_SEQ_DECODE"
                      • "SQL_HEX_DECODE"
                      • "CSS_DECODE"
                      • "JS_DECODE"
                      • "NORMALIZE_PATH"
                      • "NORMALIZE_PATH_WIN"
                      • "REMOVE_NULLS"
                      • "REPLACE_NULLS"
                      • "BASE64_DECODE_EXT"
                      • "URL_DECODE_UNI"
                      • "UTF8_TO_UNICODE"
                  • PositionalConstraint — required — (String)

                    The area within the portion of a web request that you want WAF to search for SearchString. Valid values include the following:

                    CONTAINS

                    The specified part of the web request must include the value of SearchString, but the location doesn't matter.

                    CONTAINS_WORD

                    The specified part of the web request must include the value of SearchString, and SearchString must contain only alphanumeric characters or underscore (A-Z, a-z, 0-9, or ). In addition, SearchString must be a word, which means that both of the following are true:

                    • SearchString is at the beginning of the specified part of the web request or is preceded by a character other than an alphanumeric character or underscore (). Examples include the value of a header and ;BadBot.

                    • SearchString is at the end of the specified part of the web request or is followed by a character other than an alphanumeric character or underscore (_), for example, BadBot; and -BadBot;.

                    EXACTLY

                    The value of the specified part of the web request must exactly match the value of SearchString.

                    STARTS_WITH

                    The value of SearchString must appear at the beginning of the specified part of the web request.

                    ENDS_WITH

                    The value of SearchString must appear at the end of the specified part of the web request.

                    Possible values include:
                    • "EXACTLY"
                    • "STARTS_WITH"
                    • "ENDS_WITH"
                    • "CONTAINS"
                    • "CONTAINS_WORD"
                • SqliMatchStatement — (map)

                  Attackers sometimes insert malicious SQL code into web requests in an effort to extract data from your database. To allow or block web requests that appear to contain malicious SQL code, create one or more SQL injection match conditions. An SQL injection match condition identifies the part of web requests, such as the URI or the query string, that you want WAF to inspect. Later in the process, when you create a web ACL, you specify whether to allow or block requests that appear to contain malicious SQL code.

                  • FieldToMatch — required — (map)

                    The part of a web request that you want WAF to inspect. For more information, see FieldToMatch.

                    • SingleHeader — (map)

                      Inspect a single header. Provide the name of the header to inspect, for example, User-Agent or Referer. This setting isn't case sensitive.

                      Example JSON: "SingleHeader": { "Name": "haystack" }

                      • Name — required — (String)

                        The name of the query header to inspect.

                    • SingleQueryArgument — (map)

                      Inspect a single query argument. Provide the name of the query argument to inspect, such as UserName or SalesRegion. The name can be up to 30 characters long and isn't case sensitive.

                      This is used only to indicate the web request component for WAF to inspect, in the FieldToMatch specification.

                      Example JSON: "SingleQueryArgument": { "Name": "myArgument" }

                      • Name — required — (String)

                        The name of the query argument to inspect.

                    • AllQueryArguments — (map)

                      Inspect all query arguments.

                    • UriPath — (map)

                      Inspect the request URI path. This is the part of a web request that identifies a resource, for example, /images/daily-ad.jpg.

                    • QueryString — (map)

                      Inspect the query string. This is the part of a URL that appears after a ? character, if any.

                    • Body — (map)

                      Inspect the request body as plain text. The request body immediately follows the request headers. This is the part of a request that contains any additional data that you want to send to your web server as the HTTP request body, such as data from a form.

                      Note that only the first 8 KB (8192 bytes) of the request body are forwarded to WAF for inspection by the underlying host service. If you don't need to inspect more than 8 KB, you can guarantee that you don't allow additional bytes in by combining a statement that inspects the body of the web request, such as ByteMatchStatement or RegexPatternSetReferenceStatement, with a SizeConstraintStatement that enforces an 8 KB size limit on the body of the request. WAF doesn't support inspecting the entire contents of web requests whose bodies exceed the 8 KB limit.

                    • Method — (map)

                      Inspect the HTTP method. The method indicates the type of operation that the request is asking the origin to perform.

                    • JsonBody — (map)

                      Inspect the request body as JSON. The request body immediately follows the request headers. This is the part of a request that contains any additional data that you want to send to your web server as the HTTP request body, such as data from a form.

                      Note that only the first 8 KB (8192 bytes) of the request body are forwarded to WAF for inspection by the underlying host service. If you don't need to inspect more than 8 KB, you can guarantee that you don't allow additional bytes in by combining a statement that inspects the body of the web request, such as ByteMatchStatement or RegexPatternSetReferenceStatement, with a SizeConstraintStatement that enforces an 8 KB size limit on the body of the request. WAF doesn't support inspecting the entire contents of web requests whose bodies exceed the 8 KB limit.

                      • MatchPattern — required — (map)

                        The patterns to look for in the JSON body. WAF inspects the results of these pattern matches against the rule inspection criteria.

                        • All — (map)

                          Match all of the elements. See also MatchScope in JsonBody.

                          You must specify either this setting or the IncludedPaths setting, but not both.

                        • IncludedPaths — (Array<String>)

                          Match only the specified include paths. See also MatchScope in JsonBody.

                          Provide the include paths using JSON Pointer syntax. For example, "IncludedPaths": ["/dogs/0/name", "/dogs/1/name"]. For information about this syntax, see the Internet Engineering Task Force (IETF) documentation JavaScript Object Notation (JSON) Pointer.

                          You must specify either this setting or the All setting, but not both.

                          Note: Don't use this option to include all paths. Instead, use the All setting.
                      • MatchScope — required — (String)

                        The parts of the JSON to match against using the MatchPattern. If you specify All, WAF matches against keys and values.

                        Possible values include:
                        • "ALL"
                        • "KEY"
                        • "VALUE"
                      • InvalidFallbackBehavior — (String)

                        What WAF should do if it fails to completely parse the JSON body. The options are the following:

                        • EVALUATE_AS_STRING - Inspect the body as plain text. WAF applies the text transformations and inspection criteria that you defined for the JSON inspection to the body text string.

                        • MATCH - Treat the web request as matching the rule statement. WAF applies the rule action to the request.

                        • NO_MATCH - Treat the web request as not matching the rule statement.

                        If you don't provide this setting, WAF parses and evaluates the content only up to the first parsing failure that it encounters.

                        WAF does its best to parse the entire JSON body, but might be forced to stop for reasons such as invalid characters, duplicate keys, truncation, and any content whose root node isn't an object or an array.

                        WAF parses the JSON in the following examples as two valid key, value pairs:

                        • Missing comma: {"key1":"value1""key2":"value2"}

                        • Missing colon: {"key1":"value1","key2""value2"}

                        • Extra colons: {"key1"::"value1","key2""value2"}

                        Possible values include:
                        • "MATCH"
                        • "NO_MATCH"
                        • "EVALUATE_AS_STRING"
                  • TextTransformations — required — (Array<map>)

                    Text transformations eliminate some of the unusual formatting that attackers use in web requests in an effort to bypass detection. If you specify one or more transformations in a rule statement, WAF performs all transformations on the content of the request component identified by FieldToMatch, starting from the lowest priority setting, before inspecting the content for a match.

                    • Priority — required — (Integer)

                      Sets the relative processing order for multiple transformations that are defined for a rule statement. WAF processes all transformations, from lowest priority to highest, before inspecting the transformed content. The priorities don't need to be consecutive, but they must all be different.

                    • Type — required — (String)

                      You can specify the following transformation types:

                      BASE64_DECODE - Decode a Base64-encoded string.

                      BASE64_DECODE_EXT - Decode a Base64-encoded string, but use a forgiving implementation that ignores characters that aren't valid.

                      CMD_LINE - Command-line transformations. These are helpful in reducing effectiveness of attackers who inject an operating system command-line command and use unusual formatting to disguise some or all of the command.

                      • Delete the following characters: \ " ' ^

                      • Delete spaces before the following characters: / (

                      • Replace the following characters with a space: , ;

                      • Replace multiple spaces with one space

                      • Convert uppercase letters (A-Z) to lowercase (a-z)

                      COMPRESS_WHITE_SPACE - Replace these characters with a space character (decimal 32):

                      • \f, formfeed, decimal 12

                      • \t, tab, decimal 9

                      • \n, newline, decimal 10

                      • \r, carriage return, decimal 13

                      • \v, vertical tab, decimal 11

                      • Non-breaking space, decimal 160

                      COMPRESS_WHITE_SPACE also replaces multiple spaces with one space.

                      CSS_DECODE - Decode characters that were encoded using CSS 2.x escape rules syndata.html#characters. This function uses up to two bytes in the decoding process, so it can help to uncover ASCII characters that were encoded using CSS encoding that wouldn’t typically be encoded. It's also useful in countering evasion, which is a combination of a backslash and non-hexadecimal characters. For example, ja\vascript for javascript.

                      ESCAPE_SEQ_DECODE - Decode the following ANSI C escape sequences: \a, \b, \f, \n, \r, \t, \v, \, \?, \', \", \xHH (hexadecimal), \0OOO (octal). Encodings that aren't valid remain in the output.

                      HEX_DECODE - Decode a string of hexadecimal characters into a binary.

                      HTML_ENTITY_DECODE - Replace HTML-encoded characters with unencoded characters. HTML_ENTITY_DECODE performs these operations:

                      • Replaces (ampersand)quot; with "

                      • Replaces (ampersand)nbsp; with a non-breaking space, decimal 160

                      • Replaces (ampersand)lt; with a "less than" symbol

                      • Replaces (ampersand)gt; with >

                      • Replaces characters that are represented in hexadecimal format, (ampersand)#xhhhh;, with the corresponding characters

                      • Replaces characters that are represented in decimal format, (ampersand)#nnnn;, with the corresponding characters

                      JS_DECODE - Decode JavaScript escape sequences. If a \ u HHHH code is in the full-width ASCII code range of FF01-FF5E, then the higher byte is used to detect and adjust the lower byte. If not, only the lower byte is used and the higher byte is zeroed, causing a possible loss of information.

                      LOWERCASE - Convert uppercase letters (A-Z) to lowercase (a-z).

                      MD5 - Calculate an MD5 hash from the data in the input. The computed hash is in a raw binary form.

                      NONE - Specify NONE if you don't want any text transformations.

                      NORMALIZE_PATH - Remove multiple slashes, directory self-references, and directory back-references that are not at the beginning of the input from an input string.

                      NORMALIZE_PATH_WIN - This is the same as NORMALIZE_PATH, but first converts backslash characters to forward slashes.

                      REMOVE_NULLS - Remove all NULL bytes from the input.

                      REPLACE_COMMENTS - Replace each occurrence of a C-style comment (/* ... */) with a single space. Multiple consecutive occurrences are not compressed. Unterminated comments are also replaced with a space (ASCII 0x20). However, a standalone termination of a comment (*/) is not acted upon.

                      REPLACE_NULLS - Replace NULL bytes in the input with space characters (ASCII 0x20).

                      SQL_HEX_DECODE - Decode SQL hex data. Example (0x414243) will be decoded to (ABC).

                      URL_DECODE - Decode a URL-encoded value.

                      URL_DECODE_UNI - Like URL_DECODE, but with support for Microsoft-specific %u encoding. If the code is in the full-width ASCII code range of FF01-FF5E, the higher byte is used to detect and adjust the lower byte. Otherwise, only the lower byte is used and the higher byte is zeroed.

                      UTF8_TO_UNICODE - Convert all UTF-8 character sequences to Unicode. This helps input normalization, and minimizing false-positives and false-negatives for non-English languages.

                      Possible values include:
                      • "NONE"
                      • "COMPRESS_WHITE_SPACE"
                      • "HTML_ENTITY_DECODE"
                      • "LOWERCASE"
                      • "CMD_LINE"
                      • "URL_DECODE"
                      • "BASE64_DECODE"
                      • "HEX_DECODE"
                      • "MD5"
                      • "REPLACE_COMMENTS"
                      • "ESCAPE_SEQ_DECODE"
                      • "SQL_HEX_DECODE"
                      • "CSS_DECODE"
                      • "JS_DECODE"
                      • "NORMALIZE_PATH"
                      • "NORMALIZE_PATH_WIN"
                      • "REMOVE_NULLS"
                      • "REPLACE_NULLS"
                      • "BASE64_DECODE_EXT"
                      • "URL_DECODE_UNI"
                      • "UTF8_TO_UNICODE"
                • XssMatchStatement — (map)

                  A rule statement that defines a cross-site scripting (XSS) match search for WAF to apply to web requests. XSS attacks are those where the attacker uses vulnerabilities in a benign website as a vehicle to inject malicious client-site scripts into other legitimate web browsers. The XSS match statement provides the location in requests that you want WAF to search and text transformations to use on the search area before WAF searches for character sequences that are likely to be malicious strings.

                  • FieldToMatch — required — (map)

                    The part of a web request that you want WAF to inspect. For more information, see FieldToMatch.

                    • SingleHeader — (map)

                      Inspect a single header. Provide the name of the header to inspect, for example, User-Agent or Referer. This setting isn't case sensitive.

                      Example JSON: "SingleHeader": { "Name": "haystack" }

                      • Name — required — (String)

                        The name of the query header to inspect.

                    • SingleQueryArgument — (map)

                      Inspect a single query argument. Provide the name of the query argument to inspect, such as UserName or SalesRegion. The name can be up to 30 characters long and isn't case sensitive.

                      This is used only to indicate the web request component for WAF to inspect, in the FieldToMatch specification.

                      Example JSON: "SingleQueryArgument": { "Name": "myArgument" }

                      • Name — required — (String)

                        The name of the query argument to inspect.

                    • AllQueryArguments — (map)

                      Inspect all query arguments.

                    • UriPath — (map)

                      Inspect the request URI path. This is the part of a web request that identifies a resource, for example, /images/daily-ad.jpg.

                    • QueryString — (map)

                      Inspect the query string. This is the part of a URL that appears after a ? character, if any.

                    • Body — (map)

                      Inspect the request body as plain text. The request body immediately follows the request headers. This is the part of a request that contains any additional data that you want to send to your web server as the HTTP request body, such as data from a form.

                      Note that only the first 8 KB (8192 bytes) of the request body are forwarded to WAF for inspection by the underlying host service. If you don't need to inspect more than 8 KB, you can guarantee that you don't allow additional bytes in by combining a statement that inspects the body of the web request, such as ByteMatchStatement or RegexPatternSetReferenceStatement, with a SizeConstraintStatement that enforces an 8 KB size limit on the body of the request. WAF doesn't support inspecting the entire contents of web requests whose bodies exceed the 8 KB limit.

                    • Method — (map)

                      Inspect the HTTP method. The method indicates the type of operation that the request is asking the origin to perform.

                    • JsonBody — (map)

                      Inspect the request body as JSON. The request body immediately follows the request headers. This is the part of a request that contains any additional data that you want to send to your web server as the HTTP request body, such as data from a form.

                      Note that only the first 8 KB (8192 bytes) of the request body are forwarded to WAF for inspection by the underlying host service. If you don't need to inspect more than 8 KB, you can guarantee that you don't allow additional bytes in by combining a statement that inspects the body of the web request, such as ByteMatchStatement or RegexPatternSetReferenceStatement, with a SizeConstraintStatement that enforces an 8 KB size limit on the body of the request. WAF doesn't support inspecting the entire contents of web requests whose bodies exceed the 8 KB limit.

                      • MatchPattern — required — (map)

                        The patterns to look for in the JSON body. WAF inspects the results of these pattern matches against the rule inspection criteria.

                        • All — (map)

                          Match all of the elements. See also MatchScope in JsonBody.

                          You must specify either this setting or the IncludedPaths setting, but not both.

                        • IncludedPaths — (Array<String>)

                          Match only the specified include paths. See also MatchScope in JsonBody.

                          Provide the include paths using JSON Pointer syntax. For example, "IncludedPaths": ["/dogs/0/name", "/dogs/1/name"]. For information about this syntax, see the Internet Engineering Task Force (IETF) documentation JavaScript Object Notation (JSON) Pointer.

                          You must specify either this setting or the All setting, but not both.

                          Note: Don't use this option to include all paths. Instead, use the All setting.
                      • MatchScope — required — (String)

                        The parts of the JSON to match against using the MatchPattern. If you specify All, WAF matches against keys and values.

                        Possible values include:
                        • "ALL"
                        • "KEY"
                        • "VALUE"
                      • InvalidFallbackBehavior — (String)

                        What WAF should do if it fails to completely parse the JSON body. The options are the following:

                        • EVALUATE_AS_STRING - Inspect the body as plain text. WAF applies the text transformations and inspection criteria that you defined for the JSON inspection to the body text string.

                        • MATCH - Treat the web request as matching the rule statement. WAF applies the rule action to the request.

                        • NO_MATCH - Treat the web request as not matching the rule statement.

                        If you don't provide this setting, WAF parses and evaluates the content only up to the first parsing failure that it encounters.

                        WAF does its best to parse the entire JSON body, but might be forced to stop for reasons such as invalid characters, duplicate keys, truncation, and any content whose root node isn't an object or an array.

                        WAF parses the JSON in the following examples as two valid key, value pairs:

                        • Missing comma: {"key1":"value1""key2":"value2"}

                        • Missing colon: {"key1":"value1","key2""value2"}

                        • Extra colons: {"key1"::"value1","key2""value2"}

                        Possible values include:
                        • "MATCH"
                        • "NO_MATCH"
                        • "EVALUATE_AS_STRING"
                  • TextTransformations — required — (Array<map>)

                    Text transformations eliminate some of the unusual formatting that attackers use in web requests in an effort to bypass detection. If you specify one or more transformations in a rule statement, WAF performs all transformations on the content of the request component identified by FieldToMatch, starting from the lowest priority setting, before inspecting the content for a match.

                    • Priority — required — (Integer)

                      Sets the relative processing order for multiple transformations that are defined for a rule statement. WAF processes all transformations, from lowest priority to highest, before inspecting the transformed content. The priorities don't need to be consecutive, but they must all be different.

                    • Type — required — (String)

                      You can specify the following transformation types:

                      BASE64_DECODE - Decode a Base64-encoded string.

                      BASE64_DECODE_EXT - Decode a Base64-encoded string, but use a forgiving implementation that ignores characters that aren't valid.

                      CMD_LINE - Command-line transformations. These are helpful in reducing effectiveness of attackers who inject an operating system command-line command and use unusual formatting to disguise some or all of the command.

                      • Delete the following characters: \ " ' ^

                      • Delete spaces before the following characters: / (

                      • Replace the following characters with a space: , ;

                      • Replace multiple spaces with one space

                      • Convert uppercase letters (A-Z) to lowercase (a-z)

                      COMPRESS_WHITE_SPACE - Replace these characters with a space character (decimal 32):

                      • \f, formfeed, decimal 12

                      • \t, tab, decimal 9

                      • \n, newline, decimal 10

                      • \r, carriage return, decimal 13

                      • \v, vertical tab, decimal 11

                      • Non-breaking space, decimal 160

                      COMPRESS_WHITE_SPACE also replaces multiple spaces with one space.

                      CSS_DECODE - Decode characters that were encoded using CSS 2.x escape rules syndata.html#characters. This function uses up to two bytes in the decoding process, so it can help to uncover ASCII characters that were encoded using CSS encoding that wouldn’t typically be encoded. It's also useful in countering evasion, which is a combination of a backslash and non-hexadecimal characters. For example, ja\vascript for javascript.

                      ESCAPE_SEQ_DECODE - Decode the following ANSI C escape sequences: \a, \b, \f, \n, \r, \t, \v, \, \?, \', \", \xHH (hexadecimal), \0OOO (octal). Encodings that aren't valid remain in the output.

                      HEX_DECODE - Decode a string of hexadecimal characters into a binary.

                      HTML_ENTITY_DECODE - Replace HTML-encoded characters with unencoded characters. HTML_ENTITY_DECODE performs these operations:

                      • Replaces (ampersand)quot; with "

                      • Replaces (ampersand)nbsp; with a non-breaking space, decimal 160

                      • Replaces (ampersand)lt; with a "less than" symbol

                      • Replaces (ampersand)gt; with >

                      • Replaces characters that are represented in hexadecimal format, (ampersand)#xhhhh;, with the corresponding characters

                      • Replaces characters that are represented in decimal format, (ampersand)#nnnn;, with the corresponding characters

                      JS_DECODE - Decode JavaScript escape sequences. If a \ u HHHH code is in the full-width ASCII code range of FF01-FF5E, then the higher byte is used to detect and adjust the lower byte. If not, only the lower byte is used and the higher byte is zeroed, causing a possible loss of information.

                      LOWERCASE - Convert uppercase letters (A-Z) to lowercase (a-z).

                      MD5 - Calculate an MD5 hash from the data in the input. The computed hash is in a raw binary form.

                      NONE - Specify NONE if you don't want any text transformations.

                      NORMALIZE_PATH - Remove multiple slashes, directory self-references, and directory back-references that are not at the beginning of the input from an input string.

                      NORMALIZE_PATH_WIN - This is the same as NORMALIZE_PATH, but first converts backslash characters to forward slashes.

                      REMOVE_NULLS - Remove all NULL bytes from the input.

                      REPLACE_COMMENTS - Replace each occurrence of a C-style comment (/* ... */) with a single space. Multiple consecutive occurrences are not compressed. Unterminated comments are also replaced with a space (ASCII 0x20). However, a standalone termination of a comment (*/) is not acted upon.

                      REPLACE_NULLS - Replace NULL bytes in the input with space characters (ASCII 0x20).

                      SQL_HEX_DECODE - Decode SQL hex data. Example (0x414243) will be decoded to (ABC).

                      URL_DECODE - Decode a URL-encoded value.

                      URL_DECODE_UNI - Like URL_DECODE, but with support for Microsoft-specific %u encoding. If the code is in the full-width ASCII code range of FF01-FF5E, the higher byte is used to detect and adjust the lower byte. Otherwise, only the lower byte is used and the higher byte is zeroed.

                      UTF8_TO_UNICODE - Convert all UTF-8 character sequences to Unicode. This helps input normalization, and minimizing false-positives and false-negatives for non-English languages.

                      Possible values include:
                      • "NONE"
                      • "COMPRESS_WHITE_SPACE"
                      • "HTML_ENTITY_DECODE"
                      • "LOWERCASE"
                      • "CMD_LINE"
                      • "URL_DECODE"
                      • "BASE64_DECODE"
                      • "HEX_DECODE"
                      • "MD5"
                      • "REPLACE_COMMENTS"
                      • "ESCAPE_SEQ_DECODE"
                      • "SQL_HEX_DECODE"
                      • "CSS_DECODE"
                      • "JS_DECODE"
                      • "NORMALIZE_PATH"
                      • "NORMALIZE_PATH_WIN"
                      • "REMOVE_NULLS"
                      • "REPLACE_NULLS"
                      • "BASE64_DECODE_EXT"
                      • "URL_DECODE_UNI"
                      • "UTF8_TO_UNICODE"
                • SizeConstraintStatement — (map)

                  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 first 8192 bytes (8 KB). If the request body for your web requests never exceeds 8192 bytes, you can create a size constraint condition and block requests that have a request body greater than 8192 bytes.

                  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.

                  • FieldToMatch — required — (map)

                    The part of a web request that you want WAF to inspect. For more information, see FieldToMatch.

                    • SingleHeader — (map)

                      Inspect a single header. Provide the name of the header to inspect, for example, User-Agent or Referer. This setting isn't case sensitive.

                      Example JSON: "SingleHeader": { "Name": "haystack" }

                      • Name — required — (String)

                        The name of the query header to inspect.

                    • SingleQueryArgument — (map)

                      Inspect a single query argument. Provide the name of the query argument to inspect, such as UserName or SalesRegion. The name can be up to 30 characters long and isn't case sensitive.

                      This is used only to indicate the web request component for WAF to inspect, in the FieldToMatch specification.

                      Example JSON: "SingleQueryArgument": { "Name": "myArgument" }

                      • Name — required — (String)

                        The name of the query argument to inspect.

                    • AllQueryArguments — (map)

                      Inspect all query arguments.

                    • UriPath — (map)

                      Inspect the request URI path. This is the part of a web request that identifies a resource, for example, /images/daily-ad.jpg.

                    • QueryString — (map)

                      Inspect the query string. This is the part of a URL that appears after a ? character, if any.

                    • Body — (map)

                      Inspect the request body as plain text. The request body immediately follows the request headers. This is the part of a request that contains any additional data that you want to send to your web server as the HTTP request body, such as data from a form.

                      Note that only the first 8 KB (8192 bytes) of the request body are forwarded to WAF for inspection by the underlying host service. If you don't need to inspect more than 8 KB, you can guarantee that you don't allow additional bytes in by combining a statement that inspects the body of the web request, such as ByteMatchStatement or RegexPatternSetReferenceStatement, with a SizeConstraintStatement that enforces an 8 KB size limit on the body of the request. WAF doesn't support inspecting the entire contents of web requests whose bodies exceed the 8 KB limit.

                    • Method — (map)

                      Inspect the HTTP method. The method indicates the type of operation that the request is asking the origin to perform.

                    • JsonBody — (map)

                      Inspect the request body as JSON. The request body immediately follows the request headers. This is the part of a request that contains any additional data that you want to send to your web server as the HTTP request body, such as data from a form.

                      Note that only the first 8 KB (8192 bytes) of the request body are forwarded to WAF for inspection by the underlying host service. If you don't need to inspect more than 8 KB, you can guarantee that you don't allow additional bytes in by combining a statement that inspects the body of the web request, such as ByteMatchStatement or RegexPatternSetReferenceStatement, with a SizeConstraintStatement that enforces an 8 KB size limit on the body of the request. WAF doesn't support inspecting the entire contents of web requests whose bodies exceed the 8 KB limit.

                      • MatchPattern — required — (map)

                        The patterns to look for in the JSON body. WAF inspects the results of these pattern matches against the rule inspection criteria.

                        • All — (map)

                          Match all of the elements. See also MatchScope in JsonBody.

                          You must specify either this setting or the IncludedPaths setting, but not both.

                        • IncludedPaths — (Array<String>)

                          Match only the specified include paths. See also MatchScope in JsonBody.

                          Provide the include paths using JSON Pointer syntax. For example, "IncludedPaths": ["/dogs/0/name", "/dogs/1/name"]. For information about this syntax, see the Internet Engineering Task Force (IETF) documentation JavaScript Object Notation (JSON) Pointer.

                          You must specify either this setting or the All setting, but not both.

                          Note: Don't use this option to include all paths. Instead, use the All setting.
                      • MatchScope — required — (String)

                        The parts of the JSON to match against using the MatchPattern. If you specify All, WAF matches against keys and values.

                        Possible values include:
                        • "ALL"
                        • "KEY"
                        • "VALUE"
                      • InvalidFallbackBehavior — (String)

                        What WAF should do if it fails to completely parse the JSON body. The options are the following:

                        • EVALUATE_AS_STRING - Inspect the body as plain text. WAF applies the text transformations and inspection criteria that you defined for the JSON inspection to the body text string.

                        • MATCH - Treat the web request as matching the rule statement. WAF applies the rule action to the request.

                        • NO_MATCH - Treat the web request as not matching the rule statement.

                        If you don't provide this setting, WAF parses and evaluates the content only up to the first parsing failure that it encounters.

                        WAF does its best to parse the entire JSON body, but might be forced to stop for reasons such as invalid characters, duplicate keys, truncation, and any content whose root node isn't an object or an array.

                        WAF parses the JSON in the following examples as two valid key, value pairs:

                        • Missing comma: {"key1":"value1""key2":"value2"}

                        • Missing colon: {"key1":"value1","key2""value2"}

                        • Extra colons: {"key1"::"value1","key2""value2"}

                        Possible values include:
                        • "MATCH"
                        • "NO_MATCH"
                        • "EVALUATE_AS_STRING"
                  • ComparisonOperator — required — (String)

                    The operator to use to compare the request part to the size setting.

                    Possible values include:
                    • "EQ"
                    • "NE"
                    • "LE"
                    • "LT"
                    • "GE"
                    • "GT"
                  • Size — required — (Integer)

                    The size, in byte, to compare to the request part, after any transformations.

                  • TextTransformations — required — (Array<map>)

                    Text transformations eliminate some of the unusual formatting that attackers use in web requests in an effort to bypass detection. If you specify one or more transformations in a rule statement, WAF performs all transformations on the content of the request component identified by FieldToMatch, starting from the lowest priority setting, before inspecting the content for a match.

                    • Priority — required — (Integer)

                      Sets the relative processing order for multiple transformations that are defined for a rule statement. WAF processes all transformations, from lowest priority to highest, before inspecting the transformed content. The priorities don't need to be consecutive, but they must all be different.

                    • Type — required — (String)

                      You can specify the following transformation types:

                      BASE64_DECODE - Decode a Base64-encoded string.

                      BASE64_DECODE_EXT - Decode a Base64-encoded string, but use a forgiving implementation that ignores characters that aren't valid.

                      CMD_LINE - Command-line transformations. These are helpful in reducing effectiveness of attackers who inject an operating system command-line command and use unusual formatting to disguise some or all of the command.

                      • Delete the following characters: \ " ' ^

                      • Delete spaces before the following characters: / (

                      • Replace the following characters with a space: , ;

                      • Replace multiple spaces with one space

                      • Convert uppercase letters (A-Z) to lowercase (a-z)

                      COMPRESS_WHITE_SPACE - Replace these characters with a space character (decimal 32):

                      • \f, formfeed, decimal 12

                      • \t, tab, decimal 9

                      • \n, newline, decimal 10

                      • \r, carriage return, decimal 13

                      • \v, vertical tab, decimal 11

                      • Non-breaking space, decimal 160

                      COMPRESS_WHITE_SPACE also replaces multiple spaces with one space.

                      CSS_DECODE - Decode characters that were encoded using CSS 2.x escape rules syndata.html#characters. This function uses up to two bytes in the decoding process, so it can help to uncover ASCII characters that were encoded using CSS encoding that wouldn’t typically be encoded. It's also useful in countering evasion, which is a combination of a backslash and non-hexadecimal characters. For example, ja\vascript for javascript.

                      ESCAPE_SEQ_DECODE - Decode the following ANSI C escape sequences: \a, \b, \f, \n, \r, \t, \v, \, \?, \', \", \xHH (hexadecimal), \0OOO (octal). Encodings that aren't valid remain in the output.

                      HEX_DECODE - Decode a string of hexadecimal characters into a binary.

                      HTML_ENTITY_DECODE - Replace HTML-encoded characters with unencoded characters. HTML_ENTITY_DECODE performs these operations:

                      • Replaces (ampersand)quot; with "

                      • Replaces (ampersand)nbsp; with a non-breaking space, decimal 160

                      • Replaces (ampersand)lt; with a "less than" symbol

                      • Replaces (ampersand)gt; with >

                      • Replaces characters that are represented in hexadecimal format, (ampersand)#xhhhh;, with the corresponding characters

                      • Replaces characters that are represented in decimal format, (ampersand)#nnnn;, with the corresponding characters

                      JS_DECODE - Decode JavaScript escape sequences. If a \ u HHHH code is in the full-width ASCII code range of FF01-FF5E, then the higher byte is used to detect and adjust the lower byte. If not, only the lower byte is used and the higher byte is zeroed, causing a possible loss of information.

                      LOWERCASE - Convert uppercase letters (A-Z) to lowercase (a-z).

                      MD5 - Calculate an MD5 hash from the data in the input. The computed hash is in a raw binary form.

                      NONE - Specify NONE if you don't want any text transformations.

                      NORMALIZE_PATH - Remove multiple slashes, directory self-references, and directory back-references that are not at the beginning of the input from an input string.

                      NORMALIZE_PATH_WIN - This is the same as NORMALIZE_PATH, but first converts backslash characters to forward slashes.

                      REMOVE_NULLS - Remove all NULL bytes from the input.

                      REPLACE_COMMENTS - Replace each occurrence of a C-style comment (/* ... */) with a single space. Multiple consecutive occurrences are not compressed. Unterminated comments are also replaced with a space (ASCII 0x20). However, a standalone termination of a comment (*/) is not acted upon.

                      REPLACE_NULLS - Replace NULL bytes in the input with space characters (ASCII 0x20).

                      SQL_HEX_DECODE - Decode SQL hex data. Example (0x414243) will be decoded to (ABC).

                      URL_DECODE - Decode a URL-encoded value.

                      URL_DECODE_UNI - Like URL_DECODE, but with support for Microsoft-specific %u encoding. If the code is in the full-width ASCII code range of FF01-FF5E, the higher byte is used to detect and adjust the lower byte. Otherwise, only the lower byte is used and the higher byte is zeroed.

                      UTF8_TO_UNICODE - Convert all UTF-8 character sequences to Unicode. This helps input normalization, and minimizing false-positives and false-negatives for non-English languages.

                      Possible values include:
                      • "NONE"
                      • "COMPRESS_WHITE_SPACE"
                      • "HTML_ENTITY_DECODE"
                      • "LOWERCASE"
                      • "CMD_LINE"
                      • "URL_DECODE"
                      • "BASE64_DECODE"
                      • "HEX_DECODE"
                      • "MD5"
                      • "REPLACE_COMMENTS"
                      • "ESCAPE_SEQ_DECODE"
                      • "SQL_HEX_DECODE"
                      • "CSS_DECODE"
                      • "JS_DECODE"
                      • "NORMALIZE_PATH"
                      • "NORMALIZE_PATH_WIN"
                      • "REMOVE_NULLS"
                      • "REPLACE_NULLS"
                      • "BASE64_DECODE_EXT"
                      • "URL_DECODE_UNI"
                      • "UTF8_TO_UNICODE"
                • GeoMatchStatement — (map)

                  A rule statement used to identify web requests based on country of origin.

                  • CountryCodes — (Array<String>)

                    An array of two-character country codes, for example, [ "US", "CN" ], from the alpha-2 country ISO codes of the ISO 3166 international standard.

                  • ForwardedIPConfig — (map)

                    The configuration for inspecting IP addresses in an HTTP header that you specify, instead of using the IP address that's reported by the web request origin. Commonly, this is the X-Forwarded-For (XFF) header, but you can specify any header name.

                    Note: If the specified header isn't present in the request, WAF doesn't apply the rule to the web request at all.
                    • HeaderName — required — (String)

                      The name of the HTTP header to use for the IP address. For example, to use the X-Forwarded-For (XFF) header, set this to X-Forwarded-For.

                      Note: If the specified header isn't present in the request, WAF doesn't apply the rule to the web request at all.
                    • FallbackBehavior — required — (String)

                      The match status to assign to the web request if the request doesn't have a valid IP address in the specified position.

                      Note: If the specified header isn't present in the request, WAF doesn't apply the rule to the web request at all.

                      You can specify the following fallback behaviors:

                      • MATCH - Treat the web request as matching the rule statement. WAF applies the rule action to the request.

                      • NO_MATCH - Treat the web request as not matching the rule statement.

                      Possible values include:
                      • "MATCH"
                      • "NO_MATCH"
                • RuleGroupReferenceStatement — (map)

                  A rule statement used to run the rules that are defined in a RuleGroup. To use this, create a rule group with your rules, then provide the ARN of the rule group in this statement.

                  You cannot nest a RuleGroupReferenceStatement, for example for use inside a NotStatement or OrStatement. You can only use a rule group reference statement at the top level inside a web ACL.

                  • ARN — required — (String)

                    The Amazon Resource Name (ARN) of the entity.

                  • ExcludedRules — (Array<map>)

                    The rules in the referenced rule group whose actions are set to Count. When you exclude a rule, WAF evaluates it exactly as it would if the rule action setting were Count. This is a useful option for testing the rules in a rule group without modifying how they handle your web traffic.

                    • Name — required — (String)

                      The name of the rule whose action you want to override to Count.

                • IPSetReferenceStatement — (map)

                  A rule statement used to detect web requests coming from particular IP addresses or address ranges. To use this, create an IPSet that specifies the addresses you want to detect, then use the ARN of that set in this statement. To create an IP set, see CreateIPSet.

                  Each IP set rule statement references an IP set. You create and maintain the set independent of your rules. This allows you to use the single set in multiple rules. When you update the referenced set, WAF automatically updates all rules that reference it.

                  • ARN — required — (String)

                    The Amazon Resource Name (ARN) of the IPSet that this statement references.

                  • IPSetForwardedIPConfig — (map)

                    The configuration for inspecting IP addresses in an HTTP header that you specify, instead of using the IP address that's reported by the web request origin. Commonly, this is the X-Forwarded-For (XFF) header, but you can specify any header name.

                    Note: If the specified header isn't present in the request, WAF doesn't apply the rule to the web request at all.
                    • HeaderName — required — (String)

                      The name of the HTTP header to use for the IP address. For example, to use the X-Forwarded-For (XFF) header, set this to X-Forwarded-For.

                      Note: If the specified header isn't present in the request, WAF doesn't apply the rule to the web request at all.
                    • FallbackBehavior — required — (String)

                      The match status to assign to the web request if the request doesn't have a valid IP address in the specified position.

                      Note: If the specified header isn't present in the request, WAF doesn't apply the rule to the web request at all.

                      You can specify the following fallback behaviors:

                      • MATCH - Treat the web request as matching the rule statement. WAF applies the rule action to the request.

                      • NO_MATCH - Treat the web request as not matching the rule statement.

                      Possible values include:
                      • "MATCH"
                      • "NO_MATCH"
                    • Position — required — (String)

                      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:

                      • FIRST - Inspect the first IP address in the list of IP addresses in the header. This is usually the client's original IP.

                      • LAST - Inspect the last IP address in the list of IP addresses in the header.

                      • ANY - Inspect all IP addresses in the header for a match. If the header contains more than 10 IP addresses, WAF inspects the last 10.

                      Possible values include:
                      • "FIRST"
                      • "LAST"
                      • "ANY"
                • RegexPatternSetReferenceStatement — (map)

                  A rule statement used to search web request components for matches with regular expressions. To use this, create a RegexPatternSet that specifies the expressions that you want to detect, then use the ARN of that set in this statement. A web request matches the pattern set rule statement if the request component matches any of the patterns in the set. To create a regex pattern set, see CreateRegexPatternSet.

                  Each regex pattern set rule statement references a regex pattern set. You create and maintain the set independent of your rules. This allows you to use the single set in multiple rules. When you update the referenced set, WAF automatically updates all rules that reference it.

                  • ARN — required — (String)

                    The Amazon Resource Name (ARN) of the RegexPatternSet that this statement references.

                  • FieldToMatch — required — (map)

                    The part of a web request that you want WAF to inspect. For more information, see FieldToMatch.

                    • SingleHeader — (map)

                      Inspect a single header. Provide the name of the header to inspect, for example, User-Agent or Referer. This setting isn't case sensitive.

                      Example JSON: "SingleHeader": { "Name": "haystack" }

                      • Name — required — (String)

                        The name of the query header to inspect.

                    • SingleQueryArgument — (map)

                      Inspect a single query argument. Provide the name of the query argument to inspect, such as UserName or SalesRegion. The name can be up to 30 characters long and isn't case sensitive.

                      This is used only to indicate the web request component for WAF to inspect, in the FieldToMatch specification.

                      Example JSON: "SingleQueryArgument": { "Name": "myArgument" }

                      • Name — required — (String)

                        The name of the query argument to inspect.

                    • AllQueryArguments — (map)

                      Inspect all query arguments.

                    • UriPath — (map)

                      Inspect the request URI path. This is the part of a web request that identifies a resource, for example, /images/daily-ad.jpg.

                    • QueryString — (map)

                      Inspect the query string. This is the part of a URL that appears after a ? character, if any.

                    • Body — (map)

                      Inspect the request body as plain text. The request body immediately follows the request headers. This is the part of a request that contains any additional data that you want to send to your web server as the HTTP request body, such as data from a form.

                      Note that only the first 8 KB (8192 bytes) of the request body are forwarded to WAF for inspection by the underlying host service. If you don't need to inspect more than 8 KB, you can guarantee that you don't allow additional bytes in by combining a statement that inspects the body of the web request, such as ByteMatchStatement or RegexPatternSetReferenceStatement, with a SizeConstraintStatement that enforces an 8 KB size limit on the body of the request. WAF doesn't support inspecting the entire contents of web requests whose bodies exceed the 8 KB limit.

                    • Method — (map)

                      Inspect the HTTP method. The method indicates the type of operation that the request is asking the origin to perform.

                    • JsonBody — (map)

                      Inspect the request body as JSON. The request body immediately follows the request headers. This is the part of a request that contains any additional data that you want to send to your web server as the HTTP request body, such as data from a form.

                      Note that only the first 8 KB (8192 bytes) of the request body are forwarded to WAF for inspection by the underlying host service. If you don't need to inspect more than 8 KB, you can guarantee that you don't allow additional bytes in by combining a statement that inspects the body of the web request, such as ByteMatchStatement or RegexPatternSetReferenceStatement, with a SizeConstraintStatement that enforces an 8 KB size limit on the body of the request. WAF doesn't support inspecting the entire contents of web requests whose bodies exceed the 8 KB limit.

                      • MatchPattern — required — (map)

                        The patterns to look for in the JSON body. WAF inspects the results of these pattern matches against the rule inspection criteria.

                        • All — (map)

                          Match all of the elements. See also MatchScope in JsonBody.

                          You must specify either this setting or the IncludedPaths setting, but not both.

                        • IncludedPaths — (Array<String>)

                          Match only the specified include paths. See also MatchScope in JsonBody.

                          Provide the include paths using JSON Pointer syntax. For example, "IncludedPaths": ["/dogs/0/name", "/dogs/1/name"]. For information about this syntax, see the Internet Engineering Task Force (IETF) documentation JavaScript Object Notation (JSON) Pointer.

                          You must specify either this setting or the All setting, but not both.

                          Note: Don't use this option to include all paths. Instead, use the All setting.
                      • MatchScope — required — (String)

                        The parts of the JSON to match against using the MatchPattern. If you specify All, WAF matches against keys and values.

                        Possible values include:
                        • "ALL"
                        • "KEY"
                        • "VALUE"
                      • InvalidFallbackBehavior — (String)

                        What WAF should do if it fails to completely parse the JSON body. The options are the following:

                        • EVALUATE_AS_STRING - Inspect the body as plain text. WAF applies the text transformations and inspection criteria that you defined for the JSON inspection to the body text string.

                        • MATCH - Treat the web request as matching the rule statement. WAF applies the rule action to the request.

                        • NO_MATCH - Treat the web request as not matching the rule statement.

                        If you don't provide this setting, WAF parses and evaluates the content only up to the first parsing failure that it encounters.

                        WAF does its best to parse the entire JSON body, but might be forced to stop for reasons such as invalid characters, duplicate keys, truncation, and any content whose root node isn't an object or an array.

                        WAF parses the JSON in the following examples as two valid key, value pairs:

                        • Missing comma: {"key1":"value1""key2":"value2"}

                        • Missing colon: {"key1":"value1","key2""value2"}

                        • Extra colons: {"key1"::"value1","key2""value2"}

                        Possible values include:
                        • "MATCH"
                        • "NO_MATCH"
                        • "EVALUATE_AS_STRING"
                  • TextTransformations — required — (Array<map>)

                    Text transformations eliminate some of the unusual formatting that attackers use in web requests in an effort to bypass detection. If you specify one or more transformations in a rule statement, WAF performs all transformations on the content of the request component identified by FieldToMatch, starting from the lowest priority setting, before inspecting the content for a match.

                    • Priority — required — (Integer)

                      Sets the relative processing order for multiple transformations that are defined for a rule statement. WAF processes all transformations, from lowest priority to highest, before inspecting the transformed content. The priorities don't need to be consecutive, but they must all be different.

                    • Type — required — (String)

                      You can specify the following transformation types:

                      BASE64_DECODE - Decode a Base64-encoded string.

                      BASE64_DECODE_EXT - Decode a Base64-encoded string, but use a forgiving implementation that ignores characters that aren't valid.

                      CMD_LINE - Command-line transformations. These are helpful in reducing effectiveness of attackers who inject an operating system command-line command and use unusual formatting to disguise some or all of the command.

                      • Delete the following characters: \ " ' ^

                      • Delete spaces before the following characters: / (

                      • Replace the following characters with a space: , ;

                      • Replace multiple spaces with one space

                      • Convert uppercase letters (A-Z) to lowercase (a-z)

                      COMPRESS_WHITE_SPACE - Replace these characters with a space character (decimal 32):

                      • \f, formfeed, decimal 12

                      • \t, tab, decimal 9

                      • \n, newline, decimal 10

                      • \r, carriage return, decimal 13

                      • \v, vertical tab, decimal 11

                      • Non-breaking space, decimal 160

                      COMPRESS_WHITE_SPACE also replaces multiple spaces with one space.

                      CSS_DECODE - Decode characters that were encoded using CSS 2.x escape rules syndata.html#characters. This function uses up to two bytes in the decoding process, so it can help to uncover ASCII characters that were encoded using CSS encoding that wouldn’t typically be encoded. It's also useful in countering evasion, which is a combination of a backslash and non-hexadecimal characters. For example, ja\vascript for javascript.

                      ESCAPE_SEQ_DECODE - Decode the following ANSI C escape sequences: \a, \b, \f, \n, \r, \t, \v, \, \?, \', \", \xHH (hexadecimal), \0OOO (octal). Encodings that aren't valid remain in the output.

                      HEX_DECODE - Decode a string of hexadecimal characters into a binary.

                      HTML_ENTITY_DECODE - Replace HTML-encoded characters with unencoded characters. HTML_ENTITY_DECODE performs these operations:

                      • Replaces (ampersand)quot; with "

                      • Replaces (ampersand)nbsp; with a non-breaking space, decimal 160

                      • Replaces (ampersand)lt; with a "less than" symbol

                      • Replaces (ampersand)gt; with >

                      • Replaces characters that are represented in hexadecimal format, (ampersand)#xhhhh;, with the corresponding characters

                      • Replaces characters that are represented in decimal format, (ampersand)#nnnn;, with the corresponding characters

                      JS_DECODE - Decode JavaScript escape sequences. If a \ u HHHH code is in the full-width ASCII code range of FF01-FF5E, then the higher byte is used to detect and adjust the lower byte. If not, only the lower byte is used and the higher byte is zeroed, causing a possible loss of information.

                      LOWERCASE - Convert uppercase letters (A-Z) to lowercase (a-z).

                      MD5 - Calculate an MD5 hash from the data in the input. The computed hash is in a raw binary form.

                      NONE - Specify NONE if you don't want any text transformations.

                      NORMALIZE_PATH - Remove multiple slashes, directory self-references, and directory back-references that are not at the beginning of the input from an input string.

                      NORMALIZE_PATH_WIN - This is the same as NORMALIZE_PATH, but first converts backslash characters to forward slashes.

                      REMOVE_NULLS - Remove all NULL bytes from the input.

                      REPLACE_COMMENTS - Replace each occurrence of a C-style comment (/* ... */) with a single space. Multiple consecutive occurrences are not compressed. Unterminated comments are also replaced with a space (ASCII 0x20). However, a standalone termination of a comment (*/) is not acted upon.

                      REPLACE_NULLS - Replace NULL bytes in the input with space characters (ASCII 0x20).

                      SQL_HEX_DECODE - Decode SQL hex data. Example (0x414243) will be decoded to (ABC).

                      URL_DECODE - Decode a URL-encoded value.

                      URL_DECODE_UNI - Like URL_DECODE, but with support for Microsoft-specific %u encoding. If the code is in the full-width ASCII code range of FF01-FF5E, the higher byte is used to detect and adjust the lower byte. Otherwise, only the lower byte is used and the higher byte is zeroed.

                      UTF8_TO_UNICODE - Convert all UTF-8 character sequences to Unicode. This helps input normalization, and minimizing false-positives and false-negatives for non-English languages.

                      Possible values include:
                      • "NONE"
                      • "COMPRESS_WHITE_SPACE"
                      • "HTML_ENTITY_DECODE"
                      • "LOWERCASE"
                      • "CMD_LINE"
                      • "URL_DECODE"
                      • "BASE64_DECODE"
                      • "HEX_DECODE"
                      • "MD5"
                      • "REPLACE_COMMENTS"
                      • "ESCAPE_SEQ_DECODE"
                      • "SQL_HEX_DECODE"
                      • "CSS_DECODE"
                      • "JS_DECODE"
                      • "NORMALIZE_PATH"
                      • "NORMALIZE_PATH_WIN"
                      • "REMOVE_NULLS"
                      • "REPLACE_NULLS"
                      • "BASE64_DECODE_EXT"
                      • "URL_DECODE_UNI"
                      • "UTF8_TO_UNICODE"
                • RateBasedStatement — (map)

                  A rate-based rule tracks the rate of requests for each originating IP address, and triggers the rule action when the rate exceeds a limit that you specify on the number of requests in any 5-minute time span. You can use this to put a temporary block on requests from an IP address that is sending excessive requests.

                  WAF tracks and manages web requests separately for each instance of a rate-based rule that you use. For example, if you provide the same rate-based rule settings in two web ACLs, each of the two rule statements represents a separate instance of the rate-based rule and gets its own tracking and management by WAF. If you define a rate-based rule inside a rule group, and then use that rule group in multiple places, each use creates a separate instance of the rate-based rule that gets its own tracking and management by WAF.

                  When the rule action triggers, WAF blocks additional requests from the IP address until the request rate falls below the limit.

                  You can optionally nest another statement inside the rate-based statement, to narrow the scope of the rule so that it only counts requests that match the nested statement. For example, based on recent requests that you have seen from an attacker, you might create a rate-based rule with a nested AND rule statement that contains the following nested statements:

                  • An IP match statement with an IP set that specified the address 192.0.2.44.

                  • A string match statement that searches in the User-Agent header for the string BadBot.

                  In this rate-based rule, you also define a rate limit. For this example, the rate limit is 1,000. Requests that meet both of the conditions in the statements are counted. If the count exceeds 1,000 requests per five minutes, the rule action triggers. Requests that do not meet both conditions are not counted towards the rate limit and are not affected by this rule.

                  You cannot nest a RateBasedStatement inside another statement, for example inside a NotStatement or OrStatement. You can define a RateBasedStatement inside a web ACL and inside a rule group.

                  • Limit — required — (Integer)

                    The limit on requests per 5-minute period for a single originating IP address. If the statement includes a ScopeDownStatement, this limit is applied only to the requests that match the statement.

                  • AggregateKeyType — required — (String)

                    Setting that indicates how to aggregate the request counts. The options are the following:

                    • IP - Aggregate the request counts on the IP address from the web request origin.

                    • FORWARDED_IP - Aggregate the request counts on the first IP address in an HTTP header. If you use this, configure the ForwardedIPConfig, to specify the header to use.

                    Possible values include:
                    • "IP"
                    • "FORWARDED_IP"
                  • ForwardedIPConfig — (map)

                    The configuration for inspecting IP addresses in an HTTP header that you specify, instead of using the IP address that's reported by the web request origin. Commonly, this is the X-Forwarded-For (XFF) header, but you can specify any header name.

                    Note: If the specified header isn't present in the request, WAF doesn't apply the rule to the web request at all.

                    This is required if AggregateKeyType is set to FORWARDED_IP.

                    • HeaderName — required — (String)

                      The name of the HTTP header to use for the IP address. For example, to use the X-Forwarded-For (XFF) header, set this to X-Forwarded-For.

                      Note: If the specified header isn't present in the request, WAF doesn't apply the rule to the web request at all.
                    • FallbackBehavior — required — (String)

                      The match status to assign to the web request if the request doesn't have a valid IP address in the specified position.

                      Note: If the specified header isn't present in the request, WAF doesn't apply the rule to the web request at all.

                      You can specify the following fallback behaviors:

                      • MATCH - Treat the web request as matching the rule statement. WAF applies the rule action to the request.

                      • NO_MATCH - Treat the web request as not matching the rule statement.

                      Possible values include:
                      • "MATCH"
                      • "NO_MATCH"
                • AndStatement — (map)

                  A logical rule statement used to combine other rule statements with AND logic. You provide more than one Statement within the AndStatement.

                  • Statements — required — (Array<map>)

                    The statements to combine with AND logic. You can use any statements that can be nested.

                • OrStatement — (map)

                  A logical rule statement used to combine other rule statements with OR logic. You provide more than one Statement within the OrStatement.

                  • Statements — required — (Array<map>)

                    The statements to combine with OR logic. You can use any statements that can be nested.

                • NotStatement — (map)

                  A logical rule statement used to negate the results of another rule statement. You provide one Statement within the NotStatement.

                • LabelMatchStatement — (map)

                  A rule statement that defines a string match search against labels that have been added to the web request by rules that have already run in the web ACL.

                  The label match statement provides the label or namespace string to search for. The label string can represent a part or all of the fully qualified label name that had been added to the web request. Fully qualified labels have a prefix, optional namespaces, and label name. The prefix identifies the rule group or web ACL context of the rule that added the label. If you do not provide the fully qualified name in your label match string, WAF performs the search for labels that were added in the same context as the label match statement.

                  • Scope — required — (String)

                    Specify whether you want to match using the label name or just the namespace.

                    Possible values include:
                    • "LABEL"
                    • "NAMESPACE"
                  • Key — required — (String)

                    The string to match against. The setting you provide for this depends on the match statement's Scope setting:

                    • If the Scope indicates LABEL, then this specification must include the name and can include any number of preceding namespace specifications and prefix up to providing the fully qualified label name.

                    • If the Scope indicates NAMESPACE, then this specification can include any number of contiguous namespace strings, and can include the entire label namespace prefix from the rule group or web ACL where the label originates.

                    Labels are case sensitive and components of a label must be separated by colon, for example NS1:NS2:name.

                • RegexMatchStatement — (map)

                  A rule statement used to search web request components for a match against a single regular expression.

                  • RegexString — required — (String)

                    The string representing the regular expression.

                  • FieldToMatch — required — (map)

                    The part of a web request that you want WAF to inspect. For more information, see FieldToMatch.

                    • SingleHeader — (map)

                      Inspect a single header. Provide the name of the header to inspect, for example, User-Agent or Referer. This setting isn't case sensitive.

                      Example JSON: "SingleHeader": { "Name": "haystack" }

                      • Name — required — (String)

                        The name of the query header to inspect.

                    • SingleQueryArgument — (map)

                      Inspect a single query argument. Provide the name of the query argument to inspect, such as UserName or SalesRegion. The name can be up to 30 characters long and isn't case sensitive.

                      This is used only to indicate the web request component for WAF to inspect, in the FieldToMatch specification.

                      Example JSON: "SingleQueryArgument": { "Name": "myArgument" }

                      • Name — required — (String)

                        The name of the query argument to inspect.

                    • AllQueryArguments — (map)

                      Inspect all query arguments.

                    • UriPath — (map)

                      Inspect the request URI path. This is the part of a web request that identifies a resource, for example, /images/daily-ad.jpg.

                    • QueryString — (map)

                      Inspect the query string. This is the part of a URL that appears after a ? character, if any.

                    • Body — (map)

                      Inspect the request body as plain text. The request body immediately follows the request headers. This is the part of a request that contains any additional data that you want to send to your web server as the HTTP request body, such as data from a form.

                      Note that only the first 8 KB (8192 bytes) of the request body are forwarded to WAF for inspection by the underlying host service. If you don't need to inspect more than 8 KB, you can guarantee that you don't allow additional bytes in by combining a statement that inspects the body of the web request, such as ByteMatchStatement or RegexPatternSetReferenceStatement, with a SizeConstraintStatement that enforces an 8 KB size limit on the body of the request. WAF doesn't support inspecting the entire contents of web requests whose bodies exceed the 8 KB limit.

                    • Method — (map)

                      Inspect the HTTP method. The method indicates the type of operation that the request is asking the origin to perform.

                    • JsonBody — (map)

                      Inspect the request body as JSON. The request body immediately follows the request headers. This is the part of a request that contains any additional data that you want to send to your web server as the HTTP request body, such as data from a form.

                      Note that only the first 8 KB (8192 bytes) of the request body are forwarded to WAF for inspection by the underlying host service. If you don't need to inspect more than 8 KB, you can guarantee that you don't allow additional bytes in by combining a statement that inspects the body of the web request, such as ByteMatchStatement or RegexPatternSetReferenceStatement, with a SizeConstraintStatement that enforces an 8 KB size limit on the body of the request. WAF doesn't support inspecting the entire contents of web requests whose bodies exceed the 8 KB limit.

                      • MatchPattern — required — (map)

                        The patterns to look for in the JSON body. WAF inspects the results of these pattern matches against the rule inspection criteria.

                        • All — (map)

                          Match all of the elements. See also MatchScope in JsonBody.

                          You must specify either this setting or the IncludedPaths setting, but not both.

                        • IncludedPaths — (Array<String>)

                          Match only the specified include paths. See also MatchScope in JsonBody.

                          Provide the include paths using JSON Pointer syntax. For example, "IncludedPaths": ["/dogs/0/name", "/dogs/1/name"]. For information about this syntax, see the Internet Engineering Task Force (IETF) documentation JavaScript Object Notation (JSON) Pointer.

                          You must specify either this setting or the All setting, but not both.

                          Note: Don't use this option to include all paths. Instead, use the All setting.
                      • MatchScope — required — (String)

                        The parts of the JSON to match against using the MatchPattern. If you specify All, WAF matches against keys and values.

                        Possible values include:
                        • "ALL"
                        • "KEY"
                        • "VALUE"
                      • InvalidFallbackBehavior — (String)

                        What WAF should do if it fails to completely parse the JSON body. The options are the following:

                        • EVALUATE_AS_STRING - Inspect the body as plain text. WAF applies the text transformations and inspection criteria that you defined for the JSON inspection to the body text string.

                        • MATCH - Treat the web request as matching the rule statement. WAF applies the rule action to the request.

                        • NO_MATCH - Treat the web request as not matching the rule statement.

                        If you don't provide this setting, WAF parses and evaluates the content only up to the first parsing failure that it encounters.

                        WAF does its best to parse the entire JSON body, but might be forced to stop for reasons such as invalid characters, duplicate keys, truncation, and any content whose root node isn't an object or an array.

                        WAF parses the JSON in the following examples as two valid key, value pairs:

                        • Missing comma: {"key1":"value1""key2":"value2"}

                        • Missing colon: {"key1":"value1","key2""value2"}

                        • Extra colons: {"key1"::"value1","key2""value2"}

                        Possible values include:
                        • "MATCH"
                        • "NO_MATCH"
                        • "EVALUATE_AS_STRING"
                  • TextTransformations — required — (Array<map>)

                    Text transformations eliminate some of the unusual formatting that attackers use in web requests in an effort to bypass detection. If you specify one or more transformations in a rule statement, WAF performs all transformations on the content of the request component identified by FieldToMatch, starting from the lowest priority setting, before inspecting the content for a match.

                    • Priority — required — (Integer)

                      Sets the relative processing order for multiple transformations that are defined for a rule statement. WAF processes all transformations, from lowest priority to highest, before inspecting the transformed content. The priorities don't need to be consecutive, but they must all be different.

                    • Type — required — (String)

                      You can specify the following transformation types:

                      BASE64_DECODE - Decode a Base64-encoded string.

                      BASE64_DECODE_EXT - Decode a Base64-encoded string, but use a forgiving implementation that ignores characters that aren't valid.

                      CMD_LINE - Command-line transformations. These are helpful in reducing effectiveness of attackers who inject an operating system command-line command and use unusual formatting to disguise some or all of the command.

                      • Delete the following characters: \ " ' ^

                      • Delete spaces before the following characters: / (

                      • Replace the following characters with a space: , ;

                      • Replace multiple spaces with one space

                      • Convert uppercase letters (A-Z) to lowercase (a-z)

                      COMPRESS_WHITE_SPACE - Replace these characters with a space character (decimal 32):

                      • \f, formfeed, decimal 12

                      • \t, tab, decimal 9

                      • \n, newline, decimal 10

                      • \r, carriage return, decimal 13

                      • \v, vertical tab, decimal 11

                      • Non-breaking space, decimal 160

                      COMPRESS_WHITE_SPACE also replaces multiple spaces with one space.

                      CSS_DECODE - Decode characters that were encoded using CSS 2.x escape rules syndata.html#characters. This function uses up to two bytes in the decoding process, so it can help to uncover ASCII characters that were encoded using CSS encoding that wouldn’t typically be encoded. It's also useful in countering evasion, which is a combination of a backslash and non-hexadecimal characters. For example, ja\vascript for javascript.

                      ESCAPE_SEQ_DECODE - Decode the following ANSI C escape sequences: \a, \b, \f, \n, \r, \t, \v, \, \?, \', \", \xHH (hexadecimal), \0OOO (octal). Encodings that aren't valid remain in the output.

                      HEX_DECODE - Decode a string of hexadecimal characters into a binary.

                      HTML_ENTITY_DECODE - Replace HTML-encoded characters with unencoded characters. HTML_ENTITY_DECODE performs these operations:

                      • Replaces (ampersand)quot; with "

                      • Replaces (ampersand)nbsp; with a non-breaking space, decimal 160

                      • Replaces (ampersand)lt; with a "less than" symbol

                      • Replaces (ampersand)gt; with >

                      • Replaces characters that are represented in hexadecimal format, (ampersand)#xhhhh;, with the corresponding characters

                      • Replaces characters that are represented in decimal format, (ampersand)#nnnn;, with the corresponding characters

                      JS_DECODE - Decode JavaScript escape sequences. If a \ u HHHH code is in the full-width ASCII code range of FF01-FF5E, then the higher byte is used to detect and adjust the lower byte. If not, only the lower byte is used and the higher byte is zeroed, causing a possible loss of information.

                      LOWERCASE - Convert uppercase letters (A-Z) to lowercase (a-z).

                      MD5 - Calculate an MD5 hash from the data in the input. The computed hash is in a raw binary form.

                      NONE - Specify NONE if you don't want any text transformations.

                      NORMALIZE_PATH - Remove multiple slashes, directory self-references, and directory back-references that are not at the beginning of the input from an input string.

                      NORMALIZE_PATH_WIN - This is the same as NORMALIZE_PATH, but first converts backslash characters to forward slashes.

                      REMOVE_NULLS - Remove all NULL bytes from the input.

                      REPLACE_COMMENTS - Replace each occurrence of a C-style comment (/* ... */) with a single space. Multiple consecutive occurrences are not compressed. Unterminated comments are also replaced with a space (ASCII 0x20). However, a standalone termination of a comment (*/) is not acted upon.

                      REPLACE_NULLS - Replace NULL bytes in the input with space characters (ASCII 0x20).

                      SQL_HEX_DECODE - Decode SQL hex data. Example (0x414243) will be decoded to (ABC).

                      URL_DECODE - Decode a URL-encoded value.

                      URL_DECODE_UNI - Like URL_DECODE, but with support for Microsoft-specific %u encoding. If the code is in the full-width ASCII code range of FF01-FF5E, the higher byte is used to detect and adjust the lower byte. Otherwise, only the lower byte is used and the higher byte is zeroed.

                      UTF8_TO_UNICODE - Convert all UTF-8 character sequences to Unicode. This helps input normalization, and minimizing false-positives and false-negatives for non-English languages.

                      Possible values include:
                      • "NONE"
                      • "COMPRESS_WHITE_SPACE"
                      • "HTML_ENTITY_DECODE"
                      • "LOWERCASE"
                      • "CMD_LINE"
                      • "URL_DECODE"
                      • "BASE64_DECODE"
                      • "HEX_DECODE"
                      • "MD5"
                      • "REPLACE_COMMENTS"
                      • "ESCAPE_SEQ_DECODE"
                      • "SQL_HEX_DECODE"
                      • "CSS_DECODE"
                      • "JS_DECODE"
                      • "NORMALIZE_PATH"
                      • "NORMALIZE_PATH_WIN"
                      • "REMOVE_NULLS"
                      • "REPLACE_NULLS"
                      • "BASE64_DECODE_EXT"
                      • "URL_DECODE_UNI"
                      • "UTF8_TO_UNICODE"
            • RuleGroupReferenceStatement — (map)

              A rule statement used to run the rules that are defined in a RuleGroup. To use this, create a rule group with your rules, then provide the ARN of the rule group in this statement.

              You cannot nest a RuleGroupReferenceStatement, for example for use inside a NotStatement or OrStatement. You can only use a rule group reference statement at the top level inside a web ACL.

              • ARN — required — (String)

                The Amazon Resource Name (ARN) of the entity.

              • ExcludedRules — (Array<map>)

                The rules in the referenced rule group whose actions are set to Count. When you exclude a rule, WAF evaluates it exactly as it would if the rule action setting were Count. This is a useful option for testing the rules in a rule group without modifying how they handle your web traffic.

                • Name — required — (String)

                  The name of the rule whose action you want to override to Count.

          • OverrideAction — required — (map)

            The action to use in the place of the action that results from the rule group evaluation. Set the override action to none to leave the result of the rule group alone. Set it to count to override the result to count only.

            You can only use this for rule statements that reference a rule group, like RuleGroupReferenceStatement and ManagedRuleGroupStatement.

            Note: This option is usually set to none. It does not affect how the rules in the rule group are evaluated. If you want the rules in the rule group to only count matches, do not use this and instead exclude those rules in your rule group reference statement settings.
            • Count — (map)

              Override the rule group evaluation result to count only.

              Note: This option is usually set to none. It does not affect how the rules in the rule group are evaluated. If you want the rules in the rule group to only count matches, do not use this and instead exclude those rules in your rule group reference statement settings.
              • CustomRequestHandling — (map)

                Defines custom handling for the web request.

                For information about customizing web requests and responses, see Customizing web requests and responses in WAF in the WAF Developer Guide.

                • InsertHeaders — required — (Array<map>)

                  The HTTP headers to insert into the request. Duplicate header names are not allowed.

                  For information about the limits on count and size for custom request and response settings, see WAF quotas in the WAF Developer Guide.

                  • Name — required — (String)

                    The name of the custom header.

                    For custom request header insertion, when WAF inserts the header into the request, it prefixes this name x-amzn-waf-, to avoid confusion with the headers that are already in the request. For example, for the header name sample, WAF inserts the header x-amzn-waf-sample.

                  • Value — required — (String)

                    The value of the custom header.

            • None — (map)

              Don't override the rule group evaluation result. This is the most common setting.

          • VisibilityConfig — required — (map)

            Defines and enables Amazon CloudWatch metrics and web request sample collection.

            • SampledRequestsEnabled — required — (Boolean)

              A boolean indicating whether WAF should store a sampling of the web requests that match the rules. You can view the sampled requests through the WAF console.

            • CloudWatchMetricsEnabled — required — (Boolean)

              A boolean indicating whether the associated resource sends metrics to Amazon CloudWatch. For the list of available metrics, see WAF Metrics.

            • MetricName — required — (String)

              A name of the Amazon CloudWatch metric. The name can contain only the characters: A-Z, a-z, 0-9, - (hyphen), and _ (underscore). The name can be from one to 128 characters long. It can't contain whitespace or metric names reserved for WAF, for example "All" and "Default_Action."

        • ManagedByFirewallManager — (Boolean)

          Indicates whether this web ACL is managed by Firewall Manager. If true, then only Firewall Manager can delete the web ACL or any Firewall Manager rule groups in the web ACL.

        • LabelNamespace — (String)

          The label namespace prefix for this web ACL. All labels added by rules in this web ACL have this prefix.

          • The syntax for the label namespace prefix for a web ACL is the following:

            awswaf:<account ID>:webacl:<web ACL name>:

          • When a rule with a label matches a web request, WAF adds the fully qualified label to the request. A fully qualified label is made up of the label namespace from the rule group or web ACL where the rule is defined and the label from the rule, separated by a colon:

            <label namespace>:<label from rule>

        • CustomResponseBodies — (map<map>)

          A map of custom response keys and content bodies. When you create a rule with a block action, you can send a custom response to the web request. You define these for the web ACL, and then use them in the rules and default actions that you define in the web ACL.

          For information about customizing web requests and responses, see Customizing web requests and responses in WAF in the WAF Developer Guide.

          For information about the limits on count and size for custom request and response settings, see WAF quotas in the WAF Developer Guide.

          • ContentType — required — (String)

            The type of content in the payload that you are defining in the Content string.

            Possible values include:
            • "TEXT_PLAIN"
            • "TEXT_HTML"
            • "APPLICATION_JSON"
          • Content — required — (String)

            The payload of the custom response.

            You can use JSON escape strings in JSON content. To do this, you must specify JSON content in the ContentType setting.

            For information about the limits on count and size for custom request and response settings, see WAF quotas in the WAF Developer Guide.

        • CaptchaConfig — (map)

          Specifies how WAF should handle CAPTCHA evaluations for rules that don't have their own CaptchaConfig settings. If you don't specify this, WAF uses its default settings for CaptchaConfig.

          • ImmunityTimeProperty — (map)

            Determines how long a CAPTCHA token remains valid after the client successfully solves a CAPTCHA puzzle.

            • ImmunityTime — required — (Integer)

              The amount of time, in seconds, that a CAPTCHA token is valid. The default setting is 300.

Returns:

  • (AWS.Request) —

    a handle to the operation request for subsequent event callback registration.

listAvailableManagedRuleGroups(params = {}, callback) ⇒ AWS.Request

Retrieves an array of managed rule groups that are available for you to use. This list includes all Amazon Web Services Managed Rules rule groups and all of the Amazon Web Services Marketplace managed rule groups that you're subscribed to.

Service Reference:

Examples:

Calling the listAvailableManagedRuleGroups operation

var params = {
  Scope: CLOUDFRONT | REGIONAL, /* required */
  Limit: 'NUMBER_VALUE',
  NextMarker: 'STRING_VALUE'
};
wafv2.listAvailableManagedRuleGroups(params, function(err, data) {
  if (err) console.log(err, err.stack); // an error occurred
  else     console.log(data);           // successful response
});

Parameters:

  • params (Object) (defaults to: {}) —
    • Scope — (String)

      Specifies whether this is for an Amazon CloudFront distribution or for a regional application. A regional application can be an Application Load Balancer (ALB), an Amazon API Gateway REST API, or an AppSync GraphQL API.

      To work with CloudFront, you must also specify the Region US East (N. Virginia) as follows:

      • CLI - Specify the Region when you use the CloudFront scope: --scope=CLOUDFRONT --region=us-east-1.

      • API and SDKs - For all calls, use the Region endpoint us-east-1.

      Possible values include:
      • "CLOUDFRONT"
      • "REGIONAL"
    • NextMarker — (String)

      When you request a list of objects with a Limit setting, if the number of objects that are still available for retrieval exceeds the limit, WAF returns a NextMarker value in the response. To retrieve the next batch of objects, provide the marker from the prior call in your next request.

    • Limit — (Integer)

      The maximum number of objects that you want WAF to return for this request. If more objects are available, in the response, WAF provides a NextMarker value that you can use in a subsequent call to get the next batch of objects.

Callback (callback):

  • function(err, data) { ... }

    Called when a response from the service is returned. If a callback is not supplied, you must call AWS.Request.send() on the returned request object to initiate the request.

    Context (this):

    • (AWS.Response) —

      the response object containing error, data properties, and the original request object.

    Parameters:

    • err (Error) —

      the error object returned from the request. Set to null if the request is successful.

    • data (Object) —

      the de-serialized data returned from the request. Set to null if a request error occurs. The data object has the following properties:

      • NextMarker — (String)

        When you request a list of objects with a Limit setting, if the number of objects that are still available for retrieval exceeds the limit, WAF returns a NextMarker value in the response. To retrieve the next batch of objects, provide the marker from the prior call in your next request.

      • ManagedRuleGroups — (Array<map>)

        • VendorName — (String)

          The name of the managed rule group vendor. You use this, along with the rule group name, to identify the rule group.

        • Name — (String)

          The name of the managed rule group. You use this, along with the vendor name, to identify the rule group.

        • Description — (String)

          The description of the managed rule group, provided by Amazon Web Services Managed Rules or the Amazon Web Services Marketplace seller who manages it.

Returns:

  • (AWS.Request) —

    a handle to the operation request for subsequent event callback registration.

listAvailableManagedRuleGroupVersions(params = {}, callback) ⇒ AWS.Request

Returns a list of the available versions for the specified managed rule group.

Service Reference:

Examples:

Calling the listAvailableManagedRuleGroupVersions operation

var params = {
  Name: 'STRING_VALUE', /* required */
  Scope: CLOUDFRONT | REGIONAL, /* required */
  VendorName: 'STRING_VALUE', /* required */
  Limit: 'NUMBER_VALUE',
  NextMarker: 'STRING_VALUE'
};
wafv2.listAvailableManagedRuleGroupVersions(params, function(err, data) {
  if (err) console.log(err, err.stack); // an error occurred
  else     console.log(data);           // successful response
});

Parameters:

  • params (Object) (defaults to: {}) —
    • VendorName — (String)

      The name of the managed rule group vendor. You use this, along with the rule group name, to identify the rule group.

    • Name — (String)

      The name of the managed rule group. You use this, along with the vendor name, to identify the rule group.

    • Scope — (String)

      Specifies whether this is for an Amazon CloudFront distribution or for a regional application. A regional application can be an Application Load Balancer (ALB), an Amazon API Gateway REST API, or an AppSync GraphQL API.

      To work with CloudFront, you must also specify the Region US East (N. Virginia) as follows:

      • CLI - Specify the Region when you use the CloudFront scope: --scope=CLOUDFRONT --region=us-east-1.

      • API and SDKs - For all calls, use the Region endpoint us-east-1.

      Possible values include:
      • "CLOUDFRONT"
      • "REGIONAL"
    • NextMarker — (String)

      When you request a list of objects with a Limit setting, if the number of objects that are still available for retrieval exceeds the limit, WAF returns a NextMarker value in the response. To retrieve the next batch of objects, provide the marker from the prior call in your next request.

    • Limit — (Integer)

      The maximum number of objects that you want WAF to return for this request. If more objects are available, in the response, WAF provides a NextMarker value that you can use in a subsequent call to get the next batch of objects.

Callback (callback):

  • function(err, data) { ... }

    Called when a response from the service is returned. If a callback is not supplied, you must call AWS.Request.send() on the returned request object to initiate the request.

    Context (this):

    • (AWS.Response) —

      the response object containing error, data properties, and the original request object.

    Parameters:

    • err (Error) —

      the error object returned from the request. Set to null if the request is successful.

    • data (Object) —

      the de-serialized data returned from the request. Set to null if a request error occurs. The data object has the following properties:

      • NextMarker — (String)

        When you request a list of objects with a Limit setting, if the number of objects that are still available for retrieval exceeds the limit, WAF returns a NextMarker value in the response. To retrieve the next batch of objects, provide the marker from the prior call in your next request.

      • Versions — (Array<map>)

        The versions that are currently available for the specified managed rule group.

        • Name — (String)

          The version name.

        • LastUpdateTimestamp — (Date)

          The date and time that the managed rule group owner updated the rule group version information.

Returns:

  • (AWS.Request) —

    a handle to the operation request for subsequent event callback registration.

listIPSets(params = {}, callback) ⇒ AWS.Request

Retrieves an array of IPSetSummary objects for the IP sets that you manage.

Service Reference:

Examples:

Calling the listIPSets operation

var params = {
  Scope: CLOUDFRONT | REGIONAL, /* required */
  Limit: 'NUMBER_VALUE',
  NextMarker: 'STRING_VALUE'
};
wafv2.listIPSets(params, function(err, data) {
  if (err) console.log(err, err.stack); // an error occurred
  else     console.log(data);           // successful response
});

Parameters:

  • params (Object) (defaults to: {}) —
    • Scope — (String)

      Specifies whether this is for an Amazon CloudFront distribution or for a regional application. A regional application can be an Application Load Balancer (ALB), an Amazon API Gateway REST API, or an AppSync GraphQL API.

      To work with CloudFront, you must also specify the Region US East (N. Virginia) as follows:

      • CLI - Specify the Region when you use the CloudFront scope: --scope=CLOUDFRONT --region=us-east-1.

      • API and SDKs - For all calls, use the Region endpoint us-east-1.

      Possible values include:
      • "CLOUDFRONT"
      • "REGIONAL"
    • NextMarker — (String)

      When you request a list of objects with a Limit setting, if the number of objects that are still available for retrieval exceeds the limit, WAF returns a NextMarker value in the response. To retrieve the next batch of objects, provide the marker from the prior call in your next request.

    • Limit — (Integer)

      The maximum number of objects that you want WAF to return for this request. If more objects are available, in the response, WAF provides a NextMarker value that you can use in a subsequent call to get the next batch of objects.

Callback (callback):

  • function(err, data) { ... }

    Called when a response from the service is returned. If a callback is not supplied, you must call AWS.Request.send() on the returned request object to initiate the request.

    Context (this):

    • (AWS.Response) —

      the response object containing error, data properties, and the original request object.

    Parameters:

    • err (Error) —

      the error object returned from the request. Set to null if the request is successful.

    • data (Object) —

      the de-serialized data returned from the request. Set to null if a request error occurs. The data object has the following properties:

      • NextMarker — (String)

        When you request a list of objects with a Limit setting, if the number of objects that are still available for retrieval exceeds the limit, WAF returns a NextMarker value in the response. To retrieve the next batch of objects, provide the marker from the prior call in your next request.

      • IPSets — (Array<map>)

        Array of IPSets. This may not be the full list of IPSets that you have defined. See the Limit specification for this request.

        • Name — (String)

          The name of the IP set. You cannot change the name of an IPSet after you create it.

        • Id — (String)

          A unique identifier for the set. This ID is returned in the responses to create and list commands. You provide it to operations like update and delete.

        • Description — (String)

          A description of the IP set that helps with identification.

        • LockToken — (String)

          A token used for optimistic locking. WAF returns a token to your get and list requests, to mark the state of the entity at the time of the request. To make changes to the entity associated with the token, you provide the token to operations like update and delete. WAF uses the token to ensure that no changes have been made to the entity since you last retrieved it. If a change has been made, the update fails with a WAFOptimisticLockException. If this happens, perform another get, and use the new token returned by that operation.

        • ARN — (String)

          The Amazon Resource Name (ARN) of the entity.

Returns:

  • (AWS.Request) —

    a handle to the operation request for subsequent event callback registration.

listLoggingConfigurations(params = {}, callback) ⇒ AWS.Request

Retrieves an array of your LoggingConfiguration objects.

Service Reference:

Examples:

Calling the listLoggingConfigurations operation

var params = {
  Scope: CLOUDFRONT | REGIONAL, /* required */
  Limit: 'NUMBER_VALUE',
  NextMarker: 'STRING_VALUE'
};
wafv2.listLoggingConfigurations(params, function(err, data) {
  if (err) console.log(err, err.stack); // an error occurred
  else     console.log(data);           // successful response
});

Parameters:

  • params (Object) (defaults to: {}) —
    • Scope — (String)

      Specifies whether this is for an Amazon CloudFront distribution or for a regional application. A regional application can be an Application Load Balancer (ALB), an Amazon API Gateway REST API, or an AppSync GraphQL API.

      To work with CloudFront, you must also specify the Region US East (N. Virginia) as follows:

      • CLI - Specify the Region when you use the CloudFront scope: --scope=CLOUDFRONT --region=us-east-1.

      • API and SDKs - For all calls, use the Region endpoint us-east-1.

      Possible values include:
      • "CLOUDFRONT"
      • "REGIONAL"
    • NextMarker — (String)

      When you request a list of objects with a Limit setting, if the number of objects that are still available for retrieval exceeds the limit, WAF returns a NextMarker value in the response. To retrieve the next batch of objects, provide the marker from the prior call in your next request.

    • Limit — (Integer)

      The maximum number of objects that you want WAF to return for this request. If more objects are available, in the response, WAF provides a NextMarker value that you can use in a subsequent call to get the next batch of objects.

Callback (callback):

  • function(err, data) { ... }

    Called when a response from the service is returned. If a callback is not supplied, you must call AWS.Request.send() on the returned request object to initiate the request.

    Context (this):

    • (AWS.Response) —

      the response object containing error, data properties, and the original request object.

    Parameters:

    • err (Error) —

      the error object returned from the request. Set to null if the request is successful.

    • data (Object) —

      the de-serialized data returned from the request. Set to null if a request error occurs. The data object has the following properties:

      • LoggingConfigurations — (Array<map>)

        • ResourceArn — required — (String)

          The Amazon Resource Name (ARN) of the web ACL that you want to associate with LogDestinationConfigs.

        • LogDestinationConfigs — required — (Array<String>)

          The Amazon Kinesis Data Firehose Amazon Resource Name (ARNs) that you want to associate with the web ACL.

        • RedactedFields — (Array<map>)

          The parts of the request that you want to keep out of the logs. For example, if you redact the SingleHeader field, the HEADER field in the firehose will be xxx.

          Note: You can specify only the following fields for redaction: UriPath, QueryString, SingleHeader, Method, and JsonBody.
          • SingleHeader — (map)

            Inspect a single header. Provide the name of the header to inspect, for example, User-Agent or Referer. This setting isn't case sensitive.

            Example JSON: "SingleHeader": { "Name": "haystack" }

            • Name — required — (String)

              The name of the query header to inspect.

          • SingleQueryArgument — (map)

            Inspect a single query argument. Provide the name of the query argument to inspect, such as UserName or SalesRegion. The name can be up to 30 characters long and isn't case sensitive.

            This is used only to indicate the web request component for WAF to inspect, in the FieldToMatch specification.

            Example JSON: "SingleQueryArgument": { "Name": "myArgument" }

            • Name — required — (String)

              The name of the query argument to inspect.

          • AllQueryArguments — (map)

            Inspect all query arguments.

          • UriPath — (map)

            Inspect the request URI path. This is the part of a web request that identifies a resource, for example, /images/daily-ad.jpg.

          • QueryString — (map)

            Inspect the query string. This is the part of a URL that appears after a ? character, if any.

          • Body — (map)

            Inspect the request body as plain text. The request body immediately follows the request headers. This is the part of a request that contains any additional data that you want to send to your web server as the HTTP request body, such as data from a form.

            Note that only the first 8 KB (8192 bytes) of the request body are forwarded to WAF for inspection by the underlying host service. If you don't need to inspect more than 8 KB, you can guarantee that you don't allow additional bytes in by combining a statement that inspects the body of the web request, such as ByteMatchStatement or RegexPatternSetReferenceStatement, with a SizeConstraintStatement that enforces an 8 KB size limit on the body of the request. WAF doesn't support inspecting the entire contents of web requests whose bodies exceed the 8 KB limit.

          • Method — (map)

            Inspect the HTTP method. The method indicates the type of operation that the request is asking the origin to perform.

          • JsonBody — (map)

            Inspect the request body as JSON. The request body immediately follows the request headers. This is the part of a request that contains any additional data that you want to send to your web server as the HTTP request body, such as data from a form.

            Note that only the first 8 KB (8192 bytes) of the request body are forwarded to WAF for inspection by the underlying host service. If you don't need to inspect more than 8 KB, you can guarantee that you don't allow additional bytes in by combining a statement that inspects the body of the web request, such as ByteMatchStatement or RegexPatternSetReferenceStatement, with a SizeConstraintStatement that enforces an 8 KB size limit on the body of the request. WAF doesn't support inspecting the entire contents of web requests whose bodies exceed the 8 KB limit.

            • MatchPattern — required — (map)

              The patterns to look for in the JSON body. WAF inspects the results of these pattern matches against the rule inspection criteria.

              • All — (map)

                Match all of the elements. See also MatchScope in JsonBody.

                You must specify either this setting or the IncludedPaths setting, but not both.

              • IncludedPaths — (Array<String>)

                Match only the specified include paths. See also MatchScope in JsonBody.

                Provide the include paths using JSON Pointer syntax. For example, "IncludedPaths": ["/dogs/0/name", "/dogs/1/name"]. For information about this syntax, see the Internet Engineering Task Force (IETF) documentation JavaScript Object Notation (JSON) Pointer.

                You must specify either this setting or the All setting, but not both.

                Note: Don't use this option to include all paths. Instead, use the All setting.
            • MatchScope — required — (String)

              The parts of the JSON to match against using the MatchPattern. If you specify All, WAF matches against keys and values.

              Possible values include:
              • "ALL"
              • "KEY"
              • "VALUE"
            • InvalidFallbackBehavior — (String)

              What WAF should do if it fails to completely parse the JSON body. The options are the following:

              • EVALUATE_AS_STRING - Inspect the body as plain text. WAF applies the text transformations and inspection criteria that you defined for the JSON inspection to the body text string.

              • MATCH - Treat the web request as matching the rule statement. WAF applies the rule action to the request.

              • NO_MATCH - Treat the web request as not matching the rule statement.

              If you don't provide this setting, WAF parses and evaluates the content only up to the first parsing failure that it encounters.

              WAF does its best to parse the entire JSON body, but might be forced to stop for reasons such as invalid characters, duplicate keys, truncation, and any content whose root node isn't an object or an array.

              WAF parses the JSON in the following examples as two valid key, value pairs:

              • Missing comma: {"key1":"value1""key2":"value2"}

              • Missing colon: {"key1":"value1","key2""value2"}

              • Extra colons: {"key1"::"value1","key2""value2"}

              Possible values include:
              • "MATCH"
              • "NO_MATCH"
              • "EVALUATE_AS_STRING"
        • ManagedByFirewallManager — (Boolean)

          Indicates whether the logging configuration was created by Firewall Manager, as part of an WAF policy configuration. If true, only Firewall Manager can modify or delete the configuration.

        • LoggingFilter — (map)

          Filtering that specifies which web requests are kept in the logs and which are dropped. You can filter on the rule action and on the web request labels that were applied by matching rules during web ACL evaluation.

          • Filters — required — (Array<map>)

            The filters that you want to apply to the logs.

            • Behavior — required — (String)

              How to handle logs that satisfy the filter's conditions and requirement.

              Possible values include:
              • "KEEP"
              • "DROP"
            • Requirement — required — (String)

              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.

              Possible values include:
              • "MEETS_ALL"
              • "MEETS_ANY"
            • Conditions — required — (Array<map>)

              Match conditions for the filter.

              • ActionCondition — (map)

                A single action condition.

                • Action — required — (String)

                  The action setting that a log record must contain in order to meet the condition.

                  Possible values include:
                  • "ALLOW"
                  • "BLOCK"
                  • "COUNT"
                  • "CAPTCHA"
                  • "EXCLUDED_AS_COUNT"
              • LabelNameCondition — (map)

                A single label name condition.

                • LabelName — required — (String)

                  The label name that a log record must contain in order to meet the condition. This must be a fully qualified label name. Fully qualified labels have a prefix, optional namespaces, and label name. The prefix identifies the rule group or web ACL context of the rule that added the label.

          • DefaultBehavior — required — (String)

            Default handling for logs that don't match any of the specified filtering conditions.

            Possible values include:
            • "KEEP"
            • "DROP"
      • NextMarker — (String)

        When you request a list of objects with a Limit setting, if the number of objects that are still available for retrieval exceeds the limit, WAF returns a NextMarker value in the response. To retrieve the next batch of objects, provide the marker from the prior call in your next request.

Returns:

  • (AWS.Request) —

    a handle to the operation request for subsequent event callback registration.

listManagedRuleSets(params = {}, callback) ⇒ AWS.Request

Retrieves the managed rule sets that you own.

Note: This is intended for use only by vendors of managed rule sets. Vendors are Amazon Web Services and Amazon Web Services Marketplace sellers. Vendors, you can use the managed rule set APIs to provide controlled rollout of your versioned managed rule group offerings for your customers. The APIs are ListManagedRuleSets, GetManagedRuleSet, PutManagedRuleSetVersions, and UpdateManagedRuleSetVersionExpiryDate.

Service Reference:

Examples:

Calling the listManagedRuleSets operation

var params = {
  Scope: CLOUDFRONT | REGIONAL, /* required */
  Limit: 'NUMBER_VALUE',
  NextMarker: 'STRING_VALUE'
};
wafv2.listManagedRuleSets(params, function(err, data) {
  if (err) console.log(err, err.stack); // an error occurred
  else     console.log(data);           // successful response
});

Parameters:

  • params (Object) (defaults to: {}) —
    • Scope — (String)

      Specifies whether this is for an Amazon CloudFront distribution or for a regional application. A regional application can be an Application Load Balancer (ALB), an Amazon API Gateway REST API, or an AppSync GraphQL API.

      To work with CloudFront, you must also specify the Region US East (N. Virginia) as follows:

      • CLI - Specify the Region when you use the CloudFront scope: --scope=CLOUDFRONT --region=us-east-1.

      • API and SDKs - For all calls, use the Region endpoint us-east-1.

      Possible values include:
      • "CLOUDFRONT"
      • "REGIONAL"
    • NextMarker — (String)

      When you request a list of objects with a Limit setting, if the number of objects that are still available for retrieval exceeds the limit, WAF returns a NextMarker value in the response. To retrieve the next batch of objects, provide the marker from the prior call in your next request.

    • Limit — (Integer)

      The maximum number of objects that you want WAF to return for this request. If more objects are available, in the response, WAF provides a NextMarker value that you can use in a subsequent call to get the next batch of objects.

Callback (callback):

  • function(err, data) { ... }

    Called when a response from the service is returned. If a callback is not supplied, you must call AWS.Request.send() on the returned request object to initiate the request.

    Context (this):

    • (AWS.Response) —

      the response object containing error, data properties, and the original request object.

    Parameters:

    • err (Error) —

      the error object returned from the request. Set to null if the request is successful.

    • data (Object) —

      the de-serialized data returned from the request. Set to null if a request error occurs. The data object has the following properties:

      • NextMarker — (String)

        When you request a list of objects with a Limit setting, if the number of objects that are still available for retrieval exceeds the limit, WAF returns a NextMarker value in the response. To retrieve the next batch of objects, provide the marker from the prior call in your next request.

      • ManagedRuleSets — (Array<map>)

        Your managed rule sets.

        • Name — (String)

          The name of the managed rule set. You use this, along with the rule set ID, to identify the rule set.

          This name is assigned to the corresponding managed rule group, which your customers can access and use.

        • Id — (String)

          A unique identifier for the managed rule set. The ID is returned in the responses to commands like list. You provide it to operations like get and update.

        • Description — (String)

          A description of the set that helps with identification.

        • LockToken — (String)

          A token used for optimistic locking. WAF returns a token to your get and list requests, to mark the state of the entity at the time of the request. To make changes to the entity associated with the token, you provide the token to operations like update and delete. WAF uses the token to ensure that no changes have been made to the entity since you last retrieved it. If a change has been made, the update fails with a WAFOptimisticLockException. If this happens, perform another get, and use the new token returned by that operation.

        • ARN — (String)

          The Amazon Resource Name (ARN) of the entity.

        • LabelNamespace — (String)

          The label namespace prefix for the managed rule groups that are offered to customers from this managed rule set. All labels that are added by rules in the managed rule group have this prefix.

          • The syntax for the label namespace prefix for a managed rule group is the following:

            awswaf:managed:<vendor>:<rule group name>:

          • When a rule with a label matches a web request, WAF adds the fully qualified label to the request. A fully qualified label is made up of the label namespace from the rule group or web ACL where the rule is defined and the label from the rule, separated by a colon:

            <label namespace>:<label from rule>

Returns:

  • (AWS.Request) —

    a handle to the operation request for subsequent event callback registration.

listRegexPatternSets(params = {}, callback) ⇒ AWS.Request

Retrieves an array of RegexPatternSetSummary objects for the regex pattern sets that you manage.

Service Reference:

Examples:

Calling the listRegexPatternSets operation

var params = {
  Scope: CLOUDFRONT | REGIONAL, /* required */
  Limit: 'NUMBER_VALUE',
  NextMarker: 'STRING_VALUE'
};
wafv2.listRegexPatternSets(params, function(err, data) {
  if (err) console.log(err, err.stack); // an error occurred
  else     console.log(data);           // successful response
});

Parameters:

  • params (Object) (defaults to: {}) —
    • Scope — (String)

      Specifies whether this is for an Amazon CloudFront distribution or for a regional application. A regional application can be an Application Load Balancer (ALB), an Amazon API Gateway REST API, or an AppSync GraphQL API.

      To work with CloudFront, you must also specify the Region US East (N. Virginia) as follows:

      • CLI - Specify the Region when you use the CloudFront scope: --scope=CLOUDFRONT --region=us-east-1.

      • API and SDKs - For all calls, use the Region endpoint us-east-1.

      Possible values include:
      • "CLOUDFRONT"
      • "REGIONAL"
    • NextMarker — (String)

      When you request a list of objects with a Limit setting, if the number of objects that are still available for retrieval exceeds the limit, WAF returns a NextMarker value in the response. To retrieve the next batch of objects, provide the marker from the prior call in your next request.

    • Limit — (Integer)

      The maximum number of objects that you want WAF to return for this request. If more objects are available, in the response, WAF provides a NextMarker value that you can use in a subsequent call to get the next batch of objects.

Callback (callback):

  • function(err, data) { ... }

    Called when a response from the service is returned. If a callback is not supplied, you must call AWS.Request.send() on the returned request object to initiate the request.

    Context (this):

    • (AWS.Response) —

      the response object containing error, data properties, and the original request object.

    Parameters:

    • err (Error) —

      the error object returned from the request. Set to null if the request is successful.

    • data (Object) —

      the de-serialized data returned from the request. Set to null if a request error occurs. The data object has the following properties:

      • NextMarker — (String)

        When you request a list of objects with a Limit setting, if the number of objects that are still available for retrieval exceeds the limit, WAF returns a NextMarker value in the response. To retrieve the next batch of objects, provide the marker from the prior call in your next request.

      • RegexPatternSets — (Array<map>)

        • Name — (String)

          The name of the data type instance. You cannot change the name after you create the instance.

        • Id — (String)

          A unique identifier for the set. This ID is returned in the responses to create and list commands. You provide it to operations like update and delete.

        • Description — (String)

          A description of the set that helps with identification.

        • LockToken — (String)

          A token used for optimistic locking. WAF returns a token to your get and list requests, to mark the state of the entity at the time of the request. To make changes to the entity associated with the token, you provide the token to operations like update and delete. WAF uses the token to ensure that no changes have been made to the entity since you last retrieved it. If a change has been made, the update fails with a WAFOptimisticLockException. If this happens, perform another get, and use the new token returned by that operation.

        • ARN — (String)

          The Amazon Resource Name (ARN) of the entity.

Returns:

  • (AWS.Request) —

    a handle to the operation request for subsequent event callback registration.

listResourcesForWebACL(params = {}, callback) ⇒ AWS.Request

Retrieves an array of the Amazon Resource Names (ARNs) for the regional resources that are associated with the specified web ACL. If you want the list of Amazon CloudFront resources, use the CloudFront call ListDistributionsByWebACLId.

Service Reference:

Examples:

Calling the listResourcesForWebACL operation

var params = {
  WebACLArn: 'STRING_VALUE', /* required */
  ResourceType: APPLICATION_LOAD_BALANCER | API_GATEWAY | APPSYNC
};
wafv2.listResourcesForWebACL(params, function(err, data) {
  if (err) console.log(err, err.stack); // an error occurred
  else     console.log(data);           // successful response
});

Parameters:

  • params (Object) (defaults to: {}) —
    • WebACLArn — (String)

      The Amazon Resource Name (ARN) of the web ACL.

    • ResourceType — (String)

      Used for web ACLs that are scoped for regional applications. A regional application can be an Application Load Balancer (ALB), an Amazon API Gateway REST API, or an AppSync GraphQL API.

      Possible values include:
      • "APPLICATION_LOAD_BALANCER"
      • "API_GATEWAY"
      • "APPSYNC"

Callback (callback):

  • function(err, data) { ... }

    Called when a response from the service is returned. If a callback is not supplied, you must call AWS.Request.send() on the returned request object to initiate the request.

    Context (this):

    • (AWS.Response) —

      the response object containing error, data properties, and the original request object.

    Parameters:

    • err (Error) —

      the error object returned from the request. Set to null if the request is successful.

    • data (Object) —

      the de-serialized data returned from the request. Set to null if a request error occurs. The data object has the following properties:

      • ResourceArns — (Array<String>)

        The array of Amazon Resource Names (ARNs) of the associated resources.

Returns:

  • (AWS.Request) —

    a handle to the operation request for subsequent event callback registration.

listRuleGroups(params = {}, callback) ⇒ AWS.Request

Retrieves an array of RuleGroupSummary objects for the rule groups that you manage.

Service Reference:

Examples:

Calling the listRuleGroups operation

var params = {
  Scope: CLOUDFRONT | REGIONAL, /* required */
  Limit: 'NUMBER_VALUE',
  NextMarker: 'STRING_VALUE'
};
wafv2.listRuleGroups(params, function(err, data) {
  if (err) console.log(err, err.stack); // an error occurred
  else     console.log(data);           // successful response
});

Parameters:

  • params (Object) (defaults to: {}) —
    • Scope — (String)

      Specifies whether this is for an Amazon CloudFront distribution or for a regional application. A regional application can be an Application Load Balancer (ALB), an Amazon API Gateway REST API, or an AppSync GraphQL API.

      To work with CloudFront, you must also specify the Region US East (N. Virginia) as follows:

      • CLI - Specify the Region when you use the CloudFront scope: --scope=CLOUDFRONT --region=us-east-1.

      • API and SDKs - For all calls, use the Region endpoint us-east-1.

      Possible values include:
      • "CLOUDFRONT"
      • "REGIONAL"
    • NextMarker — (String)

      When you request a list of objects with a Limit setting, if the number of objects that are still available for retrieval exceeds the limit, WAF returns a NextMarker value in the response. To retrieve the next batch of objects, provide the marker from the prior call in your next request.

    • Limit — (Integer)

      The maximum number of objects that you want WAF to return for this request. If more objects are available, in the response, WAF provides a NextMarker value that you can use in a subsequent call to get the next batch of objects.

Callback (callback):

  • function(err, data) { ... }

    Called when a response from the service is returned. If a callback is not supplied, you must call AWS.Request.send() on the returned request object to initiate the request.

    Context (this):

    • (AWS.Response) —

      the response object containing error, data properties, and the original request object.

    Parameters:

    • err (Error) —

      the error object returned from the request. Set to null if the request is successful.

    • data (Object) —

      the de-serialized data returned from the request. Set to null if a request error occurs. The data object has the following properties:

      • NextMarker — (String)

        When you request a list of objects with a Limit setting, if the number of objects that are still available for retrieval exceeds the limit, WAF returns a NextMarker value in the response. To retrieve the next batch of objects, provide the marker from the prior call in your next request.

      • RuleGroups — (Array<map>)

        • Name — (String)

          The name of the data type instance. You cannot change the name after you create the instance.

        • Id — (String)

          A unique identifier for the rule group. This ID is returned in the responses to create and list commands. You provide it to operations like update and delete.

        • Description — (String)

          A description of the rule group that helps with identification.

        • LockToken — (String)

          A token used for optimistic locking. WAF returns a token to your get and list requests, to mark the state of the entity at the time of the request. To make changes to the entity associated with the token, you provide the token to operations like update and delete. WAF uses the token to ensure that no changes have been made to the entity since you last retrieved it. If a change has been made, the update fails with a WAFOptimisticLockException. If this happens, perform another get, and use the new token returned by that operation.

        • ARN — (String)

          The Amazon Resource Name (ARN) of the entity.

Returns:

  • (AWS.Request) —

    a handle to the operation request for subsequent event callback registration.

listTagsForResource(params = {}, callback) ⇒ AWS.Request

Retrieves the TagInfoForResource for the specified resource. Tags 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 Amazon Web Services resource, up to 50 tags for a resource.

You can tag the Amazon Web Services resources that you manage through WAF: web ACLs, rule groups, IP sets, and regex pattern sets. You can't manage or view tags through the WAF console.

Service Reference:

Examples:

Calling the listTagsForResource operation

var params = {
  ResourceARN: 'STRING_VALUE', /* required */
  Limit: 'NUMBER_VALUE',
  NextMarker: 'STRING_VALUE'
};
wafv2.listTagsForResource(params, function(err, data) {
  if (err) console.log(err, err.stack); // an error occurred
  else     console.log(data);           // successful response
});

Parameters:

  • params (Object) (defaults to: {}) —
    • NextMarker — (String)

      When you request a list of objects with a Limit setting, if the number of objects that are still available for retrieval exceeds the limit, WAF returns a NextMarker value in the response. To retrieve the next batch of objects, provide the marker from the prior call in your next request.

    • Limit — (Integer)

      The maximum number of objects that you want WAF to return for this request. If more objects are available, in the response, WAF provides a NextMarker value that you can use in a subsequent call to get the next batch of objects.

    • ResourceARN — (String)

      The Amazon Resource Name (ARN) of the resource.

Callback (callback):

  • function(err, data) { ... }

    Called when a response from the service is returned. If a callback is not supplied, you must call AWS.Request.send() on the returned request object to initiate the request.

    Context (this):

    • (AWS.Response) —

      the response object containing error, data properties, and the original request object.

    Parameters:

    • err (Error) —

      the error object returned from the request. Set to null if the request is successful.

    • data (Object) —

      the de-serialized data returned from the request. Set to null if a request error occurs. The data object has the following properties:

      • NextMarker — (String)

        When you request a list of objects with a Limit setting, if the number of objects that are still available for retrieval exceeds the limit, WAF returns a NextMarker value in the response. To retrieve the next batch of objects, provide the marker from the prior call in your next request.

      • TagInfoForResource — (map)

        The collection of tagging definitions for the resource.

        • ResourceARN — (String)

          The Amazon Resource Name (ARN) of the resource.

        • TagList — (Array<map>)

          The array of Tag objects defined for the resource.

          • Key — required — (String)

            Part of the key:value pair that defines a tag. You can use a tag key to describe a category of information, such as "customer." Tag keys are case-sensitive.

          • Value — required — (String)

            Part of the key:value pair that defines a tag. You can use a tag value to describe a specific value within a category, such as "companyA" or "companyB." Tag values are case-sensitive.

Returns:

  • (AWS.Request) —

    a handle to the operation request for subsequent event callback registration.

listWebACLs(params = {}, callback) ⇒ AWS.Request

Retrieves an array of WebACLSummary objects for the web ACLs that you manage.

Service Reference:

Examples:

Calling the listWebACLs operation

var params = {
  Scope: CLOUDFRONT | REGIONAL, /* required */
  Limit: 'NUMBER_VALUE',
  NextMarker: 'STRING_VALUE'
};
wafv2.listWebACLs(params, function(err, data) {
  if (err) console.log(err, err.stack); // an error occurred
  else     console.log(data);           // successful response
});

Parameters:

  • params (Object) (defaults to: {}) —
    • Scope — (String)

      Specifies whether this is for an Amazon CloudFront distribution or for a regional application. A regional application can be an Application Load Balancer (ALB), an Amazon API Gateway REST API, or an AppSync GraphQL API.

      To work with CloudFront, you must also specify the Region US East (N. Virginia) as follows:

      • CLI - Specify the Region when you use the CloudFront scope: --scope=CLOUDFRONT --region=us-east-1.

      • API and SDKs - For all calls, use the Region endpoint us-east-1.

      Possible values include:
      • "CLOUDFRONT"
      • "REGIONAL"
    • NextMarker — (String)

      When you request a list of objects with a Limit setting, if the number of objects that are still available for retrieval exceeds the limit, WAF returns a NextMarker value in the response. To retrieve the next batch of objects, provide the marker from the prior call in your next request.

    • Limit — (Integer)

      The maximum number of objects that you want WAF to return for this request. If more objects are available, in the response, WAF provides a NextMarker value that you can use in a subsequent call to get the next batch of objects.

Callback (callback):

  • function(err, data) { ... }

    Called when a response from the service is returned. If a callback is not supplied, you must call AWS.Request.send() on the returned request object to initiate the request.

    Context (this):

    • (AWS.Response) —

      the response object containing error, data properties, and the original request object.

    Parameters:

    • err (Error) —

      the error object returned from the request. Set to null if the request is successful.

    • data (Object) —

      the de-serialized data returned from the request. Set to null if a request error occurs. The data object has the following properties:

      • NextMarker — (String)

        When you request a list of objects with a Limit setting, if the number of objects that are still available for retrieval exceeds the limit, WAF returns a NextMarker value in the response. To retrieve the next batch of objects, provide the marker from the prior call in your next request.

      • WebACLs — (Array<map>)

        • Name — (String)

          The name of the web ACL. You cannot change the name of a web ACL after you create it.

        • Id — (String)

          The unique identifier for the web ACL. This ID is returned in the responses to create and list commands. You provide it to operations like update and delete.

        • Description — (String)

          A description of the web ACL that helps with identification.

        • LockToken — (String)

          A token used for optimistic locking. WAF returns a token to your get and list requests, to mark the state of the entity at the time of the request. To make changes to the entity associated with the token, you provide the token to operations like update and delete. WAF uses the token to ensure that no changes have been made to the entity since you last retrieved it. If a change has been made, the update fails with a WAFOptimisticLockException. If this happens, perform another get, and use the new token returned by that operation.

        • ARN — (String)

          The Amazon Resource Name (ARN) of the entity.

Returns:

  • (AWS.Request) —

    a handle to the operation request for subsequent event callback registration.

putLoggingConfiguration(params = {}, callback) ⇒ AWS.Request

Enables the specified LoggingConfiguration, to start logging from a web ACL, according to the configuration provided.

You can access information about all traffic that 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. If you are capturing logs for Amazon CloudFront, always create the firehose in US East (N. Virginia).

    Give the data firehose a name that starts with the prefix aws-waf-logs-. For example, aws-waf-logs-us-east-2-analytics.

    Note: 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.

When you successfully enable logging using a PutLoggingConfiguration request, WAF will create a service linked role with the necessary permissions to write logs to the Amazon Kinesis Data Firehose. For more information, see Logging Web ACL Traffic Information in the WAF Developer Guide.

Note: This operation completely replaces the mutable specifications that you already have for the logging configuration with the ones that you provide to this call. To modify the logging configuration, retrieve it by calling GetLoggingConfiguration, update the settings as needed, and then provide the complete logging configuration specification to this call.

Service Reference:

Examples:

Calling the putLoggingConfiguration operation

var params = {
  LoggingConfiguration: { /* required */
    LogDestinationConfigs: [ /* required */
      'STRING_VALUE',
      /* more items */
    ],
    ResourceArn: 'STRING_VALUE', /* required */
    LoggingFilter: {
      DefaultBehavior: KEEP | DROP, /* required */
      Filters: [ /* required */
        {
          Behavior: KEEP | DROP, /* required */
          Conditions: [ /* required */
            {
              ActionCondition: {
                Action: ALLOW | BLOCK | COUNT | CAPTCHA | EXCLUDED_AS_COUNT /* required */
              },
              LabelNameCondition: {
                LabelName: 'STRING_VALUE' /* required */
              }
            },
            /* more items */
          ],
          Requirement: MEETS_ALL | MEETS_ANY /* required */
        },
        /* more items */
      ]
    },
    ManagedByFirewallManager: true || false,
    RedactedFields: [
      {
        AllQueryArguments: {
        },
        Body: {
        },
        JsonBody: {
          MatchPattern: { /* required */
            All: {
            },
            IncludedPaths: [
              'STRING_VALUE',
              /* more items */
            ]
          },
          MatchScope: ALL | KEY | VALUE, /* required */
          InvalidFallbackBehavior: MATCH | NO_MATCH | EVALUATE_AS_STRING
        },
        Method: {
        },
        QueryString: {
        },
        SingleHeader: {
          Name: 'STRING_VALUE' /* required */
        },
        SingleQueryArgument: {
          Name: 'STRING_VALUE' /* required */
        },
        UriPath: {
        }
      },
      /* more items */
    ]
  }
};
wafv2.putLoggingConfiguration(params, function(err, data) {
  if (err) console.log(err, err.stack); // an error occurred
  else     console.log(data);           // successful response
});

Parameters:

  • params (Object) (defaults to: {}) —
    • LoggingConfiguration — (map)

      • ResourceArn — required — (String)

        The Amazon Resource Name (ARN) of the web ACL that you want to associate with LogDestinationConfigs.

      • LogDestinationConfigs — required — (Array<String>)

        The Amazon Kinesis Data Firehose Amazon Resource Name (ARNs) that you want to associate with the web ACL.

      • RedactedFields — (Array<map>)

        The parts of the request that you want to keep out of the logs. For example, if you redact the SingleHeader field, the HEADER field in the firehose will be xxx.

        Note: You can specify only the following fields for redaction: UriPath, QueryString, SingleHeader, Method, and JsonBody.
        • SingleHeader — (map)

          Inspect a single header. Provide the name of the header to inspect, for example, User-Agent or Referer. This setting isn't case sensitive.

          Example JSON: "SingleHeader": { "Name": "haystack" }

          • Name — required — (String)

            The name of the query header to inspect.

        • SingleQueryArgument — (map)

          Inspect a single query argument. Provide the name of the query argument to inspect, such as UserName or SalesRegion. The name can be up to 30 characters long and isn't case sensitive.

          This is used only to indicate the web request component for WAF to inspect, in the FieldToMatch specification.

          Example JSON: "SingleQueryArgument": { "Name": "myArgument" }

          • Name — required — (String)

            The name of the query argument to inspect.

        • AllQueryArguments — (map)

          Inspect all query arguments.

        • UriPath — (map)

          Inspect the request URI path. This is the part of a web request that identifies a resource, for example, /images/daily-ad.jpg.

        • QueryString — (map)

          Inspect the query string. This is the part of a URL that appears after a ? character, if any.

        • Body — (map)

          Inspect the request body as plain text. The request body immediately follows the request headers. This is the part of a request that contains any additional data that you want to send to your web server as the HTTP request body, such as data from a form.

          Note that only the first 8 KB (8192 bytes) of the request body are forwarded to WAF for inspection by the underlying host service. If you don't need to inspect more than 8 KB, you can guarantee that you don't allow additional bytes in by combining a statement that inspects the body of the web request, such as ByteMatchStatement or RegexPatternSetReferenceStatement, with a SizeConstraintStatement that enforces an 8 KB size limit on the body of the request. WAF doesn't support inspecting the entire contents of web requests whose bodies exceed the 8 KB limit.

        • Method — (map)

          Inspect the HTTP method. The method indicates the type of operation that the request is asking the origin to perform.

        • JsonBody — (map)

          Inspect the request body as JSON. The request body immediately follows the request headers. This is the part of a request that contains any additional data that you want to send to your web server as the HTTP request body, such as data from a form.

          Note that only the first 8 KB (8192 bytes) of the request body are forwarded to WAF for inspection by the underlying host service. If you don't need to inspect more than 8 KB, you can guarantee that you don't allow additional bytes in by combining a statement that inspects the body of the web request, such as ByteMatchStatement or RegexPatternSetReferenceStatement, with a SizeConstraintStatement that enforces an 8 KB size limit on the body of the request. WAF doesn't support inspecting the entire contents of web requests whose bodies exceed the 8 KB limit.

          • MatchPattern — required — (map)

            The patterns to look for in the JSON body. WAF inspects the results of these pattern matches against the rule inspection criteria.

            • All — (map)

              Match all of the elements. See also MatchScope in JsonBody.

              You must specify either this setting or the IncludedPaths setting, but not both.

            • IncludedPaths — (Array<String>)

              Match only the specified include paths. See also MatchScope in JsonBody.

              Provide the include paths using JSON Pointer syntax. For example, "IncludedPaths": ["/dogs/0/name", "/dogs/1/name"]. For information about this syntax, see the Internet Engineering Task Force (IETF) documentation JavaScript Object Notation (JSON) Pointer.

              You must specify either this setting or the All setting, but not both.

              Note: Don't use this option to include all paths. Instead, use the All setting.
          • MatchScope — required — (String)

            The parts of the JSON to match against using the MatchPattern. If you specify All, WAF matches against keys and values.

            Possible values include:
            • "ALL"
            • "KEY"
            • "VALUE"
          • InvalidFallbackBehavior — (String)

            What WAF should do if it fails to completely parse the JSON body. The options are the following:

            • EVALUATE_AS_STRING - Inspect the body as plain text. WAF applies the text transformations and inspection criteria that you defined for the JSON inspection to the body text string.

            • MATCH - Treat the web request as matching the rule statement. WAF applies the rule action to the request.

            • NO_MATCH - Treat the web request as not matching the rule statement.

            If you don't provide this setting, WAF parses and evaluates the content only up to the first parsing failure that it encounters.

            WAF does its best to parse the entire JSON body, but might be forced to stop for reasons such as invalid characters, duplicate keys, truncation, and any content whose root node isn't an object or an array.

            WAF parses the JSON in the following examples as two valid key, value pairs:

            • Missing comma: {"key1":"value1""key2":"value2"}

            • Missing colon: {"key1":"value1","key2""value2"}

            • Extra colons: {"key1"::"value1","key2""value2"}

            Possible values include:
            • "MATCH"
            • "NO_MATCH"
            • "EVALUATE_AS_STRING"
      • ManagedByFirewallManager — (Boolean)

        Indicates whether the logging configuration was created by Firewall Manager, as part of an WAF policy configuration. If true, only Firewall Manager can modify or delete the configuration.

      • LoggingFilter — (map)

        Filtering that specifies which web requests are kept in the logs and which are dropped. You can filter on the rule action and on the web request labels that were applied by matching rules during web ACL evaluation.

        • Filters — required — (Array<map>)

          The filters that you want to apply to the logs.

          • Behavior — required — (String)

            How to handle logs that satisfy the filter's conditions and requirement.

            Possible values include:
            • "KEEP"
            • "DROP"
          • Requirement — required — (String)

            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.

            Possible values include:
            • "MEETS_ALL"
            • "MEETS_ANY"
          • Conditions — required — (Array<map>)

            Match conditions for the filter.

            • ActionCondition — (map)

              A single action condition.

              • Action — required — (String)

                The action setting that a log record must contain in order to meet the condition.

                Possible values include:
                • "ALLOW"
                • "BLOCK"
                • "COUNT"
                • "CAPTCHA"
                • "EXCLUDED_AS_COUNT"
            • LabelNameCondition — (map)

              A single label name condition.

              • LabelName — required — (String)

                The label name that a log record must contain in order to meet the condition. This must be a fully qualified label name. Fully qualified labels have a prefix, optional namespaces, and label name. The prefix identifies the rule group or web ACL context of the rule that added the label.

        • DefaultBehavior — required — (String)

          Default handling for logs that don't match any of the specified filtering conditions.

          Possible values include:
          • "KEEP"
          • "DROP"

Callback (callback):

  • function(err, data) { ... }

    Called when a response from the service is returned. If a callback is not supplied, you must call AWS.Request.send() on the returned request object to initiate the request.

    Context (this):

    • (AWS.Response) —

      the response object containing error, data properties, and the original request object.

    Parameters:

    • err (Error) —

      the error object returned from the request. Set to null if the request is successful.

    • data (Object) —

      the de-serialized data returned from the request. Set to null if a request error occurs. The data object has the following properties:

      • LoggingConfiguration — (map)

        • ResourceArn — required — (String)

          The Amazon Resource Name (ARN) of the web ACL that you want to associate with LogDestinationConfigs.

        • LogDestinationConfigs — required — (Array<String>)

          The Amazon Kinesis Data Firehose Amazon Resource Name (ARNs) that you want to associate with the web ACL.

        • RedactedFields — (Array<map>)

          The parts of the request that you want to keep out of the logs. For example, if you redact the SingleHeader field, the HEADER field in the firehose will be xxx.

          Note: You can specify only the following fields for redaction: UriPath, QueryString, SingleHeader, Method, and JsonBody.
          • SingleHeader — (map)

            Inspect a single header. Provide the name of the header to inspect, for example, User-Agent or Referer. This setting isn't case sensitive.

            Example JSON: "SingleHeader": { "Name": "haystack" }

            • Name — required — (String)

              The name of the query header to inspect.

          • SingleQueryArgument — (map)

            Inspect a single query argument. Provide the name of the query argument to inspect, such as UserName or SalesRegion. The name can be up to 30 characters long and isn't case sensitive.

            This is used only to indicate the web request component for WAF to inspect, in the FieldToMatch specification.

            Example JSON: "SingleQueryArgument": { "Name": "myArgument" }

            • Name — required — (String)

              The name of the query argument to inspect.

          • AllQueryArguments — (map)

            Inspect all query arguments.

          • UriPath — (map)

            Inspect the request URI path. This is the part of a web request that identifies a resource, for example, /images/daily-ad.jpg.

          • QueryString — (map)

            Inspect the query string. This is the part of a URL that appears after a ? character, if any.

          • Body — (map)

            Inspect the request body as plain text. The request body immediately follows the request headers. This is the part of a request that contains any additional data that you want to send to your web server as the HTTP request body, such as data from a form.

            Note that only the first 8 KB (8192 bytes) of the request body are forwarded to WAF for inspection by the underlying host service. If you don't need to inspect more than 8 KB, you can guarantee that you don't allow additional bytes in by combining a statement that inspects the body of the web request, such as ByteMatchStatement or RegexPatternSetReferenceStatement, with a SizeConstraintStatement that enforces an 8 KB size limit on the body of the request. WAF doesn't support inspecting the entire contents of web requests whose bodies exceed the 8 KB limit.

          • Method — (map)

            Inspect the HTTP method. The method indicates the type of operation that the request is asking the origin to perform.

          • JsonBody — (map)

            Inspect the request body as JSON. The request body immediately follows the request headers. This is the part of a request that contains any additional data that you want to send to your web server as the HTTP request body, such as data from a form.

            Note that only the first 8 KB (8192 bytes) of the request body are forwarded to WAF for inspection by the underlying host service. If you don't need to inspect more than 8 KB, you can guarantee that you don't allow additional bytes in by combining a statement that inspects the body of the web request, such as ByteMatchStatement or RegexPatternSetReferenceStatement, with a SizeConstraintStatement that enforces an 8 KB size limit on the body of the request. WAF doesn't support inspecting the entire contents of web requests whose bodies exceed the 8 KB limit.

            • MatchPattern — required — (map)

              The patterns to look for in the JSON body. WAF inspects the results of these pattern matches against the rule inspection criteria.

              • All — (map)

                Match all of the elements. See also MatchScope in JsonBody.

                You must specify either this setting or the IncludedPaths setting, but not both.

              • IncludedPaths — (Array<String>)

                Match only the specified include paths. See also MatchScope in JsonBody.

                Provide the include paths using JSON Pointer syntax. For example, "IncludedPaths": ["/dogs/0/name", "/dogs/1/name"]. For information about this syntax, see the Internet Engineering Task Force (IETF) documentation JavaScript Object Notation (JSON) Pointer.

                You must specify either this setting or the All setting, but not both.

                Note: Don't use this option to include all paths. Instead, use the All setting.
            • MatchScope — required — (String)

              The parts of the JSON to match against using the MatchPattern. If you specify All, WAF matches against keys and values.

              Possible values include:
              • "ALL"
              • "KEY"
              • "VALUE"
            • InvalidFallbackBehavior — (String)

              What WAF should do if it fails to completely parse the JSON body. The options are the following:

              • EVALUATE_AS_STRING - Inspect the body as plain text. WAF applies the text transformations and inspection criteria that you defined for the JSON inspection to the body text string.

              • MATCH - Treat the web request as matching the rule statement. WAF applies the rule action to the request.

              • NO_MATCH - Treat the web request as not matching the rule statement.

              If you don't provide this setting, WAF parses and evaluates the content only up to the first parsing failure that it encounters.

              WAF does its best to parse the entire JSON body, but might be forced to stop for reasons such as invalid characters, duplicate keys, truncation, and any content whose root node isn't an object or an array.

              WAF parses the JSON in the following examples as two valid key, value pairs:

              • Missing comma: {"key1":"value1""key2":"value2"}

              • Missing colon: {"key1":"value1","key2""value2"}

              • Extra colons: {"key1"::"value1","key2""value2"}

              Possible values include:
              • "MATCH"
              • "NO_MATCH"
              • "EVALUATE_AS_STRING"
        • ManagedByFirewallManager — (Boolean)

          Indicates whether the logging configuration was created by Firewall Manager, as part of an WAF policy configuration. If true, only Firewall Manager can modify or delete the configuration.

        • LoggingFilter — (map)

          Filtering that specifies which web requests are kept in the logs and which are dropped. You can filter on the rule action and on the web request labels that were applied by matching rules during web ACL evaluation.

          • Filters — required — (Array<map>)

            The filters that you want to apply to the logs.

            • Behavior — required — (String)

              How to handle logs that satisfy the filter's conditions and requirement.

              Possible values include:
              • "KEEP"
              • "DROP"
            • Requirement — required — (String)

              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.

              Possible values include:
              • "MEETS_ALL"
              • "MEETS_ANY"
            • Conditions — required — (Array<map>)

              Match conditions for the filter.

              • ActionCondition — (map)

                A single action condition.

                • Action — required — (String)

                  The action setting that a log record must contain in order to meet the condition.

                  Possible values include:
                  • "ALLOW"
                  • "BLOCK"
                  • "COUNT"
                  • "CAPTCHA"
                  • "EXCLUDED_AS_COUNT"
              • LabelNameCondition — (map)

                A single label name condition.

                • LabelName — required — (String)

                  The label name that a log record must contain in order to meet the condition. This must be a fully qualified label name. Fully qualified labels have a prefix, optional namespaces, and label name. The prefix identifies the rule group or web ACL context of the rule that added the label.

          • DefaultBehavior — required — (String)

            Default handling for logs that don't match any of the specified filtering conditions.

            Possible values include:
            • "KEEP"
            • "DROP"

Returns:

  • (AWS.Request) —

    a handle to the operation request for subsequent event callback registration.

putManagedRuleSetVersions(params = {}, callback) ⇒ AWS.Request

Defines the versions of your managed rule set that you are offering to the customers. Customers see your offerings as managed rule groups with versioning.

Note: This is intended for use only by vendors of managed rule sets. Vendors are Amazon Web Services and Amazon Web Services Marketplace sellers. Vendors, you can use the managed rule set APIs to provide controlled rollout of your versioned managed rule group offerings for your customers. The APIs are ListManagedRuleSets, GetManagedRuleSet, PutManagedRuleSetVersions, and UpdateManagedRuleSetVersionExpiryDate.

Customers retrieve their managed rule group list by calling ListAvailableManagedRuleGroups. The name that you provide here for your managed rule set is the name the customer sees for the corresponding managed rule group. Customers can retrieve the available versions for a managed rule group by calling ListAvailableManagedRuleGroupVersions. You provide a rule group specification for each version. For each managed rule set, you must specify a version that you recommend using.

To initiate the expiration of a managed rule group version, use UpdateManagedRuleSetVersionExpiryDate.

Service Reference:

Examples:

Calling the putManagedRuleSetVersions operation

var params = {
  Id: 'STRING_VALUE', /* required */
  LockToken: 'STRING_VALUE', /* required */
  Name: 'STRING_VALUE', /* required */
  Scope: CLOUDFRONT | REGIONAL, /* required */
  RecommendedVersion: 'STRING_VALUE',
  VersionsToPublish: {
    '<VersionKeyString>': {
      AssociatedRuleGroupArn: 'STRING_VALUE',
      ForecastedLifetime: 'NUMBER_VALUE'
    },
    /* '<VersionKeyString>': ... */
  }
};
wafv2.putManagedRuleSetVersions(params, function(err, data) {
  if (err) console.log(err, err.stack); // an error occurred
  else     console.log(data);           // successful response
});

Parameters:

  • params (Object) (defaults to: {}) —
    • Name — (String)

      The name of the managed rule set. You use this, along with the rule set ID, to identify the rule set.

      This name is assigned to the corresponding managed rule group, which your customers can access and use.

    • Scope — (String)

      Specifies whether this is for an Amazon CloudFront distribution or for a regional application. A regional application can be an Application Load Balancer (ALB), an Amazon API Gateway REST API, or an AppSync GraphQL API.

      To work with CloudFront, you must also specify the Region US East (N. Virginia) as follows:

      • CLI - Specify the Region when you use the CloudFront scope: --scope=CLOUDFRONT --region=us-east-1.

      • API and SDKs - For all calls, use the Region endpoint us-east-1.

      Possible values include:
      • "CLOUDFRONT"
      • "REGIONAL"
    • Id — (String)

      A unique identifier for the managed rule set. The ID is returned in the responses to commands like list. You provide it to operations like get and update.

    • LockToken — (String)

      A token used for optimistic locking. WAF returns a token to your get and list requests, to mark the state of the entity at the time of the request. To make changes to the entity associated with the token, you provide the token to operations like update and delete. WAF uses the token to ensure that no changes have been made to the entity since you last retrieved it. If a change has been made, the update fails with a WAFOptimisticLockException. If this happens, perform another get, and use the new token returned by that operation.

    • RecommendedVersion — (String)

      The version of the named managed rule group that you'd like your customers to choose, from among your version offerings.

    • VersionsToPublish — (map<map>)

      The versions of the named managed rule group that you want to offer to your customers.

      • AssociatedRuleGroupArn — (String)

        The Amazon Resource Name (ARN) of the vendor's rule group that's used in the published managed rule group version.

      • ForecastedLifetime — (Integer)

        The amount of time the vendor expects this version of the managed rule group to last, in days.

Callback (callback):

  • function(err, data) { ... }

    Called when a response from the service is returned. If a callback is not supplied, you must call AWS.Request.send() on the returned request object to initiate the request.

    Context (this):

    • (AWS.Response) —

      the response object containing error, data properties, and the original request object.

    Parameters:

    • err (Error) —

      the error object returned from the request. Set to null if the request is successful.

    • data (Object) —

      the de-serialized data returned from the request. Set to null if a request error occurs. The data object has the following properties:

      • NextLockToken — (String)

        A token used for optimistic locking. WAF returns a token to your get and list requests, to mark the state of the entity at the time of the request. To make changes to the entity associated with the token, you provide the token to operations like update and delete. WAF uses the token to ensure that no changes have been made to the entity since you last retrieved it. If a change has been made, the update fails with a WAFOptimisticLockException. If this happens, perform another get, and use the new token returned by that operation.

Returns:

  • (AWS.Request) —

    a handle to the operation request for subsequent event callback registration.

putPermissionPolicy(params = {}, callback) ⇒ AWS.Request

Attaches an IAM policy to the specified resource. Use this to share a rule group across accounts.

You must be the owner of the rule group to perform this operation.

This action is subject to the following restrictions:

  • You can attach only one policy with each PutPermissionPolicy request.

  • The ARN in the request must be a valid WAF RuleGroup ARN and the rule group must exist in the same Region.

  • The user making the request must be the owner of the rule group.

Service Reference:

Examples:

Calling the putPermissionPolicy operation

var params = {
  Policy: 'STRING_VALUE', /* required */
  ResourceArn: 'STRING_VALUE' /* required */
};
wafv2.putPermissionPolicy(params, function(err, data) {
  if (err) console.log(err, err.stack); // an error occurred
  else     console.log(data);           // successful response
});

Parameters:

  • params (Object) (defaults to: {}) —
    • ResourceArn — (String)

      The Amazon Resource Name (ARN) of the RuleGroup to which you want to attach the policy.

    • Policy — (String)

      The policy to attach to the specified rule group.

      The policy specifications must conform to the following:

      • The policy must be composed using IAM Policy version 2012-10-17 or version 2015-01-01.

      • The policy must include specifications for Effect, Action, and Principal.

      • Effect must specify Allow.

      • Action must specify wafv2:CreateWebACL, wafv2:UpdateWebACL, and wafv2:PutFirewallManagerRuleGroups. WAF rejects any extra actions or wildcard actions in the policy.

      • The policy must not include a Resource parameter.

      For more information, see IAM Policies.

Callback (callback):

  • function(err, data) { ... }

    Called when a response from the service is returned. If a callback is not supplied, you must call AWS.Request.send() on the returned request object to initiate the request.

    Context (this):

    • (AWS.Response) —

      the response object containing error, data properties, and the original request object.

    Parameters:

    • err (Error) —

      the error object returned from the request. Set to null if the request is successful.

    • data (Object) —

      the de-serialized data returned from the request. Set to null if a request error occurs.

Returns:

  • (AWS.Request) —

    a handle to the operation request for subsequent event callback registration.

tagResource(params = {}, callback) ⇒ AWS.Request

Associates tags with the specified Amazon Web Services resource. Tags 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 Amazon Web Services resource, up to 50 tags for a resource.

You can tag the Amazon Web Services resources that you manage through WAF: web ACLs, rule groups, IP sets, and regex pattern sets. You can't manage or view tags through the WAF console.

Service Reference:

Examples:

Calling the tagResource operation

var params = {
  ResourceARN: 'STRING_VALUE', /* required */
  Tags: [ /* required */
    {
      Key: 'STRING_VALUE', /* required */
      Value: 'STRING_VALUE' /* required */
    },
    /* more items */
  ]
};
wafv2.tagResource(params, function(err, data) {
  if (err) console.log(err, err.stack); // an error occurred
  else     console.log(data);           // successful response
});

Parameters:

  • params (Object) (defaults to: {}) —
    • ResourceARN — (String)

      The Amazon Resource Name (ARN) of the resource.

    • Tags — (Array<map>)

      An array of key:value pairs to associate with the resource.

      • Key — required — (String)

        Part of the key:value pair that defines a tag. You can use a tag key to describe a category of information, such as "customer." Tag keys are case-sensitive.

      • Value — required — (String)

        Part of the key:value pair that defines a tag. You can use a tag value to describe a specific value within a category, such as "companyA" or "companyB." Tag values are case-sensitive.

Callback (callback):

  • function(err, data) { ... }

    Called when a response from the service is returned. If a callback is not supplied, you must call AWS.Request.send() on the returned request object to initiate the request.

    Context (this):

    • (AWS.Response) —

      the response object containing error, data properties, and the original request object.

    Parameters:

    • err (Error) —

      the error object returned from the request. Set to null if the request is successful.

    • data (Object) —

      the de-serialized data returned from the request. Set to null if a request error occurs.

Returns:

  • (AWS.Request) —

    a handle to the operation request for subsequent event callback registration.

untagResource(params = {}, callback) ⇒ AWS.Request

Disassociates tags from an Amazon Web Services resource. Tags are key:value pairs that you can associate with Amazon Web Services resources. For example, the tag key might be "customer" and the tag value might be "companyA." You can specify one or more tags to add to each container. You can add up to 50 tags to each Amazon Web Services resource.

Service Reference:

Examples:

Calling the untagResource operation

var params = {
  ResourceARN: 'STRING_VALUE', /* required */
  TagKeys: [ /* required */
    'STRING_VALUE',
    /* more items */
  ]
};
wafv2.untagResource(params, function(err, data) {
  if (err) console.log(err, err.stack); // an error occurred
  else     console.log(data);           // successful response
});

Parameters:

  • params (Object) (defaults to: {}) —
    • ResourceARN — (String)

      The Amazon Resource Name (ARN) of the resource.

    • TagKeys — (Array<String>)

      An array of keys identifying the tags to disassociate from the resource.

Callback (callback):

  • function(err, data) { ... }

    Called when a response from the service is returned. If a callback is not supplied, you must call AWS.Request.send() on the returned request object to initiate the request.

    Context (this):

    • (AWS.Response) —

      the response object containing error, data properties, and the original request object.

    Parameters:

    • err (Error) —

      the error object returned from the request. Set to null if the request is successful.

    • data (Object) —

      the de-serialized data returned from the request. Set to null if a request error occurs.

Returns:

  • (AWS.Request) —

    a handle to the operation request for subsequent event callback registration.

updateIPSet(params = {}, callback) ⇒ AWS.Request

Updates the specified IPSet.

Note: This operation completely replaces the mutable specifications that you already have for the IP set with the ones that you provide to this call. To modify the IP set, retrieve it by calling GetIPSet, update the settings as needed, and then provide the complete IP set specification to this call.

Service Reference:

Examples:

Calling the updateIPSet operation

var params = {
  Addresses: [ /* required */
    'STRING_VALUE',
    /* more items */
  ],
  Id: 'STRING_VALUE', /* required */
  LockToken: 'STRING_VALUE', /* required */
  Name: 'STRING_VALUE', /* required */
  Scope: CLOUDFRONT | REGIONAL, /* required */
  Description: 'STRING_VALUE'
};
wafv2.updateIPSet(params, function(err, data) {
  if (err) console.log(err, err.stack); // an error occurred
  else     console.log(data);           // successful response
});

Parameters:

  • params (Object) (defaults to: {}) —
    • Name — (String)

      The name of the IP set. You cannot change the name of an IPSet after you create it.

    • Scope — (String)

      Specifies whether this is for an Amazon CloudFront distribution or for a regional application. A regional application can be an Application Load Balancer (ALB), an Amazon API Gateway REST API, or an AppSync GraphQL API.

      To work with CloudFront, you must also specify the Region US East (N. Virginia) as follows:

      • CLI - Specify the Region when you use the CloudFront scope: --scope=CLOUDFRONT --region=us-east-1.

      • API and SDKs - For all calls, use the Region endpoint us-east-1.

      Possible values include:
      • "CLOUDFRONT"
      • "REGIONAL"
    • Id — (String)

      A unique identifier for the set. This ID is returned in the responses to create and list commands. You provide it to operations like update and delete.

    • Description — (String)

      A description of the IP set that helps with identification.

    • Addresses — (Array<String>)

      Contains an array of strings that specify one or more IP addresses or blocks of IP addresses in Classless Inter-Domain Routing (CIDR) notation. WAF supports all IPv4 and IPv6 CIDR ranges except for /0.

      Examples:

      • To configure WAF to allow, block, or count requests that originated from the IP address 192.0.2.44, specify 192.0.2.44/32.

      • To configure WAF to allow, block, or count requests that originated from IP addresses from 192.0.2.0 to 192.0.2.255, specify 192.0.2.0/24.

      • To configure WAF to allow, block, or count requests that originated from the IP address 1111:0000:0000:0000:0000:0000:0000:0111, specify 1111:0000:0000:0000:0000:0000:0000:0111/128.

      • To configure WAF to allow, block, or count requests that originated from IP addresses 1111:0000:0000:0000:0000:0000:0000:0000 to 1111:0000:0000:0000:ffff:ffff:ffff:ffff, specify 1111:0000:0000:0000:0000:0000:0000:0000/64.

      For more information about CIDR notation, see the Wikipedia entry Classless Inter-Domain Routing.

    • LockToken — (String)

      A token used for optimistic locking. WAF returns a token to your get and list requests, to mark the state of the entity at the time of the request. To make changes to the entity associated with the token, you provide the token to operations like update and delete. WAF uses the token to ensure that no changes have been made to the entity since you last retrieved it. If a change has been made, the update fails with a WAFOptimisticLockException. If this happens, perform another get, and use the new token returned by that operation.

Callback (callback):

  • function(err, data) { ... }

    Called when a response from the service is returned. If a callback is not supplied, you must call AWS.Request.send() on the returned request object to initiate the request.

    Context (this):

    • (AWS.Response) —

      the response object containing error, data properties, and the original request object.

    Parameters:

    • err (Error) —

      the error object returned from the request. Set to null if the request is successful.

    • data (Object) —

      the de-serialized data returned from the request. Set to null if a request error occurs. The data object has the following properties:

      • NextLockToken — (String)

        A token used for optimistic locking. WAF returns this token to your update requests. You use NextLockToken in the same manner as you use LockToken.

Returns:

  • (AWS.Request) —

    a handle to the operation request for subsequent event callback registration.

updateManagedRuleSetVersionExpiryDate(params = {}, callback) ⇒ AWS.Request

Updates the expiration information for your managed rule set. Use this to initiate the expiration of a managed rule group version. After you initiate expiration for a version, WAF excludes it from the reponse to ListAvailableManagedRuleGroupVersions for the managed rule group.

Note: This is intended for use only by vendors of managed rule sets. Vendors are Amazon Web Services and Amazon Web Services Marketplace sellers. Vendors, you can use the managed rule set APIs to provide controlled rollout of your versioned managed rule group offerings for your customers. The APIs are ListManagedRuleSets, GetManagedRuleSet, PutManagedRuleSetVersions, and UpdateManagedRuleSetVersionExpiryDate.

Service Reference:

Examples:

Calling the updateManagedRuleSetVersionExpiryDate operation

var params = {
  ExpiryTimestamp: new Date || 'Wed Dec 31 1969 16:00:00 GMT-0800 (PST)' || 123456789, /* required */
  Id: 'STRING_VALUE', /* required */
  LockToken: 'STRING_VALUE', /* required */
  Name: 'STRING_VALUE', /* required */
  Scope: CLOUDFRONT | REGIONAL, /* required */
  VersionToExpire: 'STRING_VALUE' /* required */
};
wafv2.updateManagedRuleSetVersionExpiryDate(params, function(err, data) {
  if (err) console.log(err, err.stack); // an error occurred
  else     console.log(data);           // successful response
});

Parameters:

  • params (Object) (defaults to: {}) —
    • Name — (String)

      The name of the managed rule set. You use this, along with the rule set ID, to identify the rule set.

      This name is assigned to the corresponding managed rule group, which your customers can access and use.

    • Scope — (String)

      Specifies whether this is for an Amazon CloudFront distribution or for a regional application. A regional application can be an Application Load Balancer (ALB), an Amazon API Gateway REST API, or an AppSync GraphQL API.

      To work with CloudFront, you must also specify the Region US East (N. Virginia) as follows:

      • CLI - Specify the Region when you use the CloudFront scope: --scope=CLOUDFRONT --region=us-east-1.

      • API and SDKs - For all calls, use the Region endpoint us-east-1.

      Possible values include:
      • "CLOUDFRONT"
      • "REGIONAL"
    • Id — (String)

      A unique identifier for the managed rule set. The ID is returned in the responses to commands like list. You provide it to operations like get and update.

    • LockToken — (String)

      A token used for optimistic locking. WAF returns a token to your get and list requests, to mark the state of the entity at the time of the request. To make changes to the entity associated with the token, you provide the token to operations like update and delete. WAF uses the token to ensure that no changes have been made to the entity since you last retrieved it. If a change has been made, the update fails with a WAFOptimisticLockException. If this happens, perform another get, and use the new token returned by that operation.

    • VersionToExpire — (String)

      The version that you want to remove from your list of offerings for the named managed rule group.

    • ExpiryTimestamp — (Date)

      The time that you want the version to expire.

      Times are in Coordinated Universal Time (UTC) format. UTC format includes the special designator, Z. For example, "2016-09-27T14:50Z".

Callback (callback):

  • function(err, data) { ... }

    Called when a response from the service is returned. If a callback is not supplied, you must call AWS.Request.send() on the returned request object to initiate the request.

    Context (this):

    • (AWS.Response) —

      the response object containing error, data properties, and the original request object.

    Parameters:

    • err (Error) —

      the error object returned from the request. Set to null if the request is successful.

    • data (Object) —

      the de-serialized data returned from the request. Set to null if a request error occurs. The data object has the following properties:

      • ExpiringVersion — (String)

        The version that is set to expire.

      • ExpiryTimestamp — (Date)

        The time that the version will expire.

        Times are in Coordinated Universal Time (UTC) format. UTC format includes the special designator, Z. For example, "2016-09-27T14:50Z".

      • NextLockToken — (String)

        A token used for optimistic locking. WAF returns a token to your get and list requests, to mark the state of the entity at the time of the request. To make changes to the entity associated with the token, you provide the token to operations like update and delete. WAF uses the token to ensure that no changes have been made to the entity since you last retrieved it. If a change has been made, the update fails with a WAFOptimisticLockException. If this happens, perform another get, and use the new token returned by that operation.

Returns:

  • (AWS.Request) —

    a handle to the operation request for subsequent event callback registration.

updateRegexPatternSet(params = {}, callback) ⇒ AWS.Request

Updates the specified RegexPatternSet.

Note: This operation completely replaces the mutable specifications that you already have for the regex pattern set with the ones that you provide to this call. To modify the regex pattern set, retrieve it by calling GetRegexPatternSet, update the settings as needed, and then provide the complete regex pattern set specification to this call.

Service Reference:

Examples:

Calling the updateRegexPatternSet operation

var params = {
  Id: 'STRING_VALUE', /* required */
  LockToken: 'STRING_VALUE', /* required */
  Name: 'STRING_VALUE', /* required */
  RegularExpressionList: [ /* required */
    {
      RegexString: 'STRING_VALUE'
    },
    /* more items */
  ],
  Scope: CLOUDFRONT | REGIONAL, /* required */
  Description: 'STRING_VALUE'
};
wafv2.updateRegexPatternSet(params, function(err, data) {
  if (err) console.log(err, err.stack); // an error occurred
  else     console.log(data);           // successful response
});

Parameters:

  • params (Object) (defaults to: {}) —
    • Name — (String)

      The name of the set. You cannot change the name after you create the set.

    • Scope — (String)

      Specifies whether this is for an Amazon CloudFront distribution or for a regional application. A regional application can be an Application Load Balancer (ALB), an Amazon API Gateway REST API, or an AppSync GraphQL API.

      To work with CloudFront, you must also specify the Region US East (N. Virginia) as follows:

      • CLI - Specify the Region when you use the CloudFront scope: --scope=CLOUDFRONT --region=us-east-1.

      • API and SDKs - For all calls, use the Region endpoint us-east-1.

      Possible values include:
      • "CLOUDFRONT"
      • "REGIONAL"
    • Id — (String)

      A unique identifier for the set. This ID is returned in the responses to create and list commands. You provide it to operations like update and delete.

    • Description — (String)

      A description of the set that helps with identification.

    • RegularExpressionList — (Array<map>)

      • RegexString — (String)

        The string representing the regular expression.

    • LockToken — (String)

      A token used for optimistic locking. WAF returns a token to your get and list requests, to mark the state of the entity at the time of the request. To make changes to the entity associated with the token, you provide the token to operations like update and delete. WAF uses the token to ensure that no changes have been made to the entity since you last retrieved it. If a change has been made, the update fails with a WAFOptimisticLockException. If this happens, perform another get, and use the new token returned by that operation.

Callback (callback):

  • function(err, data) { ... }

    Called when a response from the service is returned. If a callback is not supplied, you must call AWS.Request.send() on the returned request object to initiate the request.

    Context (this):

    • (AWS.Response) —

      the response object containing error, data properties, and the original request object.

    Parameters:

    • err (Error) —

      the error object returned from the request. Set to null if the request is successful.

    • data (Object) —

      the de-serialized data returned from the request. Set to null if a request error occurs. The data object has the following properties:

      • NextLockToken — (String)

        A token used for optimistic locking. WAF returns this token to your update requests. You use NextLockToken in the same manner as you use LockToken.

Returns:

  • (AWS.Request) —

    a handle to the operation request for subsequent event callback registration.

updateRuleGroup(params = {}, callback) ⇒ AWS.Request

Updates the specified RuleGroup.

Note: This operation completely replaces the mutable specifications that you already have for the rule group with the ones that you provide to this call. To modify the rule group, retrieve it by calling GetRuleGroup, update the settings as needed, and then provide the complete rule group specification to this call.

A rule group defines a collection of rules to inspect and control web requests that you can use in a WebACL. When you create a rule group, you define an immutable capacity limit. If you update a rule group, you must stay within the capacity. This allows others to reuse the rule group with confidence in its capacity requirements.

Service Reference:

Examples:

Calling the updateRuleGroup operation

var params = {
  Id: 'STRING_VALUE', /* required */
  LockToken: 'STRING_VALUE', /* required */
  Name: 'STRING_VALUE', /* required */
  Scope: CLOUDFRONT | REGIONAL, /* required */
  VisibilityConfig: { /* required */
    CloudWatchMetricsEnabled: true || false, /* required */
    MetricName: 'STRING_VALUE', /* required */
    SampledRequestsEnabled: true || false /* required */
  },
  CustomResponseBodies: {
    '<EntityName>': {
      Content: 'STRING_VALUE', /* required */
      ContentType: TEXT_PLAIN | TEXT_HTML | APPLICATION_JSON /* required */
    },
    /* '<EntityName>': ... */
  },
  Description: 'STRING_VALUE',
  Rules: [
    {
      Name: 'STRING_VALUE', /* required */
      Priority: 'NUMBER_VALUE', /* required */
      Statement: { /* Statement */ /* required */
        AndStatement: {
          Statements: [ /* required */
            /* recursive Statement */,
            /* more items */
          ]
        },
        ByteMatchStatement: {
          FieldToMatch: { /* required */
            AllQueryArguments: {
            },
            Body: {
            },
            JsonBody: {
              MatchPattern: { /* required */
                All: {
                },
                IncludedPaths: [
                  'STRING_VALUE',
                  /* more items */
                ]
              },
              MatchScope: ALL | KEY | VALUE, /* required */
              InvalidFallbackBehavior: MATCH | NO_MATCH | EVALUATE_AS_STRING
            },
            Method: {
            },
            QueryString: {
            },
            SingleHeader: {
              Name: 'STRING_VALUE' /* required */
            },
            SingleQueryArgument: {
              Name: 'STRING_VALUE' /* required */
            },
            UriPath: {
            }
          },
          PositionalConstraint: EXACTLY | STARTS_WITH | ENDS_WITH | CONTAINS | CONTAINS_WORD, /* required */
          SearchString: Buffer.from('...') || 'STRING_VALUE' /* Strings will be Base-64 encoded on your behalf */, /* required */
          TextTransformations: [ /* required */
            {
              Priority: 'NUMBER_VALUE', /* required */
              Type: NONE | COMPRESS_WHITE_SPACE | HTML_ENTITY_DECODE | LOWERCASE | CMD_LINE | URL_DECODE | BASE64_DECODE | HEX_DECODE | MD5 | REPLACE_COMMENTS | ESCAPE_SEQ_DECODE | SQL_HEX_DECODE | CSS_DECODE | JS_DECODE | NORMALIZE_PATH | NORMALIZE_PATH_WIN | REMOVE_NULLS | REPLACE_NULLS | BASE64_DECODE_EXT | URL_DECODE_UNI | UTF8_TO_UNICODE /* required */
            },
            /* more items */
          ]
        },
        GeoMatchStatement: {
          CountryCodes: [
            AF | AX | AL | DZ | AS | AD | AO | AI | AQ | AG | AR | AM | AW | AU | AT | AZ | BS | BH | BD | BB | BY | BE | BZ | BJ | BM | BT | BO | BQ | BA | BW | BV | BR | IO | BN | BG | BF | BI | KH | CM | CA | CV | KY | CF | TD | CL | CN | CX | CC | CO | KM | CG | CD | CK | CR | CI | HR | CU | CW | CY | CZ | DK | DJ | DM | DO | EC | EG | SV | GQ | ER | EE | ET | FK | FO | FJ | FI | FR | GF | PF | TF | GA | GM | GE | DE | GH | GI | GR | GL | GD | GP | GU | GT | GG | GN | GW | GY | HT | HM | VA | HN | HK | HU | IS | IN | ID | IR | IQ | IE | IM | IL | IT | JM | JP | JE | JO | KZ | KE | KI | KP | KR | KW | KG | LA | LV | LB | LS | LR | LY | LI | LT | LU | MO | MK | MG | MW | MY | MV | ML | MT | MH | MQ | MR | MU | YT | MX | FM | MD | MC | MN | ME | MS | MA | MZ | MM | NA | NR | NP | NL | NC | NZ | NI | NE | NG | NU | NF | MP | NO | OM | PK | PW | PS | PA | PG | PY | PE | PH | PN | PL | PT | PR | QA | RE | RO | RU | RW | BL | SH | KN | LC | MF | PM | VC | WS | SM | ST | SA | SN | RS | SC | SL | SG | SX | SK | SI | SB | SO | ZA | GS | SS | ES | LK | SD | SR | SJ | SZ | SE | CH | SY | TW | TJ | TZ | TH | TL | TG | TK | TO | TT | TN | TR | TM | TC | TV | UG | UA | AE | GB | US | UM | UY | UZ | VU | VE | VN | VG | VI | WF | EH | YE | ZM | ZW,
            /* more items */
          ],
          ForwardedIPConfig: {
            FallbackBehavior: MATCH | NO_MATCH, /* required */
            HeaderName: 'STRING_VALUE' /* required */
          }
        },
        IPSetReferenceStatement: {
          ARN: 'STRING_VALUE', /* required */
          IPSetForwardedIPConfig: {
            FallbackBehavior: MATCH | NO_MATCH, /* required */
            HeaderName: 'STRING_VALUE', /* required */
            Position: FIRST | LAST | ANY /* required */
          }
        },
        LabelMatchStatement: {
          Key: 'STRING_VALUE', /* required */
          Scope: LABEL | NAMESPACE /* required */
        },
        ManagedRuleGroupStatement: {
          Name: 'STRING_VALUE', /* required */
          VendorName: 'STRING_VALUE', /* required */
          ExcludedRules: [
            {
              Name: 'STRING_VALUE' /* required */
            },
            /* more items */
          ],
          ScopeDownStatement: /* recursive Statement */,
          Version: 'STRING_VALUE'
        },
        NotStatement: {
          Statement: /* recursive Statement */
        },
        OrStatement: {
          Statements: [ /* required */
            /* recursive Statement */,
            /* more items */
          ]
        },
        RateBasedStatement: {
          AggregateKeyType: IP | FORWARDED_IP, /* required */
          Limit: 'NUMBER_VALUE', /* required */
          ForwardedIPConfig: {
            FallbackBehavior: MATCH | NO_MATCH, /* required */
            HeaderName: 'STRING_VALUE' /* required */
          },
          ScopeDownStatement: /* recursive Statement */
        },
        RegexMatchStatement: {
          FieldToMatch: { /* required */
            AllQueryArguments: {
            },
            Body: {
            },
            JsonBody: {
              MatchPattern: { /* required */
                All: {
                },
                IncludedPaths: [
                  'STRING_VALUE',
                  /* more items */
                ]
              },
              MatchScope: ALL | KEY | VALUE, /* required */
              InvalidFallbackBehavior: MATCH | NO_MATCH | EVALUATE_AS_STRING
            },
            Method: {
            },
            QueryString: {
            },
            SingleHeader: {
              Name: 'STRING_VALUE' /* required */
            },
            SingleQueryArgument: {
              Name: 'STRING_VALUE' /* required */
            },
            UriPath: {
            }
          },
          RegexString: 'STRING_VALUE', /* required */
          TextTransformations: [ /* required */
            {
              Priority: 'NUMBER_VALUE', /* required */
              Type: NONE | COMPRESS_WHITE_SPACE | HTML_ENTITY_DECODE | LOWERCASE | CMD_LINE | URL_DECODE | BASE64_DECODE | HEX_DECODE | MD5 | REPLACE_COMMENTS | ESCAPE_SEQ_DECODE | SQL_HEX_DECODE | CSS_DECODE | JS_DECODE | NORMALIZE_PATH | NORMALIZE_PATH_WIN | REMOVE_NULLS | REPLACE_NULLS | BASE64_DECODE_EXT | URL_DECODE_UNI | UTF8_TO_UNICODE /* required */
            },
            /* more items */
          ]
        },
        RegexPatternSetReferenceStatement: {
          ARN: 'STRING_VALUE', /* required */
          FieldToMatch: { /* required */
            AllQueryArguments: {
            },
            Body: {
            },
            JsonBody: {
              MatchPattern: { /* required */
                All: {
                },
                IncludedPaths: [
                  'STRING_VALUE',
                  /* more items */
                ]
              },
              MatchScope: ALL | KEY | VALUE, /* required */
              InvalidFallbackBehavior: MATCH | NO_MATCH | EVALUATE_AS_STRING
            },
            Method: {
            },
            QueryString: {
            },
            SingleHeader: {
              Name: 'STRING_VALUE' /* required */
            },
            SingleQueryArgument: {
              Name: 'STRING_VALUE' /* required */
            },
            UriPath: {
            }
          },
          TextTransformations: [ /* required */
            {
              Priority: 'NUMBER_VALUE', /* required */
              Type: NONE | COMPRESS_WHITE_SPACE | HTML_ENTITY_DECODE | LOWERCASE | CMD_LINE | URL_DECODE | BASE64_DECODE | HEX_DECODE | MD5 | REPLACE_COMMENTS | ESCAPE_SEQ_DECODE | SQL_HEX_DECODE | CSS_DECODE | JS_DECODE | NORMALIZE_PATH | NORMALIZE_PATH_WIN | REMOVE_NULLS | REPLACE_NULLS | BASE64_DECODE_EXT | URL_DECODE_UNI | UTF8_TO_UNICODE /* required */
            },
            /* more items */
          ]
        },
        RuleGroupReferenceStatement: {
          ARN: 'STRING_VALUE', /* required */
          ExcludedRules: [
            {
              Name: 'STRING_VALUE' /* required */
            },
            /* more items */
          ]
        },
        SizeConstraintStatement: {
          ComparisonOperator: EQ | NE | LE | LT | GE | GT, /* required */
          FieldToMatch: { /* required */
            AllQueryArguments: {
            },
            Body: {
            },
            JsonBody: {
              MatchPattern: { /* required */
                All: {
                },
                IncludedPaths: [
                  'STRING_VALUE',
                  /* more items */
                ]
              },
              MatchScope: ALL | KEY | VALUE, /* required */
              InvalidFallbackBehavior: MATCH | NO_MATCH | EVALUATE_AS_STRING
            },
            Method: {
            },
            QueryString: {
            },
            SingleHeader: {
              Name: 'STRING_VALUE' /* required */
            },
            SingleQueryArgument: {
              Name: 'STRING_VALUE' /* required */
            },
            UriPath: {
            }
          },
          Size: 'NUMBER_VALUE', /* required */
          TextTransformations: [ /* required */
            {
              Priority: 'NUMBER_VALUE', /* required */
              Type: NONE | COMPRESS_WHITE_SPACE | HTML_ENTITY_DECODE | LOWERCASE | CMD_LINE | URL_DECODE | BASE64_DECODE | HEX_DECODE | MD5 | REPLACE_COMMENTS | ESCAPE_SEQ_DECODE | SQL_HEX_DECODE | CSS_DECODE | JS_DECODE | NORMALIZE_PATH | NORMALIZE_PATH_WIN | REMOVE_NULLS | REPLACE_NULLS | BASE64_DECODE_EXT | URL_DECODE_UNI | UTF8_TO_UNICODE /* required */
            },
            /* more items */
          ]
        },
        SqliMatchStatement: {
          FieldToMatch: { /* required */
            AllQueryArguments: {
            },
            Body: {
            },
            JsonBody: {
              MatchPattern: { /* required */
                All: {
                },
                IncludedPaths: [
                  'STRING_VALUE',
                  /* more items */
                ]
              },
              MatchScope: ALL | KEY | VALUE, /* required */
              InvalidFallbackBehavior: MATCH | NO_MATCH | EVALUATE_AS_STRING
            },
            Method: {
            },
            QueryString: {
            },
            SingleHeader: {
              Name: 'STRING_VALUE' /* required */
            },
            SingleQueryArgument: {
              Name: 'STRING_VALUE' /* required */
            },
            UriPath: {
            }
          },
          TextTransformations: [ /* required */
            {
              Priority: 'NUMBER_VALUE', /* required */
              Type: NONE | COMPRESS_WHITE_SPACE | HTML_ENTITY_DECODE | LOWERCASE | CMD_LINE | URL_DECODE | BASE64_DECODE | HEX_DECODE | MD5 | REPLACE_COMMENTS | ESCAPE_SEQ_DECODE | SQL_HEX_DECODE | CSS_DECODE | JS_DECODE | NORMALIZE_PATH | NORMALIZE_PATH_WIN | REMOVE_NULLS | REPLACE_NULLS | BASE64_DECODE_EXT | URL_DECODE_UNI | UTF8_TO_UNICODE /* required */
            },
            /* more items */
          ]
        },
        XssMatchStatement: {
          FieldToMatch: { /* required */
            AllQueryArguments: {
            },
            Body: {
            },
            JsonBody: {
              MatchPattern: { /* required */
                All: {
                },
                IncludedPaths: [
                  'STRING_VALUE',
                  /* more items */
                ]
              },
              MatchScope: ALL | KEY | VALUE, /* required */
              InvalidFallbackBehavior: MATCH | NO_MATCH | EVALUATE_AS_STRING
            },
            Method: {
            },
            QueryString: {
            },
            SingleHeader: {
              Name: 'STRING_VALUE' /* required */
            },
            SingleQueryArgument: {
              Name: 'STRING_VALUE' /* required */
            },
            UriPath: {
            }
          },
          TextTransformations: [ /* required */
            {
              Priority: 'NUMBER_VALUE', /* required */
              Type: NONE | COMPRESS_WHITE_SPACE | HTML_ENTITY_DECODE | LOWERCASE | CMD_LINE | URL_DECODE | BASE64_DECODE | HEX_DECODE | MD5 | REPLACE_COMMENTS | ESCAPE_SEQ_DECODE | SQL_HEX_DECODE | CSS_DECODE | JS_DECODE | NORMALIZE_PATH | NORMALIZE_PATH_WIN | REMOVE_NULLS | REPLACE_NULLS | BASE64_DECODE_EXT | URL_DECODE_UNI | UTF8_TO_UNICODE /* required */
            },
            /* more items */
          ]
        }
      },
      VisibilityConfig: { /* required */
        CloudWatchMetricsEnabled: true || false, /* required */
        MetricName: 'STRING_VALUE', /* required */
        SampledRequestsEnabled: true || false /* required */
      },
      Action: {
        Allow: {
          CustomRequestHandling: {
            InsertHeaders: [ /* required */
              {
                Name: 'STRING_VALUE', /* required */
                Value: 'STRING_VALUE' /* required */
              },
              /* more items */
            ]
          }
        },
        Block: {
          CustomResponse: {
            ResponseCode: 'NUMBER_VALUE', /* required */
            CustomResponseBodyKey: 'STRING_VALUE',
            ResponseHeaders: [
              {
                Name: 'STRING_VALUE', /* required */
                Value: 'STRING_VALUE' /* required */
              },
              /* more items */
            ]
          }
        },
        Captcha: {
          CustomRequestHandling: {
            InsertHeaders: [ /* required */
              {
                Name: 'STRING_VALUE', /* required */
                Value: 'STRING_VALUE' /* required */
              },
              /* more items */
            ]
          }
        },
        Count: {
          CustomRequestHandling: {
            InsertHeaders: [ /* required */
              {
                Name: 'STRING_VALUE', /* required */
                Value: 'STRING_VALUE' /* required */
              },
              /* more items */
            ]
          }
        }
      },
      CaptchaConfig: {
        ImmunityTimeProperty: {
          ImmunityTime: 'NUMBER_VALUE' /* required */
        }
      },
      OverrideAction: {
        Count: {
          CustomRequestHandling: {
            InsertHeaders: [ /* required */
              {
                Name: 'STRING_VALUE', /* required */
                Value: 'STRING_VALUE' /* required */
              },
              /* more items */
            ]
          }
        },
        None: {
        }
      },
      RuleLabels: [
        {
          Name: 'STRING_VALUE' /* required */
        },
        /* more items */
      ]
    },
    /* more items */
  ]
};
wafv2.updateRuleGroup(params, function(err, data) {
  if (err) console.log(err, err.stack); // an error occurred
  else     console.log(data);           // successful response
});

Parameters:

  • params (Object) (defaults to: {}) —
    • Name — (String)

      The name of the rule group. You cannot change the name of a rule group after you create it.

    • Scope — (String)

      Specifies whether this is for an Amazon CloudFront distribution or for a regional application. A regional application can be an Application Load Balancer (ALB), an Amazon API Gateway REST API, or an AppSync GraphQL API.

      To work with CloudFront, you must also specify the Region US East (N. Virginia) as follows:

      • CLI - Specify the Region when you use the CloudFront scope: --scope=CLOUDFRONT --region=us-east-1.

      • API and SDKs - For all calls, use the Region endpoint us-east-1.

      Possible values include:
      • "CLOUDFRONT"
      • "REGIONAL"
    • Id — (String)

      A unique identifier for the rule group. This ID is returned in the responses to create and list commands. You provide it to operations like update and delete.

    • Description — (String)

      A description of the rule group that helps with identification.

    • Rules — (Array<map>)

      The Rule statements used to identify the web requests that you want to allow, block, or count. Each rule includes one top-level statement that WAF uses to identify matching web requests, and parameters that govern how WAF handles them.

      • Name — required — (String)

        The name of the rule. You can't change the name of a Rule after you create it.

      • Priority — required — (Integer)

        If you define more than one Rule in a WebACL, WAF evaluates each request against the Rules in order based on the value of Priority. WAF processes rules with lower priority first. The priorities don't need to be consecutive, but they must all be different.

      • Statement — required — (map)

        The WAF processing statement for the rule, for example ByteMatchStatement or SizeConstraintStatement.

        • ByteMatchStatement — (map)

          A rule statement that defines a string match search for WAF to apply to web requests. The byte match statement provides the bytes to search for, the location in requests that you want WAF to search, and other settings. The bytes to search for are typically a string that corresponds with ASCII characters. In the WAF console and the developer guide, this is refered to as a string match statement.

          • SearchString — required — (Buffer, Typed Array, Blob, String)

            A string value that you want WAF to search for. WAF searches only in the part of web requests that you designate for inspection in FieldToMatch. The maximum length of the value is 50 bytes.

            Valid values depend on the component that you specify for inspection in FieldToMatch:

            • Method: The HTTP method that you want WAF to search for. This indicates the type of operation specified in the request.

            • UriPath: The value that you want WAF to search for in the URI path, for example, /images/daily-ad.jpg.

            If SearchString includes alphabetic characters A-Z and a-z, note that the value is case sensitive.

            If you're using the WAF API

            Specify a base64-encoded version of the value. The maximum length of the value before you base64-encode it is 50 bytes.

            For example, suppose the value of Type is HEADER and the value of Data is User-Agent. If you want to search the User-Agent header for the value BadBot, you base64-encode BadBot using MIME base64-encoding and include the resulting value, QmFkQm90, in the value of SearchString.

            If you're using the CLI or one of the Amazon Web Services SDKs

            The value that you want WAF to search for. The SDK automatically base64 encodes the value.

          • FieldToMatch — required — (map)

            The part of a web request that you want WAF to inspect. For more information, see FieldToMatch.

            • SingleHeader — (map)

              Inspect a single header. Provide the name of the header to inspect, for example, User-Agent or Referer. This setting isn't case sensitive.

              Example JSON: "SingleHeader": { "Name": "haystack" }

              • Name — required — (String)

                The name of the query header to inspect.

            • SingleQueryArgument — (map)

              Inspect a single query argument. Provide the name of the query argument to inspect, such as UserName or SalesRegion. The name can be up to 30 characters long and isn't case sensitive.

              This is used only to indicate the web request component for WAF to inspect, in the FieldToMatch specification.

              Example JSON: "SingleQueryArgument": { "Name": "myArgument" }

              • Name — required — (String)

                The name of the query argument to inspect.

            • AllQueryArguments — (map)

              Inspect all query arguments.

            • UriPath — (map)

              Inspect the request URI path. This is the part of a web request that identifies a resource, for example, /images/daily-ad.jpg.

            • QueryString — (map)

              Inspect the query string. This is the part of a URL that appears after a ? character, if any.

            • Body — (map)

              Inspect the request body as plain text. The request body immediately follows the request headers. This is the part of a request that contains any additional data that you want to send to your web server as the HTTP request body, such as data from a form.

              Note that only the first 8 KB (8192 bytes) of the request body are forwarded to WAF for inspection by the underlying host service. If you don't need to inspect more than 8 KB, you can guarantee that you don't allow additional bytes in by combining a statement that inspects the body of the web request, such as ByteMatchStatement or RegexPatternSetReferenceStatement, with a SizeConstraintStatement that enforces an 8 KB size limit on the body of the request. WAF doesn't support inspecting the entire contents of web requests whose bodies exceed the 8 KB limit.

            • Method — (map)

              Inspect the HTTP method. The method indicates the type of operation that the request is asking the origin to perform.

            • JsonBody — (map)

              Inspect the request body as JSON. The request body immediately follows the request headers. This is the part of a request that contains any additional data that you want to send to your web server as the HTTP request body, such as data from a form.

              Note that only the first 8 KB (8192 bytes) of the request body are forwarded to WAF for inspection by the underlying host service. If you don't need to inspect more than 8 KB, you can guarantee that you don't allow additional bytes in by combining a statement that inspects the body of the web request, such as ByteMatchStatement or RegexPatternSetReferenceStatement, with a SizeConstraintStatement that enforces an 8 KB size limit on the body of the request. WAF doesn't support inspecting the entire contents of web requests whose bodies exceed the 8 KB limit.

              • MatchPattern — required — (map)

                The patterns to look for in the JSON body. WAF inspects the results of these pattern matches against the rule inspection criteria.

                • All — (map)

                  Match all of the elements. See also MatchScope in JsonBody.

                  You must specify either this setting or the IncludedPaths setting, but not both.

                • IncludedPaths — (Array<String>)

                  Match only the specified include paths. See also MatchScope in JsonBody.

                  Provide the include paths using JSON Pointer syntax. For example, "IncludedPaths": ["/dogs/0/name", "/dogs/1/name"]. For information about this syntax, see the Internet Engineering Task Force (IETF) documentation JavaScript Object Notation (JSON) Pointer.

                  You must specify either this setting or the All setting, but not both.

                  Note: Don't use this option to include all paths. Instead, use the All setting.
              • MatchScope — required — (String)

                The parts of the JSON to match against using the MatchPattern. If you specify All, WAF matches against keys and values.

                Possible values include:
                • "ALL"
                • "KEY"
                • "VALUE"
              • InvalidFallbackBehavior — (String)

                What WAF should do if it fails to completely parse the JSON body. The options are the following:

                • EVALUATE_AS_STRING - Inspect the body as plain text. WAF applies the text transformations and inspection criteria that you defined for the JSON inspection to the body text string.

                • MATCH - Treat the web request as matching the rule statement. WAF applies the rule action to the request.

                • NO_MATCH - Treat the web request as not matching the rule statement.

                If you don't provide this setting, WAF parses and evaluates the content only up to the first parsing failure that it encounters.

                WAF does its best to parse the entire JSON body, but might be forced to stop for reasons such as invalid characters, duplicate keys, truncation, and any content whose root node isn't an object or an array.

                WAF parses the JSON in the following examples as two valid key, value pairs:

                • Missing comma: {"key1":"value1""key2":"value2"}

                • Missing colon: {"key1":"value1","key2""value2"}

                • Extra colons: {"key1"::"value1","key2""value2"}

                Possible values include:
                • "MATCH"
                • "NO_MATCH"
                • "EVALUATE_AS_STRING"
          • TextTransformations — required — (Array<map>)

            Text transformations eliminate some of the unusual formatting that attackers use in web requests in an effort to bypass detection. If you specify one or more transformations in a rule statement, WAF performs all transformations on the content of the request component identified by FieldToMatch, starting from the lowest priority setting, before inspecting the content for a match.

            • Priority — required — (Integer)

              Sets the relative processing order for multiple transformations that are defined for a rule statement. WAF processes all transformations, from lowest priority to highest, before inspecting the transformed content. The priorities don't need to be consecutive, but they must all be different.

            • Type — required — (String)

              You can specify the following transformation types:

              BASE64_DECODE - Decode a Base64-encoded string.

              BASE64_DECODE_EXT - Decode a Base64-encoded string, but use a forgiving implementation that ignores characters that aren't valid.

              CMD_LINE - Command-line transformations. These are helpful in reducing effectiveness of attackers who inject an operating system command-line command and use unusual formatting to disguise some or all of the command.

              • Delete the following characters: \ " ' ^

              • Delete spaces before the following characters: / (

              • Replace the following characters with a space: , ;

              • Replace multiple spaces with one space

              • Convert uppercase letters (A-Z) to lowercase (a-z)

              COMPRESS_WHITE_SPACE - Replace these characters with a space character (decimal 32):

              • \f, formfeed, decimal 12

              • \t, tab, decimal 9

              • \n, newline, decimal 10

              • \r, carriage return, decimal 13

              • \v, vertical tab, decimal 11

              • Non-breaking space, decimal 160

              COMPRESS_WHITE_SPACE also replaces multiple spaces with one space.

              CSS_DECODE - Decode characters that were encoded using CSS 2.x escape rules syndata.html#characters. This function uses up to two bytes in the decoding process, so it can help to uncover ASCII characters that were encoded using CSS encoding that wouldn’t typically be encoded. It's also useful in countering evasion, which is a combination of a backslash and non-hexadecimal characters. For example, ja\vascript for javascript.

              ESCAPE_SEQ_DECODE - Decode the following ANSI C escape sequences: \a, \b, \f, \n, \r, \t, \v, \, \?, \', \", \xHH (hexadecimal), \0OOO (octal). Encodings that aren't valid remain in the output.

              HEX_DECODE - Decode a string of hexadecimal characters into a binary.

              HTML_ENTITY_DECODE - Replace HTML-encoded characters with unencoded characters. HTML_ENTITY_DECODE performs these operations:

              • Replaces (ampersand)quot; with "

              • Replaces (ampersand)nbsp; with a non-breaking space, decimal 160

              • Replaces (ampersand)lt; with a "less than" symbol

              • Replaces (ampersand)gt; with >

              • Replaces characters that are represented in hexadecimal format, (ampersand)#xhhhh;, with the corresponding characters

              • Replaces characters that are represented in decimal format, (ampersand)#nnnn;, with the corresponding characters

              JS_DECODE - Decode JavaScript escape sequences. If a \ u HHHH code is in the full-width ASCII code range of FF01-FF5E, then the higher byte is used to detect and adjust the lower byte. If not, only the lower byte is used and the higher byte is zeroed, causing a possible loss of information.

              LOWERCASE - Convert uppercase letters (A-Z) to lowercase (a-z).

              MD5 - Calculate an MD5 hash from the data in the input. The computed hash is in a raw binary form.

              NONE - Specify NONE if you don't want any text transformations.

              NORMALIZE_PATH - Remove multiple slashes, directory self-references, and directory back-references that are not at the beginning of the input from an input string.

              NORMALIZE_PATH_WIN - This is the same as NORMALIZE_PATH, but first converts backslash characters to forward slashes.

              REMOVE_NULLS - Remove all NULL bytes from the input.

              REPLACE_COMMENTS - Replace each occurrence of a C-style comment (/* ... */) with a single space. Multiple consecutive occurrences are not compressed. Unterminated comments are also replaced with a space (ASCII 0x20). However, a standalone termination of a comment (*/) is not acted upon.

              REPLACE_NULLS - Replace NULL bytes in the input with space characters (ASCII 0x20).

              SQL_HEX_DECODE - Decode SQL hex data. Example (0x414243) will be decoded to (ABC).

              URL_DECODE - Decode a URL-encoded value.

              URL_DECODE_UNI - Like URL_DECODE, but with support for Microsoft-specific %u encoding. If the code is in the full-width ASCII code range of FF01-FF5E, the higher byte is used to detect and adjust the lower byte. Otherwise, only the lower byte is used and the higher byte is zeroed.

              UTF8_TO_UNICODE - Convert all UTF-8 character sequences to Unicode. This helps input normalization, and minimizing false-positives and false-negatives for non-English languages.

              Possible values include:
              • "NONE"
              • "COMPRESS_WHITE_SPACE"
              • "HTML_ENTITY_DECODE"
              • "LOWERCASE"
              • "CMD_LINE"
              • "URL_DECODE"
              • "BASE64_DECODE"
              • "HEX_DECODE"
              • "MD5"
              • "REPLACE_COMMENTS"
              • "ESCAPE_SEQ_DECODE"
              • "SQL_HEX_DECODE"
              • "CSS_DECODE"
              • "JS_DECODE"
              • "NORMALIZE_PATH"
              • "NORMALIZE_PATH_WIN"
              • "REMOVE_NULLS"
              • "REPLACE_NULLS"
              • "BASE64_DECODE_EXT"
              • "URL_DECODE_UNI"
              • "UTF8_TO_UNICODE"
          • PositionalConstraint — required — (String)

            The area within the portion of a web request that you want WAF to search for SearchString. Valid values include the following:

            CONTAINS

            The specified part of the web request must include the value of SearchString, but the location doesn't matter.

            CONTAINS_WORD

            The specified part of the web request must include the value of SearchString, and SearchString must contain only alphanumeric characters or underscore (A-Z, a-z, 0-9, or ). In addition, SearchString must be a word, which means that both of the following are true:

            • SearchString is at the beginning of the specified part of the web request or is preceded by a character other than an alphanumeric character or underscore (). Examples include the value of a header and ;BadBot.

            • SearchString is at the end of the specified part of the web request or is followed by a character other than an alphanumeric character or underscore (_), for example, BadBot; and -BadBot;.

            EXACTLY

            The value of the specified part of the web request must exactly match the value of SearchString.

            STARTS_WITH

            The value of SearchString must appear at the beginning of the specified part of the web request.

            ENDS_WITH

            The value of SearchString must appear at the end of the specified part of the web request.

            Possible values include:
            • "EXACTLY"
            • "STARTS_WITH"
            • "ENDS_WITH"
            • "CONTAINS"
            • "CONTAINS_WORD"
        • SqliMatchStatement — (map)

          Attackers sometimes insert malicious SQL code into web requests in an effort to extract data from your database. To allow or block web requests that appear to contain malicious SQL code, create one or more SQL injection match conditions. An SQL injection match condition identifies the part of web requests, such as the URI or the query string, that you want WAF to inspect. Later in the process, when you create a web ACL, you specify whether to allow or block requests that appear to contain malicious SQL code.

          • FieldToMatch — required — (map)

            The part of a web request that you want WAF to inspect. For more information, see FieldToMatch.

            • SingleHeader — (map)

              Inspect a single header. Provide the name of the header to inspect, for example, User-Agent or Referer. This setting isn't case sensitive.

              Example JSON: "SingleHeader": { "Name": "haystack" }

              • Name — required — (String)

                The name of the query header to inspect.

            • SingleQueryArgument — (map)

              Inspect a single query argument. Provide the name of the query argument to inspect, such as UserName or SalesRegion. The name can be up to 30 characters long and isn't case sensitive.

              This is used only to indicate the web request component for WAF to inspect, in the FieldToMatch specification.

              Example JSON: "SingleQueryArgument": { "Name": "myArgument" }

              • Name — required — (String)

                The name of the query argument to inspect.

            • AllQueryArguments — (map)

              Inspect all query arguments.

            • UriPath — (map)

              Inspect the request URI path. This is the part of a web request that identifies a resource, for example, /images/daily-ad.jpg.

            • QueryString — (map)

              Inspect the query string. This is the part of a URL that appears after a ? character, if any.

            • Body — (map)

              Inspect the request body as plain text. The request body immediately follows the request headers. This is the part of a request that contains any additional data that you want to send to your web server as the HTTP request body, such as data from a form.

              Note that only the first 8 KB (8192 bytes) of the request body are forwarded to WAF for inspection by the underlying host service. If you don't need to inspect more than 8 KB, you can guarantee that you don't allow additional bytes in by combining a statement that inspects the body of the web request, such as ByteMatchStatement or RegexPatternSetReferenceStatement, with a SizeConstraintStatement that enforces an 8 KB size limit on the body of the request. WAF doesn't support inspecting the entire contents of web requests whose bodies exceed the 8 KB limit.

            • Method — (map)

              Inspect the HTTP method. The method indicates the type of operation that the request is asking the origin to perform.

            • JsonBody — (map)

              Inspect the request body as JSON. The request body immediately follows the request headers. This is the part of a request that contains any additional data that you want to send to your web server as the HTTP request body, such as data from a form.

              Note that only the first 8 KB (8192 bytes) of the request body are forwarded to WAF for inspection by the underlying host service. If you don't need to inspect more than 8 KB, you can guarantee that you don't allow additional bytes in by combining a statement that inspects the body of the web request, such as ByteMatchStatement or RegexPatternSetReferenceStatement, with a SizeConstraintStatement that enforces an 8 KB size limit on the body of the request. WAF doesn't support inspecting the entire contents of web requests whose bodies exceed the 8 KB limit.

              • MatchPattern — required — (map)

                The patterns to look for in the JSON body. WAF inspects the results of these pattern matches against the rule inspection criteria.

                • All — (map)

                  Match all of the elements. See also MatchScope in JsonBody.

                  You must specify either this setting or the IncludedPaths setting, but not both.

                • IncludedPaths — (Array<String>)

                  Match only the specified include paths. See also MatchScope in JsonBody.

                  Provide the include paths using JSON Pointer syntax. For example, "IncludedPaths": ["/dogs/0/name", "/dogs/1/name"]. For information about this syntax, see the Internet Engineering Task Force (IETF) documentation JavaScript Object Notation (JSON) Pointer.

                  You must specify either this setting or the All setting, but not both.

                  Note: Don't use this option to include all paths. Instead, use the All setting.
              • MatchScope — required — (String)

                The parts of the JSON to match against using the MatchPattern. If you specify All, WAF matches against keys and values.

                Possible values include:
                • "ALL"
                • "KEY"
                • "VALUE"
              • InvalidFallbackBehavior — (String)

                What WAF should do if it fails to completely parse the JSON body. The options are the following:

                • EVALUATE_AS_STRING - Inspect the body as plain text. WAF applies the text transformations and inspection criteria that you defined for the JSON inspection to the body text string.

                • MATCH - Treat the web request as matching the rule statement. WAF applies the rule action to the request.

                • NO_MATCH - Treat the web request as not matching the rule statement.

                If you don't provide this setting, WAF parses and evaluates the content only up to the first parsing failure that it encounters.

                WAF does its best to parse the entire JSON body, but might be forced to stop for reasons such as invalid characters, duplicate keys, truncation, and any content whose root node isn't an object or an array.

                WAF parses the JSON in the following examples as two valid key, value pairs:

                • Missing comma: {"key1":"value1""key2":"value2"}

                • Missing colon: {"key1":"value1","key2""value2"}

                • Extra colons: {"key1"::"value1","key2""value2"}

                Possible values include:
                • "MATCH"
                • "NO_MATCH"
                • "EVALUATE_AS_STRING"
          • TextTransformations — required — (Array<map>)

            Text transformations eliminate some of the unusual formatting that attackers use in web requests in an effort to bypass detection. If you specify one or more transformations in a rule statement, WAF performs all transformations on the content of the request component identified by FieldToMatch, starting from the lowest priority setting, before inspecting the content for a match.

            • Priority — required — (Integer)

              Sets the relative processing order for multiple transformations that are defined for a rule statement. WAF processes all transformations, from lowest priority to highest, before inspecting the transformed content. The priorities don't need to be consecutive, but they must all be different.

            • Type — required — (String)

              You can specify the following transformation types:

              BASE64_DECODE - Decode a Base64-encoded string.

              BASE64_DECODE_EXT - Decode a Base64-encoded string, but use a forgiving implementation that ignores characters that aren't valid.

              CMD_LINE - Command-line transformations. These are helpful in reducing effectiveness of attackers who inject an operating system command-line command and use unusual formatting to disguise some or all of the command.

              • Delete the following characters: \ " ' ^

              • Delete spaces before the following characters: / (

              • Replace the following characters with a space: , ;

              • Replace multiple spaces with one space

              • Convert uppercase letters (A-Z) to lowercase (a-z)

              COMPRESS_WHITE_SPACE - Replace these characters with a space character (decimal 32):

              • \f, formfeed, decimal 12

              • \t, tab, decimal 9

              • \n, newline, decimal 10

              • \r, carriage return, decimal 13

              • \v, vertical tab, decimal 11

              • Non-breaking space, decimal 160

              COMPRESS_WHITE_SPACE also replaces multiple spaces with one space.

              CSS_DECODE - Decode characters that were encoded using CSS 2.x escape rules syndata.html#characters. This function uses up to two bytes in the decoding process, so it can help to uncover ASCII characters that were encoded using CSS encoding that wouldn’t typically be encoded. It's also useful in countering evasion, which is a combination of a backslash and non-hexadecimal characters. For example, ja\vascript for javascript.

              ESCAPE_SEQ_DECODE - Decode the following ANSI C escape sequences: \a, \b, \f, \n, \r, \t, \v, \, \?, \', \", \xHH (hexadecimal), \0OOO (octal). Encodings that aren't valid remain in the output.

              HEX_DECODE - Decode a string of hexadecimal characters into a binary.

              HTML_ENTITY_DECODE - Replace HTML-encoded characters with unencoded characters. HTML_ENTITY_DECODE performs these operations:

              • Replaces (ampersand)quot; with "

              • Replaces (ampersand)nbsp; with a non-breaking space, decimal 160

              • Replaces (ampersand)lt; with a "less than" symbol

              • Replaces (ampersand)gt; with >

              • Replaces characters that are represented in hexadecimal format, (ampersand)#xhhhh;, with the corresponding characters

              • Replaces characters that are represented in decimal format, (ampersand)#nnnn;, with the corresponding characters

              JS_DECODE - Decode JavaScript escape sequences. If a \ u HHHH code is in the full-width ASCII code range of FF01-FF5E, then the higher byte is used to detect and adjust the lower byte. If not, only the lower byte is used and the higher byte is zeroed, causing a possible loss of information.

              LOWERCASE - Convert uppercase letters (A-Z) to lowercase (a-z).

              MD5 - Calculate an MD5 hash from the data in the input. The computed hash is in a raw binary form.

              NONE - Specify NONE if you don't want any text transformations.

              NORMALIZE_PATH - Remove multiple slashes, directory self-references, and directory back-references that are not at the beginning of the input from an input string.

              NORMALIZE_PATH_WIN - This is the same as NORMALIZE_PATH, but first converts backslash characters to forward slashes.

              REMOVE_NULLS - Remove all NULL bytes from the input.

              REPLACE_COMMENTS - Replace each occurrence of a C-style comment (/* ... */) with a single space. Multiple consecutive occurrences are not compressed. Unterminated comments are also replaced with a space (ASCII 0x20). However, a standalone termination of a comment (*/) is not acted upon.

              REPLACE_NULLS - Replace NULL bytes in the input with space characters (ASCII 0x20).

              SQL_HEX_DECODE - Decode SQL hex data. Example (0x414243) will be decoded to (ABC).

              URL_DECODE - Decode a URL-encoded value.

              URL_DECODE_UNI - Like URL_DECODE, but with support for Microsoft-specific %u encoding. If the code is in the full-width ASCII code range of FF01-FF5E, the higher byte is used to detect and adjust the lower byte. Otherwise, only the lower byte is used and the higher byte is zeroed.

              UTF8_TO_UNICODE - Convert all UTF-8 character sequences to Unicode. This helps input normalization, and minimizing false-positives and false-negatives for non-English languages.

              Possible values include:
              • "NONE"
              • "COMPRESS_WHITE_SPACE"
              • "HTML_ENTITY_DECODE"
              • "LOWERCASE"
              • "CMD_LINE"
              • "URL_DECODE"
              • "BASE64_DECODE"
              • "HEX_DECODE"
              • "MD5"
              • "REPLACE_COMMENTS"
              • "ESCAPE_SEQ_DECODE"
              • "SQL_HEX_DECODE"
              • "CSS_DECODE"
              • "JS_DECODE"
              • "NORMALIZE_PATH"
              • "NORMALIZE_PATH_WIN"
              • "REMOVE_NULLS"
              • "REPLACE_NULLS"
              • "BASE64_DECODE_EXT"
              • "URL_DECODE_UNI"
              • "UTF8_TO_UNICODE"
        • XssMatchStatement — (map)

          A rule statement that defines a cross-site scripting (XSS) match search for WAF to apply to web requests. XSS attacks are those where the attacker uses vulnerabilities in a benign website as a vehicle to inject malicious client-site scripts into other legitimate web browsers. The XSS match statement provides the location in requests that you want WAF to search and text transformations to use on the search area before WAF searches for character sequences that are likely to be malicious strings.

          • FieldToMatch — required — (map)

            The part of a web request that you want WAF to inspect. For more information, see FieldToMatch.

            • SingleHeader — (map)

              Inspect a single header. Provide the name of the header to inspect, for example, User-Agent or Referer. This setting isn't case sensitive.

              Example JSON: "SingleHeader": { "Name": "haystack" }

              • Name — required — (String)

                The name of the query header to inspect.

            • SingleQueryArgument — (map)

              Inspect a single query argument. Provide the name of the query argument to inspect, such as UserName or SalesRegion. The name can be up to 30 characters long and isn't case sensitive.

              This is used only to indicate the web request component for WAF to inspect, in the FieldToMatch specification.

              Example JSON: "SingleQueryArgument": { "Name": "myArgument" }

              • Name — required — (String)

                The name of the query argument to inspect.

            • AllQueryArguments — (map)

              Inspect all query arguments.

            • UriPath — (map)

              Inspect the request URI path. This is the part of a web request that identifies a resource, for example, /images/daily-ad.jpg.

            • QueryString — (map)

              Inspect the query string. This is the part of a URL that appears after a ? character, if any.

            • Body — (map)

              Inspect the request body as plain text. The request body immediately follows the request headers. This is the part of a request that contains any additional data that you want to send to your web server as the HTTP request body, such as data from a form.

              Note that only the first 8 KB (8192 bytes) of the request body are forwarded to WAF for inspection by the underlying host service. If you don't need to inspect more than 8 KB, you can guarantee that you don't allow additional bytes in by combining a statement that inspects the body of the web request, such as ByteMatchStatement or RegexPatternSetReferenceStatement, with a SizeConstraintStatement that enforces an 8 KB size limit on the body of the request. WAF doesn't support inspecting the entire contents of web requests whose bodies exceed the 8 KB limit.

            • Method — (map)

              Inspect the HTTP method. The method indicates the type of operation that the request is asking the origin to perform.

            • JsonBody — (map)

              Inspect the request body as JSON. The request body immediately follows the request headers. This is the part of a request that contains any additional data that you want to send to your web server as the HTTP request body, such as data from a form.

              Note that only the first 8 KB (8192 bytes) of the request body are forwarded to WAF for inspection by the underlying host service. If you don't need to inspect more than 8 KB, you can guarantee that you don't allow additional bytes in by combining a statement that inspects the body of the web request, such as ByteMatchStatement or RegexPatternSetReferenceStatement, with a SizeConstraintStatement that enforces an 8 KB size limit on the body of the request. WAF doesn't support inspecting the entire contents of web requests whose bodies exceed the 8 KB limit.

              • MatchPattern — required — (map)

                The patterns to look for in the JSON body. WAF inspects the results of these pattern matches against the rule inspection criteria.

                • All — (map)

                  Match all of the elements. See also MatchScope in JsonBody.

                  You must specify either this setting or the IncludedPaths setting, but not both.

                • IncludedPaths — (Array<String>)

                  Match only the specified include paths. See also MatchScope in JsonBody.

                  Provide the include paths using JSON Pointer syntax. For example, "IncludedPaths": ["/dogs/0/name", "/dogs/1/name"]. For information about this syntax, see the Internet Engineering Task Force (IETF) documentation JavaScript Object Notation (JSON) Pointer.

                  You must specify either this setting or the All setting, but not both.

                  Note: Don't use this option to include all paths. Instead, use the All setting.
              • MatchScope — required — (String)

                The parts of the JSON to match against using the MatchPattern. If you specify All, WAF matches against keys and values.

                Possible values include:
                • "ALL"
                • "KEY"
                • "VALUE"
              • InvalidFallbackBehavior — (String)

                What WAF should do if it fails to completely parse the JSON body. The options are the following:

                • EVALUATE_AS_STRING - Inspect the body as plain text. WAF applies the text transformations and inspection criteria that you defined for the JSON inspection to the body text string.

                • MATCH - Treat the web request as matching the rule statement. WAF applies the rule action to the request.

                • NO_MATCH - Treat the web request as not matching the rule statement.

                If you don't provide this setting, WAF parses and evaluates the content only up to the first parsing failure that it encounters.

                WAF does its best to parse the entire JSON body, but might be forced to stop for reasons such as invalid characters, duplicate keys, truncation, and any content whose root node isn't an object or an array.

                WAF parses the JSON in the following examples as two valid key, value pairs:

                • Missing comma: {"key1":"value1""key2":"value2"}

                • Missing colon: {"key1":"value1","key2""value2"}

                • Extra colons: {"key1"::"value1","key2""value2"}

                Possible values include:
                • "MATCH"
                • "NO_MATCH"
                • "EVALUATE_AS_STRING"
          • TextTransformations — required — (Array<map>)

            Text transformations eliminate some of the unusual formatting that attackers use in web requests in an effort to bypass detection. If you specify one or more transformations in a rule statement, WAF performs all transformations on the content of the request component identified by FieldToMatch, starting from the lowest priority setting, before inspecting the content for a match.

            • Priority — required — (Integer)

              Sets the relative processing order for multiple transformations that are defined for a rule statement. WAF processes all transformations, from lowest priority to highest, before inspecting the transformed content. The priorities don't need to be consecutive, but they must all be different.

            • Type — required — (String)

              You can specify the following transformation types:

              BASE64_DECODE - Decode a Base64-encoded string.

              BASE64_DECODE_EXT - Decode a Base64-encoded string, but use a forgiving implementation that ignores characters that aren't valid.

              CMD_LINE - Command-line transformations. These are helpful in reducing effectiveness of attackers who inject an operating system command-line command and use unusual formatting to disguise some or all of the command.

              • Delete the following characters: \ " ' ^

              • Delete spaces before the following characters: / (

              • Replace the following characters with a space: , ;

              • Replace multiple spaces with one space

              • Convert uppercase letters (A-Z) to lowercase (a-z)

              COMPRESS_WHITE_SPACE - Replace these characters with a space character (decimal 32):

              • \f, formfeed, decimal 12

              • \t, tab, decimal 9

              • \n, newline, decimal 10

              • \r, carriage return, decimal 13

              • \v, vertical tab, decimal 11

              • Non-breaking space, decimal 160

              COMPRESS_WHITE_SPACE also replaces multiple spaces with one space.

              CSS_DECODE - Decode characters that were encoded using CSS 2.x escape rules syndata.html#characters. This function uses up to two bytes in the decoding process, so it can help to uncover ASCII characters that were encoded using CSS encoding that wouldn’t typically be encoded. It's also useful in countering evasion, which is a combination of a backslash and non-hexadecimal characters. For example, ja\vascript for javascript.

              ESCAPE_SEQ_DECODE - Decode the following ANSI C escape sequences: \a, \b, \f, \n, \r, \t, \v, \, \?, \', \", \xHH (hexadecimal), \0OOO (octal). Encodings that aren't valid remain in the output.

              HEX_DECODE - Decode a string of hexadecimal characters into a binary.

              HTML_ENTITY_DECODE - Replace HTML-encoded characters with unencoded characters. HTML_ENTITY_DECODE performs these operations:

              • Replaces (ampersand)quot; with "

              • Replaces (ampersand)nbsp; with a non-breaking space, decimal 160

              • Replaces (ampersand)lt; with a "less than" symbol

              • Replaces (ampersand)gt; with >

              • Replaces characters that are represented in hexadecimal format, (ampersand)#xhhhh;, with the corresponding characters

              • Replaces characters that are represented in decimal format, (ampersand)#nnnn;, with the corresponding characters

              JS_DECODE - Decode JavaScript escape sequences. If a \ u HHHH code is in the full-width ASCII code range of FF01-FF5E, then the higher byte is used to detect and adjust the lower byte. If not, only the lower byte is used and the higher byte is zeroed, causing a possible loss of information.

              LOWERCASE - Convert uppercase letters (A-Z) to lowercase (a-z).

              MD5 - Calculate an MD5 hash from the data in the input. The computed hash is in a raw binary form.

              NONE - Specify NONE if you don't want any text transformations.

              NORMALIZE_PATH - Remove multiple slashes, directory self-references, and directory back-references that are not at the beginning of the input from an input string.

              NORMALIZE_PATH_WIN - This is the same as NORMALIZE_PATH, but first converts backslash characters to forward slashes.

              REMOVE_NULLS - Remove all NULL bytes from the input.

              REPLACE_COMMENTS - Replace each occurrence of a C-style comment (/* ... */) with a single space. Multiple consecutive occurrences are not compressed. Unterminated comments are also replaced with a space (ASCII 0x20). However, a standalone termination of a comment (*/) is not acted upon.

              REPLACE_NULLS - Replace NULL bytes in the input with space characters (ASCII 0x20).

              SQL_HEX_DECODE - Decode SQL hex data. Example (0x414243) will be decoded to (ABC).

              URL_DECODE - Decode a URL-encoded value.

              URL_DECODE_UNI - Like URL_DECODE, but with support for Microsoft-specific %u encoding. If the code is in the full-width ASCII code range of FF01-FF5E, the higher byte is used to detect and adjust the lower byte. Otherwise, only the lower byte is used and the higher byte is zeroed.

              UTF8_TO_UNICODE - Convert all UTF-8 character sequences to Unicode. This helps input normalization, and minimizing false-positives and false-negatives for non-English languages.

              Possible values include:
              • "NONE"
              • "COMPRESS_WHITE_SPACE"
              • "HTML_ENTITY_DECODE"
              • "LOWERCASE"
              • "CMD_LINE"
              • "URL_DECODE"
              • "BASE64_DECODE"
              • "HEX_DECODE"
              • "MD5"
              • "REPLACE_COMMENTS"
              • "ESCAPE_SEQ_DECODE"
              • "SQL_HEX_DECODE"
              • "CSS_DECODE"
              • "JS_DECODE"
              • "NORMALIZE_PATH"
              • "NORMALIZE_PATH_WIN"
              • "REMOVE_NULLS"
              • "REPLACE_NULLS"
              • "BASE64_DECODE_EXT"
              • "URL_DECODE_UNI"
              • "UTF8_TO_UNICODE"
        • SizeConstraintStatement — (map)

          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 first 8192 bytes (8 KB). If the request body for your web requests never exceeds 8192 bytes, you can create a size constraint condition and block requests that have a request body greater than 8192 bytes.

          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.

          • FieldToMatch — required — (map)

            The part of a web request that you want WAF to inspect. For more information, see FieldToMatch.

            • SingleHeader — (map)

              Inspect a single header. Provide the name of the header to inspect, for example, User-Agent or Referer. This setting isn't case sensitive.

              Example JSON: "SingleHeader": { "Name": "haystack" }

              • Name — required — (String)

                The name of the query header to inspect.

            • SingleQueryArgument — (map)

              Inspect a single query argument. Provide the name of the query argument to inspect, such as UserName or SalesRegion. The name can be up to 30 characters long and isn't case sensitive.

              This is used only to indicate the web request component for WAF to inspect, in the FieldToMatch specification.

              Example JSON: "SingleQueryArgument": { "Name": "myArgument" }

              • Name — required — (String)

                The name of the query argument to inspect.

            • AllQueryArguments — (map)

              Inspect all query arguments.

            • UriPath — (map)

              Inspect the request URI path. This is the part of a web request that identifies a resource, for example, /images/daily-ad.jpg.

            • QueryString — (map)

              Inspect the query string. This is the part of a URL that appears after a ? character, if any.

            • Body — (map)

              Inspect the request body as plain text. The request body immediately follows the request headers. This is the part of a request that contains any additional data that you want to send to your web server as the HTTP request body, such as data from a form.

              Note that only the first 8 KB (8192 bytes) of the request body are forwarded to WAF for inspection by the underlying host service. If you don't need to inspect more than 8 KB, you can guarantee that you don't allow additional bytes in by combining a statement that inspects the body of the web request, such as ByteMatchStatement or RegexPatternSetReferenceStatement, with a SizeConstraintStatement that enforces an 8 KB size limit on the body of the request. WAF doesn't support inspecting the entire contents of web requests whose bodies exceed the 8 KB limit.

            • Method — (map)

              Inspect the HTTP method. The method indicates the type of operation that the request is asking the origin to perform.

            • JsonBody — (map)

              Inspect the request body as JSON. The request body immediately follows the request headers. This is the part of a request that contains any additional data that you want to send to your web server as the HTTP request body, such as data from a form.

              Note that only the first 8 KB (8192 bytes) of the request body are forwarded to WAF for inspection by the underlying host service. If you don't need to inspect more than 8 KB, you can guarantee that you don't allow additional bytes in by combining a statement that inspects the body of the web request, such as ByteMatchStatement or RegexPatternSetReferenceStatement, with a SizeConstraintStatement that enforces an 8 KB size limit on the body of the request. WAF doesn't support inspecting the entire contents of web requests whose bodies exceed the 8 KB limit.

              • MatchPattern — required — (map)

                The patterns to look for in the JSON body. WAF inspects the results of these pattern matches against the rule inspection criteria.

                • All — (map)

                  Match all of the elements. See also MatchScope in JsonBody.

                  You must specify either this setting or the IncludedPaths setting, but not both.

                • IncludedPaths — (Array<String>)

                  Match only the specified include paths. See also MatchScope in JsonBody.

                  Provide the include paths using JSON Pointer syntax. For example, "IncludedPaths": ["/dogs/0/name", "/dogs/1/name"]. For information about this syntax, see the Internet Engineering Task Force (IETF) documentation JavaScript Object Notation (JSON) Pointer.

                  You must specify either this setting or the All setting, but not both.

                  Note: Don't use this option to include all paths. Instead, use the All setting.
              • MatchScope — required — (String)

                The parts of the JSON to match against using the MatchPattern. If you specify All, WAF matches against keys and values.

                Possible values include:
                • "ALL"
                • "KEY"
                • "VALUE"
              • InvalidFallbackBehavior — (String)

                What WAF should do if it fails to completely parse the JSON body. The options are the following:

                • EVALUATE_AS_STRING - Inspect the body as plain text. WAF applies the text transformations and inspection criteria that you defined for the JSON inspection to the body text string.

                • MATCH - Treat the web request as matching the rule statement. WAF applies the rule action to the request.

                • NO_MATCH - Treat the web request as not matching the rule statement.

                If you don't provide this setting, WAF parses and evaluates the content only up to the first parsing failure that it encounters.

                WAF does its best to parse the entire JSON body, but might be forced to stop for reasons such as invalid characters, duplicate keys, truncation, and any content whose root node isn't an object or an array.

                WAF parses the JSON in the following examples as two valid key, value pairs:

                • Missing comma: {"key1":"value1""key2":"value2"}

                • Missing colon: {"key1":"value1","key2""value2"}

                • Extra colons: {"key1"::"value1","key2""value2"}

                Possible values include:
                • "MATCH"
                • "NO_MATCH"
                • "EVALUATE_AS_STRING"
          • ComparisonOperator — required — (String)

            The operator to use to compare the request part to the size setting.

            Possible values include:
            • "EQ"
            • "NE"
            • "LE"
            • "LT"
            • "GE"
            • "GT"
          • Size — required — (Integer)

            The size, in byte, to compare to the request part, after any transformations.

          • TextTransformations — required — (Array<map>)

            Text transformations eliminate some of the unusual formatting that attackers use in web requests in an effort to bypass detection. If you specify one or more transformations in a rule statement, WAF performs all transformations on the content of the request component identified by FieldToMatch, starting from the lowest priority setting, before inspecting the content for a match.

            • Priority — required — (Integer)

              Sets the relative processing order for multiple transformations that are defined for a rule statement. WAF processes all transformations, from lowest priority to highest, before inspecting the transformed content. The priorities don't need to be consecutive, but they must all be different.

            • Type — required — (String)

              You can specify the following transformation types:

              BASE64_DECODE - Decode a Base64-encoded string.

              BASE64_DECODE_EXT - Decode a Base64-encoded string, but use a forgiving implementation that ignores characters that aren't valid.

              CMD_LINE - Command-line transformations. These are helpful in reducing effectiveness of attackers who inject an operating system command-line command and use unusual formatting to disguise some or all of the command.

              • Delete the following characters: \ " ' ^

              • Delete spaces before the following characters: / (

              • Replace the following characters with a space: , ;

              • Replace multiple spaces with one space

              • Convert uppercase letters (A-Z) to lowercase (a-z)

              COMPRESS_WHITE_SPACE - Replace these characters with a space character (decimal 32):

              • \f, formfeed, decimal 12

              • \t, tab, decimal 9

              • \n, newline, decimal 10

              • \r, carriage return, decimal 13

              • \v, vertical tab, decimal 11

              • Non-breaking space, decimal 160

              COMPRESS_WHITE_SPACE also replaces multiple spaces with one space.

              CSS_DECODE - Decode characters that were encoded using CSS 2.x escape rules syndata.html#characters. This function uses up to two bytes in the decoding process, so it can help to uncover ASCII characters that were encoded using CSS encoding that wouldn’t typically be encoded. It's also useful in countering evasion, which is a combination of a backslash and non-hexadecimal characters. For example, ja\vascript for javascript.

              ESCAPE_SEQ_DECODE - Decode the following ANSI C escape sequences: \a, \b, \f, \n, \r, \t, \v, \, \?, \', \", \xHH (hexadecimal), \0OOO (octal). Encodings that aren't valid remain in the output.

              HEX_DECODE - Decode a string of hexadecimal characters into a binary.

              HTML_ENTITY_DECODE - Replace HTML-encoded characters with unencoded characters. HTML_ENTITY_DECODE performs these operations:

              • Replaces (ampersand)quot; with "

              • Replaces (ampersand)nbsp; with a non-breaking space, decimal 160

              • Replaces (ampersand)lt; with a "less than" symbol

              • Replaces (ampersand)gt; with >

              • Replaces characters that are represented in hexadecimal format, (ampersand)#xhhhh;, with the corresponding characters

              • Replaces characters that are represented in decimal format, (ampersand)#nnnn;, with the corresponding characters

              JS_DECODE - Decode JavaScript escape sequences. If a \ u HHHH code is in the full-width ASCII code range of FF01-FF5E, then the higher byte is used to detect and adjust the lower byte. If not, only the lower byte is used and the higher byte is zeroed, causing a possible loss of information.

              LOWERCASE - Convert uppercase letters (A-Z) to lowercase (a-z).

              MD5 - Calculate an MD5 hash from the data in the input. The computed hash is in a raw binary form.

              NONE - Specify NONE if you don't want any text transformations.

              NORMALIZE_PATH - Remove multiple slashes, directory self-references, and directory back-references that are not at the beginning of the input from an input string.

              NORMALIZE_PATH_WIN - This is the same as NORMALIZE_PATH, but first converts backslash characters to forward slashes.

              REMOVE_NULLS - Remove all NULL bytes from the input.

              REPLACE_COMMENTS - Replace each occurrence of a C-style comment (/* ... */) with a single space. Multiple consecutive occurrences are not compressed. Unterminated comments are also replaced with a space (ASCII 0x20). However, a standalone termination of a comment (*/) is not acted upon.

              REPLACE_NULLS - Replace NULL bytes in the input with space characters (ASCII 0x20).

              SQL_HEX_DECODE - Decode SQL hex data. Example (0x414243) will be decoded to (ABC).

              URL_DECODE - Decode a URL-encoded value.

              URL_DECODE_UNI - Like URL_DECODE, but with support for Microsoft-specific %u encoding. If the code is in the full-width ASCII code range of FF01-FF5E, the higher byte is used to detect and adjust the lower byte. Otherwise, only the lower byte is used and the higher byte is zeroed.

              UTF8_TO_UNICODE - Convert all UTF-8 character sequences to Unicode. This helps input normalization, and minimizing false-positives and false-negatives for non-English languages.

              Possible values include:
              • "NONE"
              • "COMPRESS_WHITE_SPACE"
              • "HTML_ENTITY_DECODE"
              • "LOWERCASE"
              • "CMD_LINE"
              • "URL_DECODE"
              • "BASE64_DECODE"
              • "HEX_DECODE"
              • "MD5"
              • "REPLACE_COMMENTS"
              • "ESCAPE_SEQ_DECODE"
              • "SQL_HEX_DECODE"
              • "CSS_DECODE"
              • "JS_DECODE"
              • "NORMALIZE_PATH"
              • "NORMALIZE_PATH_WIN"
              • "REMOVE_NULLS"
              • "REPLACE_NULLS"
              • "BASE64_DECODE_EXT"
              • "URL_DECODE_UNI"
              • "UTF8_TO_UNICODE"
        • GeoMatchStatement — (map)

          A rule statement used to identify web requests based on country of origin.

          • CountryCodes — (Array<String>)

            An array of two-character country codes, for example, [ "US", "CN" ], from the alpha-2 country ISO codes of the ISO 3166 international standard.

          • ForwardedIPConfig — (map)

            The configuration for inspecting IP addresses in an HTTP header that you specify, instead of using the IP address that's reported by the web request origin. Commonly, this is the X-Forwarded-For (XFF) header, but you can specify any header name.

            Note: If the specified header isn't present in the request, WAF doesn't apply the rule to the web request at all.
            • HeaderName — required — (String)

              The name of the HTTP header to use for the IP address. For example, to use the X-Forwarded-For (XFF) header, set this to X-Forwarded-For.

              Note: If the specified header isn't present in the request, WAF doesn't apply the rule to the web request at all.
            • FallbackBehavior — required — (String)

              The match status to assign to the web request if the request doesn't have a valid IP address in the specified position.

              Note: If the specified header isn't present in the request, WAF doesn't apply the rule to the web request at all.

              You can specify the following fallback behaviors:

              • MATCH - Treat the web request as matching the rule statement. WAF applies the rule action to the request.

              • NO_MATCH - Treat the web request as not matching the rule statement.

              Possible values include:
              • "MATCH"
              • "NO_MATCH"
        • RuleGroupReferenceStatement — (map)

          A rule statement used to run the rules that are defined in a RuleGroup. To use this, create a rule group with your rules, then provide the ARN of the rule group in this statement.

          You cannot nest a RuleGroupReferenceStatement, for example for use inside a NotStatement or OrStatement. You can only use a rule group reference statement at the top level inside a web ACL.

          • ARN — required — (String)

            The Amazon Resource Name (ARN) of the entity.

          • ExcludedRules — (Array<map>)

            The rules in the referenced rule group whose actions are set to Count. When you exclude a rule, WAF evaluates it exactly as it would if the rule action setting were Count. This is a useful option for testing the rules in a rule group without modifying how they handle your web traffic.

            • Name — required — (String)

              The name of the rule whose action you want to override to Count.

        • IPSetReferenceStatement — (map)

          A rule statement used to detect web requests coming from particular IP addresses or address ranges. To use this, create an IPSet that specifies the addresses you want to detect, then use the ARN of that set in this statement. To create an IP set, see CreateIPSet.

          Each IP set rule statement references an IP set. You create and maintain the set independent of your rules. This allows you to use the single set in multiple rules. When you update the referenced set, WAF automatically updates all rules that reference it.

          • ARN — required — (String)

            The Amazon Resource Name (ARN) of the IPSet that this statement references.

          • IPSetForwardedIPConfig — (map)

            The configuration for inspecting IP addresses in an HTTP header that you specify, instead of using the IP address that's reported by the web request origin. Commonly, this is the X-Forwarded-For (XFF) header, but you can specify any header name.

            Note: If the specified header isn't present in the request, WAF doesn't apply the rule to the web request at all.
            • HeaderName — required — (String)

              The name of the HTTP header to use for the IP address. For example, to use the X-Forwarded-For (XFF) header, set this to X-Forwarded-For.

              Note: If the specified header isn't present in the request, WAF doesn't apply the rule to the web request at all.
            • FallbackBehavior — required — (String)

              The match status to assign to the web request if the request doesn't have a valid IP address in the specified position.

              Note: If the specified header isn't present in the request, WAF doesn't apply the rule to the web request at all.

              You can specify the following fallback behaviors:

              • MATCH - Treat the web request as matching the rule statement. WAF applies the rule action to the request.

              • NO_MATCH - Treat the web request as not matching the rule statement.

              Possible values include:
              • "MATCH"
              • "NO_MATCH"
            • Position — required — (String)

              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:

              • FIRST - Inspect the first IP address in the list of IP addresses in the header. This is usually the client's original IP.

              • LAST - Inspect the last IP address in the list of IP addresses in the header.

              • ANY - Inspect all IP addresses in the header for a match. If the header contains more than 10 IP addresses, WAF inspects the last 10.

              Possible values include:
              • "FIRST"
              • "LAST"
              • "ANY"
        • RegexPatternSetReferenceStatement — (map)

          A rule statement used to search web request components for matches with regular expressions. To use this, create a RegexPatternSet that specifies the expressions that you want to detect, then use the ARN of that set in this statement. A web request matches the pattern set rule statement if the request component matches any of the patterns in the set. To create a regex pattern set, see CreateRegexPatternSet.

          Each regex pattern set rule statement references a regex pattern set. You create and maintain the set independent of your rules. This allows you to use the single set in multiple rules. When you update the referenced set, WAF automatically updates all rules that reference it.

          • ARN — required — (String)

            The Amazon Resource Name (ARN) of the RegexPatternSet that this statement references.

          • FieldToMatch — required — (map)

            The part of a web request that you want WAF to inspect. For more information, see FieldToMatch.

            • SingleHeader — (map)

              Inspect a single header. Provide the name of the header to inspect, for example, User-Agent or Referer. This setting isn't case sensitive.

              Example JSON: "SingleHeader": { "Name": "haystack" }

              • Name — required — (String)

                The name of the query header to inspect.

            • SingleQueryArgument — (map)

              Inspect a single query argument. Provide the name of the query argument to inspect, such as UserName or SalesRegion. The name can be up to 30 characters long and isn't case sensitive.

              This is used only to indicate the web request component for WAF to inspect, in the FieldToMatch specification.

              Example JSON: "SingleQueryArgument": { "Name": "myArgument" }

              • Name — required — (String)

                The name of the query argument to inspect.

            • AllQueryArguments — (map)

              Inspect all query arguments.

            • UriPath — (map)

              Inspect the request URI path. This is the part of a web request that identifies a resource, for example, /images/daily-ad.jpg.

            • QueryString — (map)

              Inspect the query string. This is the part of a URL that appears after a ? character, if any.

            • Body — (map)

              Inspect the request body as plain text. The request body immediately follows the request headers. This is the part of a request that contains any additional data that you want to send to your web server as the HTTP request body, such as data from a form.

              Note that only the first 8 KB (8192 bytes) of the request body are forwarded to WAF for inspection by the underlying host service. If you don't need to inspect more than 8 KB, you can guarantee that you don't allow additional bytes in by combining a statement that inspects the body of the web request, such as ByteMatchStatement or RegexPatternSetReferenceStatement, with a SizeConstraintStatement that enforces an 8 KB size limit on the body of the request. WAF doesn't support inspecting the entire contents of web requests whose bodies exceed the 8 KB limit.

            • Method — (map)

              Inspect the HTTP method. The method indicates the type of operation that the request is asking the origin to perform.

            • JsonBody — (map)

              Inspect the request body as JSON. The request body immediately follows the request headers. This is the part of a request that contains any additional data that you want to send to your web server as the HTTP request body, such as data from a form.

              Note that only the first 8 KB (8192 bytes) of the request body are forwarded to WAF for inspection by the underlying host service. If you don't need to inspect more than 8 KB, you can guarantee that you don't allow additional bytes in by combining a statement that inspects the body of the web request, such as ByteMatchStatement or RegexPatternSetReferenceStatement, with a SizeConstraintStatement that enforces an 8 KB size limit on the body of the request. WAF doesn't support inspecting the entire contents of web requests whose bodies exceed the 8 KB limit.

              • MatchPattern — required — (map)

                The patterns to look for in the JSON body. WAF inspects the results of these pattern matches against the rule inspection criteria.

                • All — (map)

                  Match all of the elements. See also MatchScope in JsonBody.

                  You must specify either this setting or the IncludedPaths setting, but not both.

                • IncludedPaths — (Array<String>)

                  Match only the specified include paths. See also MatchScope in JsonBody.

                  Provide the include paths using JSON Pointer syntax. For example, "IncludedPaths": ["/dogs/0/name", "/dogs/1/name"]. For information about this syntax, see the Internet Engineering Task Force (IETF) documentation JavaScript Object Notation (JSON) Pointer.

                  You must specify either this setting or the All setting, but not both.

                  Note: Don't use this option to include all paths. Instead, use the All setting.
              • MatchScope — required — (String)

                The parts of the JSON to match against using the MatchPattern. If you specify All, WAF matches against keys and values.

                Possible values include:
                • "ALL"
                • "KEY"
                • "VALUE"
              • InvalidFallbackBehavior — (String)

                What WAF should do if it fails to completely parse the JSON body. The options are the following:

                • EVALUATE_AS_STRING - Inspect the body as plain text. WAF applies the text transformations and inspection criteria that you defined for the JSON inspection to the body text string.

                • MATCH - Treat the web request as matching the rule statement. WAF applies the rule action to the request.

                • NO_MATCH - Treat the web request as not matching the rule statement.

                If you don't provide this setting, WAF parses and evaluates the content only up to the first parsing failure that it encounters.

                WAF does its best to parse the entire JSON body, but might be forced to stop for reasons such as invalid characters, duplicate keys, truncation, and any content whose root node isn't an object or an array.

                WAF parses the JSON in the following examples as two valid key, value pairs:

                • Missing comma: {"key1":"value1""key2":"value2"}

                • Missing colon: {"key1":"value1","key2""value2"}

                • Extra colons: {"key1"::"value1","key2""value2"}

                Possible values include:
                • "MATCH"
                • "NO_MATCH"
                • "EVALUATE_AS_STRING"
          • TextTransformations — required — (Array<map>)

            Text transformations eliminate some of the unusual formatting that attackers use in web requests in an effort to bypass detection. If you specify one or more transformations in a rule statement, WAF performs all transformations on the content of the request component identified by FieldToMatch, starting from the lowest priority setting, before inspecting the content for a match.

            • Priority — required — (Integer)

              Sets the relative processing order for multiple transformations that are defined for a rule statement. WAF processes all transformations, from lowest priority to highest, before inspecting the transformed content. The priorities don't need to be consecutive, but they must all be different.

            • Type — required — (String)

              You can specify the following transformation types:

              BASE64_DECODE - Decode a Base64-encoded string.

              BASE64_DECODE_EXT - Decode a Base64-encoded string, but use a forgiving implementation that ignores characters that aren't valid.

              CMD_LINE - Command-line transformations. These are helpful in reducing effectiveness of attackers who inject an operating system command-line command and use unusual formatting to disguise some or all of the command.

              • Delete the following characters: \ " ' ^

              • Delete spaces before the following characters: / (

              • Replace the following characters with a space: , ;

              • Replace multiple spaces with one space

              • Convert uppercase letters (A-Z) to lowercase (a-z)

              COMPRESS_WHITE_SPACE - Replace these characters with a space character (decimal 32):

              • \f, formfeed, decimal 12

              • \t, tab, decimal 9

              • \n, newline, decimal 10

              • \r, carriage return, decimal 13

              • \v, vertical tab, decimal 11

              • Non-breaking space, decimal 160

              COMPRESS_WHITE_SPACE also replaces multiple spaces with one space.

              CSS_DECODE - Decode characters that were encoded using CSS 2.x escape rules syndata.html#characters. This function uses up to two bytes in the decoding process, so it can help to uncover ASCII characters that were encoded using CSS encoding that wouldn’t typically be encoded. It's also useful in countering evasion, which is a combination of a backslash and non-hexadecimal characters. For example, ja\vascript for javascript.

              ESCAPE_SEQ_DECODE - Decode the following ANSI C escape sequences: \a, \b, \f, \n, \r, \t, \v, \, \?, \', \", \xHH (hexadecimal), \0OOO (octal). Encodings that aren't valid remain in the output.

              HEX_DECODE - Decode a string of hexadecimal characters into a binary.

              HTML_ENTITY_DECODE - Replace HTML-encoded characters with unencoded characters. HTML_ENTITY_DECODE performs these operations:

              • Replaces (ampersand)quot; with "

              • Replaces (ampersand)nbsp; with a non-breaking space, decimal 160

              • Replaces (ampersand)lt; with a "less than" symbol

              • Replaces (ampersand)gt; with >

              • Replaces characters that are represented in hexadecimal format, (ampersand)#xhhhh;, with the corresponding characters

              • Replaces characters that are represented in decimal format, (ampersand)#nnnn;, with the corresponding characters

              JS_DECODE - Decode JavaScript escape sequences. If a \ u HHHH code is in the full-width ASCII code range of FF01-FF5E, then the higher byte is used to detect and adjust the lower byte. If not, only the lower byte is used and the higher byte is zeroed, causing a possible loss of information.

              LOWERCASE - Convert uppercase letters (A-Z) to lowercase (a-z).

              MD5 - Calculate an MD5 hash from the data in the input. The computed hash is in a raw binary form.

              NONE - Specify NONE if you don't want any text transformations.

              NORMALIZE_PATH - Remove multiple slashes, directory self-references, and directory back-references that are not at the beginning of the input from an input string.

              NORMALIZE_PATH_WIN - This is the same as NORMALIZE_PATH, but first converts backslash characters to forward slashes.

              REMOVE_NULLS - Remove all NULL bytes from the input.

              REPLACE_COMMENTS - Replace each occurrence of a C-style comment (/* ... */) with a single space. Multiple consecutive occurrences are not compressed. Unterminated comments are also replaced with a space (ASCII 0x20). However, a standalone termination of a comment (*/) is not acted upon.

              REPLACE_NULLS - Replace NULL bytes in the input with space characters (ASCII 0x20).

              SQL_HEX_DECODE - Decode SQL hex data. Example (0x414243) will be decoded to (ABC).

              URL_DECODE - Decode a URL-encoded value.

              URL_DECODE_UNI - Like URL_DECODE, but with support for Microsoft-specific %u encoding. If the code is in the full-width ASCII code range of FF01-FF5E, the higher byte is used to detect and adjust the lower byte. Otherwise, only the lower byte is used and the higher byte is zeroed.

              UTF8_TO_UNICODE - Convert all UTF-8 character sequences to Unicode. This helps input normalization, and minimizing false-positives and false-negatives for non-English languages.

              Possible values include:
              • "NONE"
              • "COMPRESS_WHITE_SPACE"
              • "HTML_ENTITY_DECODE"
              • "LOWERCASE"
              • "CMD_LINE"
              • "URL_DECODE"
              • "BASE64_DECODE"
              • "HEX_DECODE"
              • "MD5"
              • "REPLACE_COMMENTS"
              • "ESCAPE_SEQ_DECODE"
              • "SQL_HEX_DECODE"
              • "CSS_DECODE"
              • "JS_DECODE"
              • "NORMALIZE_PATH"
              • "NORMALIZE_PATH_WIN"
              • "REMOVE_NULLS"
              • "REPLACE_NULLS"
              • "BASE64_DECODE_EXT"
              • "URL_DECODE_UNI"
              • "UTF8_TO_UNICODE"
        • RateBasedStatement — (map)

          A rate-based rule tracks the rate of requests for each originating IP address, and triggers the rule action when the rate exceeds a limit that you specify on the number of requests in any 5-minute time span. You can use this to put a temporary block on requests from an IP address that is sending excessive requests.

          WAF tracks and manages web requests separately for each instance of a rate-based rule that you use. For example, if you provide the same rate-based rule settings in two web ACLs, each of the two rule statements represents a separate instance of the rate-based rule and gets its own tracking and management by WAF. If you define a rate-based rule inside a rule group, and then use that rule group in multiple places, each use creates a separate instance of the rate-based rule that gets its own tracking and management by WAF.

          When the rule action triggers, WAF blocks additional requests from the IP address until the request rate falls below the limit.

          You can optionally nest another statement inside the rate-based statement, to narrow the scope of the rule so that it only counts requests that match the nested statement. For example, based on recent requests that you have seen from an attacker, you might create a rate-based rule with a nested AND rule statement that contains the following nested statements:

          • An IP match statement with an IP set that specified the address 192.0.2.44.

          • A string match statement that searches in the User-Agent header for the string BadBot.

          In this rate-based rule, you also define a rate limit. For this example, the rate limit is 1,000. Requests that meet both of the conditions in the statements are counted. If the count exceeds 1,000 requests per five minutes, the rule action triggers. Requests that do not meet both conditions are not counted towards the rate limit and are not affected by this rule.

          You cannot nest a RateBasedStatement inside another statement, for example inside a NotStatement or OrStatement. You can define a RateBasedStatement inside a web ACL and inside a rule group.

          • Limit — required — (Integer)

            The limit on requests per 5-minute period for a single originating IP address. If the statement includes a ScopeDownStatement, this limit is applied only to the requests that match the statement.

          • AggregateKeyType — required — (String)

            Setting that indicates how to aggregate the request counts. The options are the following:

            • IP - Aggregate the request counts on the IP address from the web request origin.

            • FORWARDED_IP - Aggregate the request counts on the first IP address in an HTTP header. If you use this, configure the ForwardedIPConfig, to specify the header to use.

            Possible values include:
            • "IP"
            • "FORWARDED_IP"
          • ForwardedIPConfig — (map)

            The configuration for inspecting IP addresses in an HTTP header that you specify, instead of using the IP address that's reported by the web request origin. Commonly, this is the X-Forwarded-For (XFF) header, but you can specify any header name.

            Note: If the specified header isn't present in the request, WAF doesn't apply the rule to the web request at all.

            This is required if AggregateKeyType is set to FORWARDED_IP.

            • HeaderName — required — (String)

              The name of the HTTP header to use for the IP address. For example, to use the X-Forwarded-For (XFF) header, set this to X-Forwarded-For.

              Note: If the specified header isn't present in the request, WAF doesn't apply the rule to the web request at all.
            • FallbackBehavior — required — (String)

              The match status to assign to the web request if the request doesn't have a valid IP address in the specified position.

              Note: If the specified header isn't present in the request, WAF doesn't apply the rule to the web request at all.

              You can specify the following fallback behaviors:

              • MATCH - Treat the web request as matching the rule statement. WAF applies the rule action to the request.

              • NO_MATCH - Treat the web request as not matching the rule statement.

              Possible values include:
              • "MATCH"
              • "NO_MATCH"
        • AndStatement — (map)

          A logical rule statement used to combine other rule statements with AND logic. You provide more than one Statement within the AndStatement.

          • Statements — required — (Array<map>)

            The statements to combine with AND logic. You can use any statements that can be nested.

        • OrStatement — (map)

          A logical rule statement used to combine other rule statements with OR logic. You provide more than one Statement within the OrStatement.

          • Statements — required — (Array<map>)

            The statements to combine with OR logic. You can use any statements that can be nested.

        • NotStatement — (map)

          A logical rule statement used to negate the results of another rule statement. You provide one Statement within the NotStatement.

        • ManagedRuleGroupStatement — (map)

          A rule statement used to run the rules that are defined in a managed rule group. To use this, provide the vendor name and the name of the rule group in this statement. You can retrieve the required names by calling ListAvailableManagedRuleGroups.

          You cannot nest a ManagedRuleGroupStatement, for example for use inside a NotStatement or OrStatement. It can only be referenced as a top-level statement within a rule.

          • VendorName — required — (String)

            The name of the managed rule group vendor. You use this, along with the rule group name, to identify the rule group.

          • Name — required — (String)

            The name of the managed rule group. You use this, along with the vendor name, to identify the rule group.

          • Version — (String)

            The version of the managed rule group to use. If you specify this, the version setting is fixed until you change it. If you don't specify this, WAF uses the vendor's default version, and then keeps the version at the vendor's default when the vendor updates the managed rule group settings.

          • ExcludedRules — (Array<map>)

            The rules in the referenced rule group whose actions are set to Count. When you exclude a rule, WAF evaluates it exactly as it would if the rule action setting were Count. This is a useful option for testing the rules in a rule group without modifying how they handle your web traffic.

            • Name — required — (String)

              The name of the rule whose action you want to override to Count.

        • LabelMatchStatement — (map)

          A rule statement that defines a string match search against labels that have been added to the web request by rules that have already run in the web ACL.

          The label match statement provides the label or namespace string to search for. The label string can represent a part or all of the fully qualified label name that had been added to the web request. Fully qualified labels have a prefix, optional namespaces, and label name. The prefix identifies the rule group or web ACL context of the rule that added the label. If you do not provide the fully qualified name in your label match string, WAF performs the search for labels that were added in the same context as the label match statement.

          • Scope — required — (String)

            Specify whether you want to match using the label name or just the namespace.

            Possible values include:
            • "LABEL"
            • "NAMESPACE"
          • Key — required — (String)

            The string to match against. The setting you provide for this depends on the match statement's Scope setting:

            • If the Scope indicates LABEL, then this specification must include the name and can include any number of preceding namespace specifications and prefix up to providing the fully qualified label name.

            • If the Scope indicates NAMESPACE, then this specification can include any number of contiguous namespace strings, and can include the entire label namespace prefix from the rule group or web ACL where the label originates.

            Labels are case sensitive and components of a label must be separated by colon, for example NS1:NS2:name.

        • RegexMatchStatement — (map)

          A rule statement used to search web request components for a match against a single regular expression.

          • RegexString — required — (String)

            The string representing the regular expression.

          • FieldToMatch — required — (map)

            The part of a web request that you want WAF to inspect. For more information, see FieldToMatch.

            • SingleHeader — (map)

              Inspect a single header. Provide the name of the header to inspect, for example, User-Agent or Referer. This setting isn't case sensitive.

              Example JSON: "SingleHeader": { "Name": "haystack" }

              • Name — required — (String)

                The name of the query header to inspect.

            • SingleQueryArgument — (map)

              Inspect a single query argument. Provide the name of the query argument to inspect, such as UserName or SalesRegion. The name can be up to 30 characters long and isn't case sensitive.

              This is used only to indicate the web request component for WAF to inspect, in the FieldToMatch specification.

              Example JSON: "SingleQueryArgument": { "Name": "myArgument" }

              • Name — required — (String)

                The name of the query argument to inspect.

            • AllQueryArguments — (map)

              Inspect all query arguments.

            • UriPath — (map)

              Inspect the request URI path. This is the part of a web request that identifies a resource, for example, /images/daily-ad.jpg.

            • QueryString — (map)

              Inspect the query string. This is the part of a URL that appears after a ? character, if any.

            • Body — (map)

              Inspect the request body as plain text. The request body immediately follows the request headers. This is the part of a request that contains any additional data that you want to send to your web server as the HTTP request body, such as data from a form.

              Note that only the first 8 KB (8192 bytes) of the request body are forwarded to WAF for inspection by the underlying host service. If you don't need to inspect more than 8 KB, you can guarantee that you don't allow additional bytes in by combining a statement that inspects the body of the web request, such as ByteMatchStatement or RegexPatternSetReferenceStatement, with a SizeConstraintStatement that enforces an 8 KB size limit on the body of the request. WAF doesn't support inspecting the entire contents of web requests whose bodies exceed the 8 KB limit.

            • Method — (map)

              Inspect the HTTP method. The method indicates the type of operation that the request is asking the origin to perform.

            • JsonBody — (map)

              Inspect the request body as JSON. The request body immediately follows the request headers. This is the part of a request that contains any additional data that you want to send to your web server as the HTTP request body, such as data from a form.

              Note that only the first 8 KB (8192 bytes) of the request body are forwarded to WAF for inspection by the underlying host service. If you don't need to inspect more than 8 KB, you can guarantee that you don't allow additional bytes in by combining a statement that inspects the body of the web request, such as ByteMatchStatement or RegexPatternSetReferenceStatement, with a SizeConstraintStatement that enforces an 8 KB size limit on the body of the request. WAF doesn't support inspecting the entire contents of web requests whose bodies exceed the 8 KB limit.

              • MatchPattern — required — (map)

                The patterns to look for in the JSON body. WAF inspects the results of these pattern matches against the rule inspection criteria.

                • All — (map)

                  Match all of the elements. See also MatchScope in JsonBody.

                  You must specify either this setting or the IncludedPaths setting, but not both.

                • IncludedPaths — (Array<String>)

                  Match only the specified include paths. See also MatchScope in JsonBody.

                  Provide the include paths using JSON Pointer syntax. For example, "IncludedPaths": ["/dogs/0/name", "/dogs/1/name"]. For information about this syntax, see the Internet Engineering Task Force (IETF) documentation JavaScript Object Notation (JSON) Pointer.

                  You must specify either this setting or the All setting, but not both.

                  Note: Don't use this option to include all paths. Instead, use the All setting.
              • MatchScope — required — (String)

                The parts of the JSON to match against using the MatchPattern. If you specify All, WAF matches against keys and values.

                Possible values include:
                • "ALL"
                • "KEY"
                • "VALUE"
              • InvalidFallbackBehavior — (String)

                What WAF should do if it fails to completely parse the JSON body. The options are the following:

                • EVALUATE_AS_STRING - Inspect the body as plain text. WAF applies the text transformations and inspection criteria that you defined for the JSON inspection to the body text string.

                • MATCH - Treat the web request as matching the rule statement. WAF applies the rule action to the request.

                • NO_MATCH - Treat the web request as not matching the rule statement.

                If you don't provide this setting, WAF parses and evaluates the content only up to the first parsing failure that it encounters.

                WAF does its best to parse the entire JSON body, but might be forced to stop for reasons such as invalid characters, duplicate keys, truncation, and any content whose root node isn't an object or an array.

                WAF parses the JSON in the following examples as two valid key, value pairs:

                • Missing comma: {"key1":"value1""key2":"value2"}

                • Missing colon: {"key1":"value1","key2""value2"}

                • Extra colons: {"key1"::"value1","key2""value2"}

                Possible values include:
                • "MATCH"
                • "NO_MATCH"
                • "EVALUATE_AS_STRING"
          • TextTransformations — required — (Array<map>)

            Text transformations eliminate some of the unusual formatting that attackers use in web requests in an effort to bypass detection. If you specify one or more transformations in a rule statement, WAF performs all transformations on the content of the request component identified by FieldToMatch, starting from the lowest priority setting, before inspecting the content for a match.

            • Priority — required — (Integer)

              Sets the relative processing order for multiple transformations that are defined for a rule statement. WAF processes all transformations, from lowest priority to highest, before inspecting the transformed content. The priorities don't need to be consecutive, but they must all be different.

            • Type — required — (String)

              You can specify the following transformation types:

              BASE64_DECODE - Decode a Base64-encoded string.

              BASE64_DECODE_EXT - Decode a Base64-encoded string, but use a forgiving implementation that ignores characters that aren't valid.

              CMD_LINE - Command-line transformations. These are helpful in reducing effectiveness of attackers who inject an operating system command-line command and use unusual formatting to disguise some or all of the command.

              • Delete the following characters: \ " ' ^

              • Delete spaces before the following characters: / (

              • Replace the following characters with a space: , ;

              • Replace multiple spaces with one space

              • Convert uppercase letters (A-Z) to lowercase (a-z)

              COMPRESS_WHITE_SPACE - Replace these characters with a space character (decimal 32):

              • \f, formfeed, decimal 12

              • \t, tab, decimal 9

              • \n, newline, decimal 10

              • \r, carriage return, decimal 13

              • \v, vertical tab, decimal 11

              • Non-breaking space, decimal 160

              COMPRESS_WHITE_SPACE also replaces multiple spaces with one space.

              CSS_DECODE - Decode characters that were encoded using CSS 2.x escape rules syndata.html#characters. This function uses up to two bytes in the decoding process, so it can help to uncover ASCII characters that were encoded using CSS encoding that wouldn’t typically be encoded. It's also useful in countering evasion, which is a combination of a backslash and non-hexadecimal characters. For example, ja\vascript for javascript.

              ESCAPE_SEQ_DECODE - Decode the following ANSI C escape sequences: \a, \b, \f, \n, \r, \t, \v, \, \?, \', \", \xHH (hexadecimal), \0OOO (octal). Encodings that aren't valid remain in the output.

              HEX_DECODE - Decode a string of hexadecimal characters into a binary.

              HTML_ENTITY_DECODE - Replace HTML-encoded characters with unencoded characters. HTML_ENTITY_DECODE performs these operations:

              • Replaces (ampersand)quot; with "

              • Replaces (ampersand)nbsp; with a non-breaking space, decimal 160

              • Replaces (ampersand)lt; with a "less than" symbol

              • Replaces (ampersand)gt; with >

              • Replaces characters that are represented in hexadecimal format, (ampersand)#xhhhh;, with the corresponding characters

              • Replaces characters that are represented in decimal format, (ampersand)#nnnn;, with the corresponding characters

              JS_DECODE - Decode JavaScript escape sequences. If a \ u HHHH code is in the full-width ASCII code range of FF01-FF5E, then the higher byte is used to detect and adjust the lower byte. If not, only the lower byte is used and the higher byte is zeroed, causing a possible loss of information.

              LOWERCASE - Convert uppercase letters (A-Z) to lowercase (a-z).

              MD5 - Calculate an MD5 hash from the data in the input. The computed hash is in a raw binary form.

              NONE - Specify NONE if you don't want any text transformations.

              NORMALIZE_PATH - Remove multiple slashes, directory self-references, and directory back-references that are not at the beginning of the input from an input string.

              NORMALIZE_PATH_WIN - This is the same as NORMALIZE_PATH, but first converts backslash characters to forward slashes.

              REMOVE_NULLS - Remove all NULL bytes from the input.

              REPLACE_COMMENTS - Replace each occurrence of a C-style comment (/* ... */) with a single space. Multiple consecutive occurrences are not compressed. Unterminated comments are also replaced with a space (ASCII 0x20). However, a standalone termination of a comment (*/) is not acted upon.

              REPLACE_NULLS - Replace NULL bytes in the input with space characters (ASCII 0x20).

              SQL_HEX_DECODE - Decode SQL hex data. Example (0x414243) will be decoded to (ABC).

              URL_DECODE - Decode a URL-encoded value.

              URL_DECODE_UNI - Like URL_DECODE, but with support for Microsoft-specific %u encoding. If the code is in the full-width ASCII code range of FF01-FF5E, the higher byte is used to detect and adjust the lower byte. Otherwise, only the lower byte is used and the higher byte is zeroed.

              UTF8_TO_UNICODE - Convert all UTF-8 character sequences to Unicode. This helps input normalization, and minimizing false-positives and false-negatives for non-English languages.

              Possible values include:
              • "NONE"
              • "COMPRESS_WHITE_SPACE"
              • "HTML_ENTITY_DECODE"
              • "LOWERCASE"
              • "CMD_LINE"
              • "URL_DECODE"
              • "BASE64_DECODE"
              • "HEX_DECODE"
              • "MD5"
              • "REPLACE_COMMENTS"
              • "ESCAPE_SEQ_DECODE"
              • "SQL_HEX_DECODE"
              • "CSS_DECODE"
              • "JS_DECODE"
              • "NORMALIZE_PATH"
              • "NORMALIZE_PATH_WIN"
              • "REMOVE_NULLS"
              • "REPLACE_NULLS"
              • "BASE64_DECODE_EXT"
              • "URL_DECODE_UNI"
              • "UTF8_TO_UNICODE"
      • Action — (map)

        The action that WAF should take on a web request when it matches the rule statement. Settings at the web ACL level can override the rule action setting.

        This is used only for rules whose statements do not reference a rule group. Rule statements that reference a rule group include RuleGroupReferenceStatement and ManagedRuleGroupStatement.

        You must specify either this Action setting or the rule OverrideAction setting, but not both:

        • If the rule statement does not reference a rule group, use this rule action setting and not the rule override action setting.

        • If the rule statement references a rule group, use the override action setting and not this action setting.

        • Block — (map)

          Instructs WAF to block the web request.

          • CustomResponse — (map)

            Defines a custom response for the web request.

            For information about customizing web requests and responses, see Customizing web requests and responses in WAF in the WAF Developer Guide.

            • ResponseCode — required — (Integer)

              The HTTP status code to return to the client.

              For a list of status codes that you can use in your custom reqponses, see Supported status codes for custom response in the WAF Developer Guide.

            • CustomResponseBodyKey — (String)

              References the response body that you want WAF to return to the web request client. You can define a custom response for a rule action or a default web ACL action that is set to block. To do this, you first define the response body key and value in the CustomResponseBodies setting for the WebACL or RuleGroup where you want to use it. Then, in the rule action or web ACL default action BlockAction setting, you reference the response body using this key.

            • ResponseHeaders — (Array<map>)

              The HTTP headers to use in the response. Duplicate header names are not allowed.

              For information about the limits on count and size for custom request and response settings, see WAF quotas in the WAF Developer Guide.

              • Name — required — (String)

                The name of the custom header.

                For custom request header insertion, when WAF inserts the header into the request, it prefixes this name x-amzn-waf-, to avoid confusion with the headers that are already in the request. For example, for the header name sample, WAF inserts the header x-amzn-waf-sample.

              • Value — required — (String)

                The value of the custom header.

        • Allow — (map)

          Instructs WAF to allow the web request.

          • CustomRequestHandling — (map)

            Defines custom handling for the web request.

            For information about customizing web requests and responses, see Customizing web requests and responses in WAF in the WAF Developer Guide.

            • InsertHeaders — required — (Array<map>)

              The HTTP headers to insert into the request. Duplicate header names are not allowed.

              For information about the limits on count and size for custom request and response settings, see WAF quotas in the WAF Developer Guide.

              • Name — required — (String)

                The name of the custom header.

                For custom request header insertion, when WAF inserts the header into the request, it prefixes this name x-amzn-waf-, to avoid confusion with the headers that are already in the request. For example, for the header name sample, WAF inserts the header x-amzn-waf-sample.

              • Value — required — (String)

                The value of the custom header.

        • Count — (map)

          Instructs WAF to count the web request and allow it.

          • CustomRequestHandling — (map)

            Defines custom handling for the web request.

            For information about customizing web requests and responses, see Customizing web requests and responses in WAF in the WAF Developer Guide.

            • InsertHeaders — required — (Array<map>)

              The HTTP headers to insert into the request. Duplicate header names are not allowed.

              For information about the limits on count and size for custom request and response settings, see WAF quotas in the WAF Developer Guide.

              • Name — required — (String)

                The name of the custom header.

                For custom request header insertion, when WAF inserts the header into the request, it prefixes this name x-amzn-waf-, to avoid confusion with the headers that are already in the request. For example, for the header name sample, WAF inserts the header x-amzn-waf-sample.

              • Value — required — (String)

                The value of the custom header.

        • Captcha — (map)

          Instructs WAF to run a CAPTCHA check against the web request.

          • CustomRequestHandling — (map)

            Defines custom handling for the web request.

            For information about customizing web requests and responses, see Customizing web requests and responses in WAF in the WAF Developer Guide.

            • InsertHeaders — required — (Array<map>)

              The HTTP headers to insert into the request. Duplicate header names are not allowed.

              For information about the limits on count and size for custom request and response settings, see WAF quotas in the WAF Developer Guide.

              • Name — required — (String)

                The name of the custom header.

                For custom request header insertion, when WAF inserts the header into the request, it prefixes this name x-amzn-waf-, to avoid confusion with the headers that are already in the request. For example, for the header name sample, WAF inserts the header x-amzn-waf-sample.

              • Value — required — (String)

                The value of the custom header.

      • OverrideAction — (map)

        The action to use in the place of the action that results from the rule group evaluation. Set the override action to none to leave the result of the rule group alone. Set it to count to override the result to count only.

        You can only use this for rule statements that reference a rule group, like RuleGroupReferenceStatement and ManagedRuleGroupStatement.

        Note: This option is usually set to none. It does not affect how the rules in the rule group are evaluated. If you want the rules in the rule group to only count matches, do not use this and instead exclude those rules in your rule group reference statement settings.
        • Count — (map)

          Override the rule group evaluation result to count only.

          Note: This option is usually set to none. It does not affect how the rules in the rule group are evaluated. If you want the rules in the rule group to only count matches, do not use this and instead exclude those rules in your rule group reference statement settings.
          • CustomRequestHandling — (map)

            Defines custom handling for the web request.

            For information about customizing web requests and responses, see Customizing web requests and responses in WAF in the WAF Developer Guide.

            • InsertHeaders — required — (Array<map>)

              The HTTP headers to insert into the request. Duplicate header names are not allowed.

              For information about the limits on count and size for custom request and response settings, see WAF quotas in the WAF Developer Guide.

              • Name — required — (String)

                The name of the custom header.

                For custom request header insertion, when WAF inserts the header into the request, it prefixes this name x-amzn-waf-, to avoid confusion with the headers that are already in the request. For example, for the header name sample, WAF inserts the header x-amzn-waf-sample.

              • Value — required — (String)

                The value of the custom header.

        • None — (map)

          Don't override the rule group evaluation result. This is the most common setting.

      • RuleLabels — (Array<map>)

        Labels to apply to web requests that match the rule match statement. WAF applies fully qualified labels to matching web requests. A fully qualified label is the concatenation of a label namespace and a rule label. The rule's rule group or web ACL defines the label namespace.

        Rules that run after this rule in the web ACL can match against these labels using a LabelMatchStatement.

        For each label, provide a case-sensitive string containing optional namespaces and a label name, according to the following guidelines:

        • Separate each component of the label with a colon.

        • Each namespace or name can have up to 128 characters.

        • You can specify up to 5 namespaces in a label.

        • Don't use the following reserved words in your label specification: aws, waf, managed, rulegroup, webacl, regexpatternset, or ipset.

        For example, myLabelName or nameSpace1:nameSpace2:myLabelName.

        • Name — required — (String)

          The label string.

      • VisibilityConfig — required — (map)

        Defines and enables Amazon CloudWatch metrics and web request sample collection.

        • SampledRequestsEnabled — required — (Boolean)

          A boolean indicating whether WAF should store a sampling of the web requests that match the rules. You can view the sampled requests through the WAF console.

        • CloudWatchMetricsEnabled — required — (Boolean)

          A boolean indicating whether the associated resource sends metrics to Amazon CloudWatch. For the list of available metrics, see WAF Metrics.

        • MetricName — required — (String)

          A name of the Amazon CloudWatch metric. The name can contain only the characters: A-Z, a-z, 0-9, - (hyphen), and _ (underscore). The name can be from one to 128 characters long. It can't contain whitespace or metric names reserved for WAF, for example "All" and "Default_Action."

      • CaptchaConfig — (map)

        Specifies how WAF should handle CAPTCHA evaluations. If you don't specify this, WAF uses the CAPTCHA configuration that's defined for the web ACL.

        • ImmunityTimeProperty — (map)

          Determines how long a CAPTCHA token remains valid after the client successfully solves a CAPTCHA puzzle.

          • ImmunityTime — required — (Integer)

            The amount of time, in seconds, that a CAPTCHA token is valid. The default setting is 300.

    • VisibilityConfig — (map)

      Defines and enables Amazon CloudWatch metrics and web request sample collection.

      • SampledRequestsEnabled — required — (Boolean)

        A boolean indicating whether WAF should store a sampling of the web requests that match the rules. You can view the sampled requests through the WAF console.

      • CloudWatchMetricsEnabled — required — (Boolean)

        A boolean indicating whether the associated resource sends metrics to Amazon CloudWatch. For the list of available metrics, see WAF Metrics.

      • MetricName — required — (String)

        A name of the Amazon CloudWatch metric. The name can contain only the characters: A-Z, a-z, 0-9, - (hyphen), and _ (underscore). The name can be from one to 128 characters long. It can't contain whitespace or metric names reserved for WAF, for example "All" and "Default_Action."

    • LockToken — (String)

      A token used for optimistic locking. WAF returns a token to your get and list requests, to mark the state of the entity at the time of the request. To make changes to the entity associated with the token, you provide the token to operations like update and delete. WAF uses the token to ensure that no changes have been made to the entity since you last retrieved it. If a change has been made, the update fails with a WAFOptimisticLockException. If this happens, perform another get, and use the new token returned by that operation.

    • CustomResponseBodies — (map<map>)

      A map of custom response keys and content bodies. When you create a rule with a block action, you can send a custom response to the web request. You define these for the rule group, and then use them in the rules that you define in the rule group.

      For information about customizing web requests and responses, see Customizing web requests and responses in WAF in the WAF Developer Guide.

      For information about the limits on count and size for custom request and response settings, see WAF quotas in the WAF Developer Guide.

      • ContentType — required — (String)

        The type of content in the payload that you are defining in the Content string.

        Possible values include:
        • "TEXT_PLAIN"
        • "TEXT_HTML"
        • "APPLICATION_JSON"
      • Content — required — (String)

        The payload of the custom response.

        You can use JSON escape strings in JSON content. To do this, you must specify JSON content in the ContentType setting.

        For information about the limits on count and size for custom request and response settings, see WAF quotas in the WAF Developer Guide.

Callback (callback):

  • function(err, data) { ... }

    Called when a response from the service is returned. If a callback is not supplied, you must call AWS.Request.send() on the returned request object to initiate the request.

    Context (this):

    • (AWS.Response) —

      the response object containing error, data properties, and the original request object.

    Parameters:

    • err (Error) —

      the error object returned from the request. Set to null if the request is successful.

    • data (Object) —

      the de-serialized data returned from the request. Set to null if a request error occurs. The data object has the following properties:

      • NextLockToken — (String)

        A token used for optimistic locking. WAF returns this token to your update requests. You use NextLockToken in the same manner as you use LockToken.

Returns:

  • (AWS.Request) —

    a handle to the operation request for subsequent event callback registration.

updateWebACL(params = {}, callback) ⇒ AWS.Request

Updates the specified WebACL.

Note: This operation completely replaces the mutable specifications that you already have for the web ACL with the ones that you provide to this call. To modify the web ACL, retrieve it by calling GetWebACL, update the settings as needed, and then provide the complete web ACL specification to this call.

A web ACL defines a collection of rules to use to inspect and control web requests. Each rule has an action defined (allow, block, or count) for requests that match the statement of the rule. In the web ACL, you assign a default action to take (allow, block) for any request that does not match any of the rules. The rules in a web ACL can be a combination of the types Rule, RuleGroup, and managed rule group. You can associate a web ACL with one or more Amazon Web Services resources to protect. The resources can be an Amazon CloudFront distribution, an Amazon API Gateway REST API, an Application Load Balancer, or an AppSync GraphQL API.

Service Reference:

Examples:

Calling the updateWebACL operation

var params = {
  DefaultAction: { /* required */
    Allow: {
      CustomRequestHandling: {
        InsertHeaders: [ /* required */
          {
            Name: 'STRING_VALUE', /* required */
            Value: 'STRING_VALUE' /* required */
          },
          /* more items */
        ]
      }
    },
    Block: {
      CustomResponse: {
        ResponseCode: 'NUMBER_VALUE', /* required */
        CustomResponseBodyKey: 'STRING_VALUE',
        ResponseHeaders: [
          {
            Name: 'STRING_VALUE', /* required */
            Value: 'STRING_VALUE' /* required */
          },
          /* more items */
        ]
      }
    }
  },
  Id: 'STRING_VALUE', /* required */
  LockToken: 'STRING_VALUE', /* required */
  Name: 'STRING_VALUE', /* required */
  Scope: CLOUDFRONT | REGIONAL, /* required */
  VisibilityConfig: { /* required */
    CloudWatchMetricsEnabled: true || false, /* required */
    MetricName: 'STRING_VALUE', /* required */
    SampledRequestsEnabled: true || false /* required */
  },
  CaptchaConfig: {
    ImmunityTimeProperty: {
      ImmunityTime: 'NUMBER_VALUE' /* required */
    }
  },
  CustomResponseBodies: {
    '<EntityName>': {
      Content: 'STRING_VALUE', /* required */
      ContentType: TEXT_PLAIN | TEXT_HTML | APPLICATION_JSON /* required */
    },
    /* '<EntityName>': ... */
  },
  Description: 'STRING_VALUE',
  Rules: [
    {
      Name: 'STRING_VALUE', /* required */
      Priority: 'NUMBER_VALUE', /* required */
      Statement: { /* Statement */ /* required */
        AndStatement: {
          Statements: [ /* required */
            /* recursive Statement */,
            /* more items */
          ]
        },
        ByteMatchStatement: {
          FieldToMatch: { /* required */
            AllQueryArguments: {
            },
            Body: {
            },
            JsonBody: {
              MatchPattern: { /* required */
                All: {
                },
                IncludedPaths: [
                  'STRING_VALUE',
                  /* more items */
                ]
              },
              MatchScope: ALL | KEY | VALUE, /* required */
              InvalidFallbackBehavior: MATCH | NO_MATCH | EVALUATE_AS_STRING
            },
            Method: {
            },
            QueryString: {
            },
            SingleHeader: {
              Name: 'STRING_VALUE' /* required */
            },
            SingleQueryArgument: {
              Name: 'STRING_VALUE' /* required */
            },
            UriPath: {
            }
          },
          PositionalConstraint: EXACTLY | STARTS_WITH | ENDS_WITH | CONTAINS | CONTAINS_WORD, /* required */
          SearchString: Buffer.from('...') || 'STRING_VALUE' /* Strings will be Base-64 encoded on your behalf */, /* required */
          TextTransformations: [ /* required */
            {
              Priority: 'NUMBER_VALUE', /* required */
              Type: NONE | COMPRESS_WHITE_SPACE | HTML_ENTITY_DECODE | LOWERCASE | CMD_LINE | URL_DECODE | BASE64_DECODE | HEX_DECODE | MD5 | REPLACE_COMMENTS | ESCAPE_SEQ_DECODE | SQL_HEX_DECODE | CSS_DECODE | JS_DECODE | NORMALIZE_PATH | NORMALIZE_PATH_WIN | REMOVE_NULLS | REPLACE_NULLS | BASE64_DECODE_EXT | URL_DECODE_UNI | UTF8_TO_UNICODE /* required */
            },
            /* more items */
          ]
        },
        GeoMatchStatement: {
          CountryCodes: [
            AF | AX | AL | DZ | AS | AD | AO | AI | AQ | AG | AR | AM | AW | AU | AT | AZ | BS | BH | BD | BB | BY | BE | BZ | BJ | BM | BT | BO | BQ | BA | BW | BV | BR | IO | BN | BG | BF | BI | KH | CM | CA | CV | KY | CF | TD | CL | CN | CX | CC | CO | KM | CG | CD | CK | CR | CI | HR | CU | CW | CY | CZ | DK | DJ | DM | DO | EC | EG | SV | GQ | ER | EE | ET | FK | FO | FJ | FI | FR | GF | PF | TF | GA | GM | GE | DE | GH | GI | GR | GL | GD | GP | GU | GT | GG | GN | GW | GY | HT | HM | VA | HN | HK | HU | IS | IN | ID | IR | IQ | IE | IM | IL | IT | JM | JP | JE | JO | KZ | KE | KI | KP | KR | KW | KG | LA | LV | LB | LS | LR | LY | LI | LT | LU | MO | MK | MG | MW | MY | MV | ML | MT | MH | MQ | MR | MU | YT | MX | FM | MD | MC | MN | ME | MS | MA | MZ | MM | NA | NR | NP | NL | NC | NZ | NI | NE | NG | NU | NF | MP | NO | OM | PK | PW | PS | PA | PG | PY | PE | PH | PN | PL | PT | PR | QA | RE | RO | RU | RW | BL | SH | KN | LC | MF | PM | VC | WS | SM | ST | SA | SN | RS | SC | SL | SG | SX | SK | SI | SB | SO | ZA | GS | SS | ES | LK | SD | SR | SJ | SZ | SE | CH | SY | TW | TJ | TZ | TH | TL | TG | TK | TO | TT | TN | TR | TM | TC | TV | UG | UA | AE | GB | US | UM | UY | UZ | VU | VE | VN | VG | VI | WF | EH | YE | ZM | ZW,
            /* more items */
          ],
          ForwardedIPConfig: {
            FallbackBehavior: MATCH | NO_MATCH, /* required */
            HeaderName: 'STRING_VALUE' /* required */
          }
        },
        IPSetReferenceStatement: {
          ARN: 'STRING_VALUE', /* required */
          IPSetForwardedIPConfig: {
            FallbackBehavior: MATCH | NO_MATCH, /* required */
            HeaderName: 'STRING_VALUE', /* required */
            Position: FIRST | LAST | ANY /* required */
          }
        },
        LabelMatchStatement: {
          Key: 'STRING_VALUE', /* required */
          Scope: LABEL | NAMESPACE /* required */
        },
        ManagedRuleGroupStatement: {
          Name: 'STRING_VALUE', /* required */
          VendorName: 'STRING_VALUE', /* required */
          ExcludedRules: [
            {
              Name: 'STRING_VALUE' /* required */
            },
            /* more items */
          ],
          ScopeDownStatement: /* recursive Statement */,
          Version: 'STRING_VALUE'
        },
        NotStatement: {
          Statement: /* recursive Statement */
        },
        OrStatement: {
          Statements: [ /* required */
            /* recursive Statement */,
            /* more items */
          ]
        },
        RateBasedStatement: {
          AggregateKeyType: IP | FORWARDED_IP, /* required */
          Limit: 'NUMBER_VALUE', /* required */
          ForwardedIPConfig: {
            FallbackBehavior: MATCH | NO_MATCH, /* required */
            HeaderName: 'STRING_VALUE' /* required */
          },
          ScopeDownStatement: /* recursive Statement */
        },
        RegexMatchStatement: {
          FieldToMatch: { /* required */
            AllQueryArguments: {
            },
            Body: {
            },
            JsonBody: {
              MatchPattern: { /* required */
                All: {
                },
                IncludedPaths: [
                  'STRING_VALUE',
                  /* more items */
                ]
              },
              MatchScope: ALL | KEY | VALUE, /* required */
              InvalidFallbackBehavior: MATCH | NO_MATCH | EVALUATE_AS_STRING
            },
            Method: {
            },
            QueryString: {
            },
            SingleHeader: {
              Name: 'STRING_VALUE' /* required */
            },
            SingleQueryArgument: {
              Name: 'STRING_VALUE' /* required */
            },
            UriPath: {
            }
          },
          RegexString: 'STRING_VALUE', /* required */
          TextTransformations: [ /* required */
            {
              Priority: 'NUMBER_VALUE', /* required */
              Type: NONE | COMPRESS_WHITE_SPACE | HTML_ENTITY_DECODE | LOWERCASE | CMD_LINE | URL_DECODE | BASE64_DECODE | HEX_DECODE | MD5 | REPLACE_COMMENTS | ESCAPE_SEQ_DECODE | SQL_HEX_DECODE | CSS_DECODE | JS_DECODE | NORMALIZE_PATH | NORMALIZE_PATH_WIN | REMOVE_NULLS | REPLACE_NULLS | BASE64_DECODE_EXT | URL_DECODE_UNI | UTF8_TO_UNICODE /* required */
            },
            /* more items */
          ]
        },
        RegexPatternSetReferenceStatement: {
          ARN: 'STRING_VALUE', /* required */
          FieldToMatch: { /* required */
            AllQueryArguments: {
            },
            Body: {
            },
            JsonBody: {
              MatchPattern: { /* required */
                All: {
                },
                IncludedPaths: [
                  'STRING_VALUE',
                  /* more items */
                ]
              },
              MatchScope: ALL | KEY | VALUE, /* required */
              InvalidFallbackBehavior: MATCH | NO_MATCH | EVALUATE_AS_STRING
            },
            Method: {
            },
            QueryString: {
            },
            SingleHeader: {
              Name: 'STRING_VALUE' /* required */
            },
            SingleQueryArgument: {
              Name: 'STRING_VALUE' /* required */
            },
            UriPath: {
            }
          },
          TextTransformations: [ /* required */
            {
              Priority: 'NUMBER_VALUE', /* required */
              Type: NONE | COMPRESS_WHITE_SPACE | HTML_ENTITY_DECODE | LOWERCASE | CMD_LINE | URL_DECODE | BASE64_DECODE | HEX_DECODE | MD5 | REPLACE_COMMENTS | ESCAPE_SEQ_DECODE | SQL_HEX_DECODE | CSS_DECODE | JS_DECODE | NORMALIZE_PATH | NORMALIZE_PATH_WIN | REMOVE_NULLS | REPLACE_NULLS | BASE64_DECODE_EXT | URL_DECODE_UNI | UTF8_TO_UNICODE /* required */
            },
            /* more items */
          ]
        },
        RuleGroupReferenceStatement: {
          ARN: 'STRING_VALUE', /* required */
          ExcludedRules: [
            {
              Name: 'STRING_VALUE' /* required */
            },
            /* more items */
          ]
        },
        SizeConstraintStatement: {
          ComparisonOperator: EQ | NE | LE | LT | GE | GT, /* required */
          FieldToMatch: { /* required */
            AllQueryArguments: {
            },
            Body: {
            },
            JsonBody: {
              MatchPattern: { /* required */
                All: {
                },
                IncludedPaths: [
                  'STRING_VALUE',
                  /* more items */
                ]
              },
              MatchScope: ALL | KEY | VALUE, /* required */
              InvalidFallbackBehavior: MATCH | NO_MATCH | EVALUATE_AS_STRING
            },
            Method: {
            },
            QueryString: {
            },
            SingleHeader: {
              Name: 'STRING_VALUE' /* required */
            },
            SingleQueryArgument: {
              Name: 'STRING_VALUE' /* required */
            },
            UriPath: {
            }
          },
          Size: 'NUMBER_VALUE', /* required */
          TextTransformations: [ /* required */
            {
              Priority: 'NUMBER_VALUE', /* required */
              Type: NONE | COMPRESS_WHITE_SPACE | HTML_ENTITY_DECODE | LOWERCASE | CMD_LINE | URL_DECODE | BASE64_DECODE | HEX_DECODE | MD5 | REPLACE_COMMENTS | ESCAPE_SEQ_DECODE | SQL_HEX_DECODE | CSS_DECODE | JS_DECODE | NORMALIZE_PATH | NORMALIZE_PATH_WIN | REMOVE_NULLS | REPLACE_NULLS | BASE64_DECODE_EXT | URL_DECODE_UNI | UTF8_TO_UNICODE /* required */
            },
            /* more items */
          ]
        },
        SqliMatchStatement: {
          FieldToMatch: { /* required */
            AllQueryArguments: {
            },
            Body: {
            },
            JsonBody: {
              MatchPattern: { /* required */
                All: {
                },
                IncludedPaths: [
                  'STRING_VALUE',
                  /* more items */
                ]
              },
              MatchScope: ALL | KEY | VALUE, /* required */
              InvalidFallbackBehavior: MATCH | NO_MATCH | EVALUATE_AS_STRING
            },
            Method: {
            },
            QueryString: {
            },
            SingleHeader: {
              Name: 'STRING_VALUE' /* required */
            },
            SingleQueryArgument: {
              Name: 'STRING_VALUE' /* required */
            },
            UriPath: {
            }
          },
          TextTransformations: [ /* required */
            {
              Priority: 'NUMBER_VALUE', /* required */
              Type: NONE | COMPRESS_WHITE_SPACE | HTML_ENTITY_DECODE | LOWERCASE | CMD_LINE | URL_DECODE | BASE64_DECODE | HEX_DECODE | MD5 | REPLACE_COMMENTS | ESCAPE_SEQ_DECODE | SQL_HEX_DECODE | CSS_DECODE | JS_DECODE | NORMALIZE_PATH | NORMALIZE_PATH_WIN | REMOVE_NULLS | REPLACE_NULLS | BASE64_DECODE_EXT | URL_DECODE_UNI | UTF8_TO_UNICODE /* required */
            },
            /* more items */
          ]
        },
        XssMatchStatement: {
          FieldToMatch: { /* required */
            AllQueryArguments: {
            },
            Body: {
            },
            JsonBody: {
              MatchPattern: { /* required */
                All: {
                },
                IncludedPaths: [
                  'STRING_VALUE',
                  /* more items */
                ]
              },
              MatchScope: ALL | KEY | VALUE, /* required */
              InvalidFallbackBehavior: MATCH | NO_MATCH | EVALUATE_AS_STRING
            },
            Method: {
            },
            QueryString: {
            },
            SingleHeader: {
              Name: 'STRING_VALUE' /* required */
            },
            SingleQueryArgument: {
              Name: 'STRING_VALUE' /* required */
            },
            UriPath: {
            }
          },
          TextTransformations: [ /* required */
            {
              Priority: 'NUMBER_VALUE', /* required */
              Type: NONE | COMPRESS_WHITE_SPACE | HTML_ENTITY_DECODE | LOWERCASE | CMD_LINE | URL_DECODE | BASE64_DECODE | HEX_DECODE | MD5 | REPLACE_COMMENTS | ESCAPE_SEQ_DECODE | SQL_HEX_DECODE | CSS_DECODE | JS_DECODE | NORMALIZE_PATH | NORMALIZE_PATH_WIN | REMOVE_NULLS | REPLACE_NULLS | BASE64_DECODE_EXT | URL_DECODE_UNI | UTF8_TO_UNICODE /* required */
            },
            /* more items */
          ]
        }
      },
      VisibilityConfig: { /* required */
        CloudWatchMetricsEnabled: true || false, /* required */
        MetricName: 'STRING_VALUE', /* required */
        SampledRequestsEnabled: true || false /* required */
      },
      Action: {
        Allow: {
          CustomRequestHandling: {
            InsertHeaders: [ /* required */
              {
                Name: 'STRING_VALUE', /* required */
                Value: 'STRING_VALUE' /* required */
              },
              /* more items */
            ]
          }
        },
        Block: {
          CustomResponse: {
            ResponseCode: 'NUMBER_VALUE', /* required */
            CustomResponseBodyKey: 'STRING_VALUE',
            ResponseHeaders: [
              {
                Name: 'STRING_VALUE', /* required */
                Value: 'STRING_VALUE' /* required */
              },
              /* more items */
            ]
          }
        },
        Captcha: {
          CustomRequestHandling: {
            InsertHeaders: [ /* required */
              {
                Name: 'STRING_VALUE', /* required */
                Value: 'STRING_VALUE' /* required */
              },
              /* more items */
            ]
          }
        },
        Count: {
          CustomRequestHandling: {
            InsertHeaders: [ /* required */
              {
                Name: 'STRING_VALUE', /* required */
                Value: 'STRING_VALUE' /* required */
              },
              /* more items */
            ]
          }
        }
      },
      CaptchaConfig: {
        ImmunityTimeProperty: {
          ImmunityTime: 'NUMBER_VALUE' /* required */
        }
      },
      OverrideAction: {
        Count: {
          CustomRequestHandling: {
            InsertHeaders: [ /* required */
              {
                Name: 'STRING_VALUE', /* required */
                Value: 'STRING_VALUE' /* required */
              },
              /* more items */
            ]
          }
        },
        None: {
        }
      },
      RuleLabels: [
        {
          Name: 'STRING_VALUE' /* required */
        },
        /* more items */
      ]
    },
    /* more items */
  ]
};
wafv2.updateWebACL(params, function(err, data) {
  if (err) console.log(err, err.stack); // an error occurred
  else     console.log(data);           // successful response
});

Parameters:

  • params (Object) (defaults to: {}) —
    • Name — (String)

      The name of the web ACL. You cannot change the name of a web ACL after you create it.

    • Scope — (String)

      Specifies whether this is for an Amazon CloudFront distribution or for a regional application. A regional application can be an Application Load Balancer (ALB), an Amazon API Gateway REST API, or an AppSync GraphQL API.

      To work with CloudFront, you must also specify the Region US East (N. Virginia) as follows:

      • CLI - Specify the Region when you use the CloudFront scope: --scope=CLOUDFRONT --region=us-east-1.

      • API and SDKs - For all calls, use the Region endpoint us-east-1.

      Possible values include:
      • "CLOUDFRONT"
      • "REGIONAL"
    • Id — (String)

      The unique identifier for the web ACL. This ID is returned in the responses to create and list commands. You provide it to operations like update and delete.

    • DefaultAction — (map)

      The action to perform if none of the Rules contained in the WebACL match.

      • Block — (map)

        Specifies that WAF should block requests by default.

        • CustomResponse — (map)

          Defines a custom response for the web request.

          For information about customizing web requests and responses, see Customizing web requests and responses in WAF in the WAF Developer Guide.

          • ResponseCode — required — (Integer)

            The HTTP status code to return to the client.

            For a list of status codes that you can use in your custom reqponses, see Supported status codes for custom response in the WAF Developer Guide.

          • CustomResponseBodyKey — (String)

            References the response body that you want WAF to return to the web request client. You can define a custom response for a rule action or a default web ACL action that is set to block. To do this, you first define the response body key and value in the CustomResponseBodies setting for the WebACL or RuleGroup where you want to use it. Then, in the rule action or web ACL default action BlockAction setting, you reference the response body using this key.

          • ResponseHeaders — (Array<map>)

            The HTTP headers to use in the response. Duplicate header names are not allowed.

            For information about the limits on count and size for custom request and response settings, see WAF quotas in the WAF Developer Guide.

            • Name — required — (String)

              The name of the custom header.

              For custom request header insertion, when WAF inserts the header into the request, it prefixes this name x-amzn-waf-, to avoid confusion with the headers that are already in the request. For example, for the header name sample, WAF inserts the header x-amzn-waf-sample.

            • Value — required — (String)

              The value of the custom header.

      • Allow — (map)

        Specifies that WAF should allow requests by default.

        • CustomRequestHandling — (map)

          Defines custom handling for the web request.

          For information about customizing web requests and responses, see Customizing web requests and responses in WAF in the WAF Developer Guide.

          • InsertHeaders — required — (Array<map>)

            The HTTP headers to insert into the request. Duplicate header names are not allowed.

            For information about the limits on count and size for custom request and response settings, see WAF quotas in the WAF Developer Guide.

            • Name — required — (String)

              The name of the custom header.

              For custom request header insertion, when WAF inserts the header into the request, it prefixes this name x-amzn-waf-, to avoid confusion with the headers that are already in the request. For example, for the header name sample, WAF inserts the header x-amzn-waf-sample.

            • Value — required — (String)

              The value of the custom header.

    • Description — (String)

      A description of the web ACL that helps with identification.

    • Rules — (Array<map>)

      The Rule statements used to identify the web requests that you want to allow, block, or count. Each rule includes one top-level statement that WAF uses to identify matching web requests, and parameters that govern how WAF handles them.

      • Name — required — (String)

        The name of the rule. You can't change the name of a Rule after you create it.

      • Priority — required — (Integer)

        If you define more than one Rule in a WebACL, WAF evaluates each request against the Rules in order based on the value of Priority. WAF processes rules with lower priority first. The priorities don't need to be consecutive, but they must all be different.

      • Statement — required — (map)

        The WAF processing statement for the rule, for example ByteMatchStatement or SizeConstraintStatement.

        • ByteMatchStatement — (map)

          A rule statement that defines a string match search for WAF to apply to web requests. The byte match statement provides the bytes to search for, the location in requests that you want WAF to search, and other settings. The bytes to search for are typically a string that corresponds with ASCII characters. In the WAF console and the developer guide, this is refered to as a string match statement.

          • SearchString — required — (Buffer, Typed Array, Blob, String)

            A string value that you want WAF to search for. WAF searches only in the part of web requests that you designate for inspection in FieldToMatch. The maximum length of the value is 50 bytes.

            Valid values depend on the component that you specify for inspection in FieldToMatch:

            • Method: The HTTP method that you want WAF to search for. This indicates the type of operation specified in the request.

            • UriPath: The value that you want WAF to search for in the URI path, for example, /images/daily-ad.jpg.

            If SearchString includes alphabetic characters A-Z and a-z, note that the value is case sensitive.

            If you're using the WAF API

            Specify a base64-encoded version of the value. The maximum length of the value before you base64-encode it is 50 bytes.

            For example, suppose the value of Type is HEADER and the value of Data is User-Agent. If you want to search the User-Agent header for the value BadBot, you base64-encode BadBot using MIME base64-encoding and include the resulting value, QmFkQm90, in the value of SearchString.

            If you're using the CLI or one of the Amazon Web Services SDKs

            The value that you want WAF to search for. The SDK automatically base64 encodes the value.

          • FieldToMatch — required — (map)

            The part of a web request that you want WAF to inspect. For more information, see FieldToMatch.

            • SingleHeader — (map)

              Inspect a single header. Provide the name of the header to inspect, for example, User-Agent or Referer. This setting isn't case sensitive.

              Example JSON: "SingleHeader": { "Name": "haystack" }

              • Name — required — (String)

                The name of the query header to inspect.

            • SingleQueryArgument — (map)

              Inspect a single query argument. Provide the name of the query argument to inspect, such as UserName or SalesRegion. The name can be up to 30 characters long and isn't case sensitive.

              This is used only to indicate the web request component for WAF to inspect, in the FieldToMatch specification.

              Example JSON: "SingleQueryArgument": { "Name": "myArgument" }

              • Name — required — (String)

                The name of the query argument to inspect.

            • AllQueryArguments — (map)

              Inspect all query arguments.

            • UriPath — (map)

              Inspect the request URI path. This is the part of a web request that identifies a resource, for example, /images/daily-ad.jpg.

            • QueryString — (map)

              Inspect the query string. This is the part of a URL that appears after a ? character, if any.

            • Body — (map)

              Inspect the request body as plain text. The request body immediately follows the request headers. This is the part of a request that contains any additional data that you want to send to your web server as the HTTP request body, such as data from a form.

              Note that only the first 8 KB (8192 bytes) of the request body are forwarded to WAF for inspection by the underlying host service. If you don't need to inspect more than 8 KB, you can guarantee that you don't allow additional bytes in by combining a statement that inspects the body of the web request, such as ByteMatchStatement or RegexPatternSetReferenceStatement, with a SizeConstraintStatement that enforces an 8 KB size limit on the body of the request. WAF doesn't support inspecting the entire contents of web requests whose bodies exceed the 8 KB limit.

            • Method — (map)

              Inspect the HTTP method. The method indicates the type of operation that the request is asking the origin to perform.

            • JsonBody — (map)

              Inspect the request body as JSON. The request body immediately follows the request headers. This is the part of a request that contains any additional data that you want to send to your web server as the HTTP request body, such as data from a form.

              Note that only the first 8 KB (8192 bytes) of the request body are forwarded to WAF for inspection by the underlying host service. If you don't need to inspect more than 8 KB, you can guarantee that you don't allow additional bytes in by combining a statement that inspects the body of the web request, such as ByteMatchStatement or RegexPatternSetReferenceStatement, with a SizeConstraintStatement that enforces an 8 KB size limit on the body of the request. WAF doesn't support inspecting the entire contents of web requests whose bodies exceed the 8 KB limit.

              • MatchPattern — required — (map)

                The patterns to look for in the JSON body. WAF inspects the results of these pattern matches against the rule inspection criteria.

                • All — (map)

                  Match all of the elements. See also MatchScope in JsonBody.

                  You must specify either this setting or the IncludedPaths setting, but not both.

                • IncludedPaths — (Array<String>)

                  Match only the specified include paths. See also MatchScope in JsonBody.

                  Provide the include paths using JSON Pointer syntax. For example, "IncludedPaths": ["/dogs/0/name", "/dogs/1/name"]. For information about this syntax, see the Internet Engineering Task Force (IETF) documentation JavaScript Object Notation (JSON) Pointer.

                  You must specify either this setting or the All setting, but not both.

                  Note: Don't use this option to include all paths. Instead, use the All setting.
              • MatchScope — required — (String)

                The parts of the JSON to match against using the MatchPattern. If you specify All, WAF matches against keys and values.

                Possible values include:
                • "ALL"
                • "KEY"
                • "VALUE"
              • InvalidFallbackBehavior — (String)

                What WAF should do if it fails to completely parse the JSON body. The options are the following:

                • EVALUATE_AS_STRING - Inspect the body as plain text. WAF applies the text transformations and inspection criteria that you defined for the JSON inspection to the body text string.

                • MATCH - Treat the web request as matching the rule statement. WAF applies the rule action to the request.

                • NO_MATCH - Treat the web request as not matching the rule statement.

                If you don't provide this setting, WAF parses and evaluates the content only up to the first parsing failure that it encounters.

                WAF does its best to parse the entire JSON body, but might be forced to stop for reasons such as invalid characters, duplicate keys, truncation, and any content whose root node isn't an object or an array.

                WAF parses the JSON in the following examples as two valid key, value pairs:

                • Missing comma: {"key1":"value1""key2":"value2"}

                • Missing colon: {"key1":"value1","key2""value2"}

                • Extra colons: {"key1"::"value1","key2""value2"}

                Possible values include:
                • "MATCH"
                • "NO_MATCH"
                • "EVALUATE_AS_STRING"
          • TextTransformations — required — (Array<map>)

            Text transformations eliminate some of the unusual formatting that attackers use in web requests in an effort to bypass detection. If you specify one or more transformations in a rule statement, WAF performs all transformations on the content of the request component identified by FieldToMatch, starting from the lowest priority setting, before inspecting the content for a match.

            • Priority — required — (Integer)

              Sets the relative processing order for multiple transformations that are defined for a rule statement. WAF processes all transformations, from lowest priority to highest, before inspecting the transformed content. The priorities don't need to be consecutive, but they must all be different.

            • Type — required — (String)

              You can specify the following transformation types:

              BASE64_DECODE - Decode a Base64-encoded string.

              BASE64_DECODE_EXT - Decode a Base64-encoded string, but use a forgiving implementation that ignores characters that aren't valid.

              CMD_LINE - Command-line transformations. These are helpful in reducing effectiveness of attackers who inject an operating system command-line command and use unusual formatting to disguise some or all of the command.

              • Delete the following characters: \ " ' ^

              • Delete spaces before the following characters: / (

              • Replace the following characters with a space: , ;

              • Replace multiple spaces with one space

              • Convert uppercase letters (A-Z) to lowercase (a-z)

              COMPRESS_WHITE_SPACE - Replace these characters with a space character (decimal 32):

              • \f, formfeed, decimal 12

              • \t, tab, decimal 9

              • \n, newline, decimal 10

              • \r, carriage return, decimal 13

              • \v, vertical tab, decimal 11

              • Non-breaking space, decimal 160

              COMPRESS_WHITE_SPACE also replaces multiple spaces with one space.

              CSS_DECODE - Decode characters that were encoded using CSS 2.x escape rules syndata.html#characters. This function uses up to two bytes in the decoding process, so it can help to uncover ASCII characters that were encoded using CSS encoding that wouldn’t typically be encoded. It's also useful in countering evasion, which is a combination of a backslash and non-hexadecimal characters. For example, ja\vascript for javascript.

              ESCAPE_SEQ_DECODE - Decode the following ANSI C escape sequences: \a, \b, \f, \n, \r, \t, \v, \, \?, \', \", \xHH (hexadecimal), \0OOO (octal). Encodings that aren't valid remain in the output.

              HEX_DECODE - Decode a string of hexadecimal characters into a binary.

              HTML_ENTITY_DECODE - Replace HTML-encoded characters with unencoded characters. HTML_ENTITY_DECODE performs these operations:

              • Replaces (ampersand)quot; with "

              • Replaces (ampersand)nbsp; with a non-breaking space, decimal 160

              • Replaces (ampersand)lt; with a "less than" symbol

              • Replaces (ampersand)gt; with >

              • Replaces characters that are represented in hexadecimal format, (ampersand)#xhhhh;, with the corresponding characters

              • Replaces characters that are represented in decimal format, (ampersand)#nnnn;, with the corresponding characters

              JS_DECODE - Decode JavaScript escape sequences. If a \ u HHHH code is in the full-width ASCII code range of FF01-FF5E, then the higher byte is used to detect and adjust the lower byte. If not, only the lower byte is used and the higher byte is zeroed, causing a possible loss of information.

              LOWERCASE - Convert uppercase letters (A-Z) to lowercase (a-z).

              MD5 - Calculate an MD5 hash from the data in the input. The computed hash is in a raw binary form.

              NONE - Specify NONE if you don't want any text transformations.

              NORMALIZE_PATH - Remove multiple slashes, directory self-references, and directory back-references that are not at the beginning of the input from an input string.

              NORMALIZE_PATH_WIN - This is the same as NORMALIZE_PATH, but first converts backslash characters to forward slashes.

              REMOVE_NULLS - Remove all NULL bytes from the input.

              REPLACE_COMMENTS - Replace each occurrence of a C-style comment (/* ... */) with a single space. Multiple consecutive occurrences are not compressed. Unterminated comments are also replaced with a space (ASCII 0x20). However, a standalone termination of a comment (*/) is not acted upon.

              REPLACE_NULLS - Replace NULL bytes in the input with space characters (ASCII 0x20).

              SQL_HEX_DECODE - Decode SQL hex data. Example (0x414243) will be decoded to (ABC).

              URL_DECODE - Decode a URL-encoded value.

              URL_DECODE_UNI - Like URL_DECODE, but with support for Microsoft-specific %u encoding. If the code is in the full-width ASCII code range of FF01-FF5E, the higher byte is used to detect and adjust the lower byte. Otherwise, only the lower byte is used and the higher byte is zeroed.

              UTF8_TO_UNICODE - Convert all UTF-8 character sequences to Unicode. This helps input normalization, and minimizing false-positives and false-negatives for non-English languages.

              Possible values include:
              • "NONE"
              • "COMPRESS_WHITE_SPACE"
              • "HTML_ENTITY_DECODE"
              • "LOWERCASE"
              • "CMD_LINE"
              • "URL_DECODE"
              • "BASE64_DECODE"
              • "HEX_DECODE"
              • "MD5"
              • "REPLACE_COMMENTS"
              • "ESCAPE_SEQ_DECODE"
              • "SQL_HEX_DECODE"
              • "CSS_DECODE"
              • "JS_DECODE"
              • "NORMALIZE_PATH"
              • "NORMALIZE_PATH_WIN"
              • "REMOVE_NULLS"
              • "REPLACE_NULLS"
              • "BASE64_DECODE_EXT"
              • "URL_DECODE_UNI"
              • "UTF8_TO_UNICODE"
          • PositionalConstraint — required — (String)

            The area within the portion of a web request that you want WAF to search for SearchString. Valid values include the following:

            CONTAINS

            The specified part of the web request must include the value of SearchString, but the location doesn't matter.

            CONTAINS_WORD

            The specified part of the web request must include the value of SearchString, and SearchString must contain only alphanumeric characters or underscore (A-Z, a-z, 0-9, or ). In addition, SearchString must be a word, which means that both of the following are true:

            • SearchString is at the beginning of the specified part of the web request or is preceded by a character other than an alphanumeric character or underscore (). Examples include the value of a header and ;BadBot.

            • SearchString is at the end of the specified part of the web request or is followed by a character other than an alphanumeric character or underscore (_), for example, BadBot; and -BadBot;.

            EXACTLY

            The value of the specified part of the web request must exactly match the value of SearchString.

            STARTS_WITH

            The value of SearchString must appear at the beginning of the specified part of the web request.

            ENDS_WITH

            The value of SearchString must appear at the end of the specified part of the web request.

            Possible values include:
            • "EXACTLY"
            • "STARTS_WITH"
            • "ENDS_WITH"
            • "CONTAINS"
            • "CONTAINS_WORD"
        • SqliMatchStatement — (map)

          Attackers sometimes insert malicious SQL code into web requests in an effort to extract data from your database. To allow or block web requests that appear to contain malicious SQL code, create one or more SQL injection match conditions. An SQL injection match condition identifies the part of web requests, such as the URI or the query string, that you want WAF to inspect. Later in the process, when you create a web ACL, you specify whether to allow or block requests that appear to contain malicious SQL code.

          • FieldToMatch — required — (map)

            The part of a web request that you want WAF to inspect. For more information, see FieldToMatch.

            • SingleHeader — (map)

              Inspect a single header. Provide the name of the header to inspect, for example, User-Agent or Referer. This setting isn't case sensitive.

              Example JSON: "SingleHeader": { "Name": "haystack" }

              • Name — required — (String)

                The name of the query header to inspect.

            • SingleQueryArgument — (map)

              Inspect a single query argument. Provide the name of the query argument to inspect, such as UserName or SalesRegion. The name can be up to 30 characters long and isn't case sensitive.

              This is used only to indicate the web request component for WAF to inspect, in the FieldToMatch specification.

              Example JSON: "SingleQueryArgument": { "Name": "myArgument" }

              • Name — required — (String)

                The name of the query argument to inspect.

            • AllQueryArguments — (map)

              Inspect all query arguments.

            • UriPath — (map)

              Inspect the request URI path. This is the part of a web request that identifies a resource, for example, /images/daily-ad.jpg.

            • QueryString — (map)

              Inspect the query string. This is the part of a URL that appears after a ? character, if any.

            • Body — (map)

              Inspect the request body as plain text. The request body immediately follows the request headers. This is the part of a request that contains any additional data that you want to send to your web server as the HTTP request body, such as data from a form.

              Note that only the first 8 KB (8192 bytes) of the request body are forwarded to WAF for inspection by the underlying host service. If you don't need to inspect more than 8 KB, you can guarantee that you don't allow additional bytes in by combining a statement that inspects the body of the web request, such as ByteMatchStatement or RegexPatternSetReferenceStatement, with a SizeConstraintStatement that enforces an 8 KB size limit on the body of the request. WAF doesn't support inspecting the entire contents of web requests whose bodies exceed the 8 KB limit.

            • Method — (map)

              Inspect the HTTP method. The method indicates the type of operation that the request is asking the origin to perform.

            • JsonBody — (map)

              Inspect the request body as JSON. The request body immediately follows the request headers. This is the part of a request that contains any additional data that you want to send to your web server as the HTTP request body, such as data from a form.

              Note that only the first 8 KB (8192 bytes) of the request body are forwarded to WAF for inspection by the underlying host service. If you don't need to inspect more than 8 KB, you can guarantee that you don't allow additional bytes in by combining a statement that inspects the body of the web request, such as ByteMatchStatement or RegexPatternSetReferenceStatement, with a SizeConstraintStatement that enforces an 8 KB size limit on the body of the request. WAF doesn't support inspecting the entire contents of web requests whose bodies exceed the 8 KB limit.

              • MatchPattern — required — (map)

                The patterns to look for in the JSON body. WAF inspects the results of these pattern matches against the rule inspection criteria.

                • All — (map)

                  Match all of the elements. See also MatchScope in JsonBody.

                  You must specify either this setting or the IncludedPaths setting, but not both.

                • IncludedPaths — (Array<String>)

                  Match only the specified include paths. See also MatchScope in JsonBody.

                  Provide the include paths using JSON Pointer syntax. For example, "IncludedPaths": ["/dogs/0/name", "/dogs/1/name"]. For information about this syntax, see the Internet Engineering Task Force (IETF) documentation JavaScript Object Notation (JSON) Pointer.

                  You must specify either this setting or the All setting, but not both.

                  Note: Don't use this option to include all paths. Instead, use the All setting.
              • MatchScope — required — (String)

                The parts of the JSON to match against using the MatchPattern. If you specify All, WAF matches against keys and values.

                Possible values include:
                • "ALL"
                • "KEY"
                • "VALUE"
              • InvalidFallbackBehavior — (String)

                What WAF should do if it fails to completely parse the JSON body. The options are the following:

                • EVALUATE_AS_STRING - Inspect the body as plain text. WAF applies the text transformations and inspection criteria that you defined for the JSON inspection to the body text string.

                • MATCH - Treat the web request as matching the rule statement. WAF applies the rule action to the request.

                • NO_MATCH - Treat the web request as not matching the rule statement.

                If you don't provide this setting, WAF parses and evaluates the content only up to the first parsing failure that it encounters.

                WAF does its best to parse the entire JSON body, but might be forced to stop for reasons such as invalid characters, duplicate keys, truncation, and any content whose root node isn't an object or an array.

                WAF parses the JSON in the following examples as two valid key, value pairs:

                • Missing comma: {"key1":"value1""key2":"value2"}

                • Missing colon: {"key1":"value1","key2""value2"}

                • Extra colons: {"key1"::"value1","key2""value2"}

                Possible values include:
                • "MATCH"
                • "NO_MATCH"
                • "EVALUATE_AS_STRING"
          • TextTransformations — required — (Array<map>)

            Text transformations eliminate some of the unusual formatting that attackers use in web requests in an effort to bypass detection. If you specify one or more transformations in a rule statement, WAF performs all transformations on the content of the request component identified by FieldToMatch, starting from the lowest priority setting, before inspecting the content for a match.

            • Priority — required — (Integer)

              Sets the relative processing order for multiple transformations that are defined for a rule statement. WAF processes all transformations, from lowest priority to highest, before inspecting the transformed content. The priorities don't need to be consecutive, but they must all be different.

            • Type — required — (String)

              You can specify the following transformation types:

              BASE64_DECODE - Decode a Base64-encoded string.

              BASE64_DECODE_EXT - Decode a Base64-encoded string, but use a forgiving implementation that ignores characters that aren't valid.

              CMD_LINE - Command-line transformations. These are helpful in reducing effectiveness of attackers who inject an operating system command-line command and use unusual formatting to disguise some or all of the command.

              • Delete the following characters: \ " ' ^

              • Delete spaces before the following characters: / (

              • Replace the following characters with a space: , ;

              • Replace multiple spaces with one space

              • Convert uppercase letters (A-Z) to lowercase (a-z)

              COMPRESS_WHITE_SPACE - Replace these characters with a space character (decimal 32):

              • \f, formfeed, decimal 12

              • \t, tab, decimal 9

              • \n, newline, decimal 10

              • \r, carriage return, decimal 13

              • \v, vertical tab, decimal 11

              • Non-breaking space, decimal 160

              COMPRESS_WHITE_SPACE also replaces multiple spaces with one space.

              CSS_DECODE - Decode characters that were encoded using CSS 2.x escape rules syndata.html#characters. This function uses up to two bytes in the decoding process, so it can help to uncover ASCII characters that were encoded using CSS encoding that wouldn’t typically be encoded. It's also useful in countering evasion, which is a combination of a backslash and non-hexadecimal characters. For example, ja\vascript for javascript.

              ESCAPE_SEQ_DECODE - Decode the following ANSI C escape sequences: \a, \b, \f, \n, \r, \t, \v, \, \?, \', \", \xHH (hexadecimal), \0OOO (octal). Encodings that aren't valid remain in the output.

              HEX_DECODE - Decode a string of hexadecimal characters into a binary.

              HTML_ENTITY_DECODE - Replace HTML-encoded characters with unencoded characters. HTML_ENTITY_DECODE performs these operations:

              • Replaces (ampersand)quot; with "

              • Replaces (ampersand)nbsp; with a non-breaking space, decimal 160

              • Replaces (ampersand)lt; with a "less than" symbol

              • Replaces (ampersand)gt; with >

              • Replaces characters that are represented in hexadecimal format, (ampersand)#xhhhh;, with the corresponding characters

              • Replaces characters that are represented in decimal format, (ampersand)#nnnn;, with the corresponding characters

              JS_DECODE - Decode JavaScript escape sequences. If a \ u HHHH code is in the full-width ASCII code range of FF01-FF5E, then the higher byte is used to detect and adjust the lower byte. If not, only the lower byte is used and the higher byte is zeroed, causing a possible loss of information.

              LOWERCASE - Convert uppercase letters (A-Z) to lowercase (a-z).

              MD5 - Calculate an MD5 hash from the data in the input. The computed hash is in a raw binary form.

              NONE - Specify NONE if you don't want any text transformations.

              NORMALIZE_PATH - Remove multiple slashes, directory self-references, and directory back-references that are not at the beginning of the input from an input string.

              NORMALIZE_PATH_WIN - This is the same as NORMALIZE_PATH, but first converts backslash characters to forward slashes.

              REMOVE_NULLS - Remove all NULL bytes from the input.

              REPLACE_COMMENTS - Replace each occurrence of a C-style comment (/* ... */) with a single space. Multiple consecutive occurrences are not compressed. Unterminated comments are also replaced with a space (ASCII 0x20). However, a standalone termination of a comment (*/) is not acted upon.

              REPLACE_NULLS - Replace NULL bytes in the input with space characters (ASCII 0x20).

              SQL_HEX_DECODE - Decode SQL hex data. Example (0x414243) will be decoded to (ABC).

              URL_DECODE - Decode a URL-encoded value.

              URL_DECODE_UNI - Like URL_DECODE, but with support for Microsoft-specific %u encoding. If the code is in the full-width ASCII code range of FF01-FF5E, the higher byte is used to detect and adjust the lower byte. Otherwise, only the lower byte is used and the higher byte is zeroed.

              UTF8_TO_UNICODE - Convert all UTF-8 character sequences to Unicode. This helps input normalization, and minimizing false-positives and false-negatives for non-English languages.

              Possible values include:
              • "NONE"
              • "COMPRESS_WHITE_SPACE"
              • "HTML_ENTITY_DECODE"
              • "LOWERCASE"
              • "CMD_LINE"
              • "URL_DECODE"
              • "BASE64_DECODE"
              • "HEX_DECODE"
              • "MD5"
              • "REPLACE_COMMENTS"
              • "ESCAPE_SEQ_DECODE"
              • "SQL_HEX_DECODE"
              • "CSS_DECODE"
              • "JS_DECODE"
              • "NORMALIZE_PATH"
              • "NORMALIZE_PATH_WIN"
              • "REMOVE_NULLS"
              • "REPLACE_NULLS"
              • "BASE64_DECODE_EXT"
              • "URL_DECODE_UNI"
              • "UTF8_TO_UNICODE"
        • XssMatchStatement — (map)

          A rule statement that defines a cross-site scripting (XSS) match search for WAF to apply to web requests. XSS attacks are those where the attacker uses vulnerabilities in a benign website as a vehicle to inject malicious client-site scripts into other legitimate web browsers. The XSS match statement provides the location in requests that you want WAF to search and text transformations to use on the search area before WAF searches for character sequences that are likely to be malicious strings.

          • FieldToMatch — required — (map)

            The part of a web request that you want WAF to inspect. For more information, see FieldToMatch.

            • SingleHeader — (map)

              Inspect a single header. Provide the name of the header to inspect, for example, User-Agent or Referer. This setting isn't case sensitive.

              Example JSON: "SingleHeader": { "Name": "haystack" }

              • Name — required — (String)

                The name of the query header to inspect.

            • SingleQueryArgument — (map)

              Inspect a single query argument. Provide the name of the query argument to inspect, such as UserName or SalesRegion. The name can be up to 30 characters long and isn't case sensitive.

              This is used only to indicate the web request component for WAF to inspect, in the FieldToMatch specification.

              Example JSON: "SingleQueryArgument": { "Name": "myArgument" }

              • Name — required — (String)

                The name of the query argument to inspect.

            • AllQueryArguments — (map)

              Inspect all query arguments.

            • UriPath — (map)

              Inspect the request URI path. This is the part of a web request that identifies a resource, for example, /images/daily-ad.jpg.

            • QueryString — (map)

              Inspect the query string. This is the part of a URL that appears after a ? character, if any.

            • Body — (map)

              Inspect the request body as plain text. The request body immediately follows the request headers. This is the part of a request that contains any additional data that you want to send to your web server as the HTTP request body, such as data from a form.

              Note that only the first 8 KB (8192 bytes) of the request body are forwarded to WAF for inspection by the underlying host service. If you don't need to inspect more than 8 KB, you can guarantee that you don't allow additional bytes in by combining a statement that inspects the body of the web request, such as ByteMatchStatement or RegexPatternSetReferenceStatement, with a SizeConstraintStatement that enforces an 8 KB size limit on the body of the request. WAF doesn't support inspecting the entire contents of web requests whose bodies exceed the 8 KB limit.

            • Method — (map)

              Inspect the HTTP method. The method indicates the type of operation that the request is asking the origin to perform.

            • JsonBody — (map)

              Inspect the request body as JSON. The request body immediately follows the request headers. This is the part of a request that contains any additional data that you want to send to your web server as the HTTP request body, such as data from a form.

              Note that only the first 8 KB (8192 bytes) of the request body are forwarded to WAF for inspection by the underlying host service. If you don't need to inspect more than 8 KB, you can guarantee that you don't allow additional bytes in by combining a statement that inspects the body of the web request, such as ByteMatchStatement or RegexPatternSetReferenceStatement, with a SizeConstraintStatement that enforces an 8 KB size limit on the body of the request. WAF doesn't support inspecting the entire contents of web requests whose bodies exceed the 8 KB limit.

              • MatchPattern — required — (map)

                The patterns to look for in the JSON body. WAF inspects the results of these pattern matches against the rule inspection criteria.

                • All — (map)

                  Match all of the elements. See also MatchScope in JsonBody.

                  You must specify either this setting or the IncludedPaths setting, but not both.

                • IncludedPaths — (Array<String>)

                  Match only the specified include paths. See also MatchScope in JsonBody.

                  Provide the include paths using JSON Pointer syntax. For example, "IncludedPaths": ["/dogs/0/name", "/dogs/1/name"]. For information about this syntax, see the Internet Engineering Task Force (IETF) documentation JavaScript Object Notation (JSON) Pointer.

                  You must specify either this setting or the All setting, but not both.

                  Note: Don't use this option to include all paths. Instead, use the All setting.
              • MatchScope — required — (String)

                The parts of the JSON to match against using the MatchPattern. If you specify All, WAF matches against keys and values.

                Possible values include:
                • "ALL"
                • "KEY"
                • "VALUE"
              • InvalidFallbackBehavior — (String)

                What WAF should do if it fails to completely parse the JSON body. The options are the following:

                • EVALUATE_AS_STRING - Inspect the body as plain text. WAF applies the text transformations and inspection criteria that you defined for the JSON inspection to the body text string.

                • MATCH - Treat the web request as matching the rule statement. WAF applies the rule action to the request.

                • NO_MATCH - Treat the web request as not matching the rule statement.

                If you don't provide this setting, WAF parses and evaluates the content only up to the first parsing failure that it encounters.

                WAF does its best to parse the entire JSON body, but might be forced to stop for reasons such as invalid characters, duplicate keys, truncation, and any content whose root node isn't an object or an array.

                WAF parses the JSON in the following examples as two valid key, value pairs:

                • Missing comma: {"key1":"value1""key2":"value2"}

                • Missing colon: {"key1":"value1","key2""value2"}

                • Extra colons: {"key1"::"value1","key2""value2"}

                Possible values include:
                • "MATCH"
                • "NO_MATCH"
                • "EVALUATE_AS_STRING"
          • TextTransformations — required — (Array<map>)

            Text transformations eliminate some of the unusual formatting that attackers use in web requests in an effort to bypass detection. If you specify one or more transformations in a rule statement, WAF performs all transformations on the content of the request component identified by FieldToMatch, starting from the lowest priority setting, before inspecting the content for a match.

            • Priority — required — (Integer)

              Sets the relative processing order for multiple transformations that are defined for a rule statement. WAF processes all transformations, from lowest priority to highest, before inspecting the transformed content. The priorities don't need to be consecutive, but they must all be different.

            • Type — required — (String)

              You can specify the following transformation types:

              BASE64_DECODE - Decode a Base64-encoded string.

              BASE64_DECODE_EXT - Decode a Base64-encoded string, but use a forgiving implementation that ignores characters that aren't valid.

              CMD_LINE - Command-line transformations. These are helpful in reducing effectiveness of attackers who inject an operating system command-line command and use unusual formatting to disguise some or all of the command.

              • Delete the following characters: \ " ' ^

              • Delete spaces before the following characters: / (

              • Replace the following characters with a space: , ;

              • Replace multiple spaces with one space

              • Convert uppercase letters (A-Z) to lowercase (a-z)

              COMPRESS_WHITE_SPACE - Replace these characters with a space character (decimal 32):

              • \f, formfeed, decimal 12

              • \t, tab, decimal 9

              • \n, newline, decimal 10

              • \r, carriage return, decimal 13

              • \v, vertical tab, decimal 11

              • Non-breaking space, decimal 160

              COMPRESS_WHITE_SPACE also replaces multiple spaces with one space.

              CSS_DECODE - Decode characters that were encoded using CSS 2.x escape rules syndata.html#characters. This function uses up to two bytes in the decoding process, so it can help to uncover ASCII characters that were encoded using CSS encoding that wouldn’t typically be encoded. It's also useful in countering evasion, which is a combination of a backslash and non-hexadecimal characters. For example, ja\vascript for javascript.

              ESCAPE_SEQ_DECODE - Decode the following ANSI C escape sequences: \a, \b, \f, \n, \r, \t, \v, \, \?, \', \", \xHH (hexadecimal), \0OOO (octal). Encodings that aren't valid remain in the output.

              HEX_DECODE - Decode a string of hexadecimal characters into a binary.

              HTML_ENTITY_DECODE - Replace HTML-encoded characters with unencoded characters. HTML_ENTITY_DECODE performs these operations:

              • Replaces (ampersand)quot; with "

              • Replaces (ampersand)nbsp; with a non-breaking space, decimal 160

              • Replaces (ampersand)lt; with a "less than" symbol

              • Replaces (ampersand)gt; with >

              • Replaces characters that are represented in hexadecimal format, (ampersand)#xhhhh;, with the corresponding characters

              • Replaces characters that are represented in decimal format, (ampersand)#nnnn;, with the corresponding characters

              JS_DECODE - Decode JavaScript escape sequences. If a \ u HHHH code is in the full-width ASCII code range of FF01-FF5E, then the higher byte is used to detect and adjust the lower byte. If not, only the lower byte is used and the higher byte is zeroed, causing a possible loss of information.

              LOWERCASE - Convert uppercase letters (A-Z) to lowercase (a-z).

              MD5 - Calculate an MD5 hash from the data in the input. The computed hash is in a raw binary form.

              NONE - Specify NONE if you don't want any text transformations.

              NORMALIZE_PATH - Remove multiple slashes, directory self-references, and directory back-references that are not at the beginning of the input from an input string.

              NORMALIZE_PATH_WIN - This is the same as NORMALIZE_PATH, but first converts backslash characters to forward slashes.

              REMOVE_NULLS - Remove all NULL bytes from the input.

              REPLACE_COMMENTS - Replace each occurrence of a C-style comment (/* ... */) with a single space. Multiple consecutive occurrences are not compressed. Unterminated comments are also replaced with a space (ASCII 0x20). However, a standalone termination of a comment (*/) is not acted upon.

              REPLACE_NULLS - Replace NULL bytes in the input with space characters (ASCII 0x20).

              SQL_HEX_DECODE - Decode SQL hex data. Example (0x414243) will be decoded to (ABC).

              URL_DECODE - Decode a URL-encoded value.

              URL_DECODE_UNI - Like URL_DECODE, but with support for Microsoft-specific %u encoding. If the code is in the full-width ASCII code range of FF01-FF5E, the higher byte is used to detect and adjust the lower byte. Otherwise, only the lower byte is used and the higher byte is zeroed.

              UTF8_TO_UNICODE - Convert all UTF-8 character sequences to Unicode. This helps input normalization, and minimizing false-positives and false-negatives for non-English languages.

              Possible values include:
              • "NONE"
              • "COMPRESS_WHITE_SPACE"
              • "HTML_ENTITY_DECODE"
              • "LOWERCASE"
              • "CMD_LINE"
              • "URL_DECODE"
              • "BASE64_DECODE"
              • "HEX_DECODE"
              • "MD5"
              • "REPLACE_COMMENTS"
              • "ESCAPE_SEQ_DECODE"
              • "SQL_HEX_DECODE"
              • "CSS_DECODE"
              • "JS_DECODE"
              • "NORMALIZE_PATH"
              • "NORMALIZE_PATH_WIN"
              • "REMOVE_NULLS"
              • "REPLACE_NULLS"
              • "BASE64_DECODE_EXT"
              • "URL_DECODE_UNI"
              • "UTF8_TO_UNICODE"
        • SizeConstraintStatement — (map)

          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 first 8192 bytes (8 KB). If the request body for your web requests never exceeds 8192 bytes, you can create a size constraint condition and block requests that have a request body greater than 8192 bytes.

          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.

          • FieldToMatch — required — (map)

            The part of a web request that you want WAF to inspect. For more information, see FieldToMatch.

            • SingleHeader — (map)

              Inspect a single header. Provide the name of the header to inspect, for example, User-Agent or Referer. This setting isn't case sensitive.

              Example JSON: "SingleHeader": { "Name": "haystack" }

              • Name — required — (String)

                The name of the query header to inspect.

            • SingleQueryArgument — (map)

              Inspect a single query argument. Provide the name of the query argument to inspect, such as UserName or SalesRegion. The name can be up to 30 characters long and isn't case sensitive.

              This is used only to indicate the web request component for WAF to inspect, in the FieldToMatch specification.

              Example JSON: "SingleQueryArgument": { "Name": "myArgument" }

              • Name — required — (String)

                The name of the query argument to inspect.

            • AllQueryArguments — (map)

              Inspect all query arguments.

            • UriPath — (map)

              Inspect the request URI path. This is the part of a web request that identifies a resource, for example, /images/daily-ad.jpg.

            • QueryString — (map)

              Inspect the query string. This is the part of a URL that appears after a ? character, if any.

            • Body — (map)

              Inspect the request body as plain text. The request body immediately follows the request headers. This is the part of a request that contains any additional data that you want to send to your web server as the HTTP request body, such as data from a form.

              Note that only the first 8 KB (8192 bytes) of the request body are forwarded to WAF for inspection by the underlying host service. If you don't need to inspect more than 8 KB, you can guarantee that you don't allow additional bytes in by combining a statement that inspects the body of the web request, such as ByteMatchStatement or RegexPatternSetReferenceStatement, with a SizeConstraintStatement that enforces an 8 KB size limit on the body of the request. WAF doesn't support inspecting the entire contents of web requests whose bodies exceed the 8 KB limit.

            • Method — (map)

              Inspect the HTTP method. The method indicates the type of operation that the request is asking the origin to perform.

            • JsonBody — (map)

              Inspect the request body as JSON. The request body immediately follows the request headers. This is the part of a request that contains any additional data that you want to send to your web server as the HTTP request body, such as data from a form.

              Note that only the first 8 KB (8192 bytes) of the request body are forwarded to WAF for inspection by the underlying host service. If you don't need to inspect more than 8 KB, you can guarantee that you don't allow additional bytes in by combining a statement that inspects the body of the web request, such as ByteMatchStatement or RegexPatternSetReferenceStatement, with a SizeConstraintStatement that enforces an 8 KB size limit on the body of the request. WAF doesn't support inspecting the entire contents of web requests whose bodies exceed the 8 KB limit.

              • MatchPattern — required — (map)

                The patterns to look for in the JSON body. WAF inspects the results of these pattern matches against the rule inspection criteria.

                • All — (map)

                  Match all of the elements. See also MatchScope in JsonBody.

                  You must specify either this setting or the IncludedPaths setting, but not both.

                • IncludedPaths — (Array<String>)

                  Match only the specified include paths. See also MatchScope in JsonBody.

                  Provide the include paths using JSON Pointer syntax. For example, "IncludedPaths": ["/dogs/0/name", "/dogs/1/name"]. For information about this syntax, see the Internet Engineering Task Force (IETF) documentation JavaScript Object Notation (JSON) Pointer.

                  You must specify either this setting or the All setting, but not both.

                  Note: Don't use this option to include all paths. Instead, use the All setting.
              • MatchScope — required — (String)

                The parts of the JSON to match against using the MatchPattern. If you specify All, WAF matches against keys and values.

                Possible values include:
                • "ALL"
                • "KEY"
                • "VALUE"
              • InvalidFallbackBehavior — (String)

                What WAF should do if it fails to completely parse the JSON body. The options are the following:

                • EVALUATE_AS_STRING - Inspect the body as plain text. WAF applies the text transformations and inspection criteria that you defined for the JSON inspection to the body text string.

                • MATCH - Treat the web request as matching the rule statement. WAF applies the rule action to the request.

                • NO_MATCH - Treat the web request as not matching the rule statement.

                If you don't provide this setting, WAF parses and evaluates the content only up to the first parsing failure that it encounters.

                WAF does its best to parse the entire JSON body, but might be forced to stop for reasons such as invalid characters, duplicate keys, truncation, and any content whose root node isn't an object or an array.

                WAF parses the JSON in the following examples as two valid key, value pairs:

                • Missing comma: {"key1":"value1""key2":"value2"}

                • Missing colon: {"key1":"value1","key2""value2"}

                • Extra colons: {"key1"::"value1","key2""value2"}

                Possible values include:
                • "MATCH"
                • "NO_MATCH"
                • "EVALUATE_AS_STRING"
          • ComparisonOperator — required — (String)

            The operator to use to compare the request part to the size setting.

            Possible values include:
            • "EQ"
            • "NE"
            • "LE"
            • "LT"
            • "GE"
            • "GT"
          • Size — required — (Integer)

            The size, in byte, to compare to the request part, after any transformations.

          • TextTransformations — required — (Array<map>)

            Text transformations eliminate some of the unusual formatting that attackers use in web requests in an effort to bypass detection. If you specify one or more transformations in a rule statement, WAF performs all transformations on the content of the request component identified by FieldToMatch, starting from the lowest priority setting, before inspecting the content for a match.

            • Priority — required — (Integer)

              Sets the relative processing order for multiple transformations that are defined for a rule statement. WAF processes all transformations, from lowest priority to highest, before inspecting the transformed content. The priorities don't need to be consecutive, but they must all be different.

            • Type — required — (String)

              You can specify the following transformation types:

              BASE64_DECODE - Decode a Base64-encoded string.

              BASE64_DECODE_EXT - Decode a Base64-encoded string, but use a forgiving implementation that ignores characters that aren't valid.

              CMD_LINE - Command-line transformations. These are helpful in reducing effectiveness of attackers who inject an operating system command-line command and use unusual formatting to disguise some or all of the command.

              • Delete the following characters: \ " ' ^

              • Delete spaces before the following characters: / (

              • Replace the following characters with a space: , ;

              • Replace multiple spaces with one space

              • Convert uppercase letters (A-Z) to lowercase (a-z)

              COMPRESS_WHITE_SPACE - Replace these characters with a space character (decimal 32):

              • \f, formfeed, decimal 12

              • \t, tab, decimal 9

              • \n, newline, decimal 10

              • \r, carriage return, decimal 13

              • \v, vertical tab, decimal 11

              • Non-breaking space, decimal 160

              COMPRESS_WHITE_SPACE also replaces multiple spaces with one space.

              CSS_DECODE - Decode characters that were encoded using CSS 2.x escape rules syndata.html#characters. This function uses up to two bytes in the decoding process, so it can help to uncover ASCII characters that were encoded using CSS encoding that wouldn’t typically be encoded. It's also useful in countering evasion, which is a combination of a backslash and non-hexadecimal characters. For example, ja\vascript for javascript.

              ESCAPE_SEQ_DECODE - Decode the following ANSI C escape sequences: \a, \b, \f, \n, \r, \t, \v, \, \?, \', \", \xHH (hexadecimal), \0OOO (octal). Encodings that aren't valid remain in the output.

              HEX_DECODE - Decode a string of hexadecimal characters into a binary.

              HTML_ENTITY_DECODE - Replace HTML-encoded characters with unencoded characters. HTML_ENTITY_DECODE performs these operations:

              • Replaces (ampersand)quot; with "

              • Replaces (ampersand)nbsp; with a non-breaking space, decimal 160

              • Replaces (ampersand)lt; with a "less than" symbol

              • Replaces (ampersand)gt; with >

              • Replaces characters that are represented in hexadecimal format, (ampersand)#xhhhh;, with the corresponding characters

              • Replaces characters that are represented in decimal format, (ampersand)#nnnn;, with the corresponding characters

              JS_DECODE - Decode JavaScript escape sequences. If a \ u HHHH code is in the full-width ASCII code range of FF01-FF5E, then the higher byte is used to detect and adjust the lower byte. If not, only the lower byte is used and the higher byte is zeroed, causing a possible loss of information.

              LOWERCASE - Convert uppercase letters (A-Z) to lowercase (a-z).

              MD5 - Calculate an MD5 hash from the data in the input. The computed hash is in a raw binary form.

              NONE - Specify NONE if you don't want any text transformations.

              NORMALIZE_PATH - Remove multiple slashes, directory self-references, and directory back-references that are not at the beginning of the input from an input string.

              NORMALIZE_PATH_WIN - This is the same as NORMALIZE_PATH, but first converts backslash characters to forward slashes.

              REMOVE_NULLS - Remove all NULL bytes from the input.

              REPLACE_COMMENTS - Replace each occurrence of a C-style comment (/* ... */) with a single space. Multiple consecutive occurrences are not compressed. Unterminated comments are also replaced with a space (ASCII 0x20). However, a standalone termination of a comment (*/) is not acted upon.

              REPLACE_NULLS - Replace NULL bytes in the input with space characters (ASCII 0x20).

              SQL_HEX_DECODE - Decode SQL hex data. Example (0x414243) will be decoded to (ABC).

              URL_DECODE - Decode a URL-encoded value.

              URL_DECODE_UNI - Like URL_DECODE, but with support for Microsoft-specific %u encoding. If the code is in the full-width ASCII code range of FF01-FF5E, the higher byte is used to detect and adjust the lower byte. Otherwise, only the lower byte is used and the higher byte is zeroed.

              UTF8_TO_UNICODE - Convert all UTF-8 character sequences to Unicode. This helps input normalization, and minimizing false-positives and false-negatives for non-English languages.

              Possible values include:
              • "NONE"
              • "COMPRESS_WHITE_SPACE"
              • "HTML_ENTITY_DECODE"
              • "LOWERCASE"
              • "CMD_LINE"
              • "URL_DECODE"
              • "BASE64_DECODE"
              • "HEX_DECODE"
              • "MD5"
              • "REPLACE_COMMENTS"
              • "ESCAPE_SEQ_DECODE"
              • "SQL_HEX_DECODE"
              • "CSS_DECODE"
              • "JS_DECODE"
              • "NORMALIZE_PATH"
              • "NORMALIZE_PATH_WIN"
              • "REMOVE_NULLS"
              • "REPLACE_NULLS"
              • "BASE64_DECODE_EXT"
              • "URL_DECODE_UNI"
              • "UTF8_TO_UNICODE"
        • GeoMatchStatement — (map)

          A rule statement used to identify web requests based on country of origin.

          • CountryCodes — (Array<String>)

            An array of two-character country codes, for example, [ "US", "CN" ], from the alpha-2 country ISO codes of the ISO 3166 international standard.

          • ForwardedIPConfig — (map)

            The configuration for inspecting IP addresses in an HTTP header that you specify, instead of using the IP address that's reported by the web request origin. Commonly, this is the X-Forwarded-For (XFF) header, but you can specify any header name.

            Note: If the specified header isn't present in the request, WAF doesn't apply the rule to the web request at all.
            • HeaderName — required — (String)

              The name of the HTTP header to use for the IP address. For example, to use the X-Forwarded-For (XFF) header, set this to X-Forwarded-For.

              Note: If the specified header isn't present in the request, WAF doesn't apply the rule to the web request at all.
            • FallbackBehavior — required — (String)

              The match status to assign to the web request if the request doesn't have a valid IP address in the specified position.

              Note: If the specified header isn't present in the request, WAF doesn't apply the rule to the web request at all.

              You can specify the following fallback behaviors:

              • MATCH - Treat the web request as matching the rule statement. WAF applies the rule action to the request.

              • NO_MATCH - Treat the web request as not matching the rule statement.

              Possible values include:
              • "MATCH"
              • "NO_MATCH"
        • RuleGroupReferenceStatement — (map)

          A rule statement used to run the rules that are defined in a RuleGroup. To use this, create a rule group with your rules, then provide the ARN of the rule group in this statement.

          You cannot nest a RuleGroupReferenceStatement, for example for use inside a NotStatement or OrStatement. You can only use a rule group reference statement at the top level inside a web ACL.

          • ARN — required — (String)

            The Amazon Resource Name (ARN) of the entity.

          • ExcludedRules — (Array<map>)

            The rules in the referenced rule group whose actions are set to Count. When you exclude a rule, WAF evaluates it exactly as it would if the rule action setting were Count. This is a useful option for testing the rules in a rule group without modifying how they handle your web traffic.

            • Name — required — (String)

              The name of the rule whose action you want to override to Count.

        • IPSetReferenceStatement — (map)

          A rule statement used to detect web requests coming from particular IP addresses or address ranges. To use this, create an IPSet that specifies the addresses you want to detect, then use the ARN of that set in this statement. To create an IP set, see CreateIPSet.

          Each IP set rule statement references an IP set. You create and maintain the set independent of your rules. This allows you to use the single set in multiple rules. When you update the referenced set, WAF automatically updates all rules that reference it.

          • ARN — required — (String)

            The Amazon Resource Name (ARN) of the IPSet that this statement references.

          • IPSetForwardedIPConfig — (map)

            The configuration for inspecting IP addresses in an HTTP header that you specify, instead of using the IP address that's reported by the web request origin. Commonly, this is the X-Forwarded-For (XFF) header, but you can specify any header name.

            Note: If the specified header isn't present in the request, WAF doesn't apply the rule to the web request at all.
            • HeaderName — required — (String)

              The name of the HTTP header to use for the IP address. For example, to use the X-Forwarded-For (XFF) header, set this to X-Forwarded-For.

              Note: If the specified header isn't present in the request, WAF doesn't apply the rule to the web request at all.
            • FallbackBehavior — required — (String)

              The match status to assign to the web request if the request doesn't have a valid IP address in the specified position.

              Note: If the specified header isn't present in the request, WAF doesn't apply the rule to the web request at all.

              You can specify the following fallback behaviors:

              • MATCH - Treat the web request as matching the rule statement. WAF applies the rule action to the request.

              • NO_MATCH - Treat the web request as not matching the rule statement.

              Possible values include:
              • "MATCH"
              • "NO_MATCH"
            • Position — required — (String)

              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:

              • FIRST - Inspect the first IP address in the list of IP addresses in the header. This is usually the client's original IP.

              • LAST - Inspect the last IP address in the list of IP addresses in the header.

              • ANY - Inspect all IP addresses in the header for a match. If the header contains more than 10 IP addresses, WAF inspects the last 10.

              Possible values include:
              • "FIRST"
              • "LAST"
              • "ANY"
        • RegexPatternSetReferenceStatement — (map)

          A rule statement used to search web request components for matches with regular expressions. To use this, create a RegexPatternSet that specifies the expressions that you want to detect, then use the ARN of that set in this statement. A web request matches the pattern set rule statement if the request component matches any of the patterns in the set. To create a regex pattern set, see CreateRegexPatternSet.

          Each regex pattern set rule statement references a regex pattern set. You create and maintain the set independent of your rules. This allows you to use the single set in multiple rules. When you update the referenced set, WAF automatically updates all rules that reference it.

          • ARN — required — (String)

            The Amazon Resource Name (ARN) of the RegexPatternSet that this statement references.

          • FieldToMatch — required — (map)

            The part of a web request that you want WAF to inspect. For more information, see FieldToMatch.

            • SingleHeader — (map)

              Inspect a single header. Provide the name of the header to inspect, for example, User-Agent or Referer. This setting isn't case sensitive.

              Example JSON: "SingleHeader": { "Name": "haystack" }

              • Name — required — (String)

                The name of the query header to inspect.

            • SingleQueryArgument — (map)

              Inspect a single query argument. Provide the name of the query argument to inspect, such as UserName or SalesRegion. The name can be up to 30 characters long and isn't case sensitive.

              This is used only to indicate the web request component for WAF to inspect, in the FieldToMatch specification.

              Example JSON: "SingleQueryArgument": { "Name": "myArgument" }

              • Name — required — (String)

                The name of the query argument to inspect.

            • AllQueryArguments — (map)

              Inspect all query arguments.

            • UriPath — (map)

              Inspect the request URI path. This is the part of a web request that identifies a resource, for example, /images/daily-ad.jpg.

            • QueryString — (map)

              Inspect the query string. This is the part of a URL that appears after a ? character, if any.

            • Body — (map)

              Inspect the request body as plain text. The request body immediately follows the request headers. This is the part of a request that contains any additional data that you want to send to your web server as the HTTP request body, such as data from a form.

              Note that only the first 8 KB (8192 bytes) of the request body are forwarded to WAF for inspection by the underlying host service. If you don't need to inspect more than 8 KB, you can guarantee that you don't allow additional bytes in by combining a statement that inspects the body of the web request, such as ByteMatchStatement or RegexPatternSetReferenceStatement, with a SizeConstraintStatement that enforces an 8 KB size limit on the body of the request. WAF doesn't support inspecting the entire contents of web requests whose bodies exceed the 8 KB limit.

            • Method — (map)

              Inspect the HTTP method. The method indicates the type of operation that the request is asking the origin to perform.

            • JsonBody — (map)

              Inspect the request body as JSON. The request body immediately follows the request headers. This is the part of a request that contains any additional data that you want to send to your web server as the HTTP request body, such as data from a form.

              Note that only the first 8 KB (8192 bytes) of the request body are forwarded to WAF for inspection by the underlying host service. If you don't need to inspect more than 8 KB, you can guarantee that you don't allow additional bytes in by combining a statement that inspects the body of the web request, such as ByteMatchStatement or RegexPatternSetReferenceStatement, with a SizeConstraintStatement that enforces an 8 KB size limit on the body of the request. WAF doesn't support inspecting the entire contents of web requests whose bodies exceed the 8 KB limit.

              • MatchPattern — required — (map)

                The patterns to look for in the JSON body. WAF inspects the results of these pattern matches against the rule inspection criteria.

                • All — (map)

                  Match all of the elements. See also MatchScope in JsonBody.

                  You must specify either this setting or the IncludedPaths setting, but not both.

                • IncludedPaths — (Array<String>)

                  Match only the specified include paths. See also MatchScope in JsonBody.

                  Provide the include paths using JSON Pointer syntax. For example, "IncludedPaths": ["/dogs/0/name", "/dogs/1/name"]. For information about this syntax, see the Internet Engineering Task Force (IETF) documentation JavaScript Object Notation (JSON) Pointer.

                  You must specify either this setting or the All setting, but not both.

                  Note: Don't use this option to include all paths. Instead, use the All setting.
              • MatchScope — required — (String)

                The parts of the JSON to match against using the MatchPattern. If you specify All, WAF matches against keys and values.

                Possible values include:
                • "ALL"
                • "KEY"
                • "VALUE"
              • InvalidFallbackBehavior — (String)

                What WAF should do if it fails to completely parse the JSON body. The options are the following:

                • EVALUATE_AS_STRING - Inspect the body as plain text. WAF applies the text transformations and inspection criteria that you defined for the JSON inspection to the body text string.

                • MATCH - Treat the web request as matching the rule statement. WAF applies the rule action to the request.

                • NO_MATCH - Treat the web request as not matching the rule statement.

                If you don't provide this setting, WAF parses and evaluates the content only up to the first parsing failure that it encounters.

                WAF does its best to parse the entire JSON body, but might be forced to stop for reasons such as invalid characters, duplicate keys, truncation, and any content whose root node isn't an object or an array.

                WAF parses the JSON in the following examples as two valid key, value pairs:

                • Missing comma: {"key1":"value1""key2":"value2"}

                • Missing colon: {"key1":"value1","key2""value2"}

                • Extra colons: {"key1"::"value1","key2""value2"}

                Possible values include:
                • "MATCH"
                • "NO_MATCH"
                • "EVALUATE_AS_STRING"
          • TextTransformations — required — (Array<map>)

            Text transformations eliminate some of the unusual formatting that attackers use in web requests in an effort to bypass detection. If you specify one or more transformations in a rule statement, WAF performs all transformations on the content of the request component identified by FieldToMatch, starting from the lowest priority setting, before inspecting the content for a match.

            • Priority — required — (Integer)

              Sets the relative processing order for multiple transformations that are defined for a rule statement. WAF processes all transformations, from lowest priority to highest, before inspecting the transformed content. The priorities don't need to be consecutive, but they must all be different.

            • Type — required — (String)

              You can specify the following transformation types:

              BASE64_DECODE - Decode a Base64-encoded string.

              BASE64_DECODE_EXT - Decode a Base64-encoded string, but use a forgiving implementation that ignores characters that aren't valid.

              CMD_LINE - Command-line transformations. These are helpful in reducing effectiveness of attackers who inject an operating system command-line command and use unusual formatting to disguise some or all of the command.

              • Delete the following characters: \ " ' ^

              • Delete spaces before the following characters: / (

              • Replace the following characters with a space: , ;

              • Replace multiple spaces with one space

              • Convert uppercase letters (A-Z) to lowercase (a-z)

              COMPRESS_WHITE_SPACE - Replace these characters with a space character (decimal 32):

              • \f, formfeed, decimal 12

              • \t, tab, decimal 9

              • \n, newline, decimal 10

              • \r, carriage return, decimal 13

              • \v, vertical tab, decimal 11

              • Non-breaking space, decimal 160

              COMPRESS_WHITE_SPACE also replaces multiple spaces with one space.

              CSS_DECODE - Decode characters that were encoded using CSS 2.x escape rules syndata.html#characters. This function uses up to two bytes in the decoding process, so it can help to uncover ASCII characters that were encoded using CSS encoding that wouldn’t typically be encoded. It's also useful in countering evasion, which is a combination of a backslash and non-hexadecimal characters. For example, ja\vascript for javascript.

              ESCAPE_SEQ_DECODE - Decode the following ANSI C escape sequences: \a, \b, \f, \n, \r, \t, \v, \, \?, \', \", \xHH (hexadecimal), \0OOO (octal). Encodings that aren't valid remain in the output.

              HEX_DECODE - Decode a string of hexadecimal characters into a binary.

              HTML_ENTITY_DECODE - Replace HTML-encoded characters with unencoded characters. HTML_ENTITY_DECODE performs these operations:

              • Replaces (ampersand)quot; with "

              • Replaces (ampersand)nbsp; with a non-breaking space, decimal 160

              • Replaces (ampersand)lt; with a "less than" symbol

              • Replaces (ampersand)gt; with >

              • Replaces characters that are represented in hexadecimal format, (ampersand)#xhhhh;, with the corresponding characters

              • Replaces characters that are represented in decimal format, (ampersand)#nnnn;, with the corresponding characters

              JS_DECODE - Decode JavaScript escape sequences. If a \ u HHHH code is in the full-width ASCII code range of FF01-FF5E, then the higher byte is used to detect and adjust the lower byte. If not, only the lower byte is used and the higher byte is zeroed, causing a possible loss of information.

              LOWERCASE - Convert uppercase letters (A-Z) to lowercase (a-z).

              MD5 - Calculate an MD5 hash from the data in the input. The computed hash is in a raw binary form.

              NONE - Specify NONE if you don't want any text transformations.

              NORMALIZE_PATH - Remove multiple slashes, directory self-references, and directory back-references that are not at the beginning of the input from an input string.

              NORMALIZE_PATH_WIN - This is the same as NORMALIZE_PATH, but first converts backslash characters to forward slashes.

              REMOVE_NULLS - Remove all NULL bytes from the input.

              REPLACE_COMMENTS - Replace each occurrence of a C-style comment (/* ... */) with a single space. Multiple consecutive occurrences are not compressed. Unterminated comments are also replaced with a space (ASCII 0x20). However, a standalone termination of a comment (*/) is not acted upon.

              REPLACE_NULLS - Replace NULL bytes in the input with space characters (ASCII 0x20).

              SQL_HEX_DECODE - Decode SQL hex data. Example (0x414243) will be decoded to (ABC).

              URL_DECODE - Decode a URL-encoded value.

              URL_DECODE_UNI - Like URL_DECODE, but with support for Microsoft-specific %u encoding. If the code is in the full-width ASCII code range of FF01-FF5E, the higher byte is used to detect and adjust the lower byte. Otherwise, only the lower byte is used and the higher byte is zeroed.

              UTF8_TO_UNICODE - Convert all UTF-8 character sequences to Unicode. This helps input normalization, and minimizing false-positives and false-negatives for non-English languages.

              Possible values include:
              • "NONE"
              • "COMPRESS_WHITE_SPACE"
              • "HTML_ENTITY_DECODE"
              • "LOWERCASE"
              • "CMD_LINE"
              • "URL_DECODE"
              • "BASE64_DECODE"
              • "HEX_DECODE"
              • "MD5"
              • "REPLACE_COMMENTS"
              • "ESCAPE_SEQ_DECODE"
              • "SQL_HEX_DECODE"
              • "CSS_DECODE"
              • "JS_DECODE"
              • "NORMALIZE_PATH"
              • "NORMALIZE_PATH_WIN"
              • "REMOVE_NULLS"
              • "REPLACE_NULLS"
              • "BASE64_DECODE_EXT"
              • "URL_DECODE_UNI"
              • "UTF8_TO_UNICODE"
        • RateBasedStatement — (map)

          A rate-based rule tracks the rate of requests for each originating IP address, and triggers the rule action when the rate exceeds a limit that you specify on the number of requests in any 5-minute time span. You can use this to put a temporary block on requests from an IP address that is sending excessive requests.

          WAF tracks and manages web requests separately for each instance of a rate-based rule that you use. For example, if you provide the same rate-based rule settings in two web ACLs, each of the two rule statements represents a separate instance of the rate-based rule and gets its own tracking and management by WAF. If you define a rate-based rule inside a rule group, and then use that rule group in multiple places, each use creates a separate instance of the rate-based rule that gets its own tracking and management by WAF.

          When the rule action triggers, WAF blocks additional requests from the IP address until the request rate falls below the limit.

          You can optionally nest another statement inside the rate-based statement, to narrow the scope of the rule so that it only counts requests that match the nested statement. For example, based on recent requests that you have seen from an attacker, you might create a rate-based rule with a nested AND rule statement that contains the following nested statements:

          • An IP match statement with an IP set that specified the address 192.0.2.44.

          • A string match statement that searches in the User-Agent header for the string BadBot.

          In this rate-based rule, you also define a rate limit. For this example, the rate limit is 1,000. Requests that meet both of the conditions in the statements are counted. If the count exceeds 1,000 requests per five minutes, the rule action triggers. Requests that do not meet both conditions are not counted towards the rate limit and are not affected by this rule.

          You cannot nest a RateBasedStatement inside another statement, for example inside a NotStatement or OrStatement. You can define a RateBasedStatement inside a web ACL and inside a rule group.

          • Limit — required — (Integer)

            The limit on requests per 5-minute period for a single originating IP address. If the statement includes a ScopeDownStatement, this limit is applied only to the requests that match the statement.

          • AggregateKeyType — required — (String)

            Setting that indicates how to aggregate the request counts. The options are the following:

            • IP - Aggregate the request counts on the IP address from the web request origin.

            • FORWARDED_IP - Aggregate the request counts on the first IP address in an HTTP header. If you use this, configure the ForwardedIPConfig, to specify the header to use.

            Possible values include:
            • "IP"
            • "FORWARDED_IP"
          • ForwardedIPConfig — (map)

            The configuration for inspecting IP addresses in an HTTP header that you specify, instead of using the IP address that's reported by the web request origin. Commonly, this is the X-Forwarded-For (XFF) header, but you can specify any header name.

            Note: If the specified header isn't present in the request, WAF doesn't apply the rule to the web request at all.

            This is required if AggregateKeyType is set to FORWARDED_IP.

            • HeaderName — required — (String)

              The name of the HTTP header to use for the IP address. For example, to use the X-Forwarded-For (XFF) header, set this to X-Forwarded-For.

              Note: If the specified header isn't present in the request, WAF doesn't apply the rule to the web request at all.
            • FallbackBehavior — required — (String)

              The match status to assign to the web request if the request doesn't have a valid IP address in the specified position.

              Note: If the specified header isn't present in the request, WAF doesn't apply the rule to the web request at all.

              You can specify the following fallback behaviors:

              • MATCH - Treat the web request as matching the rule statement. WAF applies the rule action to the request.

              • NO_MATCH - Treat the web request as not matching the rule statement.

              Possible values include:
              • "MATCH"
              • "NO_MATCH"
        • AndStatement — (map)

          A logical rule statement used to combine other rule statements with AND logic. You provide more than one Statement within the AndStatement.

          • Statements — required — (Array<map>)

            The statements to combine with AND logic. You can use any statements that can be nested.

        • OrStatement — (map)

          A logical rule statement used to combine other rule statements with OR logic. You provide more than one Statement within the OrStatement.

          • Statements — required — (Array<map>)

            The statements to combine with OR logic. You can use any statements that can be nested.

        • NotStatement — (map)

          A logical rule statement used to negate the results of another rule statement. You provide one Statement within the NotStatement.

        • ManagedRuleGroupStatement — (map)

          A rule statement used to run the rules that are defined in a managed rule group. To use this, provide the vendor name and the name of the rule group in this statement. You can retrieve the required names by calling ListAvailableManagedRuleGroups.

          You cannot nest a ManagedRuleGroupStatement, for example for use inside a NotStatement or OrStatement. It can only be referenced as a top-level statement within a rule.

          • VendorName — required — (String)

            The name of the managed rule group vendor. You use this, along with the rule group name, to identify the rule group.

          • Name — required — (String)

            The name of the managed rule group. You use this, along with the vendor name, to identify the rule group.

          • Version — (String)

            The version of the managed rule group to use. If you specify this, the version setting is fixed until you change it. If you don't specify this, WAF uses the vendor's default version, and then keeps the version at the vendor's default when the vendor updates the managed rule group settings.

          • ExcludedRules — (Array<map>)

            The rules in the referenced rule group whose actions are set to Count. When you exclude a rule, WAF evaluates it exactly as it would if the rule action setting were Count. This is a useful option for testing the rules in a rule group without modifying how they handle your web traffic.

            • Name — required — (String)

              The name of the rule whose action you want to override to Count.

        • LabelMatchStatement — (map)

          A rule statement that defines a string match search against labels that have been added to the web request by rules that have already run in the web ACL.

          The label match statement provides the label or namespace string to search for. The label string can represent a part or all of the fully qualified label name that had been added to the web request. Fully qualified labels have a prefix, optional namespaces, and label name. The prefix identifies the rule group or web ACL context of the rule that added the label. If you do not provide the fully qualified name in your label match string, WAF performs the search for labels that were added in the same context as the label match statement.

          • Scope — required — (String)

            Specify whether you want to match using the label name or just the namespace.

            Possible values include:
            • "LABEL"
            • "NAMESPACE"
          • Key — required — (String)

            The string to match against. The setting you provide for this depends on the match statement's Scope setting:

            • If the Scope indicates LABEL, then this specification must include the name and can include any number of preceding namespace specifications and prefix up to providing the fully qualified label name.

            • If the Scope indicates NAMESPACE, then this specification can include any number of contiguous namespace strings, and can include the entire label namespace prefix from the rule group or web ACL where the label originates.

            Labels are case sensitive and components of a label must be separated by colon, for example NS1:NS2:name.

        • RegexMatchStatement — (map)

          A rule statement used to search web request components for a match against a single regular expression.

          • RegexString — required — (String)

            The string representing the regular expression.

          • FieldToMatch — required — (map)

            The part of a web request that you want WAF to inspect. For more information, see FieldToMatch.

            • SingleHeader — (map)

              Inspect a single header. Provide the name of the header to inspect, for example, User-Agent or Referer. This setting isn't case sensitive.

              Example JSON: "SingleHeader": { "Name": "haystack" }

              • Name — required — (String)

                The name of the query header to inspect.

            • SingleQueryArgument — (map)

              Inspect a single query argument. Provide the name of the query argument to inspect, such as UserName or SalesRegion. The name can be up to 30 characters long and isn't case sensitive.

              This is used only to indicate the web request component for WAF to inspect, in the FieldToMatch specification.

              Example JSON: "SingleQueryArgument": { "Name": "myArgument" }

              • Name — required — (String)

                The name of the query argument to inspect.

            • AllQueryArguments — (map)

              Inspect all query arguments.

            • UriPath — (map)

              Inspect the request URI path. This is the part of a web request that identifies a resource, for example, /images/daily-ad.jpg.

            • QueryString — (map)

              Inspect the query string. This is the part of a URL that appears after a ? character, if any.

            • Body — (map)

              Inspect the request body as plain text. The request body immediately follows the request headers. This is the part of a request that contains any additional data that you want to send to your web server as the HTTP request body, such as data from a form.

              Note that only the first 8 KB (8192 bytes) of the request body are forwarded to WAF for inspection by the underlying host service. If you don't need to inspect more than 8 KB, you can guarantee that you don't allow additional bytes in by combining a statement that inspects the body of the web request, such as ByteMatchStatement or RegexPatternSetReferenceStatement, with a SizeConstraintStatement that enforces an 8 KB size limit on the body of the request. WAF doesn't support inspecting the entire contents of web requests whose bodies exceed the 8 KB limit.

            • Method — (map)

              Inspect the HTTP method. The method indicates the type of operation that the request is asking the origin to perform.

            • JsonBody — (map)

              Inspect the request body as JSON. The request body immediately follows the request headers. This is the part of a request that contains any additional data that you want to send to your web server as the HTTP request body, such as data from a form.

              Note that only the first 8 KB (8192 bytes) of the request body are forwarded to WAF for inspection by the underlying host service. If you don't need to inspect more than 8 KB, you can guarantee that you don't allow additional bytes in by combining a statement that inspects the body of the web request, such as ByteMatchStatement or RegexPatternSetReferenceStatement, with a SizeConstraintStatement that enforces an 8 KB size limit on the body of the request. WAF doesn't support inspecting the entire contents of web requests whose bodies exceed the 8 KB limit.

              • MatchPattern — required — (map)

                The patterns to look for in the JSON body. WAF inspects the results of these pattern matches against the rule inspection criteria.

                • All — (map)

                  Match all of the elements. See also MatchScope in JsonBody.

                  You must specify either this setting or the IncludedPaths setting, but not both.

                • IncludedPaths — (Array<String>)

                  Match only the specified include paths. See also MatchScope in JsonBody.

                  Provide the include paths using JSON Pointer syntax. For example, "IncludedPaths": ["/dogs/0/name", "/dogs/1/name"]. For information about this syntax, see the Internet Engineering Task Force (IETF) documentation JavaScript Object Notation (JSON) Pointer.

                  You must specify either this setting or the All setting, but not both.

                  Note: Don't use this option to include all paths. Instead, use the All setting.
              • MatchScope — required — (String)

                The parts of the JSON to match against using the MatchPattern. If you specify All, WAF matches against keys and values.

                Possible values include:
                • "ALL"
                • "KEY"
                • "VALUE"
              • InvalidFallbackBehavior — (String)

                What WAF should do if it fails to completely parse the JSON body. The options are the following:

                • EVALUATE_AS_STRING - Inspect the body as plain text. WAF applies the text transformations and inspection criteria that you defined for the JSON inspection to the body text string.

                • MATCH - Treat the web request as matching the rule statement. WAF applies the rule action to the request.

                • NO_MATCH - Treat the web request as not matching the rule statement.

                If you don't provide this setting, WAF parses and evaluates the content only up to the first parsing failure that it encounters.

                WAF does its best to parse the entire JSON body, but might be forced to stop for reasons such as invalid characters, duplicate keys, truncation, and any content whose root node isn't an object or an array.

                WAF parses the JSON in the following examples as two valid key, value pairs:

                • Missing comma: {"key1":"value1""key2":"value2"}

                • Missing colon: {"key1":"value1","key2""value2"}

                • Extra colons: {"key1"::"value1","key2""value2"}

                Possible values include:
                • "MATCH"
                • "NO_MATCH"
                • "EVALUATE_AS_STRING"
          • TextTransformations — required — (Array<map>)

            Text transformations eliminate some of the unusual formatting that attackers use in web requests in an effort to bypass detection. If you specify one or more transformations in a rule statement, WAF performs all transformations on the content of the request component identified by FieldToMatch, starting from the lowest priority setting, before inspecting the content for a match.

            • Priority — required — (Integer)

              Sets the relative processing order for multiple transformations that are defined for a rule statement. WAF processes all transformations, from lowest priority to highest, before inspecting the transformed content. The priorities don't need to be consecutive, but they must all be different.

            • Type — required — (String)

              You can specify the following transformation types:

              BASE64_DECODE - Decode a Base64-encoded string.

              BASE64_DECODE_EXT - Decode a Base64-encoded string, but use a forgiving implementation that ignores characters that aren't valid.

              CMD_LINE - Command-line transformations. These are helpful in reducing effectiveness of attackers who inject an operating system command-line command and use unusual formatting to disguise some or all of the command.

              • Delete the following characters: \ " ' ^

              • Delete spaces before the following characters: / (

              • Replace the following characters with a space: , ;

              • Replace multiple spaces with one space

              • Convert uppercase letters (A-Z) to lowercase (a-z)

              COMPRESS_WHITE_SPACE - Replace these characters with a space character (decimal 32):

              • \f, formfeed, decimal 12

              • \t, tab, decimal 9

              • \n, newline, decimal 10

              • \r, carriage return, decimal 13

              • \v, vertical tab, decimal 11

              • Non-breaking space, decimal 160

              COMPRESS_WHITE_SPACE also replaces multiple spaces with one space.

              CSS_DECODE - Decode characters that were encoded using CSS 2.x escape rules syndata.html#characters. This function uses up to two bytes in the decoding process, so it can help to uncover ASCII characters that were encoded using CSS encoding that wouldn’t typically be encoded. It's also useful in countering evasion, which is a combination of a backslash and non-hexadecimal characters. For example, ja\vascript for javascript.

              ESCAPE_SEQ_DECODE - Decode the following ANSI C escape sequences: \a, \b, \f, \n, \r, \t, \v, \, \?, \', \", \xHH (hexadecimal), \0OOO (octal). Encodings that aren't valid remain in the output.

              HEX_DECODE - Decode a string of hexadecimal characters into a binary.

              HTML_ENTITY_DECODE - Replace HTML-encoded characters with unencoded characters. HTML_ENTITY_DECODE performs these operations:

              • Replaces (ampersand)quot; with "

              • Replaces (ampersand)nbsp; with a non-breaking space, decimal 160

              • Replaces (ampersand)lt; with a "less than" symbol

              • Replaces (ampersand)gt; with >

              • Replaces characters that are represented in hexadecimal format, (ampersand)#xhhhh;, with the corresponding characters

              • Replaces characters that are represented in decimal format, (ampersand)#nnnn;, with the corresponding characters

              JS_DECODE - Decode JavaScript escape sequences. If a \ u HHHH code is in the full-width ASCII code range of FF01-FF5E, then the higher byte is used to detect and adjust the lower byte. If not, only the lower byte is used and the higher byte is zeroed, causing a possible loss of information.

              LOWERCASE - Convert uppercase letters (A-Z) to lowercase (a-z).

              MD5 - Calculate an MD5 hash from the data in the input. The computed hash is in a raw binary form.

              NONE - Specify NONE if you don't want any text transformations.

              NORMALIZE_PATH - Remove multiple slashes, directory self-references, and directory back-references that are not at the beginning of the input from an input string.

              NORMALIZE_PATH_WIN - This is the same as NORMALIZE_PATH, but first converts backslash characters to forward slashes.

              REMOVE_NULLS - Remove all NULL bytes from the input.

              REPLACE_COMMENTS - Replace each occurrence of a C-style comment (/* ... */) with a single space. Multiple consecutive occurrences are not compressed. Unterminated comments are also replaced with a space (ASCII 0x20). However, a standalone termination of a comment (*/) is not acted upon.

              REPLACE_NULLS - Replace NULL bytes in the input with space characters (ASCII 0x20).

              SQL_HEX_DECODE - Decode SQL hex data. Example (0x414243) will be decoded to (ABC).

              URL_DECODE - Decode a URL-encoded value.

              URL_DECODE_UNI - Like URL_DECODE, but with support for Microsoft-specific %u encoding. If the code is in the full-width ASCII code range of FF01-FF5E, the higher byte is used to detect and adjust the lower byte. Otherwise, only the lower byte is used and the higher byte is zeroed.

              UTF8_TO_UNICODE - Convert all UTF-8 character sequences to Unicode. This helps input normalization, and minimizing false-positives and false-negatives for non-English languages.

              Possible values include:
              • "NONE"
              • "COMPRESS_WHITE_SPACE"
              • "HTML_ENTITY_DECODE"
              • "LOWERCASE"
              • "CMD_LINE"
              • "URL_DECODE"
              • "BASE64_DECODE"
              • "HEX_DECODE"
              • "MD5"
              • "REPLACE_COMMENTS"
              • "ESCAPE_SEQ_DECODE"
              • "SQL_HEX_DECODE"
              • "CSS_DECODE"
              • "JS_DECODE"
              • "NORMALIZE_PATH"
              • "NORMALIZE_PATH_WIN"
              • "REMOVE_NULLS"
              • "REPLACE_NULLS"
              • "BASE64_DECODE_EXT"
              • "URL_DECODE_UNI"
              • "UTF8_TO_UNICODE"
      • Action — (map)

        The action that WAF should take on a web request when it matches the rule statement. Settings at the web ACL level can override the rule action setting.

        This is used only for rules whose statements do not reference a rule group. Rule statements that reference a rule group include RuleGroupReferenceStatement and ManagedRuleGroupStatement.

        You must specify either this Action setting or the rule OverrideAction setting, but not both:

        • If the rule statement does not reference a rule group, use this rule action setting and not the rule override action setting.

        • If the rule statement references a rule group, use the override action setting and not this action setting.

        • Block — (map)

          Instructs WAF to block the web request.

          • CustomResponse — (map)

            Defines a custom response for the web request.

            For information about customizing web requests and responses, see Customizing web requests and responses in WAF in the WAF Developer Guide.

            • ResponseCode — required — (Integer)

              The HTTP status code to return to the client.

              For a list of status codes that you can use in your custom reqponses, see Supported status codes for custom response in the WAF Developer Guide.

            • CustomResponseBodyKey — (String)

              References the response body that you want WAF to return to the web request client. You can define a custom response for a rule action or a default web ACL action that is set to block. To do this, you first define the response body key and value in the CustomResponseBodies setting for the WebACL or RuleGroup where you want to use it. Then, in the rule action or web ACL default action BlockAction setting, you reference the response body using this key.

            • ResponseHeaders — (Array<map>)

              The HTTP headers to use in the response. Duplicate header names are not allowed.

              For information about the limits on count and size for custom request and response settings, see WAF quotas in the WAF Developer Guide.

              • Name — required — (String)

                The name of the custom header.

                For custom request header insertion, when WAF inserts the header into the request, it prefixes this name x-amzn-waf-, to avoid confusion with the headers that are already in the request. For example, for the header name sample, WAF inserts the header x-amzn-waf-sample.

              • Value — required — (String)

                The value of the custom header.

        • Allow — (map)

          Instructs WAF to allow the web request.

          • CustomRequestHandling — (map)

            Defines custom handling for the web request.

            For information about customizing web requests and responses, see Customizing web requests and responses in WAF in the WAF Developer Guide.

            • InsertHeaders — required — (Array<map>)

              The HTTP headers to insert into the request. Duplicate header names are not allowed.

              For information about the limits on count and size for custom request and response settings, see WAF quotas in the WAF Developer Guide.

              • Name — required — (String)

                The name of the custom header.

                For custom request header insertion, when WAF inserts the header into the request, it prefixes this name x-amzn-waf-, to avoid confusion with the headers that are already in the request. For example, for the header name sample, WAF inserts the header x-amzn-waf-sample.

              • Value — required — (String)

                The value of the custom header.

        • Count — (map)

          Instructs WAF to count the web request and allow it.

          • CustomRequestHandling — (map)

            Defines custom handling for the web request.

            For information about customizing web requests and responses, see Customizing web requests and responses in WAF in the WAF Developer Guide.

            • InsertHeaders — required — (Array<map>)

              The HTTP headers to insert into the request. Duplicate header names are not allowed.

              For information about the limits on count and size for custom request and response settings, see WAF quotas in the WAF Developer Guide.

              • Name — required — (String)

                The name of the custom header.

                For custom request header insertion, when WAF inserts the header into the request, it prefixes this name x-amzn-waf-, to avoid confusion with the headers that are already in the request. For example, for the header name sample, WAF inserts the header x-amzn-waf-sample.

              • Value — required — (String)

                The value of the custom header.

        • Captcha — (map)

          Instructs WAF to run a CAPTCHA check against the web request.

          • CustomRequestHandling — (map)

            Defines custom handling for the web request.

            For information about customizing web requests and responses, see Customizing web requests and responses in WAF in the WAF Developer Guide.

            • InsertHeaders — required — (Array<map>)

              The HTTP headers to insert into the request. Duplicate header names are not allowed.

              For information about the limits on count and size for custom request and response settings, see WAF quotas in the WAF Developer Guide.

              • Name — required — (String)

                The name of the custom header.

                For custom request header insertion, when WAF inserts the header into the request, it prefixes this name x-amzn-waf-, to avoid confusion with the headers that are already in the request. For example, for the header name sample, WAF inserts the header x-amzn-waf-sample.

              • Value — required — (String)

                The value of the custom header.

      • OverrideAction — (map)

        The action to use in the place of the action that results from the rule group evaluation. Set the override action to none to leave the result of the rule group alone. Set it to count to override the result to count only.

        You can only use this for rule statements that reference a rule group, like RuleGroupReferenceStatement and ManagedRuleGroupStatement.

        Note: This option is usually set to none. It does not affect how the rules in the rule group are evaluated. If you want the rules in the rule group to only count matches, do not use this and instead exclude those rules in your rule group reference statement settings.
        • Count — (map)

          Override the rule group evaluation result to count only.

          Note: This option is usually set to none. It does not affect how the rules in the rule group are evaluated. If you want the rules in the rule group to only count matches, do not use this and instead exclude those rules in your rule group reference statement settings.
          • CustomRequestHandling — (map)

            Defines custom handling for the web request.

            For information about customizing web requests and responses, see Customizing web requests and responses in WAF in the WAF Developer Guide.

            • InsertHeaders — required — (Array<map>)

              The HTTP headers to insert into the request. Duplicate header names are not allowed.

              For information about the limits on count and size for custom request and response settings, see WAF quotas in the WAF Developer Guide.

              • Name — required — (String)

                The name of the custom header.

                For custom request header insertion, when WAF inserts the header into the request, it prefixes this name x-amzn-waf-, to avoid confusion with the headers that are already in the request. For example, for the header name sample, WAF inserts the header x-amzn-waf-sample.

              • Value — required — (String)

                The value of the custom header.

        • None — (map)

          Don't override the rule group evaluation result. This is the most common setting.

      • RuleLabels — (Array<map>)

        Labels to apply to web requests that match the rule match statement. WAF applies fully qualified labels to matching web requests. A fully qualified label is the concatenation of a label namespace and a rule label. The rule's rule group or web ACL defines the label namespace.

        Rules that run after this rule in the web ACL can match against these labels using a LabelMatchStatement.

        For each label, provide a case-sensitive string containing optional namespaces and a label name, according to the following guidelines:

        • Separate each component of the label with a colon.

        • Each namespace or name can have up to 128 characters.

        • You can specify up to 5 namespaces in a label.

        • Don't use the following reserved words in your label specification: aws, waf, managed, rulegroup, webacl, regexpatternset, or ipset.

        For example, myLabelName or nameSpace1:nameSpace2:myLabelName.

        • Name — required — (String)

          The label string.

      • VisibilityConfig — required — (map)

        Defines and enables Amazon CloudWatch metrics and web request sample collection.

        • SampledRequestsEnabled — required — (Boolean)

          A boolean indicating whether WAF should store a sampling of the web requests that match the rules. You can view the sampled requests through the WAF console.

        • CloudWatchMetricsEnabled — required — (Boolean)

          A boolean indicating whether the associated resource sends metrics to Amazon CloudWatch. For the list of available metrics, see WAF Metrics.

        • MetricName — required — (String)

          A name of the Amazon CloudWatch metric. The name can contain only the characters: A-Z, a-z, 0-9, - (hyphen), and _ (underscore). The name can be from one to 128 characters long. It can't contain whitespace or metric names reserved for WAF, for example "All" and "Default_Action."

      • CaptchaConfig — (map)

        Specifies how WAF should handle CAPTCHA evaluations. If you don't specify this, WAF uses the CAPTCHA configuration that's defined for the web ACL.

        • ImmunityTimeProperty — (map)

          Determines how long a CAPTCHA token remains valid after the client successfully solves a CAPTCHA puzzle.

          • ImmunityTime — required — (Integer)

            The amount of time, in seconds, that a CAPTCHA token is valid. The default setting is 300.

    • VisibilityConfig — (map)

      Defines and enables Amazon CloudWatch metrics and web request sample collection.

      • SampledRequestsEnabled — required — (Boolean)

        A boolean indicating whether WAF should store a sampling of the web requests that match the rules. You can view the sampled requests through the WAF console.

      • CloudWatchMetricsEnabled — required — (Boolean)

        A boolean indicating whether the associated resource sends metrics to Amazon CloudWatch. For the list of available metrics, see WAF Metrics.

      • MetricName — required — (String)

        A name of the Amazon CloudWatch metric. The name can contain only the characters: A-Z, a-z, 0-9, - (hyphen), and _ (underscore). The name can be from one to 128 characters long. It can't contain whitespace or metric names reserved for WAF, for example "All" and "Default_Action."

    • LockToken — (String)

      A token used for optimistic locking. WAF returns a token to your get and list requests, to mark the state of the entity at the time of the request. To make changes to the entity associated with the token, you provide the token to operations like update and delete. WAF uses the token to ensure that no changes have been made to the entity since you last retrieved it. If a change has been made, the update fails with a WAFOptimisticLockException. If this happens, perform another get, and use the new token returned by that operation.

    • CustomResponseBodies — (map<map>)

      A map of custom response keys and content bodies. When you create a rule with a block action, you can send a custom response to the web request. You define these for the web ACL, and then use them in the rules and default actions that you define in the web ACL.

      For information about customizing web requests and responses, see Customizing web requests and responses in WAF in the WAF Developer Guide.

      For information about the limits on count and size for custom request and response settings, see WAF quotas in the WAF Developer Guide.

      • ContentType — required — (String)

        The type of content in the payload that you are defining in the Content string.

        Possible values include:
        • "TEXT_PLAIN"
        • "TEXT_HTML"
        • "APPLICATION_JSON"
      • Content — required — (String)

        The payload of the custom response.

        You can use JSON escape strings in JSON content. To do this, you must specify JSON content in the ContentType setting.

        For information about the limits on count and size for custom request and response settings, see WAF quotas in the WAF Developer Guide.

    • CaptchaConfig — (map)

      Specifies how WAF should handle CAPTCHA evaluations for rules that don't have their own CaptchaConfig settings. If you don't specify this, WAF uses its default settings for CaptchaConfig.

      • ImmunityTimeProperty — (map)

        Determines how long a CAPTCHA token remains valid after the client successfully solves a CAPTCHA puzzle.

        • ImmunityTime — required — (Integer)

          The amount of time, in seconds, that a CAPTCHA token is valid. The default setting is 300.

Callback (callback):

  • function(err, data) { ... }

    Called when a response from the service is returned. If a callback is not supplied, you must call AWS.Request.send() on the returned request object to initiate the request.

    Context (this):

    • (AWS.Response) —

      the response object containing error, data properties, and the original request object.

    Parameters:

    • err (Error) —

      the error object returned from the request. Set to null if the request is successful.

    • data (Object) —

      the de-serialized data returned from the request. Set to null if a request error occurs. The data object has the following properties:

      • NextLockToken — (String)

        A token used for optimistic locking. WAF returns this token to your update requests. You use NextLockToken in the same manner as you use LockToken.

Returns:

  • (AWS.Request) —

    a handle to the operation request for subsequent event callback registration.