Generally, any inconsistencies of this type last only a few seconds. This temporary inconsistency can occur when you first associate a web ACL with an AWS resource and when you change a web ACL that is already associated with a resource. Or if you add an IP address to an IP set used in a blocking rule, the new address might briefly be blocked in one area while still allowed in another. So, for example, if you change a rule action setting, the action might be the old action in one area and the new action in another area. Your changes are applied within seconds, but there might be a brief period of inconsistency when the changes have arrived in some places and not in others. When you create a web ACL or make changes to a web ACL or web ACL components, like rules and rule groups, AWS WAF propagates the changes everywhere that the web ACL and its components are stored and used. For information, see AWS::CloudFront::Distribution.

To disassociate a web ACL, provide an empty ARN. To associate a web ACL with a distribution, provide the Amazon Resource Name (ARN) of the AWS::WAFv2::WebACL to your CloudFront distribution configuration. Instead, use your CloudFront distribution configuration.

Use a web ACL association to define an association between a web ACL and a regional application resource, to protect the resource.Ī regional application can be an Application Load Balancer (ALB), an Amazon API Gateway REST API, an AWS AppSync GraphQL API,Īn Amazon Cognito user pool, or an AWS App Runner service.įor Amazon CloudFront, don't use this resource. For information, including how to migrate your AWS WAF resources from the prior release, see the AWS WAF Developer Guide. This is the latest version of AWS WAF, named AWS WAFV2, released in November, 2019.

Aws wafv2