Creates a WebACL per the specifications provided.
See https://www.paws-r-sdk.com/docs/wafv2_create_web_acl/ for full documentation.
wafv2_create_web_acl(
Name,
Scope,
DefaultAction,
Description = NULL,
Rules = NULL,
VisibilityConfig,
Tags = NULL,
CustomResponseBodies = NULL,
CaptchaConfig = NULL,
ChallengeConfig = NULL,
TokenDomains = NULL,
AssociationConfig = NULL
)[required] The name of the web ACL. You cannot change the name of a web ACL after you create it.
[required] Specifies whether this is for an Amazon CloudFront distribution or for a regional application. 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.
To work with CloudFront, you must also specify the Region US East (N. Virginia) as follows:
CLI - Specify the Region when you use the CloudFront scope:
--scope=CLOUDFRONT --region=us-east-1.
API and SDKs - For all calls, use the Region endpoint us-east-1.
[required] The action to perform if none of the Rules contained in the WebACL
match.
A description of the web ACL that helps with identification.
The Rule statements used to identify the web requests that you want to manage. Each rule includes one top-level statement that WAF uses to identify matching web requests, and parameters that govern how WAF handles them.
[required] Defines and enables Amazon CloudWatch metrics and web request sample collection.
An array of key:value pairs to associate with the resource.
A map of custom response keys and content bodies. When you create a rule with a block action, you can send a custom response to the web request. You define these for the web ACL, and then use them in the rules and default actions that you define in the web ACL.
For information about customizing web requests and responses, see Customizing web requests and responses in WAF in the WAF Developer Guide.
For information about the limits on count and size for custom request and response settings, see WAF quotas in the WAF Developer Guide.
Specifies how WAF should handle CAPTCHA evaluations for rules that
don't have their own CaptchaConfig settings. If you don't specify
this, WAF uses its default settings for CaptchaConfig.
Specifies how WAF should handle challenge evaluations for rules that
don't have their own ChallengeConfig settings. If you don't specify
this, WAF uses its default settings for ChallengeConfig.
Specifies the domains that WAF should accept in a web request token. This enables the use of tokens across multiple protected websites. When WAF provides a token, it uses the domain of the Amazon Web Services resource that the web ACL is protecting. If you don't specify a list of token domains, WAF accepts tokens only for the domain of the protected resource. With a token domain list, WAF accepts the resource's host domain plus all domains in the token domain list, including their prefixed subdomains.
Example JSON:
"TokenDomains": { "mywebsite.com", "myotherwebsite.com" }
Public suffixes aren't allowed. For example, you can't use gov.au or
co.uk as token domains.
Specifies custom configurations for the associations between the web ACL and protected resources.
Use this to customize the maximum size of the request body that your protected resources forward to WAF for inspection. You can customize this setting for CloudFront, API Gateway, Amazon Cognito, App Runner, or Verified Access resources. The default setting is 16 KB (16,384 bytes).
You are charged additional fees when your protected resources forward body sizes that are larger than the default. For more information, see WAF Pricing.
For Application Load Balancer and AppSync, the limit is fixed at 8 KB (8,192 bytes).