AWS Security ChangesHomeSearch

AWS waf documentation change

Service: waf · 2025-06-19 · Documentation low

File: waf/latest/developerguide/waf-migrating-procedure-manual-finish.md

Summary

Updated documentation to reference 'protection pack or web ACL' terminology instead of just 'web ACL', added section about new console experience

Security assessment

Changes focus on terminology updates (adding 'protection pack' references) and console navigation changes. No specific security vulnerabilities or mitigations are mentioned. Managed rule group references and logging configurations were already present in previous version.

Diff

diff --git a/waf/latest/developerguide/waf-migrating-procedure-manual-finish.md b/waf/latest/developerguide/waf-migrating-procedure-manual-finish.md
index 86ffd19e0..3d66514b8 100644
--- a//waf/latest/developerguide/waf-migrating-procedure-manual-finish.md
+++ b//waf/latest/developerguide/waf-migrating-procedure-manual-finish.md
@@ -5 +5 @@
-# Migrating a web ACL: manual follow-up
+**Introducing a new console experience for AWS WAF**
@@ -7 +7,5 @@
-After the automated migration is complete, review the newly created web ACL and fill in the components that the migration doesn't bring over for you. The following procedure covers the aspects of web ACL management that the migration doesn't handle. For the list, see [Migration caveats and limitations](./waf-migrating-caveats.html).
+You can now use the updated experience to access AWS WAF functionality anywhere in the console. For more details, see [Working with the updated console experience](./working-with-console.html). 
+
+# Migrating a protection pack or web ACL: manual follow-up
+
+After the automated migration is complete, review the newly created protection pack or web ACL and fill in the components that the migration doesn't bring over for you. The following procedure covers the aspects of protection pack or web ACL management that the migration doesn't handle. For the list, see [Migration caveats and limitations](./waf-migrating-caveats.html).
@@ -15 +19 @@ After the automated migration is complete, review the newly created web ACL and
-  3. In the navigation pane, choose **Web ACLs**. 
+  3. In the navigation pane, choose **protection pack or web ACLs**. 
@@ -17 +21 @@ After the automated migration is complete, review the newly created web ACL and
-  4. In the **Web ACLs** page, locate your new web ACL in the list for the Region where you created it. Choose the web ACL's name to bring up the settings for the web ACL. 
+  4. In the **protection pack or web ACLs** page, locate your new protection pack or web ACL in the list for the Region where you created it. Choose the protection pack or web ACL's name to bring up the settings for the protection pack or web ACL. 
@@ -19 +23 @@ After the automated migration is complete, review the newly created web ACL and
-  5. Review all of the settings for the new web ACL against your prior AWS WAF Classic web ACL. By default, logging and protected resource associations are disabled. You enable those when you're ready to switch over. 
+  5. Review all of the settings for the new protection pack or web ACL against your prior AWS WAF Classic web ACL. By default, logging and protected resource associations are disabled. You enable those when you're ready to switch over. 
@@ -21 +25 @@ After the automated migration is complete, review the newly created web ACL and
-  6. If your AWS WAF Classic web ACL had a managed rule group, the rule group inclusion wasn't brought over in the migration. You can add managed rule groups to the new web ACL. Review the information about managed rule groups, including the list of AWS Managed Rules that are available with the new version of AWS WAF, at [Using managed rule groups in AWS WAF](./waf-managed-rule-groups.html). To add a managed rule group, do the following:
+  6. If your AWS WAF Classic protection pack or web ACL had a managed rule group, the rule group inclusion wasn't brought over in the migration. You can add managed rule groups to the new protection pack or web ACL. Review the information about managed rule groups, including the list of AWS Managed Rules that are available with the new version of AWS WAF, at [Using managed rule groups in AWS WAF](./waf-managed-rule-groups.html). To add a managed rule group, do the following:
@@ -23 +27 @@ After the automated migration is complete, review the newly created web ACL and
-    1. In your web ACL settings page, choose the web ACL **Rules** tab. 
+    1. In your protection pack or web ACL settings page, choose the protection pack or web ACL **Rules** tab. 
@@ -27 +31 @@ After the automated migration is complete, review the newly created web ACL and
-    3. Expand the listing for the vendor of your choice and select the rule groups that you want to add. For AWS Marketplace sellers, you might need to subscribe to the rule groups. For more information about using managed rule groups in your web ACL, see [Using managed rule groups in AWS WAF](./waf-managed-rule-groups.html) and [Using web ACLs with rules and rule groups in AWS WAF](./web-acl-processing.html).
+    3. Expand the listing for the vendor of your choice and select the rule groups that you want to add. For AWS Marketplace sellers, you might need to subscribe to the rule groups. For more information about using managed rule groups in your protection pack or web ACL, see [Using managed rule groups in AWS WAF](./waf-managed-rule-groups.html) and [Using protection pack or web ACLs with rules and rule groups in AWS WAF](./web-acl-processing.html).
@@ -32 +36 @@ After the automated migration is complete, review the newly created web ACL and
-After you finish the basic migration process, we recommend that you review your needs and consider additional options, to be sure that the new configuration is as efficient as possible and that it's using the latest available security options. See [Migrating a web ACL: additional considerations](./waf-migrating-procedure-additional.html).
+After you finish the basic migration process, we recommend that you review your needs and consider additional options, to be sure that the new configuration is as efficient as possible and that it's using the latest available security options. See [Migrating a protection pack or web ACL: additional considerations](./waf-migrating-procedure-additional.html).