Deciphering AWS Billing: Understanding Charges for Amazon Managed Service for Prometheus

Question

I recently discovered unexpected charges on my AWS bill related to Amazon Managed Service for Prometheus. Despite my belief that I had successfully deleted all service and workspaces (I wanted to try a few things with K8s), I've been charged daily every since I started working (about a month ago). However, when I navigate to the Prometheus site using my root accoutn, there is no workspace available for removal. Where might these charges be originating from? Any insights or guidance would be greatly appreciated.

Accepted Answer

Hello.

Could you please share an image of the invoice?  
As shown in the image below, you need to check which AWS service features are causing charges.  
https://docs.aws.amazon.com/awsaccountbilling/latest/aboutv2/getting-viewing-bill.html  
![a](/media/postImages/original/IMmHu_nUSyTsKFFPoVrHiQ0g)

In my experience, even if you don't have a workspace, you may be charged a fee if the scraper is running.  
So, please check if there are any scrapers left using the command below.  
If it remains, try deleting it with "delete-scraper".  
https://aws.amazon.com/prometheus/pricing/?nc1=h_ls  
https://docs.aws.amazon.com/prometheus/latest/userguide/AMP-collector-how-to.html#AMP-collector-list-delete  
```
aws amp list-scrapers
aws amp delete-scraper --scraper-id scraperId
```

Answer

Thank you for your helpful insight. I oversaw the bill option while looking at my billing dashboard.
Here is the screenshot:  
![Enter image description here](/media/postImages/original/IM-WcQY9-jQHKcDhtriBrUBg)
The charges are because of collector hours. What does that mean? Does it refer to the scrapers?

I also followed your advice regarding the scrapers, and found out that there was still one lurking in the shadows. I deleted it successfully! Interestingly enough, it even survived the aws-nuke command :)

I'll let you know if by deleting the scraper the suspicious charges will disappear.

Answer

I think that was it. Thank you very much!
If anyone is interested, deleting the scraper probably solved my problem. However, I have to say that I also ran aws-nuke just before that. So I think the combination of the two solved my problem.

Deciphering AWS Billing: Understanding Charges for Amazon Managed Service for Prometheus

Relevant content