AWS waf documentation change
Summary
Updated terminology from 'protection pack or web ACL' to 'protection pack (web ACL)' throughout migration documentation to clarify configuration references
Security assessment
Changes are purely terminological clarifications without addressing vulnerabilities or security features. The updates standardize references to web ACL configurations in migration context but contain no security advisories, vulnerability fixes, or new security controls.
Diff
diff --git a/waf/latest/developerguide/waf-migrating-how-it-works.md b/waf/latest/developerguide/waf-migrating-how-it-works.md index 8c6feddcc..8a7e73acc 100644 --- a//waf/latest/developerguide/waf-migrating-how-it-works.md +++ b//waf/latest/developerguide/waf-migrating-how-it-works.md @@ -11 +11 @@ You can now use the updated experience to access AWS WAF functionality anywhere -The automated migration carries over most of your AWS WAF Classic protection pack or web ACL configuration, leaving some things that you need to handle manually. +The automated migration carries over most of your AWS WAF Classic protection pack (web ACL) configuration, leaving some things that you need to handle manually. @@ -17 +17 @@ Some protection configurations cannot be automatically migrated, and require man -The following lists the high-level steps for migrating a protection pack or web ACL. +The following lists the high-level steps for migrating a protection pack (web ACL). @@ -19 +19 @@ The following lists the high-level steps for migrating a protection pack or web - 1. The automated migration reads everything related to your existing protection pack or web ACL, without modifying or deleting anything in AWS WAF Classic. It creates a representation of the web ACL and its related resources, compatible with AWS WAF. It generates an AWS CloudFormation template for the new protection pack or web ACL and stores it in an Amazon S3 bucket. + 1. The automated migration reads everything related to your existing protection pack (web ACL), without modifying or deleting anything in AWS WAF Classic. It creates a representation of the web ACL and its related resources, compatible with AWS WAF. It generates an AWS CloudFormation template for the new protection pack (web ACL) and stores it in an Amazon S3 bucket. @@ -21 +21 @@ The following lists the high-level steps for migrating a protection pack or web - 2. You deploy the template into AWS CloudFormation, in order to recreate the protection pack or web ACL and related resources in AWS WAF. + 2. You deploy the template into AWS CloudFormation, in order to recreate the protection pack (web ACL) and related resources in AWS WAF. @@ -23 +23 @@ The following lists the high-level steps for migrating a protection pack or web - 3. You review the protection pack or web ACL, and manually complete the migration, making sure that your new protection pack or web ACL takes full advantage of the capabilities of the latest AWS WAF. + 3. You review the protection pack (web ACL), and manually complete the migration, making sure that your new protection pack (web ACL) takes full advantage of the capabilities of the latest AWS WAF. @@ -25 +25 @@ The following lists the high-level steps for migrating a protection pack or web - 4. You manually switch your protected resources over to the new protection pack or web ACL. + 4. You manually switch your protected resources over to the new protection pack (web ACL). @@ -38 +38 @@ Migration caveats -Migrating a protection pack or web ACL +Migrating a protection pack (web ACL)