Smaws_Client_WAFV2.AssociateWebACL
val request :
Smaws_Lib.Context.t ->
associate_web_acl_request ->
(associate_web_acl_response,
[> Smaws_Lib.Protocols.AwsJson.error
| `WAFInternalErrorException of waf_internal_error_exception
| `WAFInvalidOperationException of waf_invalid_operation_exception
| `WAFInvalidParameterException of waf_invalid_parameter_exception
| `WAFNonexistentItemException of waf_nonexistent_item_exception
| `WAFUnavailableEntityException of waf_unavailable_entity_exception ])
Stdlib.result
Associates a web ACL with a regional application resource, to protect the resource. 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, don't use this call. Instead, use your CloudFront distribution configuration. To associate a web ACL, in the CloudFront call UpdateDistribution
, set the web ACL ID to the Amazon Resource Name (ARN) of the web ACL. For information, see UpdateDistribution in the Amazon CloudFront Developer Guide.
Required permissions for customer-managed IAM policies
This call requires permissions that are specific to the protected resource type. For details, see Permissions for AssociateWebACL in the WAF Developer Guide.
Temporary inconsistencies during updates
When you create or change a web ACL or other WAF resources, the changes take a small amount of time to propagate to all areas where the resources are stored. The propagation time can be from a few seconds to a number of minutes.
The following are examples of the temporary inconsistencies that you might notice during change propagation: