Sitemap

AWS in Plain English

New AWS, Cloud, and DevOps content every day. Follow to join our 3.5M+ monthly readers.

Hidden API Charges that can Increase your CloudWatch Bill by 50%

6 min readMay 19, 2025
Press enter or click to view image in full size
Photo by Markus Winkler on Unsplash

Note : All non-members can read my story here. From my featured story on last week, I could see I gained many non-member followers as well which is why I have included these free links on all of my stories now, so feel free to check it out if you were unable to read them completely before.

This will be the last part of CloudWatch Cost Optimisation series. I hope you have benefited from reading previous articles so far.

If you still haven’t read them yet, I am attaching the links for you in the end!

Introduction

In this article, we explore the remaining hidden factor that contribute to most of the billing in CloudWatch.

Yes, unlike other factors, these API calls do not appear anywhere in CloudWatch console as resources. These are APIs that are made in the backend by respective sources which have permission to do so.

Below are the main CloudWatch APIs which incur charges :

  1. PutMetricData
  2. GetMetricData
  3. GetMetricStatistics
  4. GetDashboard, ListDashboards, PutDashboard and DeleteDashboards

There are few additional APIs such as GetInsightRuleReport, GetMetricWidgetImage, ListMetrics

Create an account to read the full story.

The author made this story available to Medium members only.
If you’re new to Medium, create a new account to read this story on us.

Or, continue in mobile web
Already have an account? Sign in
AWS in Plain English

Published in AWS in Plain English

New AWS, Cloud, and DevOps content every day. Follow to join our 3.5M+ monthly readers.

AWSomeSolutions

Written by AWSomeSolutions

I am a Cloud Engineer and I write about AWS services mostly about ELB, AutoScaling, CloudWatch and EventBridge. I aim to publish quality content over quantity.

Responses (1)

Write a response

Hi AwesomeSolutions!

Nice article, can I use it for my newsletter edition next week? It's called the cloud Economist and I share newsletter posts on saving costs with AWS. I would love to use this article, and give you credit of course.
Let me know if that's fine with you?

5