AWS waf documentation change
Summary
Updated terminology from 'protection pack or web ACL' to 'protection pack (web ACL)' throughout the migration documentation, clarifying the relationship between protection packs and web ACLs in the new AWS WAF experience.
Security assessment
The changes are purely terminological clarifications without addressing vulnerabilities or introducing security features. The updates standardize naming conventions but do not modify security controls, mitigations, or disclose security-related changes.
Diff
diff --git a/waf/latest/developerguide/waf-migrating-procedure-manual-finish.md b/waf/latest/developerguide/waf-migrating-procedure-manual-finish.md index 3d66514b8..b370bfc93 100644 --- a//waf/latest/developerguide/waf-migrating-procedure-manual-finish.md +++ b//waf/latest/developerguide/waf-migrating-procedure-manual-finish.md @@ -9 +9 @@ You can now use the updated experience to access AWS WAF functionality anywhere -# Migrating a protection pack or web ACL: manual follow-up +# Migrating a protection pack (web ACL): manual follow-up @@ -11 +11 @@ You can now use the updated experience to access AWS WAF functionality anywhere -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). +After the automated migration is complete, review the newly created protection pack (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 (web ACL) management that the migration doesn't handle. For the list, see [Migration caveats and limitations](./waf-migrating-caveats.html). @@ -19 +19 @@ After the automated migration is complete, review the newly created protection p - 3. In the navigation pane, choose **protection pack or web ACLs**. + 3. In the navigation pane, choose **protection packs (web ACLs)**. @@ -21 +21 @@ After the automated migration is complete, review the newly created protection p - 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. + 4. In the **protection packs (web ACLs)** page, locate your new protection pack (web ACL) in the list for the Region where you created it. Choose the protection pack (web ACL)'s name to bring up the settings for the protection pack (web ACL). @@ -23 +23 @@ After the automated migration is complete, review the newly created protection p - 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. + 5. Review all of the settings for the new protection pack (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. @@ -25 +25 @@ After the automated migration is complete, review the newly created protection p - 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: + 6. If your AWS WAF Classic protection pack (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 (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: @@ -27 +27 @@ After the automated migration is complete, review the newly created protection p - 1. In your protection pack or web ACL settings page, choose the protection pack or web ACL **Rules** tab. + 1. In your protection pack (web ACL) settings page, choose the protection pack (web ACL) **Rules** tab. @@ -31 +31 @@ After the automated migration is complete, review the newly created protection p - 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). + 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 (web ACL), see [Using managed rule groups in AWS WAF](./waf-managed-rule-groups.html) and [Using protection packs (web ACLs) with rules and rule groups in AWS WAF](./web-acl-processing.html). @@ -36 +36 @@ After the automated migration is complete, review the newly created protection p -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). +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 (web ACL): additional considerations](./waf-migrating-procedure-additional.html).