- Newest
- Most votes
- Most comments
Hi,
This could be because of the disassociation of the WEB-ACL. look into cloud trial logs for disassociate-web-acl api call.
https://docs.aws.amazon.com/cli/latest/reference/wafv2/disassociate-web-acl.html
Also, there are Restrictions on multiple association
You can associate a single web ACL with one or more AWS resources, according to the following restrictions: • You can associate each AWS resource with only one web ACL. The relationship between web ACL and AWS resources is one-to-many. • You can associate a web ACL with one or more CloudFront distributions. You cannot associate a web ACL that you have associated with a CloudFront distribution with any other AWS resource type.
https://docs.aws.amazon.com/waf/latest/developerguide/web-acl-associating-aws-resource.html
Relevant content
- asked 2 years ago
- Accepted Answerasked 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 10 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago
Where can I view the cloud trial log of the disassociate-web-acl api call.No exception log was found in WAF Overview and I just associate a single web ACL with multiple Application Load Balancers. So I still don't know the reason for this problem. Thank you for your answer