AWS Cost Anomaly Detection

Connect AWS Cost Anomaly Detection to PostHog to sync your data into the PostHog data warehouse for analysis and modeling.

Sync the cost anomalies AWS detected on your account into the PostHog Data warehouse.

Create an IAM user or role with the ce:GetAnomalies, ce:GetAnomalyMonitors and ce:GetAnomalySubscriptions permissions, then paste its access key ID and secret access key. Add a session token too if you are using temporary credentials.

Cost Explorer has to be enabled once in the AWS console, and it can take up to 24 hours before data is ready. AWS keeps anomalies for 90 days, so that is as far back as a first sync reaches. You only see the monitors and subscriptions created by the account you connect, so connect the management (payer) account for organization-wide coverage.

Configuration

Option	Description
AWS access key ID Type: text Required: True
AWS secret access key Type: password Required: True
AWS session token Type: password Required: False	Only for temporary credentials. Session tokens expire after a few hours, so scheduled syncs will fail once the token expires. Use a permanent access key (starts with AKIA) for recurring imports.

Linking AWS Cost Anomaly Detection to PostHog

1. Go to the Data pipeline page in PostHog
2. Click New source and select AWS Cost Anomaly Detection
3. Fill in the required configuration fields
4. Click Next, select the tables you want to sync, and then press Import