- Newest
- Most votes
- Most comments
You're experiencing a common issue where AWS WAF charges appear even when you don't think you're using the service. This typically happens for a few reasons:
-
Web ACLs might exist in a region you haven't checked. Make sure to check the "Global" region specifically, as WAF resources associated with CloudFront are created there.
-
WAF Web ACLs can be created as part of other services without being immediately obvious. For example, if you set up CloudFront at any point, there might have been an option to create a WAF that was enabled.
-
You pay for AWS WAF Web ACLs even if no resources are associated with them. There's a monthly fee for each web ACL regardless of whether they're actively protecting resources.
To resolve this issue:
-
Check the WAF console specifically in the "Global" region, as this is where CloudFront-associated WAF resources appear.
-
If you find any Web ACLs, delete them following AWS documentation for deleting Web ACLs.
-
Review if you've set up CloudFront in the past, as WAF might have been enabled during that setup.
-
If you still can't locate the source of the charges, consider contacting AWS Support as they have tools to investigate account-specific billing information.
Remember that even after deleting resources, there might be a short delay before charges stop appearing in your billing.
Sources
Being Charged for AWS WAF even though not using this | AWS re:Post
How to stop WAF cost bills | AWS re:Post
Unexpected WAF Charges Inquiry | AWS re:Post
Do you pay for WAF Web ACL, even if no resource associated? | AWS re:Post
answered a year ago
Relevant content
asked 3 years ago
asked a year ago
- AWS OFFICIALUpdated a year ago

Ah, I DO have a "CreatedByCloudfront" Web ACL now that I checked the "Global" region! I'll have to investigate that