- Newest
- Most votes
- Most comments
This is my approach to solve this problem.
Firstly, I checked again the Billing dashboard and then looked through the costs and resources. I tried to write down the name of each service that sends me a cost in the console home in the search box above.
I go through each service and based on the region mentioning in the Billing dashboard, I change my region.
There is also a new service added to AWS called Resource Search and based on what is written on its page, it should be free. You should activate (enable) it first and then choose the region you want to see all your resources in.
Therefore, I add this to my approach to see all the resources in each possible region that costs me money.
Specifically about my problem which is written in the question, it seems that costs can come from some parts of AWS that you have no idea of it. Although WAF is a global service, but when you go to WAF page and then Web ACL, you can see that, if no ACL is showing, there is also an option to change the region, and as soon as I change it to Global, it shows and ACL. Therefore, I tried to delete it. it was not possible because it was written that it is associated with CloudFront. So in the tap associations, I deassociated it, and then I could delete all the rules and the ACL itself.
This is how from I tried to solve my problem and I hope it works, since as it is written in Billing dashboard, it may take up to 24 hours that it refreshes the list of your active services.
I hope this method would help you as well for eliminating the costs.
as you can see from the following link
AWS WAF offers standalone pricing that is charged based on your usage of web ACLs, rules, and the number of requests that are inspected.
It's worth noting that AWS WAF costs are based on your usage of web ACLs, rules, and the number of requests that are inspected. For logging configurations, you will be charged based on your usage of Amazon Kinesis Data Firehose. Additionally, AWS Bot Control rulesets that are added to your web ACLs are charged a monthly fee, with an additional charge for the number of web requests processed by Bot Control. If you choose to use Managed rules for AWS Web Application Firewall, you can subscribe to managed rules and pay only for what you use. For high request volumes, AWS Shield Advanced might help reduce the per-request charges. Lastly, using scope-down statements to limit what rules get analyzed can help reduce costs.
Remember that some services, like AWS Shield Advanced, may include AWS WAF costs in their own, so if you're using such services, the costs might be associated with them and not directly with AWS WAF.
You might have had a rule under Global as the names suggest. Have you switched to Global from the WAF&Shield console?
Hi and thank you for your answer. Actually as I checked AWS WAF is a global service and I cannot switch to other regions while I'm in this console.
Relevant content
- asked a month ago
- Accepted Answerasked 7 months ago
AWS OFFICIALUpdated 4 months ago- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
Thank you very much dear Sedat for your answer. In the next comment, I will explain what approach I have made. Hopefully it will be solved by tomorrow.
Hello i have read your approach it seems quite well hope this solves your problem
Hello dear Sedat. I just wanted to write you back and give you my feedback about my observation. I'm glad to let you know that the approached worked and the costs stopped. It seems that these rules or some services can have hidden costs, like what I have experienced, and it's more complicated to find out the resource of it and even delete it. For me, Cost Explorer is also very helpful since I could check the costs day by day to check if it stopped or not. I wish you a happy weekend and success.