AWS Cost Anomaly Detection + Alert24

Stream events from AWS Cost Anomaly Detection into Alert24 to correlate changes with incidents and shorten time to resolution.

Start Free Trial See Pricing

Receive AWS cost anomaly and spending spike alerts via SNS/EventBridge.

Auto-detected payloads

Alert24 recognizes AWS Cost Anomaly Detection webhooks out of the box and maps fields to incidents automatically.

On-call routing & escalations

Page the right engineer over SMS, voice, push, email, or chat with policy-driven escalations.

Auto-updating status pages

Promote incidents to a public or private status page with one click and keep customers informed.

Change correlation & AI RCA

Recent deploys, infra updates, and feature flag flips surface alongside the incident for faster root cause.

Quick Setup

Copy Webhook URL

Go to your Alert24 dashboard and copy the webhook URL for AWS Cost Anomaly Detection.

Configure AWS Cost Anomaly Detection

Add the webhook URL in your AWS Cost Anomaly Detection settings.

Auto-Detected

Alert24 auto-detects AWS Cost Anomaly Detection payloads and maps them to incidents.

Step-by-Step Setup Instructions

AWS Cost Anomaly Detection Webhook Setup

1.In AWS Cost Explorer, go to Cost Anomaly Detection → Alert subscriptions

2.Create a new alert subscription or edit an existing one

3.In EventBridge, create a rule with source aws.ce and detail-type Anomaly Detected

4.Set the target to an SNS topic

5.Add an HTTPS subscription to the SNS topic using the webhook URL above

6.Confirm the subscription when you receive the confirmation request

Example Webhook Payload

This is a sample payload that AWS Cost Anomaly Detection sends to Alert24 when an alert fires.

{
  "version": "0",
  "source": "aws.ce",
  "detail-type": "Anomaly Detected",
  "detail": {
    "anomalyId": "arn:aws:ce:us-east-1:123456789012:anomaly/abcdef-1234-5678",
    "monitorName": "Production AWS Services",
    "monitorArn": "arn:aws:ce:us-east-1:123456789012:anomalymonitor/abcdef-1234",
    "anomalyScore": {
      "maxScore": 0.92,
      "currentScore": 0.87
    },
    "impact": {
      "maxImpact": 450,
      "totalImpact": 320.5,
      "totalActualSpend": 1520.5,
      "totalExpectedSpend": 1200
    },
    "rootCauses": [
      {
        "service": "Amazon EC2",
        "region": "us-east-1",
        "usageType": "BoxUsage:m5.xlarge"
      }
    ],
    "anomalyStartDate": "2024-01-14",
    "anomalyEndDate": "2024-01-15"
  }
}