Alert on Cloud Cost Spikes
Every morning, WebRun opens AWS Cost Explorer and checks each service's daily spend against your baseline, cross-references Datadog for any correlated usage spikes, and posts a Slack alert if any service's costs have jumped more than your configured threshold.
How can I automatically get alerted to unexpected cloud cost spikes?
WebRun monitors your AWS cloud spend every morning so cost spikes never catch you off guard. It opens AWS Cost Explorer, compares each service's daily spend against your baseline, cross-references Datadog for usage anomalies, and posts a Slack alert the moment any service exceeds your configured threshold.
- Cost spikes caught the same morning they happen
- No manual AWS console checks needed
- Correlated spend and usage data surfaced in one Slack message
Built for engineering managers · DevOps teams · FinOps practitioners · startup CTOs
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
console.aws.amazon.com/cost-managementin a real browser with your saved login - no setup, no API keys. -
1
AWS - read service-level daily spend
WebRun opens AWS to read service-level daily spend. - Open AWS Cost Explorer and set the granularity to Daily, grouped by Service
- Read yesterday's spend for each service and compare to the 7-day average
- Flag any service where yesterday's cost exceeded the average by more than your threshold (default 30%)
Done when Services with cost spikes are identified with their dollar amount and percentage increase.
-
2
Datadog - correlate spend with usage metrics
WebRun opens Datadog to correlate spend with usage metrics. - Open Datadog and check resource utilisation metrics (compute, data transfer, storage) for the flagged services
- Determine whether the spike correlates with a known traffic event or appears anomalous
Done when Each cost spike is labelled as traffic-correlated or anomalous.
-
3
Slack - alert on cost spikes
WebRun opens Slack to alert on cost spikes. - Post a cost-spike alert to #cloud-costs listing each flagged service, yesterday's spend, the average, and the classification
- Mark anomalous spikes in bold to separate them from expected growth
Done when The team has a ranked list of cost spikes with enough context to investigate.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Will it shut down services to control costs?
No - shutting down infrastructure is irreversible and must be a deliberate human decision. WebRun alerts you to the spike; you decide what to do.
How do I set the spike threshold?
You configure the percentage in the plan - 30% is the default but you can tighten or loosen it per service.
Does it cover all AWS services, or just compute?
It covers every service visible in AWS Cost Explorer - EC2, RDS, S3, data transfer, and more.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.