WAFv2 Regional Limitations - CloudFormation Regression

With Wafv1, we were able to create WAF and CloudFront resources in the same template if we were on a region other than us-east-1 (For example, us-west-2).

Now it is impossible to do this with WafV2 automatically without a Custom Resource, as WafV2 requires the ACL to be created in us-east-1 if it is a CloudFront ACL. If you have your entire stack in another region, now you either need to pass the WafV2's att.Arn as a parameter or you need to create a custom resource to look up the arn for you. This is more obtuse than the original WAF, and IMO will stymie the adoption of WafV2 as now I have no incentive to want to jump through hoops when I can just use Wafv1.

Please allow WafV2 to be a "Global WAF", like the wafv1, so that we can create the resource in the same template as the CloudFront/S3/CodeBuild resources that support an application.

Start by reviewing the issue's WAFv1 and WAFv2 behavior for CloudFront ACLs, including the us-east-1 restriction and the need for a parameter or custom resource in another region. Done means a WAFv2 CloudFront ACL can be declared with CloudFront and related resources in one non-us-east-1 CloudFormation template without those workarounds.

Written by the indexing model from the issue text.