AWS waf documentation change
Summary
Updated migration documentation to include protection packs alongside web ACLs, added note about new console experience
Security assessment
Changes primarily expand scope to include protection packs in migration process and announce UI updates. No specific security vulnerabilities or weaknesses are addressed. Modifications are procedural improvements rather than security fixes.
Diff
diff --git a/waf/latest/developerguide/waf-migrating-how-it-works.md b/waf/latest/developerguide/waf-migrating-how-it-works.md index 8f9ac8003..8c6feddcc 100644 --- a//waf/latest/developerguide/waf-migrating-how-it-works.md +++ b//waf/latest/developerguide/waf-migrating-how-it-works.md @@ -4,0 +5,4 @@ +**Introducing a new console experience for AWS WAF** + +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). + @@ -7 +11 @@ -The automated migration carries over most of your AWS WAF Classic 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 or web ACL configuration, leaving some things that you need to handle manually. @@ -13 +17 @@ Some protection configurations cannot be automatically migrated, and require man -The following lists the high-level steps for migrating a web ACL. +The following lists the high-level steps for migrating a protection pack or web ACL. @@ -15 +19 @@ The following lists the high-level steps for migrating a web ACL. - 1. The automated migration reads everything related to your existing 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 web ACL and stores it in an Amazon S3 bucket. + 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. @@ -17 +21 @@ The following lists the high-level steps for migrating a web ACL. - 2. You deploy the template into AWS CloudFormation, in order to recreate the web ACL and related resources in AWS WAF. + 2. You deploy the template into AWS CloudFormation, in order to recreate the protection pack or web ACL and related resources in AWS WAF. @@ -19 +23 @@ The following lists the high-level steps for migrating a web ACL. - 3. You review the web ACL, and manually complete the migration, making sure that your new web ACL takes full advantage of the capabilities of the latest AWS WAF. + 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. @@ -21 +25 @@ The following lists the high-level steps for migrating a web ACL. - 4. You manually switch your protected resources over to the new web ACL. + 4. You manually switch your protected resources over to the new protection pack or web ACL. @@ -34 +38 @@ Migration caveats -Migrating a web ACL +Migrating a protection pack or web ACL