Closed omar-dulaimi closed 4 years ago
You can't use the same template to update the solution from WAF classic to WAFv2. You will need to deploy the WAF 3.0 solution as a new solution to switch to WAFv2. The new solution will deploy the resources in WAFv2.
@aijunpeng What about the IPSets that I've created? will I be able to reuse them?
Also, the v2 template, is it customizeable through the console? And I read that supports more logical operations in conditions besides the old AND in v1?
If you create your own IPSets in AWS WAF classic you will need to create them again in WAFv2 because WAF classic and WAFv2 services are not compatible with each other and they don't share IPSets. Can you clarify what you mean by "the v2 template, is it customizeable through the console?" ? If you are asking that if rules are customizable at solution deployment, the answer is no. You can customize rules through the WAF service console after deploying the solution
Yeah that's what I meant. Thank you for explaining.
Hello, What is the proper way to migrate our current AWS WAF classic to the latest AWS WAFv2 using this same template, since we used it in the past.
We don't want to break any lambda handlers, etc.
Is there a guide we can follow, since I read somewhere that we should wait until the template is updated.