AWS waf documentation change
Summary
Updated documentation to include 'protection pack' terminology alongside web ACL references, added guidance for new console experience, and modified migration steps
Security assessment
Changes primarily involve terminology updates (adding 'protection pack'), console experience references, and procedural adjustments. No specific security vulnerabilities or security feature enhancements are mentioned. The modifications focus on migration procedures and UI updates rather than security controls.
Diff
diff --git a/waf/latest/developerguide/waf-migrating-procedure-switchover.md b/waf/latest/developerguide/waf-migrating-procedure-switchover.md index 67fe33537..d417d52c4 100644 --- a//waf/latest/developerguide/waf-migrating-procedure-switchover.md +++ b//waf/latest/developerguide/waf-migrating-procedure-switchover.md @@ -5 +5 @@ -# Migrating a web ACL: switchover +**Introducing a new console experience for AWS WAF** @@ -7 +7 @@ -After you've verified your new web ACL settings, you can start to use it in place of your AWS WAF Classic web ACL. +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). @@ -9 +9 @@ After you've verified your new web ACL settings, you can start to use it in plac -###### To begin using your new AWS WAF web ACL +# Migrating a protection pack or web ACL: switchover @@ -11 +11 @@ After you've verified your new web ACL settings, you can start to use it in plac - 1. Associate the AWS WAF web ACL with the resources that you want to protect, following the guidance at [Associating or disassociating a web ACL with an AWS resource](./web-acl-associating-aws-resource.html). This automatically disassociates the resources from the old web ACL. +After you've verified your new protection pack or web ACL settings, you can start to use it in place of your AWS WAF Classic protection pack or web ACL. @@ -13 +13 @@ After you've verified your new web ACL settings, you can start to use it in plac -The switch can take from a few seconds to a number of minutes to propagate. During this time, some requests might be processed by the old web ACL and others by the new web ACL. Your resources will be protected throughout the switch, but you might notice inconsistencies in request handling until it's complete. +###### To begin using your new AWS WAF protection pack or web ACL @@ -15 +15 @@ The switch can take from a few seconds to a number of minutes to propagate. Duri - 2. Configure logging for the new web ACL, following the guidance at [Logging AWS WAF web ACL traffic](./logging.html). + 1. Associate the AWS WAF protection pack or web ACL with the resources that you want to protect, following the guidance at [Associating or disassociating protection with an AWS resource](./web-acl-associating-aws-resource.html). This automatically disassociates the resources from the old protection pack or web ACL. @@ -17 +17,5 @@ The switch can take from a few seconds to a number of minutes to propagate. Duri - 3. (Optional) If your AWS WAF Classic web ACL is no longer associated with any resources, consider removing it entirely from AWS WAF Classic. For information, see [Deleting a Web ACL](./classic-web-acl-deleting.html). +The switch can take from a few seconds to a number of minutes to propagate. During this time, some requests might be processed by the old protection pack or web ACL and others by the new protection pack or web ACL. Your resources will be protected throughout the switch, but you might notice inconsistencies in request handling until it's complete. + + 2. Configure logging for the new protection pack or web ACL, following the guidance at [Logging AWS WAF protection pack or web ACL traffic](./logging.html). + + 3. (Optional) If your AWS WAF Classic protection pack or web ACL is no longer associated with any resources, consider removing it entirely from AWS WAF Classic. For information, see [Deleting a Web ACL](./classic-web-acl-deleting.html).