How do I get AWS cost spike alerts in Slack?

Quick answer: Two ways. With AWS alone you wire Cost Anomaly Detection to an SNS topic, then to Slack through Amazon Q Developer. It runs about three times a day, on data that is 12 to 48 hours old. With watchmy.cloud you connect AWS read-only, pick a Slack channel, and we check your spend every hour. Catching single hours needs hourly granularity in Cost Explorer. AWS charges about a cent per resource per day for it.

Cost problems get fixed fast when the alert lands where the engineers are. If your team lives in Slack, an alert sitting in a billing console does nothing.

Why put cost alerts in Slack at all?

Because the person who can fix a spike is an engineer. They roll back the deploy. They kill the runaway job. They delete the environment nobody turned off. And they do not open Cost Explorer on a Tuesday.

An alert in the team channel turns a month-end surprise into a same-day fix. It leaves a record too: the spike, the cause, the fix, one thread.

An email in a busy inbox is not the same thing. A spike is a to-do, not a newsletter.

How do you do it with AWS alone?

AWS has the parts. You assemble them.

1. Create a Cost Anomaly Detection monitor in Cost Management.

2. Create an alert subscription. Choose individual alerts, not a daily summary.

3. Create an SNS topic. Subscribe to it. Confirm the subscription.

4. Set up Amazon Q Developer in chat applications. Authorize Slack. Map the topic to a channel.

5. Set a dollar floor so small moves stay quiet.

6. Come back and re-tune that floor when normal drifts.

It works, and it comes with your AWS account. It is also three services and a wiring job. Nothing in it creates itself. Nothing updates itself.

How fast is that path?

Not fast. AWS says Cost Anomaly Detection runs about three times a day. It reads Cost Explorer, which runs 12 to 48 hours behind. So a spike can hide for a day, sometimes two.

A new monitor needs 24 hours before it detects anything. A service you just started using needs 10 days of history first.

That is fine for a slow drift. It is late for a runaway job.

What does watchmy.cloud do instead?

Connect AWS. Read-only billing access. No keys. No access to what you run. One CloudFormation template, about two minutes.

Send it where work happens. Slack for fast triage. Jira for follow-up. API when you want control.

Stop worrying about it. We watch AWS spend for you, so you don't have to keep checking it.

You pick the Slack channel on Slack's own consent screen. Two rules are already on: one for a day 30% above your own 7-day average, one for an hour at three times your 24-hour average. A single dial tunes both, from 1 (relaxed) to 5 (strict). After that it runs automagically.

We check your spend every hour and post the spike to your channel. The hour-level rule needs hourly granularity turned on in Cost Explorer. AWS bills that at about a cent per resource per day. Without it, you still get the daily checks.

What does the Slack alert say?

Enough to triage without opening anything else:

• which account it is

• the value that fired, next to the threshold it crossed

• how many dollars over it went

• the services behind it, like "Compute +$30.12 · Databases +$8.00"