@aws-sdk/client-wafv2 3.675.0 → 3.676.0

package/README.md

@@ -15,10 +15,8 @@ like endpoints and namespaces, all have the versioning information added, like "
 "v2", to distinguish from the prior version. We recommend migrating your resources to
 this version, because it has a number of significant improvements.</p>
 <p>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. </p>
-<p>For information, including how to migrate your WAF resources to this version,
+WAF resources that you created before. WAF Classic support will end on September 30, 2025. </p>
+<p>For information about WAF, including how to migrate your WAF Classic resources to this version,
 see the <a href="https://docs.aws.amazon.com/waf/latest/developerguide/waf-chapter.html">WAF Developer Guide</a>. </p>
 </note>
 <p>WAF is a web application firewall that lets you monitor the HTTP and HTTPS
@@ -45,26 +43,6 @@ US East (N. Virginia): us-east-1.</p>
 </ul>
 <p>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 <a href="http://aws.amazon.com/tools/#SDKs">Amazon Web Services SDKs</a>.</p>
-<p>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:</p>
-<ul>
-<li>
-<p>You use one API for both global and regional applications. Where you need to
-distinguish the scope, you specify a <code>Scope</code> parameter and set it to
-<code>CLOUDFRONT</code> or <code>REGIONAL</code>. </p>
-</li>
-<li>
-<p>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.</p>
-</li>
-<li>
-<p>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.</p>
-</li>
-</ul>
 
 ## Installing
 

package/dist-cjs/index.js

