Skip to content

Disabling Cloudwatch

0

I enabled CloudWatch a few months ago to track how often a certain file in S3 is being accessed (100-200 times per day on average).

For whatever reason, CloudWatch has installed 139 metrics across all my AWS services and is charging me $4 a month.

I can't figure out how to disable all these other metrics, and I can't figure out what's actually incurring the costs in Cost Explorer. Even when I go into the individual services, like SES, I can't find the option to turn off metrics for that service.

I'm not a coder, so the CLI isn't really my bag, but I can copy/paste things into CloudShell. I'd rather pause all CloudWatch than spend another hour trying to figure this out!

screenshot

2 Answers
1

Hello,

AWS CloudWatch is in free tier if you use for Basic Monitoring Metrics (Metrics sent from AWS Services by default)

First of all, I would recommend reviewing your AWS bill for the CloudWatch service to review why you've been charged costs $4 for AWS Cloudwatch, also there is no way to disable AWS provided metrics in Cloudwatch, Also you're only charged for Custom Metrics not for AWS Provided Metrics.

Please find the link below for more details regarding pricing Model:

https://aws.amazon.com/cloudwatch/pricing/

EXPERT
answered 2 years ago
  • Thanks for your response.

    It's under the category: $0.30 per metric-month for the first 10,000 metrics - US East (Northern Virginia)

    Which, unfortunately, doesn't mean much to me. I'm well under 10,000 "hits" a month on the one thing I want to track.

    And it's not worth paying $40+ a year for because it doesn't change much, so I'd like to pause it and just turn it on for a few days a year as needed. If that isn't possible, I'd like to delete it. But I can't figure out how. I don't see "Custom Metrics" mentioned anywhere.

0

Hi, you are seeing a CloudWatch spend for metrics that you don't know how to identify. As indicated by Sivaraman, the default metrics are free, hence the spend you incur comes either from metrics you send yourself, or from additional opt-in metrics that you turn on in other services, such as EC2 detailed monitoring, or Lambda Insights. In your specific case, you're saying you turned on an option to monitor how often a certain file in S3 is being accessed, could that be the cause for the spend you're seeing? As indicated above, it is not a CloudWatch option, it is an S3 option. You can check a bucket extra metrics by opening the bucket in S3, clicking on the Metrics tab, choosing "View additional charts" below the bucket metrics, then open the Request metrics tab and check if you have any filters. Every filter will induce costs, so you can delete the filters you created but don't need to drive down your CloudWatch costs.

AWS
answered 2 years ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.