@aws-sdk/client-wafv2 3.130.0 → 3.131.0

package/dist-types/models/models_0.d.ts

@@ -25,8 +25,7 @@ export declare namespace ActionCondition {
 }
 /**
  * <p>Inspect all of the elements that WAF has parsed and extracted from the web request
- *          component that you've identified in your <a>FieldToMatch</a> specifications.
- *       </p>
+ *          component that you've identified in your <a>FieldToMatch</a> specifications. </p>
  *          <p>This is used only in the <a>FieldToMatch</a> specification for some web request component types. </p>
  *          <p>JSON specification: <code>"All": {}</code>
  *          </p>
@@ -103,7 +102,7 @@ export declare namespace AllowAction {
 }
 /**
  * <p>Inspect all query arguments of the web request. </p>
- *            <p>This is used only in the <a>FieldToMatch</a> specification for some web request component types. </p>
+ *          <p>This is used only in the <a>FieldToMatch</a> specification for some web request component types. </p>
  *          <p>JSON specification: <code>"AllQueryArguments": {}</code>
  *          </p>
  */
@@ -121,8 +120,9 @@ export declare enum OversizeHandling {
     NO_MATCH = "NO_MATCH"
 }
 /**
- * <p>Inspect the body of the web request. The body immediately follows the request headers.</p>
- *          <p>This is used to indicate the web request component for WAF to inspect, in the <a>FieldToMatch</a> specification. </p>
+ * <p>Inspect the body of the web request. The body immediately follows the request
+ *          headers.</p>
+ *          <p>This is used to indicate the web request component to inspect, in the <a>FieldToMatch</a> specification. </p>
  */
 export interface Body {
     /**
@@ -163,7 +163,7 @@ export declare namespace Body {
 /**
  * <p>The filter to use to identify the subset of cookies to inspect in a web request. </p>
  *          <p>You must specify exactly one setting: either <code>All</code>, <code>IncludedCookies</code>, or <code>ExcludedCookies</code>.</p>
- *          <p>Example JSON: <code>"CookieMatchPattern": { "IncludedCookies": {"KeyToInclude1", "KeyToInclude2", "KeyToInclude3"} }</code>
+ *          <p>Example JSON: <code>"MatchPattern": { "IncludedCookies": {"KeyToInclude1", "KeyToInclude2", "KeyToInclude3"} }</code>
  *          </p>
  */
 export interface CookieMatchPattern {
@@ -172,11 +172,13 @@ export interface CookieMatchPattern {
      */
     All?: All;
     /**
-     * <p>Inspect only the cookies that have a key that matches one of the strings specified here. </p>
+     * <p>Inspect only the cookies that have a key that matches one of the strings specified here.
+     *       </p>
      */
     IncludedCookies?: string[];
     /**
-     * <p>Inspect only the cookies whose keys don't match any of the strings specified here. </p>
+     * <p>Inspect only the cookies whose keys don't match any of the strings specified here.
+     *       </p>
      */
     ExcludedCookies?: string[];
 }
@@ -192,23 +194,25 @@ export declare enum MapMatchScope {
     VALUE = "VALUE"
 }
 /**
- * <p>Inspect the cookies in the web request. You can specify the parts of the cookies to inspect and you can narrow
- *    the set of cookies to inspect by including or excluding specific keys.</p>
- *          <p>This is used to indicate the web request component for WAF to inspect, in the <a>FieldToMatch</a> specification. </p>
- *          <p>Example JSON: <code>"Cookies": { "MatchPattern": { "All": {} }, "MatchScope": "KEY", "OversizeHandling": "MATCH" }</code>
+ * <p>Inspect the cookies in the web request. You can specify the parts of the cookies to
+ *          inspect and you can narrow the set of cookies to inspect by including or excluding specific
+ *          keys.</p>
+ *          <p>This is used to indicate the web request component to inspect, in the <a>FieldToMatch</a> specification. </p>
+ *          <p>Example JSON: <code>"Cookies": { "MatchPattern": { "All": {} }, "MatchScope": "KEY",
+ *             "OversizeHandling": "MATCH" }</code>
  *          </p>
  */
 export interface Cookies {
     /**
      * <p>The filter to use to identify the subset of cookies to inspect in a web request. </p>
      *          <p>You must specify exactly one setting: either <code>All</code>, <code>IncludedCookies</code>, or <code>ExcludedCookies</code>.</p>
-     *          <p>Example JSON: <code>"CookieMatchPattern": { "IncludedCookies": {"KeyToInclude1", "KeyToInclude2", "KeyToInclude3"} }</code>
+     *          <p>Example JSON: <code>"MatchPattern": { "IncludedCookies": {"KeyToInclude1", "KeyToInclude2", "KeyToInclude3"} }</code>
      *          </p>
      */
     MatchPattern: CookieMatchPattern | undefined;
     /**
-     * <p>The parts of the cookies to inspect with the rule inspection criteria. If you
-     *          specify <code>All</code>, WAF inspects both keys and values. </p>
+     * <p>The parts of the cookies to inspect with the rule inspection criteria. If you specify
+     *             <code>All</code>, WAF inspects both keys and values. </p>
      */
     MatchScope: MapMatchScope | string | undefined;
     /**
@@ -245,7 +249,7 @@ export declare namespace Cookies {
 /**
  * <p>The filter to use to identify the subset of headers to inspect in a web request. </p>
  *          <p>You must specify exactly one setting: either <code>All</code>, <code>IncludedHeaders</code>, or <code>ExcludedHeaders</code>.</p>
- *          <p>Example JSON: <code>"HeaderMatchPattern": { "ExcludedHeaders": {"KeyToExclude1", "KeyToExclude2"} }</code>
+ *          <p>Example JSON: <code>"MatchPattern": { "ExcludedHeaders": {"KeyToExclude1", "KeyToExclude2"} }</code>
  *          </p>
  */
 export interface HeaderMatchPattern {
@@ -254,11 +258,13 @@ export interface HeaderMatchPattern {
      */
     All?: All;
     /**
-     * <p>Inspect only the headers that have a key that matches one of the strings specified here. </p>
+     * <p>Inspect only the headers that have a key that matches one of the strings specified here.
+     *       </p>
      */
     IncludedHeaders?: string[];
     /**
-     * <p>Inspect only the headers whose keys don't match any of the strings specified here. </p>
+     * <p>Inspect only the headers whose keys don't match any of the strings specified here.
+     *       </p>
      */
     ExcludedHeaders?: string[];
 }
@@ -269,25 +275,28 @@ export declare namespace HeaderMatchPattern {
     const filterSensitiveLog: (obj: HeaderMatchPattern) => any;
 }
 /**
- * <p>Inspect the headers in the web request. You can specify the parts of the headers to inspect and you can narrow
- *    the set of headers to inspect by including or excluding specific keys.</p>
- *          <p>This is used to indicate the web request component for WAF to inspect, in the <a>FieldToMatch</a> specification. </p>
- *          <p>Alternately, you can use the <code>SingleHeader</code>
- *             <code>FieldToMatch</code> setting to inspect the value of a single header, identified by its key. </p>
- *          <p>Example JSON: <code>"Headers": { "MatchPattern": { "All": {} }, "MatchScope": "KEY", "OversizeHandling": "MATCH" }</code>
+ * <p>Inspect all headers in the web request. You can specify the parts of the headers to
+ *          inspect and you can narrow the set of headers to inspect by including or excluding specific
+ *          keys.</p>
+ *          <p>This is used to indicate the web request component to inspect, in the <a>FieldToMatch</a> specification. </p>
+ *          <p>If you want to inspect just the value of a single header, use the
+ *             <code>SingleHeader</code>
+ *             <code>FieldToMatch</code> setting instead.</p>
+ *          <p>Example JSON: <code>"Headers": { "MatchPattern": { "All": {} }, "MatchScope": "KEY",
+ *             "OversizeHandling": "MATCH" }</code>
  *          </p>
  */
 export interface Headers {
     /**
      * <p>The filter to use to identify the subset of headers to inspect in a web request. </p>
      *          <p>You must specify exactly one setting: either <code>All</code>, <code>IncludedHeaders</code>, or <code>ExcludedHeaders</code>.</p>
-     *          <p>Example JSON: <code>"HeaderMatchPattern": { "ExcludedHeaders": {"KeyToExclude1", "KeyToExclude2"} }</code>
+     *          <p>Example JSON: <code>"MatchPattern": { "ExcludedHeaders": {"KeyToExclude1", "KeyToExclude2"} }</code>
      *          </p>
      */
     MatchPattern: HeaderMatchPattern | undefined;
     /**
-     * <p>The parts of the headers to match with the rule inspection criteria. If you
-     *          specify <code>All</code>, WAF inspects both keys and values. </p>
+     * <p>The parts of the headers to match with the rule inspection criteria. If you specify
+     *             <code>All</code>, WAF inspects both keys and values. </p>
      */
     MatchScope: MapMatchScope | string | undefined;
     /**
@@ -370,13 +379,13 @@ export declare enum JsonMatchScope {
 /**
  * <p>Inspect the body of the web request as JSON. The body immediately follows the request
  *          headers. </p>
- *           <p>This is used to indicate the web request component for WAF to inspect, in the <a>FieldToMatch</a> specification. </p>
+ *          <p>This is used to indicate the web request component to inspect, in the <a>FieldToMatch</a> specification. </p>
  *          <p>Use the specifications in this object to indicate which parts of the JSON body to
  *          inspect using the rule's inspection criteria. WAF inspects only the parts of the JSON
- *          that result from the matches that you
- *          indicate.
+ *          that result from the matches that you indicate.
  *       </p>
- *          <p>Example JSON: <code>"JsonBody": { "MatchPattern": { "All": {} }, "MatchScope": "ALL" }</code>
+ *          <p>Example JSON: <code>"JsonBody": { "MatchPattern": { "All": {} }, "MatchScope": "ALL"
+ *             }</code>
  *          </p>
  */
 export interface JsonBody {
@@ -396,14 +405,14 @@ export interface JsonBody {
      *          <ul>
      *             <li>
      *                <p>
-     *                   <code>EVALUATE_AS_STRING</code> - 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.</p>
+     *                   <code>EVALUATE_AS_STRING</code> - 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.</p>
      *             </li>
      *             <li>
      *                <p>
-     *                   <code>MATCH</code> - Treat the web request as matching the rule statement. WAF
-     *                applies the rule action to the request.</p>
+     *                   <code>MATCH</code> - Treat the web request as matching the rule statement.
+     *                WAF applies the rule action to the request.</p>
      *             </li>
      *             <li>
      *                <p>
@@ -469,8 +478,9 @@ export declare namespace JsonBody {
     const filterSensitiveLog: (obj: JsonBody) => any;
 }
 /**
- * <p>Inspect the HTTP method of the web request. The method indicates the type of operation that the request is asking the origin to perform. </p>
- *            <p>This is used only in the <a>FieldToMatch</a> specification for some web request component types. </p>
+ * <p>Inspect the HTTP method of the web request. The method indicates the type of operation
+ *          that the request is asking the origin to perform. </p>
+ *          <p>This is used only in the <a>FieldToMatch</a> specification for some web request component types. </p>
  *          <p>JSON specification: <code>"Method": {}</code>
  *          </p>
  */
@@ -483,8 +493,9 @@ export declare namespace Method {
     const filterSensitiveLog: (obj: Method) => any;
 }
 /**
- * <p>Inspect the query string of the web request. This is the part of a URL that appears after a <code>?</code> character, if any.</p>
- *            <p>This is used only in the <a>FieldToMatch</a> specification for some web request component types. </p>
+ * <p>Inspect the query string of the web request. This is the part of a URL that appears
+ *          after a <code>?</code> character, if any.</p>
+ *          <p>This is used only in the <a>FieldToMatch</a> specification for some web request component types. </p>
  *          <p>JSON specification: <code>"QueryString": {}</code>
  *          </p>
  */
@@ -499,8 +510,9 @@ export declare namespace QueryString {
 /**
  * <p>Inspect one of the headers in the web request, identified by name, for example,
  *             <code>User-Agent</code> or <code>Referer</code>. The name isn't case sensitive.</p>
- *          <p>You can filter and inspect all headers with the <code>FieldToMatch</code> setting <code>Headers</code>.</p>
- *          <p>This is used to indicate the web request component for WAF to inspect, in the <a>FieldToMatch</a> specification. </p>
+ *          <p>You can filter and inspect all headers with the <code>FieldToMatch</code> setting
+ *             <code>Headers</code>.</p>
+ *          <p>This is used to indicate the web request component to inspect, in the <a>FieldToMatch</a> specification. </p>
  *          <p>Example JSON: <code>"SingleHeader": { "Name": "haystack" }</code>
  *          </p>
  */
@@ -518,8 +530,9 @@ export declare namespace SingleHeader {
 }
 /**
  * <p>Inspect one query argument in the web request, identified by name, for example
- *             <i>UserName</i> or <i>SalesRegion</i>. The name isn't case sensitive. </p>
- *           <p>This is used to indicate the web request component for WAF to inspect, in the <a>FieldToMatch</a> specification. </p>
+ *             <i>UserName</i> or <i>SalesRegion</i>. The name isn't case
+ *          sensitive. </p>
+ *          <p>This is used to indicate the web request component to inspect, in the <a>FieldToMatch</a> specification. </p>
  *          <p>Example JSON: <code>"SingleQueryArgument": { "Name": "myArgument" }</code>
  *          </p>
  */
@@ -536,7 +549,8 @@ export declare namespace SingleQueryArgument {
     const filterSensitiveLog: (obj: SingleQueryArgument) => any;
 }
 /**
- * <p>Inspect the path component of the URI of the web request. This is the part of the web request that identifies a resource. For example, <code>/images/daily-ad.jpg</code>.</p>
+ * <p>Inspect the path component of the URI of the web request. This is the part of the web
+ *          request that identifies a resource. For example, <code>/images/daily-ad.jpg</code>.</p>
  *          <p>This is used only in the <a>FieldToMatch</a> specification for some web request component types. </p>
  *          <p>JSON specification: <code>"UriPath": {}</code>
  *          </p>
@@ -550,14 +564,19 @@ export declare namespace UriPath {
     const filterSensitiveLog: (obj: UriPath) => any;
 }
 /**
- * <p>The part of the web request that you want WAF to inspect. Include the single <code>FieldToMatch</code> type that you want to inspect, with additional specifications as needed, according to the type. You specify a single request component in <code>FieldToMatch</code> for each rule statement that requires it. To inspect more than one component of the web request, create a separate rule statement for each component.</p>
+ * <p>The part of the web request that you want WAF to inspect. Include the single
+ *             <code>FieldToMatch</code> type that you want to inspect, with additional specifications
+ *          as needed, according to the type. You specify a single request component in
+ *             <code>FieldToMatch</code> for each rule statement that requires it. To inspect more than
+ *          one component of the web request, create a separate rule statement for each
+ *          component.</p>
  *          <p>Example JSON for a <code>QueryString</code> field to match: </p>
  *          <p>
- *             <code>    "FieldToMatch": { "QueryString": {} }</code>
+ *             <code> "FieldToMatch": { "QueryString": {} }</code>
  *          </p>
  *          <p>Example JSON for a <code>Method</code> field to match specification:</p>
  *          <p>
- *             <code>    "FieldToMatch": { "Method": { "Name": "DELETE" } }</code>
+ *             <code> "FieldToMatch": { "Method": { "Name": "DELETE" } }</code>
  *          </p>
  */
 export interface FieldToMatch {
@@ -597,9 +616,9 @@ export interface FieldToMatch {
      * <p>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. </p>
-     *          <p>Only the first 8 KB (8192 bytes) of the request body are forwarded to
-     *           WAF for inspection by the underlying host service. For information about how to
-     *       handle oversized request bodies, see the <code>Body</code> object configuration. </p>
+     *          <p>Only the first 8 KB (8192 bytes) of the request body are forwarded to WAF for
+     *          inspection by the underlying host service. For information about how to handle oversized
+     *          request bodies, see the <code>Body</code> object configuration. </p>
      */
     Body?: Body;
     /**
@@ -611,27 +630,31 @@ export interface FieldToMatch {
      * <p>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. </p>
-     *          <p>Only the first 8 KB (8192 bytes) of the request body are forwarded to
-     *           WAF for inspection by the underlying host service. For information about how to
-     *       handle oversized request bodies, see the <code>JsonBody</code> object configuration. </p>
+     *          <p>Only the first 8 KB (8192 bytes) of the request body are forwarded to WAF for
+     *          inspection by the underlying host service. For information about how to handle oversized
+     *          request bodies, see the <code>JsonBody</code> object configuration. </p>
      */
     JsonBody?: JsonBody;
     /**
-     * <p>Inspect the request headers. You must configure scope and pattern matching filters
-     *            in the <code>Headers</code> object, to define the set of headers to and the parts of the headers that WAF inspects. </p>
-     *          <p>Only the first 8 KB (8192 bytes) of a request's headers and only the first 200 headers are forwarded to
-     *           WAF for inspection by the underlying host service. You must configure
-     *           how to handle any oversize header content in the <code>Headers</code> object. WAF applies the pattern matching filters
-     *           to the headers that it receives from the underlying host service. </p>
+     * <p>Inspect the request headers. You must configure scope and pattern matching filters in
+     *          the <code>Headers</code> object, to define the set of headers to and the parts of the
+     *          headers that WAF inspects. </p>
+     *          <p>Only the first 8 KB (8192 bytes) of a request's headers and only the first 200 headers
+     *          are forwarded to WAF for inspection by the underlying host service. You must
+     *          configure how to handle any oversize header content in the <code>Headers</code> object.
+     *          WAF applies the pattern matching filters to the headers that it receives from the
+     *          underlying host service. </p>
      */
     Headers?: Headers;
     /**
-     * <p>Inspect the request cookies. You must configure scope and pattern matching filters
-     *            in the <code>Cookies</code> object, to define the set of cookies and the parts of the cookies that WAF inspects. </p>
-     *          <p>Only the first 8 KB (8192 bytes) of a request's cookies and only the first 200 cookies are forwarded to
-     *           WAF for inspection by the underlying host service. You must configure
-     *           how to handle any oversize cookie content in the <code>Cookies</code> object. WAF applies the pattern matching filters
-     *           to the cookies that it receives from the underlying host service. </p>
+     * <p>Inspect the request cookies. You must configure scope and pattern matching filters in
+     *          the <code>Cookies</code> object, to define the set of cookies and the parts of the cookies
+     *          that WAF inspects. </p>
+     *          <p>Only the first 8 KB (8192 bytes) of a request's cookies and only the first 200 cookies
+     *          are forwarded to WAF for inspection by the underlying host service. You must
+     *          configure how to handle any oversize cookie content in the <code>Cookies</code> object.
+     *          WAF applies the pattern matching filters to the cookies that it receives from the
+     *          underlying host service. </p>
      */
     Cookies?: Cookies;
 }
@@ -686,8 +709,8 @@ export interface TextTransformation {
     /**
      * <p>You can specify the following transformation types:</p>
      *          <p>
-     *             <b>BASE64_DECODE</b> - Decode a <code>Base64</code>-encoded
-     *          string.</p>
+     *             <b>BASE64_DECODE</b> - Decode a
+     *          <code>Base64</code>-encoded string.</p>
      *          <p>
      *             <b>BASE64_DECODE_EXT</b> - Decode a
      *          <code>Base64</code>-encoded string, but use a forgiving implementation that ignores
@@ -716,7 +739,6 @@ export interface TextTransformation {
      *                <p>Convert uppercase letters (A-Z) to lowercase (a-z)</p>
      *             </li>
      *          </ul>
-     *
      *          <p>
      *             <b>COMPRESS_WHITE_SPACE</b> - Replace these characters
      *          with a space character (decimal 32): </p>
@@ -749,17 +771,20 @@ export interface TextTransformation {
      *             <code>COMPRESS_WHITE_SPACE</code> also replaces multiple spaces with one space.</p>
      *          <p>
      *             <b>CSS_DECODE</b> - Decode characters that were encoded
-     *          using CSS 2.x escape rules <code>syndata.html#characters</code>. 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,
-     *          <code>ja\vascript</code> for javascript. </p>
+     *          using CSS 2.x escape rules <code>syndata.html#characters</code>. 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, <code>ja\vascript</code> for javascript. </p>
      *          <p>
-     *             <b>ESCAPE_SEQ_DECODE</b> - Decode the following ANSI C escape sequences:
-     *          <code>\a</code>, <code>\b</code>, <code>\f</code>, <code>\n</code>, <code>\r</code>, <code>\t</code>, <code>\v</code>, <code>\\</code>, <code>\?</code>, <code>\'</code>, <code>\"</code>, <code>\xHH</code> (hexadecimal), <code>\0OOO</code> (octal). Encodings
-     *          that aren't valid remain in the output. </p>
+     *             <b>ESCAPE_SEQ_DECODE</b> - Decode the following ANSI C
+     *          escape sequences: <code>\a</code>, <code>\b</code>, <code>\f</code>, <code>\n</code>,
+     *             <code>\r</code>, <code>\t</code>, <code>\v</code>, <code>\\</code>, <code>\?</code>,
+     *             <code>\'</code>, <code>\"</code>, <code>\xHH</code> (hexadecimal), <code>\0OOO</code>
+     *          (octal). Encodings that aren't valid remain in the output. </p>
      *          <p>
-     *             <b>HEX_DECODE</b> - Decode a string of hexadecimal characters into a binary.</p>
+     *             <b>HEX_DECODE</b> - Decode a string of hexadecimal
+     *          characters into a binary.</p>
      *          <p>
      *             <b>HTML_ENTITY_DECODE</b> - Replace HTML-encoded
      *          characters with unencoded characters. <code>HTML_ENTITY_DECODE</code> performs these
@@ -770,7 +795,8 @@ export interface TextTransformation {
      *                </p>
      *             </li>
      *             <li>
-     *                <p>Replaces <code>(ampersand)nbsp;</code> with a non-breaking space, decimal 160</p>
+     *                <p>Replaces <code>(ampersand)nbsp;</code> with a non-breaking space, decimal
+     *                160</p>
      *             </li>
      *             <li>
      *                <p>Replaces <code>(ampersand)lt;</code> with a "less than" symbol</p>
@@ -780,19 +806,22 @@ export interface TextTransformation {
      *                </p>
      *             </li>
      *             <li>
-     *                <p>Replaces characters that are represented in hexadecimal format, <code>(ampersand)#xhhhh;</code>, with the corresponding characters</p>
+     *                <p>Replaces characters that are represented in hexadecimal format,
+     *                   <code>(ampersand)#xhhhh;</code>, with the corresponding characters</p>
      *             </li>
      *             <li>
-     *                <p>Replaces characters that are represented in decimal format, <code>(ampersand)#nnnn;</code>, with the corresponding
-     *                characters</p>
+     *                <p>Replaces characters that are represented in decimal format,
+     *                   <code>(ampersand)#nnnn;</code>, with the corresponding characters</p>
      *             </li>
      *          </ul>
      *          <p>
      *             <b>JS_DECODE</b> - Decode JavaScript escape sequences. If
-     *          a <code>\</code>
+     *          a
+     *          <code>\</code>
      *             <code>u</code>
-     *             <code>HHHH</code> code is in the full-width ASCII code range of <code>FF01-FF5E</code>, then the higher byte is
-     *          used to detect and adjust the lower byte. If not, only the lower byte is used and the
+     *             <code>HHHH</code>
+     *          code is in the full-width ASCII code range of <code>FF01-FF5E</code>, 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. </p>
      *          <p>
      *             <b>LOWERCASE</b> - Convert uppercase letters (A-Z) to
@@ -801,35 +830,37 @@ export interface TextTransformation {
      *             <b>MD5</b> - Calculate an MD5 hash from the data in the
      *          input. The computed hash is in a raw binary form. </p>
      *          <p>
-     *             <b>NONE</b> - Specify <code>NONE</code> if you don't want any text transformations.
-     *       </p>
+     *             <b>NONE</b> - Specify <code>NONE</code> if you don't want
+     *          any text transformations. </p>
      *          <p>
      *             <b>NORMALIZE_PATH</b> - Remove multiple slashes, directory
      *          self-references, and directory back-references that are not at the beginning of the input
      *          from an input string. </p>
      *          <p>
      *             <b>NORMALIZE_PATH_WIN</b> - This is the same as
-     *          <code>NORMALIZE_PATH</code>, but first converts backslash characters to forward slashes. </p>
+     *             <code>NORMALIZE_PATH</code>, but first converts backslash characters to forward slashes. </p>
      *          <p>
      *             <b>REMOVE_NULLS</b> - Remove all <code>NULL</code> bytes
      *          from the input. </p>
      *          <p>
      *             <b>REPLACE_COMMENTS</b> - Replace each occurrence of a
-     *          C-style comment (<code>/* ... *\/</code>) 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 (<code>*\/</code>) is not acted upon. </p>
+     *          C-style comment (<code>/* ... *\/</code>) 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 (<code>*\/</code>) is not acted upon. </p>
      *          <p>
      *             <b>REPLACE_NULLS</b> - Replace NULL bytes in the input
      *          with space characters (ASCII <code>0x20</code>). </p>
      *          <p>
-     *             <b>SQL_HEX_DECODE</b> - Decode SQL hex data. Example (<code>0x414243</code>) will be decoded to (<code>ABC</code>).</p>
+     *             <b>SQL_HEX_DECODE</b> - Decode SQL hex data. Example
+     *             (<code>0x414243</code>) will be decoded to (<code>ABC</code>).</p>
      *          <p>
      *             <b>URL_DECODE</b> - Decode a URL-encoded value. </p>
      *          <p>
-     *             <b>URL_DECODE_UNI</b> - Like <code>URL_DECODE</code>, but with support
-     *          for Microsoft-specific <code>%u</code> encoding. If the code is in the full-width ASCII code range of
-     *          <code>FF01-FF5E</code>, 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. </p>
+     *             <b>URL_DECODE_UNI</b> - Like <code>URL_DECODE</code>, but
+     *          with support for Microsoft-specific <code>%u</code> encoding. If the code is in the
+     *          full-width ASCII code range of <code>FF01-FF5E</code>, 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. </p>
      *          <p>
      *             <b>UTF8_TO_UNICODE</b> - Convert all UTF-8 character
      *          sequences to Unicode. This helps input normalization, and minimizing false-positives and
@@ -844,7 +875,7 @@ export declare namespace TextTransformation {
     const filterSensitiveLog: (obj: TextTransformation) => any;
 }
 /**
- * <p>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.</p>
+ * <p>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 called a string match statement.</p>
  */
 export interface ByteMatchStatement {
     /**
@@ -885,7 +916,7 @@ export interface ByteMatchStatement {
      */
     SearchString: Uint8Array | undefined;
     /**
-     * <p>The part of the web request that you want WAF to inspect. For more information, see <a>FieldToMatch</a>. </p>
+     * <p>The part of the web request that you want WAF to inspect. </p>
      */
     FieldToMatch: FieldToMatch | undefined;
     /**
@@ -1415,9 +1446,10 @@ export declare namespace LabelMatchStatement {
     const filterSensitiveLog: (obj: LabelMatchStatement) => any;
 }
 /**
- * <p>Specifies a single rule in a rule group whose action you want to override to <code>Count</code>. When you exclude a rule,
- *            WAF evaluates it exactly as it would if the rule action setting were <code>Count</code>. This is a useful option for
- *            testing the rules in a rule group without modifying how they handle your web traffic. </p>
+ * <p>Specifies a single rule in a rule group whose action you want to override to
+ *             <code>Count</code>. When you exclude a rule, WAF evaluates it exactly as it would if
+ *          the rule action setting were <code>Count</code>. This is a useful option for testing the
+ *          rules in a rule group without modifying how they handle your web traffic. </p>
  */
 export interface ExcludedRule {
     /**
@@ -1432,7 +1464,8 @@ export declare namespace ExcludedRule {
     const filterSensitiveLog: (obj: ExcludedRule) => any;
 }
 /**
- * <p>Details about your login page password field, used in a <code>ManagedRuleGroupConfig</code>. </p>
+ * <p>Details about your login page password field, used in a
+ *             <code>ManagedRuleGroupConfig</code>. </p>
  */
 export interface PasswordField {
     /**
@@ -1451,7 +1484,8 @@ export declare enum PayloadType {
     JSON = "JSON"
 }
 /**
- * <p>Details about your login page username field, used in a <code>ManagedRuleGroupConfig</code>. </p>
+ * <p>Details about your login page username field, used in a
+ *             <code>ManagedRuleGroupConfig</code>. </p>
  */
 export interface UsernameField {
     /**
@@ -1473,7 +1507,9 @@ export declare namespace UsernameField {
  */
 export interface ManagedRuleGroupConfig {
     /**
-     * <p>The path of the login endpoint for your application. For example, for the URL <code>https://example.com/web/login</code>, you would provide the path <code>/web/login</code>.</p>
+     * <p>The path of the login endpoint for your application. For example, for the URL
+     *             <code>https://example.com/web/login</code>, you would provide the path
+     *             <code>/web/login</code>.</p>
      */
     LoginPath?: string;
     /**
@@ -1508,7 +1544,7 @@ export interface RegexMatchStatement {
      */
     RegexString: string | undefined;
     /**
-     * <p>The part of the web request that you want WAF to inspect. For more information, see <a>FieldToMatch</a>. </p>
+     * <p>The part of the web request that you want WAF to inspect. </p>
      */
     FieldToMatch: FieldToMatch | undefined;
     /**
@@ -1535,7 +1571,7 @@ export interface RegexPatternSetReferenceStatement {
      */
     ARN: string | undefined;
     /**
-     * <p>The part of the web request that you want WAF to inspect. For more information, see <a>FieldToMatch</a>. </p>
+     * <p>The part of the web request that you want WAF to inspect. </p>
      */
     FieldToMatch: FieldToMatch | undefined;
     /**
@@ -1562,9 +1598,10 @@ export interface RuleGroupReferenceStatement {
      */
     ARN: string | undefined;
     /**
-     * <p>The rules in the referenced rule group whose actions are set to <code>Count</code>.
-     *        When you exclude a rule, WAF evaluates it exactly as it would if the rule action setting were <code>Count</code>.
-     *        This is a useful option for testing the rules in a rule group without modifying how they handle your web traffic.</p>
+     * <p>The rules in the referenced rule group whose actions are set to <code>Count</code>. When
+     *          you exclude a rule, WAF evaluates it exactly as it would if the rule action setting were
+     *             <code>Count</code>. This is a useful option for testing the rules in a rule group
+     *          without modifying how they handle your web traffic.</p>
      */
     ExcludedRules?: ExcludedRule[];
 }
@@ -1584,12 +1621,12 @@ export declare enum ComparisonOperator {
 }
 /**
  * <p>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. </p>
- *          <p>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.</p>
+ *          <p>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 could use a size constraint statement to block requests that have a request body greater than 8192 bytes.</p>
  *          <p>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 <code>/logo.jpg</code> is nine characters long.</p>
  */
 export interface SizeConstraintStatement {
     /**
-     * <p>The part of the web request that you want WAF to inspect. For more information, see <a>FieldToMatch</a>. </p>
+     * <p>The part of the web request that you want WAF to inspect. </p>
      */
     FieldToMatch: FieldToMatch | undefined;
     /**
@@ -1613,12 +1650,16 @@ export declare namespace SizeConstraintStatement {
      */
     const filterSensitiveLog: (obj: SizeConstraintStatement) => any;
 }
+export declare enum SensitivityLevel {
+    HIGH = "HIGH",
+    LOW = "LOW"
+}
 /**
- * <p>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.</p>
+ * <p>A rule statement that inspects for malicious SQL code. Attackers insert malicious SQL code into web requests to do things like modify your database or extract data from it. </p>
  */
 export interface SqliMatchStatement {
     /**
-     * <p>The part of the web request that you want WAF to inspect. For more information, see <a>FieldToMatch</a>. </p>
+     * <p>The part of the web request that you want WAF to inspect. </p>
      */
     FieldToMatch: FieldToMatch | undefined;
     /**
@@ -1627,6 +1668,21 @@ export interface SqliMatchStatement {
      *          content of the request component identified by <code>FieldToMatch</code>, starting from the lowest priority setting, before inspecting the content for a match.</p>
      */
     TextTransformations: TextTransformation[] | undefined;
+    /**
+     * <p>The sensitivity that you want WAF to use to inspect for SQL injection attacks. </p>
+     *          <p>
+     *             <code>HIGH</code> detects more attacks, but might generate more false positives,
+     *        especially if your web requests frequently contain unusual strings.
+     *        For information about identifying and mitigating false positives, see
+     *            <a href="https://docs.aws.amazon.com/waf/latest/developerguide/web-acl-testing.html">Testing and tuning</a> in the
+     *            <i>WAF Developer Guide</i>.</p>
+     *          <p>
+     *             <code>LOW</code> is generally a better choice for resources that already have other
+     *            protections against SQL injection attacks or that have a low tolerance for false positives. </p>
+     *          <p>Default: <code>LOW</code>
+     *          </p>
+     */
+    SensitivityLevel?: SensitivityLevel | string;
 }
 export declare namespace SqliMatchStatement {
     /**
@@ -1635,15 +1691,12 @@ export declare namespace SqliMatchStatement {
     const filterSensitiveLog: (obj: SqliMatchStatement) => any;
 }
 /**
- * <p>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. </p>
+ * <p>A rule statement that inspects for cross-site scripting (XSS) attacks. In XSS attacks, the attacker
+ * uses vulnerabilities in a benign website as a vehicle to inject malicious client-site scripts into other legitimate web browsers. </p>
  */
 export interface XssMatchStatement {
     /**
-     * <p>The part of the web request that you want WAF to inspect. For more information, see <a>FieldToMatch</a>. </p>
+     * <p>The part of the web request that you want WAF to inspect. </p>
      */
     FieldToMatch: FieldToMatch | undefined;
     /**
@@ -1809,7 +1862,8 @@ export declare enum ParameterExceptionField {
  *                isn't among the types available at <a>DefaultAction</a>.</p>
  *             </li>
  *             <li>
- *                <p>Your request references an ARN that is malformed, or corresponds to a resource with which a web ACL can't be associated.</p>
+ *                <p>Your request references an ARN that is malformed, or corresponds to a resource
+ *                with which a web ACL can't be associated.</p>
  *             </li>
  *          </ul>
  */
@@ -1846,7 +1900,9 @@ export declare class WAFNonexistentItemException extends __BaseException {
     constructor(opts: __ExceptionOptionType<WAFNonexistentItemException, __BaseException>);
 }
 /**
- * <p>WAF couldn’t retrieve a resource that you specified for this operation. Verify the resources that you are specifying in your request parameters and then retry the operation.</p>
+ * <p>WAF couldn’t retrieve a resource that you specified for this operation. Verify the
+ *          resources that you are specifying in your request parameters and then retry the
+ *          operation.</p>
  */
 export declare class WAFUnavailableEntityException extends __BaseException {
     readonly name: "WAFUnavailableEntityException";
@@ -1866,7 +1922,7 @@ export declare class WAFUnavailableEntityException extends __BaseException {
 export interface CustomResponse {
     /**
      * <p>The HTTP status code to return to the client. </p>
-     *          <p>For a list of status codes that you can use in your custom reqponses, see <a href="https://docs.aws.amazon.com/waf/latest/developerguide/customizing-the-response-status-codes.html">Supported status codes for custom response</a> in the
+     *          <p>For a list of status codes that you can use in your custom responses, see <a href="https://docs.aws.amazon.com/waf/latest/developerguide/customizing-the-response-status-codes.html">Supported status codes for custom response</a> in the
      *          <a href="https://docs.aws.amazon.com/waf/latest/developerguide/waf-chapter.html">WAF Developer Guide</a>. </p>
      */
     ResponseCode: number | undefined;
@@ -1940,7 +1996,6 @@ export declare namespace BlockAction {
  *                in the <code>CaptchaConfig</code>
  *             <code>ImmunityTimeProperty</code> setting at the rule and web ACL level. The rule setting overrides the web ACL setting. </p>
  *          <p>This action option is available for rules. It isn't available for web ACL default actions. </p>
- *          <p>This is used in the context of other settings, for example to specify values for <a>RuleAction</a> and web ACL <a>DefaultAction</a>. </p>
  */
 export interface CaptchaAction {
     /**
@@ -2004,11 +2059,13 @@ export declare namespace RuleAction {
     const filterSensitiveLog: (obj: RuleAction) => any;
 }
 /**
- * <p>Determines how long a <code>CAPTCHA</code> token remains valid after the client successfully solves a <code>CAPTCHA</code> puzzle. </p>
+ * <p>Determines how long a <code>CAPTCHA</code> token remains valid after the client
+ *          successfully solves a <code>CAPTCHA</code> puzzle. </p>
  */
 export interface ImmunityTimeProperty {
     /**
-     * <p>The amount of time, in seconds, that a <code>CAPTCHA</code> token is valid. The default setting is 300.</p>
+     * <p>The amount of time, in seconds, that a <code>CAPTCHA</code> token is valid. The default
+     *          setting is 300.</p>
      */
     ImmunityTime: number | undefined;
 }
@@ -2019,11 +2076,13 @@ export declare namespace ImmunityTimeProperty {
     const filterSensitiveLog: (obj: ImmunityTimeProperty) => any;
 }
 /**
- * <p>Specifies how WAF should handle <code>CAPTCHA</code> evaluations. This is available at the web ACL level and in each rule.  </p>
+ * <p>Specifies how WAF should handle <code>CAPTCHA</code> evaluations. This is
+ *          available at the web ACL level and in each rule. </p>
  */
 export interface CaptchaConfig {
     /**
-     * <p>Determines how long a <code>CAPTCHA</code> token remains valid after the client successfully solves a <code>CAPTCHA</code> puzzle. </p>
+     * <p>Determines how long a <code>CAPTCHA</code> token remains valid after the client
+     *          successfully solves a <code>CAPTCHA</code> puzzle. </p>
      */
     ImmunityTimeProperty?: ImmunityTimeProperty;
 }
@@ -2034,8 +2093,9 @@ export declare namespace CaptchaConfig {
     const filterSensitiveLog: (obj: CaptchaConfig) => any;
 }
 /**
- * <p>Specifies that WAF should do nothing. This is used for the <code>OverrideAction</code> setting
- *            on a <a>Rule</a> when the rule uses a rule group reference statement. </p>
+ * <p>Specifies that WAF should do nothing. This is used for the
+ *             <code>OverrideAction</code> setting on a <a>Rule</a> when the rule uses a
+ *          rule group reference statement. </p>
  *          <p>This is used in the context of other settings, for example to specify values for <a>RuleAction</a> and web ACL <a>DefaultAction</a>. </p>
  *          <p>JSON specification: <code>"None": {}</code>
  *          </p>
@@ -2111,8 +2171,8 @@ export interface VisibilityConfig {
     /**
      * <p>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." </p>
+     *       contain whitespace or metric names reserved for WAF, for example <code>All</code> and
+     *       <code>Default_Action</code>. </p>
      */
     MetricName: string | undefined;
 }
@@ -2388,7 +2448,7 @@ export declare class WAFTagOperationException extends __BaseException {
 }
 /**
  * <p>WAF couldn’t perform your tagging operation because of an internal error. Retry
- *          ybjectNoteWebRequestComponentour request.</p>
+ *          your request.</p>
  */
 export declare class WAFTagOperationInternalErrorException extends __BaseException {
     readonly name: "WAFTagOperationInternalErrorException";
@@ -2633,12 +2693,17 @@ export declare namespace CreateWebACLResponse {
     const filterSensitiveLog: (obj: CreateWebACLResponse) => any;
 }
 /**
- * <p>The operation failed because you are inspecting the web request body, headers, or cookies without specifying how to handle oversize components.
- *        Rules that inspect the body must either provide an <code>OversizeHandling</code> configuration or they must
- *        be preceded by a <code>SizeConstraintStatement</code> that blocks the body content from being too large.
- *        Rules that inspect the headers or cookies must provide an <code>OversizeHandling</code> configuration. </p>
+ * <p>The operation failed because you are inspecting the web request body, headers, or
+ *          cookies without specifying how to handle oversize components. Rules that inspect the body
+ *          must either provide an <code>OversizeHandling</code> configuration or they must be preceded
+ *          by a <code>SizeConstraintStatement</code> that blocks the body content from being too
+ *          large. Rules that inspect the headers or cookies must provide an
+ *             <code>OversizeHandling</code> configuration. </p>
  *          <p>Provide the handling configuration and retry your operation.</p>
- *          <p>Alternately, you can suppress this warning by adding the following tag to the resource that you provide to this operation: <code>Tag</code> (key:<code>WAF:OversizeFieldsHandlingConstraintOptOut</code>, value:<code>true</code>).</p>
+ *          <p>Alternately, you can suppress this warning by adding the following tag to the resource
+ *          that you provide to this operation: <code>Tag</code>
+ *             (key:<code>WAF:OversizeFieldsHandlingConstraintOptOut</code>,
+ *          value:<code>true</code>).</p>
  */
 export declare class WAFConfigurationWarningException extends __BaseException {
     readonly name: "WAFConfigurationWarningException";
@@ -2719,9 +2784,11 @@ export declare namespace DeleteIPSetResponse {
     const filterSensitiveLog: (obj: DeleteIPSetResponse) => any;
 }
 /**
- * <p>WAF couldn’t perform the operation because your resource is being used by another resource or it’s associated with another resource. </p>
- *          <p>For <code>DeleteWebACL</code>, you will only get this exception if the web ACL is still associated with
- *           a regional resource. Deleting a web ACL that is still associated with an Amazon CloudFront distribution won't get this exception. </p>
+ * <p>WAF couldn’t perform the operation because your resource is being used by another
+ *          resource or it’s associated with another resource. </p>
+ *          <p>For <code>DeleteWebACL</code>, you will only get this exception if the web ACL is still
+ *          associated with a regional resource. Deleting a web ACL that is still associated with an
+ *          Amazon CloudFront distribution won't get this exception. </p>
  */
 export declare class WAFAssociatedItemException extends __BaseException {
     readonly name: "WAFAssociatedItemException";
@@ -2734,8 +2801,7 @@ export declare class WAFAssociatedItemException extends __BaseException {
 }
 export interface DeleteLoggingConfigurationRequest {
     /**
-     * <p>The Amazon Resource Name (ARN) of the web ACL from which you want to delete the
-     *        <a>LoggingConfiguration</a>.</p>
+     * <p>The Amazon Resource Name (ARN) of the web ACL from which you want to delete the <a>LoggingConfiguration</a>.</p>
      */
     ResourceArn: string | undefined;
 }
@@ -2921,9 +2987,8 @@ export interface DescribeManagedRuleGroupRequest {
      */
     Scope: Scope | string | undefined;
     /**
-     * <p>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.
-     *       </p>
+     * <p>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. </p>
      */
     VersionName?: string;
 }
@@ -3088,7 +3153,8 @@ export interface GenerateMobileSdkReleaseUrlRequest {
      */
     Platform: Platform | string | undefined;
     /**
-     * <p>The release version. For the latest available version, specify <code>LATEST</code>.</p>
+     * <p>The release version. For the latest available version, specify
+     *          <code>LATEST</code>.</p>
      */
     ReleaseVersion: string | undefined;
 }
@@ -3232,8 +3298,7 @@ export declare namespace GetIPSetResponse {
 }
 export interface GetLoggingConfigurationRequest {
     /**
-     * <p>The Amazon Resource Name (ARN) of the web ACL for which you want to get the
-     *        <a>LoggingConfiguration</a>.</p>
+     * <p>The Amazon Resource Name (ARN) of the web ACL for which you want to get the <a>LoggingConfiguration</a>.</p>
      */
     ResourceArn: string | undefined;
 }
@@ -3269,11 +3334,12 @@ export declare namespace LabelNameCondition {
  */
 export interface Condition {
     /**
-     * <p>A single action condition.</p>
+     * <p>A single action condition. This is the action setting that a log record must contain in order to meet the condition.</p>
      */
     ActionCondition?: ActionCondition;
     /**
-     * <p>A single label name condition.</p>
+     * <p>A single label name condition. This is the fully qualified label name that a log record must contain in order to meet the condition.
+     *        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.  </p>
      */
     LabelNameCondition?: LabelNameCondition;
 }
@@ -3335,10 +3401,10 @@ export declare namespace LoggingFilter {
     const filterSensitiveLog: (obj: LoggingFilter) => any;
 }
 /**
- * <p>Defines an association between logging destinations and a web ACL
- *          resource, for logging from WAF. As part of the association, you can specify parts of
- *          the standard logging fields to keep out of the logs and you can specify filters so that you
- *          log only a subset of the logging records. </p>
+ * <p>Defines an association between logging destinations and a web ACL resource, for logging
+ *          from WAF. As part of the association, you can specify parts of the standard logging
+ *          fields to keep out of the logs and you can specify filters so that you log only a subset of
+ *          the logging records. </p>
  *          <note>
  *             <p>You can define one logging destination per web ACL.</p>
  *          </note>
@@ -3371,18 +3437,21 @@ export interface LoggingConfiguration {
      */
     ResourceArn: string | undefined;
     /**
-     * <p>The logging destination configuration that you want to associate
-     *          with the web ACL.</p>
+     * <p>The logging destination configuration that you want to associate with the web
+     *          ACL.</p>
      *          <note>
      *             <p>You can associate one logging destination to a web ACL.</p>
      *          </note>
      */
     LogDestinationConfigs: string[] | undefined;
     /**
-     * <p>The parts of the request that you want to keep out of the logs. For
-     *           example, if you redact the <code>SingleHeader</code> field, the <code>HEADER</code> field in the logs will be <code>xxx</code>. </p>
+     * <p>The parts of the request that you want to keep out of the logs. For example, if you
+     *          redact the <code>SingleHeader</code> field, the <code>HEADER</code> field in the logs will
+     *          be <code>xxx</code>. </p>
      *          <note>
-     *            <p>You can specify only the following fields for redaction: <code>UriPath</code>, <code>QueryString</code>, <code>SingleHeader</code>, <code>Method</code>, and <code>JsonBody</code>.</p>
+     *             <p>You can specify only the following fields for redaction: <code>UriPath</code>,
+     *                <code>QueryString</code>, <code>SingleHeader</code>, <code>Method</code>, and
+     *                <code>JsonBody</code>.</p>
      *          </note>
      */
     RedactedFields?: FieldToMatch[];
@@ -3580,7 +3649,8 @@ export interface GetMobileSdkReleaseRequest {
      */
     Platform: Platform | string | undefined;
     /**
-     * <p>The release version. For the latest available version, specify <code>LATEST</code>.</p>
+     * <p>The release version. For the latest available version, specify
+     *          <code>LATEST</code>.</p>
      */
     ReleaseVersion: string | undefined;
 }
@@ -3679,12 +3749,14 @@ export interface GetRateBasedStatementManagedKeysRequest {
      */
     WebACLId: string | undefined;
     /**
-     * <p>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. </p>
+     * <p>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. </p>
      */
     RuleGroupRuleName?: string;
     /**
-     * <p>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 <code>RuleGroupRuleName</code>.</p>
+     * <p>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 <code>RuleGroupRuleName</code>.</p>
      */
     RuleName: string | undefined;
 }
@@ -3932,11 +4004,14 @@ export declare enum FailureReason {
     TOKEN_MISSING = "TOKEN_MISSING"
 }
 /**
- * <p>The result from the inspection of the web request for a valid <code>CAPTCHA</code> token. </p>
+ * <p>The result from the inspection of the web request for a valid <code>CAPTCHA</code>
+ *          token. </p>
  */
 export interface CaptchaResponse {
     /**
-     * <p>The HTTP response code indicating the status of the <code>CAPTCHA</code> token in the web request. If the token is missing, invalid, or expired, this code is <code>405 Method Not Allowed</code>.</p>
+     * <p>The HTTP response code indicating the status of the <code>CAPTCHA</code> token in the
+     *          web request. If the token is missing, invalid, or expired, this code is <code>405 Method
+     *             Not Allowed</code>.</p>
      */
     ResponseCode?: number;
     /**
@@ -4212,7 +4287,8 @@ export interface ManagedRuleGroupSummary {
      */
     Name?: string;
     /**
-     * <p>Indicates whether the managed rule group is versioned. If it is, you can retrieve the versions list by calling <a>ListAvailableManagedRuleGroupVersions</a>. </p>
+     * <p>Indicates whether the managed rule group is versioned. If it is, you can retrieve the
+     *          versions list by calling <a>ListAvailableManagedRuleGroupVersions</a>. </p>
      */
     VersioningSupported?: boolean;
     /**
@@ -4878,9 +4954,9 @@ export declare namespace PutLoggingConfigurationResponse {
     const filterSensitiveLog: (obj: PutLoggingConfigurationResponse) => any;
 }
 /**
- * <p>The operation failed because you don't have the permissions that your logging configuration requires. For information, see
- *            <a href="https://docs.aws.amazon.com/waf/latest/developerguide/logging.html">Logging web ACL traffic information</a>
- *                in the <i>WAF Developer Guide</i>.</p>
+ * <p>The operation failed because you don't have the permissions that your logging
+ *          configuration requires. For information, see <a href="https://docs.aws.amazon.com/waf/latest/developerguide/logging.html">Logging web ACL traffic information</a>
+ *          in the <i>WAF Developer Guide</i>.</p>
  */
 export declare class WAFLogDestinationPermissionIssueException extends __BaseException {
     readonly name: "WAFLogDestinationPermissionIssueException";
@@ -5355,28 +5431,26 @@ export declare namespace UpdateWebACLResponse {
     const filterSensitiveLog: (obj: UpdateWebACLResponse) => any;
 }
 /**
- * <p>The processing guidance for a <a>Rule</a>, used by WAF to determine whether a web request matches the rule. </p>
+ * <p>The processing guidance for a <a>Rule</a>, used by WAF to determine whether
+ *          a web request matches the rule. </p>
  */
 export interface Statement {
     /**
-     * <p>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.</p>
+     * <p>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 called a string match statement.</p>
      */
     ByteMatchStatement?: ByteMatchStatement;
     /**
-     * <p>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.</p>
+     * <p>A rule statement that inspects for malicious SQL code. Attackers insert malicious SQL code into web requests to do things like modify your database or extract data from it. </p>
      */
     SqliMatchStatement?: SqliMatchStatement;
     /**
-     * <p>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. </p>
+     * <p>A rule statement that inspects for cross-site scripting (XSS) attacks. In XSS attacks, the attacker
+     * uses vulnerabilities in a benign website as a vehicle to inject malicious client-site scripts into other legitimate web browsers. </p>
      */
     XssMatchStatement?: XssMatchStatement;
     /**
      * <p>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. </p>
-     *          <p>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.</p>
+     *          <p>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 could use a size constraint statement to block requests that have a request body greater than 8192 bytes.</p>
      *          <p>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 <code>/logo.jpg</code> is nine characters long.</p>
      */
     SizeConstraintStatement?: SizeConstraintStatement;
@@ -5413,7 +5487,7 @@ export interface Statement {
      *                <p>A string match statement that searches in the User-Agent header for the string BadBot.</p>
      *             </li>
      *          </ul>
-     *          <p>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.</p>
+     *          <p>In this rate-based rule, you also define a rate limit. For this example, the rate limit is 1,000. Requests that meet the criteria of both of the nested statements are counted. If the count exceeds 1,000 requests per five minutes, the rule action triggers. Requests that do not meet the criteria of both of the nested statements are not counted towards the rate limit and are not affected by this rule.</p>
      *          <p>You cannot nest a <code>RateBasedStatement</code> inside another statement, for example inside a <code>NotStatement</code> or <code>OrStatement</code>. You can define a <code>RateBasedStatement</code> inside a web ACL and inside a rule group. </p>
      */
     RateBasedStatement?: RateBasedStatement;
@@ -5465,15 +5539,16 @@ export interface ManagedRuleGroupStatement {
     Name: string | undefined;
     /**
      * <p>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. </p>
+     *          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. </p>
      */
     Version?: string;
     /**
-     * <p>The rules in the referenced rule group whose actions are set to <code>Count</code>.
-     *        When you exclude a rule, WAF evaluates it exactly as it would if the rule action setting were <code>Count</code>.
-     *        This is a useful option for testing the rules in a rule group without modifying how they handle your web traffic.</p>
+     * <p>The rules in the referenced rule group whose actions are set to <code>Count</code>. When
+     *          you exclude a rule, WAF evaluates it exactly as it would if the rule action setting were
+     *             <code>Count</code>. This is a useful option for testing the rules in a rule group
+     *          without modifying how they handle your web traffic.</p>
      */
     ExcludedRules?: ExcludedRule[];
     /**
@@ -5526,7 +5601,7 @@ export declare namespace NotStatement {
  *                <p>A string match statement that searches in the User-Agent header for the string BadBot.</p>
  *             </li>
  *          </ul>
- *          <p>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.</p>
+ *          <p>In this rate-based rule, you also define a rate limit. For this example, the rate limit is 1,000. Requests that meet the criteria of both of the nested statements are counted. If the count exceeds 1,000 requests per five minutes, the rule action triggers. Requests that do not meet the criteria of both of the nested statements are not counted towards the rate limit and are not affected by this rule.</p>
  *          <p>You cannot nest a <code>RateBasedStatement</code> inside another statement, for example inside a <code>NotStatement</code> or <code>OrStatement</code>. You can define a <code>RateBasedStatement</code> inside a web ACL and inside a rule group. </p>
  */
 export interface RateBasedStatement {