įor regional applications, you can use any of the endpoints in the list. You can make calls using the endpoints listed in AWS Service Endpoints for AWS WAF. For detailed information about AWS WAF features and an overview of how to use AWS WAF, see the AWS WAF Developer Guide. This API guide is for developers who need detailed information about AWS WAF API actions, data types, and errors. You also can configure CloudFront to return a custom error page when a request is blocked. Based on conditions that you specify, such as the IP addresses that requests originate from or the values of query strings, the API Gateway REST API, CloudFront distribution, the Application Load Balancer, or the AWS AppSync GraphQL API responds to requests either with the requested content or with an HTTP 403 status code (Forbidden). AWS WAF also lets you control access to your content. ĪWS WAF is a web application firewall that lets you monitor the HTTP and HTTPS requests that are forwarded to Amazon CloudFront, an Amazon API Gateway REST API, an Application Load Balancer, or an AWS AppSync GraphQL API.

The AWS WAF Classic APIs have retained the prior names, endpoints, and namespaces.įor information, including how to migrate your AWS WAF resources to this version, see the AWS WAF Developer Guide. You can access your old rules, web ACLs, and other AWS WAF resources only through the AWS WAF Classic APIs.

If you used AWS WAF prior to this release, you can’t use this AWS WAFV2 API to access any AWS WAF resources that you created before. We recommend migrating your resources to this version, because it has a number of significant improvements. The names of the entities that you use to access this API, like endpoints and namespaces, all have the versioning information added, like “V2” or “v2”, to distinguish from the prior version. This is the latest version of the AWS WAF API, released in November, 2019.

Wafv2