create_web_acl
¶
create_web_acl(
name: EntityName,
scope: Scope,
default_action: DefaultAction,
visibility_config: VisibilityConfig,
*,
config_overrides: Optional[WAFV2ClientConfig] = None,
description: Optional[EntityDescription] = None,
rules: Optional[Rules] = None,
data_protection_config: Optional[DataProtectionConfig] = None,
tags: Optional[TagList] = None,
custom_response_bodies: Optional[CustomResponseBodies] = None,
captcha_config: Optional[CaptchaConfig] = None,
challenge_config: Optional[ChallengeConfig] = None,
token_domains: Optional[TokenDomains] = None,
association_config: Optional[AssociationConfig] = None,
on_source_d_do_s_protection_config: Optional[OnSourceDDoSProtectionConfig] = None,
application_config: Optional[ApplicationConfig] = None,
monetization_config: Optional[MonetizationConfig] = None,
) -> CreateWebACLResponse
Creates a WebACL per the specifications provided.
A web ACL defines a collection of rules to use to inspect and control web requests. Each rule has a statement that defines what to look for in web requests and an action that WAF applies to requests that match the statement. In the web ACL, you assign a default action to take (allow, block) for any request that does not match any of the rules. The rules in a web ACL can be a combination of the types Rule, RuleGroup, and managed rule group. You can associate a web ACL with one or more Amazon Web Services resources to protect. The resource types include Amazon CloudFront distribution, Amazon API Gateway REST API, Application Load Balancer, AppSync GraphQL API, Amazon Cognito user pool, App Runner service, Amplify application, Amazon Web Services Verified Access instance, and Amazon Bedrock AgentCore Gateway.
Parameters:
-
name(EntityName) –The name of the web ACL. You cannot change the name of a web ACL after you create it.
-
scope(Scope) –Specifies whether this is for a global resource type, such as a Amazon CloudFront distribution. For an Amplify application, use
CLOUDFRONT.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.
-
-
default_action(DefaultAction) –The action to perform if none of the
Rulescontained in theWebACLmatch. -
description(Optional[EntityDescription], default:None) –A description of the web ACL that helps with identification.
-
rules(Optional[Rules], default:None) –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.
-
visibility_config(VisibilityConfig) –Defines and enables Amazon CloudWatch metrics and web request sample collection.
-
data_protection_config(Optional[DataProtectionConfig], default:None) –Specifies data protection to apply to the web request data for the web ACL. This is a web ACL level data protection option.
The data protection that you configure for the web ACL alters the data that's available for any other data collection activity, including your WAF logging destinations, web ACL request sampling, and Amazon Security Lake data collection and management. Your other option for data protection is in the logging configuration, which only affects logging.
-
tags(Optional[TagList], default:None) –An array of key:value pairs to associate with the resource.
-
custom_response_bodies(Optional[CustomResponseBodies], default:None) –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.
-
captcha_config(Optional[CaptchaConfig], default:None) –Specifies how WAF should handle
CAPTCHAevaluations for rules that don't have their ownCaptchaConfigsettings. If you don't specify this, WAF uses its default settings forCaptchaConfig. -
challenge_config(Optional[ChallengeConfig], default:None) –Specifies how WAF should handle challenge evaluations for rules that don't have their own
ChallengeConfigsettings. If you don't specify this, WAF uses its default settings forChallengeConfig. -
token_domains(Optional[TokenDomains], default:None) –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.auorco.ukas token domains. -
association_config(Optional[AssociationConfig], default:None) –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).
-
on_source_d_do_s_protection_config(Optional[OnSourceDDoSProtectionConfig], default:None) –Specifies the type of DDoS protection to apply to web request data for a web ACL. For most scenarios, it is recommended to use the default protection level,
ACTIVE_UNDER_DDOS. If a web ACL is associated with multiple Application Load Balancers, the changes you make to DDoS protection in that web ACL will apply to all associated Application Load Balancers. -
application_config(Optional[ApplicationConfig], default:None) –Configures the ability for the WAF console to store and retrieve application attributes during the web ACL creation process. Application attributes help WAF give recommendations for protection packs.
-
monetization_config(Optional[MonetizationConfig], default:None) –The monetization configuration for the web ACL. Provide this when any rule in the web ACL uses the
Monetizeaction.
Raises:
-
WAFConfigurationWarningException–The operation failed because you are inspecting the web request body, headers, or cookies without specifying how to handle oversize components. Rules that inspect the body must either provide an
OversizeHandlingconfiguration or they must be preceded by aSizeConstraintStatementthat blocks the body content from being too large. Rules that inspect the headers or cookies must provide anOversizeHandlingconfiguration.Provide the handling configuration and retry your operation.
Alternately, you can suppress this warning by adding the following tag to the resource that you provide to this operation:
Tag(key:WAF:OversizeFieldsHandlingConstraintOptOut, value:true). -
WAFDuplicateItemException–WAF couldn’t perform the operation because the resource that you tried to save is a duplicate of an existing one.
-
WAFExpiredManagedRuleGroupVersionException–The operation failed because the specified version for the managed rule group has expired. You can retrieve the available versions for the managed rule group by calling ListAvailableManagedRuleGroupVersions.
-
WAFInternalErrorException–Your request is valid, but WAF couldn’t perform the operation because of a system problem. Retry your request.
-
WAFInvalidOperationException–The operation isn't valid.
-
WAFInvalidParameterException–The operation failed because WAF didn't recognize a parameter in the request. For example:
-
You specified a parameter name or value that isn't valid.
-
Your nested statement isn't valid. You might have tried to nest a statement that can’t be nested.
-
You tried to update a
WebACLwith aDefaultActionthat isn't among the types available at DefaultAction. -
Your request references an ARN that is malformed, or corresponds to a resource with which a web ACL can't be associated.
-
-
WAFInvalidResourceException–WAF couldn’t perform the operation because the resource that you requested isn’t valid. Check the resource, and try again.
-
WAFLimitsExceededException–WAF couldn’t perform the operation because you exceeded your resource limit. For example, the maximum number of
WebACLobjects that you can create for an Amazon Web Services account. For more information, see WAF quotas in the WAF Developer Guide. -
WAFNonexistentItemException–WAF couldn’t perform the operation because your resource doesn't exist. If you've just created a resource that you're using in this operation, you might just need to wait a few minutes. It can take from a few seconds to a number of minutes for changes to propagate.
-
WAFOptimisticLockException–WAF couldn’t save your changes because you tried to update or delete a resource that has changed since you last retrieved it. Get the resource again, make any changes you need to make to the new copy, and retry your operation.
-
WAFSubscriptionNotFoundException–You tried to use a managed rule group that's available by subscription, but you aren't subscribed to it yet.
-
WAFTagOperationException–An error occurred during the tagging operation. Retry your request.
-
WAFTagOperationInternalErrorException–WAF couldn’t perform your tagging operation because of an internal error. Retry your request.
-
WAFUnavailableEntityException–WAF couldn’t retrieve a resource that you specified for this operation. If you've just created a resource that you're using in this operation, you might just need to wait a few minutes. It can take from a few seconds to a number of minutes for changes to propagate. Verify the resource specifications in your request parameters and then retry the operation.
-
UnknownServiceError–The service returned an error code this client does not model.
Source code in docs_src/capo_wafv2/_services/wafv2.py
707 708 709 710 711 712 713 714 715 716 717 718 719 720 721 722 723 724 725 726 727 728 729 730 731 732 733 734 735 736 737 738 739 740 741 742 743 744 745 746 747 748 749 750 751 752 753 754 755 756 757 758 759 760 761 762 763 764 765 766 767 768 769 770 771 772 773 774 775 776 777 778 779 780 781 782 783 784 785 786 787 788 789 790 791 792 793 794 795 796 797 798 799 800 801 802 803 804 805 806 807 808 809 810 811 812 813 814 815 816 817 818 819 820 821 822 823 824 825 826 827 828 829 830 831 832 833 834 835 836 837 838 839 840 | |