Home > Back-end >  Diagnosing Root Cause of Increasing AWS Cloudwatch Costs
Diagnosing Root Cause of Increasing AWS Cloudwatch Costs

Time:08-27

Over the past few months our Cloudwatch costs have steadily risen. This seems to be caused by metric updates. RUM was enabled for a short time but has been disabled for about 2 months now. This is not a high traffic account only currently being used for development by a single person. Help troubleshooting this would be appreciated.

May May

June June

July July

August Current August Current

CodePudding user response:

Metric updates operation is related to CloudWatch Metric Streams on console

And then you can delete it, stop it or re-configure it to limit the ingestion to a specific metric namespace

CloudWatch Metric Streams example

  • Related