1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
|
// Code generated by smithy-go-codegen DO NOT EDIT.
// Package wafv2 provides the API client, operations, and parameter types for AWS
// WAFV2.
//
// # WAF
//
// This is the latest version of the WAF API, released in November, 2019. 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. We recommend migrating your resources to
// this version, because it has a number of significant improvements.
//
// If you used WAF prior to this release, you can't use this WAFV2 API to access
// any WAF resources that you created before. You can access your old rules, web
// ACLs, and other WAF resources only through the WAF Classic APIs. The WAF Classic
// APIs have retained the prior names, endpoints, and namespaces.
//
// For information, including how to migrate your WAF resources to this version,
// see the [WAF Developer Guide].
//
// WAF is a web application firewall that lets you monitor the HTTP and HTTPS
// requests that are forwarded to an Amazon CloudFront distribution, Amazon API
// Gateway REST API, Application Load Balancer, AppSync GraphQL API, Amazon Cognito
// user pool, App Runner service, or Amazon Web Services Verified Access instance.
// WAF also lets you control access to your content, to protect the Amazon Web
// Services resource that WAF is monitoring. Based on conditions that you specify,
// such as the IP addresses that requests originate from or the values of query
// strings, the protected resource responds to requests with either the requested
// content, an HTTP 403 status code (Forbidden), or with a custom response.
//
// This API guide is for developers who need detailed information about WAF API
// actions, data types, and errors. For detailed information about WAF features and
// guidance for configuring and using WAF, see the [WAF Developer Guide].
//
// You can make calls using the endpoints listed in [WAF endpoints and quotas].
//
// - For regional applications, you can use any of the endpoints in the list. A
// regional application can be an Application Load Balancer (ALB), an Amazon API
// Gateway REST API, an AppSync GraphQL API, an Amazon Cognito user pool, an App
// Runner service, or an Amazon Web Services Verified Access instance.
//
// - For Amazon CloudFront applications, you must use the API endpoint listed
// for US East (N. Virginia): us-east-1.
//
// Alternatively, you can use one of the Amazon Web Services SDKs to access an API
// that's tailored to the programming language or platform that you're using. For
// more information, see [Amazon Web Services SDKs].
//
// We currently provide two versions of the WAF API: this API and the prior
// versions, the classic WAF APIs. This new API provides the same functionality as
// the older versions, with the following major improvements:
//
// - You use one API for both global and regional applications. Where you need
// to distinguish the scope, you specify a Scope parameter and set it to
// CLOUDFRONT or REGIONAL .
//
// - You can define a web ACL or rule group with a single call, and update it
// with a single call. You define all rule specifications in JSON format, and pass
// them to your rule group or web ACL calls.
//
// - The limits WAF places on the use of rules more closely reflects the cost of
// running each type of rule. Rule groups include capacity settings, so you know
// the maximum cost of a rule group when you use it.
//
// [WAF endpoints and quotas]: https://docs.aws.amazon.com/general/latest/gr/waf.html
// [Amazon Web Services SDKs]: http://aws.amazon.com/tools/#SDKs
// [WAF Developer Guide]: https://docs.aws.amazon.com/waf/latest/developerguide/what-is-aws-waf.html
package wafv2
|
