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.
Migrating AWS WAF Classic Web ACLs in Firewall Manager
There are two scenarios where Firewall Manager might use AWS WAF Classic WebACLs:
-
With a AWS WAF Classic policy
-
With a Shield Advanced policy created before January 2022
Migrating Web ACLs in AWS WAF Classic Policies
To migrate web ACLs from a AWS WAF Classic policy, you must first migrate any AWS WAF Classic rule groups to AWS WAF (v2) rule groups. Then you can create a new policy using the migrated rule groups.
-
Migrate your AWS WAF Classic rule groups to AWS WAF (v2) rule groups using this migration script: AWS WAF bulk migration script
. -
Create a new AWS WAF policy with the following settings:
-
Use the newly migrated AWS WAF (v2) rule groups
-
Enable automatic remediation
-
-
For each account you want to migrate:
-
Remove the account from the old AWS WAF Classic policy
-
Wait approximately 2-3 minutes
-
Add the account to the scope of the new AWS WAF policy
-
(Optional) Use resource tag filtering to narrow the policy scope to specific resources
-
-
Verify the migration:
-
Confirm that the new AWS WAF policy has created v2 web ACLs
-
Verify that Firewall Manager has associated the new web ACLs with the appropriate resources
-
Migrating Web ACLs in Shield Advanced Policies
Automatic application layer DDoS mitigation in Firewall Manager works only with web ACLs that were created using AWS WAF (v2). If you want to use automatic mitigation in your Firewall Manager policies, and your policies currently use AWS WAF Classic web ACLs, you must migrate them to AWS WAF (v2). You can either migrate all web ACLs at once or migrate them one account at a time.
Migrating All Web ACLs at Once
To migrate all web ACLs in your Shield Advanced policy at once, you can use the policy's automatic remediation feature:
-
Open the Firewall Manager console at https://console.aws.amazon.com/wafv2/fms
. -
Choose your Shield Advanced policy.
-
Enable automatic remediation and choose the option to replace AWS WAF Classic web ACLs with AWS WAF (v2) web ACLs.
Firewall Manager creates new AWS WAF (v2) web ACLs as needed and manages the migration of resource associations from Classic to v2 web ACLs.
Migrating Web ACLs One Account at a Time
To migrate web ACLs one account at a time, follow these steps:
-
Create a new Shield Advanced policy with the following settings:
-
Set automatic application layer DDoS mitigation to Disabled
-
Enable automatic remediation
-
-
For each account you want to migrate:
-
Remove the account from the old Shield Advanced policy
-
Wait approximately 2-3 minutes
-
Add the account to the scope of the new Shield Advanced policy
-
(Optional) Use resource tag filtering to narrow the policy scope to specific resources
-
-
Verify the migration:
-
Confirm that the new Shield Advanced policy has created AWS WAF (v2) web ACLs
-
Verify that Firewall Manager has associated the new web ACLs with the appropriate resources
-