COMPARE

Which tools alert on an AWS cost spike within hours?

Last reviewed:

Quick answer: Five tools read your AWS bill and alert on it: AWS Budgets, AWS Cost Anomaly Detection, Vantage, CloudZero and watchmy.cloud. The bill lags usage by 12 to 48 hours, so "hours" means hours after the data lands. Three read usage instead, faster but narrower: CloudWatch, Datadog Real-Time Costs and DoiT.

If you run a small team on AWS and want to know about a runaway job before the invoice, this is the list. Eight options, what each one reads, how long it takes, what it costs. No scores. Pick by the question you need answered.

Why can't anything alert "in real time"?

Because AWS does not tell anyone the bill in real time. Cost Explorer, the billing data every cost tool reads, runs 12 to 48 hours behind usage. A tool that reads the bill cannot beat that. It can only be fast once the data is there.

There is a second path. Instead of reading dollars, read usage: instance hours, API calls, CloudTrail events. That is close to real time, but you have to know the price of each thing and the tool has to cover each service. Today those tools cover a handful of services, mostly EC2.

So every tool below sits in one of two camps. Reads the bill, so it is complete but late. Reads usage, so it is fast but partial.

What are the eight options?

AWS Budgets. Built in. You set a dollar line for the month. When spend crosses it, you get an email or an SNS message. Budgets update up to three times a day, 8 to 12 hours apart, on Cost Explorer data. It never fires on a spike that stays under your line. The first two budgets with actions are included; after that each one costs $0.10 a day.

AWS Cost Anomaly Detection. Built in. It learns a pattern per service and flags a day that breaks it. AWS says detection can take up to 24 hours after usage, and a new service needs 10 days of history first. Alerts go to email or SNS. Slack takes a third service, Amazon Q Developer in chat applications. No charge.

CloudWatch billing alarm. Built in, and the oldest. AWS publishes an EstimatedCharges metric in one region, us-east-1, several times a day. You alarm on the month's total. It is a backstop, not a detector: it fires once, at the end, and says nothing about which service moved.

watchmy.cloud. A spike-alert service. It reads hourly Cost Explorer data through a read-only role and checks every hour. Two rules from the first minute: a day 30% above your own 7-day average, and an hour at three times its normal cost. The alert lands about an hour after the spike shows up in the data, in Slack, Jira, GitHub Issues, email, SMS or a webhook. A flat $49 a month, 30-day trial, no card.

Vantage. A FinOps platform. Reports, virtual tags, unit costs, Kubernetes, 30+ providers. It has anomaly detection and custom cost alerts on billing data. Vantage does not publish how often it refreshes that data, so we do not guess. Starter is free up to $2,500 of cloud spend, Pro is $30 a month up to $7,500, Business is $200 a month.

CloudZero. A cost-intelligence platform. Its anomaly detection runs on billing data at hourly granularity, with thresholds that follow your trailing 30-day spend, and it sends one notification per anomaly. The ingestion cadence is not published. Pricing is by quote.

Datadog Cloud Cost Management. Two layers. Cost anomalies on daily billing data, on by default, with a $5-a-day floor. And Real-Time Costs: EC2 estimates updated every five minutes, built from the Datadog Agent on each instance. Real time covers EC2 only, not EBS or networking, and only on the Enterprise tier. Pro is $5 per $1,000 of cloud spend a month billed annually, $7.20 on demand.

DoiT Cloud Intelligence. Billing-based anomalies on data that refreshes every 24 hours. Plus near real-time detection from CloudTrail events, for EC2 and RDS, on the Enhanced and Enterprise plans. It needs CloudTrail logs in an S3 bucket in one of five regions. Pricing is not public.

How do the eight compare?

Tool

Reads

How fast after the spike

Covers

Cost

Best for

AWS Budgets

The bill

Same day or next; up to 3 checks a day

All services, one total

Free; action budgets $0.10 a day after two

A monthly ceiling

AWS Cost Anomaly Detection

The bill

Up to 24 hours after usage, per AWS

All services, daily grain

Free

A free pattern check

CloudWatch billing alarm

Estimated charges

Several times a day, month total only

One number

Free tier covers it

A backstop

watchmy.cloud

The bill, hourly

About 1 hour after the data lands

All services, hourly grain

$49 a month flat

Spike alerts in Slack or Jira

Vantage

The bill

Not published

All services

Free to $2,500 spend; $30 and $200 a month

Where the money goes

CloudZero

The bill, hourly grain

Not published

All services

By quote

Cost intelligence at scale

Datadog CCM

The bill; EC2 usage in real time

Daily anomalies; EC2 every 5 minutes on Enterprise

All services daily; EC2 only in real time

$5 per $1,000 spend a month

Teams already on Datadog

DoiT

The bill; CloudTrail in real time

Daily; EC2 and RDS in near real time on paid plans

All services daily; EC2 and RDS in real time

Not public

DoiT customers

"Not published" means the vendor does not state it. It does not mean slow.

Which one should a small team pick?

Start with what you already have. Turn on AWS Budgets and Cost Anomaly Detection. They are free and they catch the slow, big things.

Then ask what you are missing. If it is "a job ran wild on Tuesday and I heard on Thursday", you need hourly grain on the bill, and a channel your team reads. That is what watchmy.cloud does, and only that. If it is "I cannot tell which team spent what", you need a platform: Vantage or CloudZero. If your fleet is EC2 and you already run the Datadog Agent, Real-Time Costs gets you to minutes for that one service.

Two tools is normal. One for the ceiling, one for the spike.

How does watchmy.cloud help here?

We sit in the first camp. We read the bill, hourly, and alert about an hour after a spike shows up in it. We do not do reports, tags or Kubernetes. One flat fee for every AWS account you connect and every channel. Read-only role, two minutes to connect, 30-day trial, no card.

FAQ

What is the fastest way to get an AWS cost spike alert? For EC2 only, a usage-based tool: Datadog Real-Time Costs or DoiT's CloudTrail detection, both on paid tiers. For every service, a tool that reads hourly Cost Explorer data and checks hourly. The alert then lands about an hour after the data does, and the data lags usage by 12 to 48 hours.

Is AWS Cost Anomaly Detection fast enough? For a spike that lasts days, yes. AWS says detection can take up to 24 hours after usage, and it runs about three times a day on daily data. A job that runs wild for six hours overnight can be over before it is flagged.

Do I need a FinOps platform to get spike alerts? No. Vantage, CloudZero and Datadog include anomaly alerts, but you pay for the platform. If alerts are the only thing you need, a single-purpose tool or the free AWS services do it.

Why does every tool say "hours" and not "minutes"? Because Cost Explorer, the source of the bill, runs 12 to 48 hours behind. Only tools that read usage directly can reach minutes, and today they cover a few services, mostly EC2.

Can I use two of these at once? Yes, and most teams should. AWS Budgets for the monthly ceiling, one spike tool for the hourly jump. They do not overlap.

Which of these needs an agent in my account? Datadog Real-Time Costs needs the Datadog Agent on each EC2 instance. DoiT real time needs CloudTrail logs in S3. The rest read the bill through a read-only role and install nothing.

watchmy.cloud
A smoke detector for your AWS bill. Built by engineers who got tired of cost surprises.

watchmy.cloud
A smoke detector for your AWS bill. Built by engineers who got tired of cost surprises.

watchmy.cloud
A smoke detector for your AWS bill. Built by engineers who got tired of cost surprises.