@@ -2877,6 +2877,7 @@ var de_WebACL = /* @__PURE__ */ __name((output, context) => {
     Name: import_smithy_client.expectString,
     PostProcessFirewallManagerRuleGroups: (_) => de_FirewallManagerRuleGroups(_, context),
     PreProcessFirewallManagerRuleGroups: (_) => de_FirewallManagerRuleGroups(_, context),
+    RetrofittedByFirewallManager: import_smithy_client.expectBoolean,
     Rules: (_) => de_Rules(_, context),
     TokenDomains: import_smithy_client._json,
     VisibilityConfig: import_smithy_client._json

package/dist-es/protocols/Aws_json1_1.js

@@ -1777,6 +1777,7 @@ const de_WebACL = (output, context) => {
         Name: __expectString,
         PostProcessFirewallManagerRuleGroups: (_) => de_FirewallManagerRuleGroups(_, context),
         PreProcessFirewallManagerRuleGroups: (_) => de_FirewallManagerRuleGroups(_, context),
+        RetrofittedByFirewallManager: __expectBoolean,
         Rules: (_) => de_Rules(_, context),
         TokenDomains: _json,
         VisibilityConfig: _json,

package/dist-types/WAFV2.d.ts

@@ -390,10 +390,8 @@ export interface WAFV2 {
  *             "v2", to distinguish from the prior version. We recommend migrating your resources to
  *             this version, because it has a number of significant improvements.</p>
  *             <p>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. </p>
- *             <p>For information, including how to migrate your WAF resources to this version,
+ *             WAF resources that you created before. WAF Classic support will end on September 30, 2025. </p>
+ *             <p>For information about WAF, including how to migrate your WAF Classic resources to this version,
  *             see the <a href="https://docs.aws.amazon.com/waf/latest/developerguide/waf-chapter.html">WAF Developer Guide</a>. </p>
  *          </note>
  *          <p>WAF is a web application firewall that lets you monitor the HTTP and HTTPS
@@ -420,26 +418,6 @@ export interface WAFV2 {
  *          </ul>
  *          <p>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 <a href="http://aws.amazon.com/tools/#SDKs">Amazon Web Services SDKs</a>.</p>
- *          <p>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:</p>
- *          <ul>
- *             <li>
- *                <p>You use one API for both global and regional applications. Where you need to
- *                distinguish the scope, you specify a <code>Scope</code> parameter and set it to
- *                   <code>CLOUDFRONT</code> or <code>REGIONAL</code>. </p>
- *             </li>
- *             <li>
- *                <p>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.</p>
- *             </li>
- *             <li>
- *                <p>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.</p>
- *             </li>
- *          </ul>
  * @public
  */
 export declare class WAFV2 extends WAFV2Client implements WAFV2 {

package/dist-types/WAFV2Client.d.ts

@@ -213,10 +213,8 @@ export interface WAFV2ClientResolvedConfig extends WAFV2ClientResolvedConfigType
  *             "v2", to distinguish from the prior version. We recommend migrating your resources to
  *             this version, because it has a number of significant improvements.</p>
  *             <p>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. </p>
- *             <p>For information, including how to migrate your WAF resources to this version,
+ *             WAF resources that you created before. WAF Classic support will end on September 30, 2025. </p>
+ *             <p>For information about WAF, including how to migrate your WAF Classic resources to this version,
  *             see the <a href="https://docs.aws.amazon.com/waf/latest/developerguide/waf-chapter.html">WAF Developer Guide</a>. </p>
  *          </note>
  *          <p>WAF is a web application firewall that lets you monitor the HTTP and HTTPS
@@ -243,26 +241,6 @@ export interface WAFV2ClientResolvedConfig extends WAFV2ClientResolvedConfigType
  *          </ul>
  *          <p>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 <a href="http://aws.amazon.com/tools/#SDKs">Amazon Web Services SDKs</a>.</p>
- *          <p>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:</p>
- *          <ul>
- *             <li>
- *                <p>You use one API for both global and regional applications. Where you need to
- *                distinguish the scope, you specify a <code>Scope</code> parameter and set it to
- *                   <code>CLOUDFRONT</code> or <code>REGIONAL</code>. </p>
- *             </li>
- *             <li>
- *                <p>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.</p>
- *             </li>
- *             <li>
- *                <p>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.</p>
- *             </li>
- *          </ul>
  * @public
  */
 export declare class WAFV2Client extends __Client<__HttpHandlerOptions, ServiceInputTypes, ServiceOutputTypes, WAFV2ClientResolvedConfig> {

package/dist-types/commands/DeleteFirewallManagerRuleGroupsCommand.d.ts

@@ -27,9 +27,8 @@ declare const DeleteFirewallManagerRuleGroupsCommand_base: {
     getEndpointParameterInstructions(): import("@smithy/middleware-endpoint").EndpointParameterInstructions;
 };
 /**
- * <p>Deletes all rule groups that are managed by Firewall Manager for the specified web ACL. </p>
- *          <p>You can only use this if <code>ManagedByFirewallManager</code> is false in the specified
- *             <a>WebACL</a>. </p>
+ * <p>Deletes all rule groups that are managed by Firewall Manager from the specified <a>WebACL</a>. </p>
+ *          <p>You can only use this if <code>ManagedByFirewallManager</code> and <code>RetrofittedByFirewallManager</code> are both false in the web ACL. </p>
  * @example
  * Use a bare-bones client and the command you need to make an API call.
  * ```javascript

package/dist-types/commands/DeleteWebACLCommand.d.ts

@@ -28,8 +28,7 @@ declare const DeleteWebACLCommand_base: {
 };
 /**
  * <p>Deletes the specified <a>WebACL</a>. </p>
- *          <p>You can only use this if <code>ManagedByFirewallManager</code> is false in the specified
- *             <a>WebACL</a>. </p>
+ *          <p>You can only use this if <code>ManagedByFirewallManager</code> is false in the web ACL. </p>
  *          <note>
  *             <p>Before deleting any web ACL, first disassociate it from all resources.</p>
  *             <ul>

package/dist-types/commands/GetWebACLCommand.d.ts

@@ -1216,6 +1216,7 @@ declare const GetWebACLCommand_base: {
  * //         },
  * //       },
  * //     },
+ * //     RetrofittedByFirewallManager: true || false,
  * //   },
  * //   LockToken: "STRING_VALUE",
  * //   ApplicationIntegrationURL: "STRING_VALUE",

package/dist-types/commands/GetWebACLForResourceCommand.d.ts

@@ -1224,6 +1224,7 @@ declare const GetWebACLForResourceCommand_base: {
  * //         },
  * //       },
  * //     },
+ * //     RetrofittedByFirewallManager: true || false,
  * //   },
  * // };
  *

package/dist-types/index.d.ts

@@ -7,10 +7,8 @@
  *             "v2", to distinguish from the prior version. We recommend migrating your resources to
  *             this version, because it has a number of significant improvements.</p>
  *             <p>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. </p>
- *             <p>For information, including how to migrate your WAF resources to this version,
+ *             WAF resources that you created before. WAF Classic support will end on September 30, 2025. </p>
+ *             <p>For information about WAF, including how to migrate your WAF Classic resources to this version,
  *             see the <a href="https://docs.aws.amazon.com/waf/latest/developerguide/waf-chapter.html">WAF Developer Guide</a>. </p>
  *          </note>
  *          <p>WAF is a web application firewall that lets you monitor the HTTP and HTTPS
@@ -37,26 +35,6 @@
  *          </ul>
  *          <p>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 <a href="http://aws.amazon.com/tools/#SDKs">Amazon Web Services SDKs</a>.</p>
- *          <p>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:</p>
- *          <ul>
- *             <li>
- *                <p>You use one API for both global and regional applications. Where you need to
- *                distinguish the scope, you specify a <code>Scope</code> parameter and set it to
- *                   <code>CLOUDFRONT</code> or <code>REGIONAL</code>. </p>
- *             </li>
- *             <li>
- *                <p>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.</p>
- *             </li>
- *             <li>
- *                <p>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.</p>
- *             </li>
- *          </ul>
  *
  * @packageDocumentation
  */

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

@@ -4834,7 +4834,11 @@ export interface LoggingConfiguration {
     /**
      * <p>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. </p>
+     *       configuration. </p>
+     *          <p>The logging configuration can be created by Firewall Manager for use with any web ACL that Firewall Manager is using for an WAF policy.
+     *        Web ACLs that Firewall Manager creates and uses have their <code>ManagedByFirewallManager</code> property set to true. Web ACLs that were created
+     *            by a customer account and then retrofitted by Firewall Manager for use by a policy have their <code>RetrofittedByFirewallManager</code> property set to true.
+     *        For either case, any corresponding logging configuration will indicate <code>ManagedByFirewallManager</code>.</p>
      * @public
      */
     ManagedByFirewallManager?: boolean;
@@ -8080,8 +8084,9 @@ export interface WebACL {
      */
     PostProcessFirewallManagerRuleGroups?: FirewallManagerRuleGroup[];
     /**
-     * <p>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. </p>
+     * <p>Indicates whether this web ACL was created by Firewall Manager and is being 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.
+     *            See also the properties <code>RetrofittedByFirewallManager</code>, <code>PreProcessFirewallManagerRuleGroups</code>, and <code>PostProcessFirewallManagerRuleGroups</code>. </p>
      * @public
      */
     ManagedByFirewallManager?: boolean;
@@ -8141,6 +8146,13 @@ export interface WebACL {
      * @public
      */
     AssociationConfig?: AssociationConfig;
+    /**
+     * <p>Indicates whether this web ACL was created by a customer account and then retrofitted by Firewall Manager. If true, then the web ACL is currently being
+     *        managed by a Firewall Manager WAF policy, and only Firewall Manager can manage any Firewall Manager rule groups in the web ACL.
+     *            See also the properties <code>ManagedByFirewallManager</code>, <code>PreProcessFirewallManagerRuleGroups</code>, and <code>PostProcessFirewallManagerRuleGroups</code>. </p>
+     * @public
+     */
+    RetrofittedByFirewallManager?: boolean;
 }
 /**
  * @public

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

@@ -1782,6 +1782,7 @@ export interface WebACL {
   ChallengeConfig?: ChallengeConfig;
   TokenDomains?: string[];
   AssociationConfig?: AssociationConfig;
+  RetrofittedByFirewallManager?: boolean;
 }
 export interface GetWebACLForResourceResponse {
   WebACL?: WebACL;

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@aws-sdk/client-wafv2",
   "description": "AWS SDK for JavaScript Wafv2 Client for Node.js, Browser and React Native",
-  "version": "3.675.0",
+  "version": "3.676.0",
   "scripts": {
     "build": "concurrently 'yarn:build:cjs' 'yarn:build:es' 'yarn:build:types'",
     "build:cjs": "node ../../scripts/compilation/inline client-wafv2",