How we handle GDPR data-subject requests on a deadline
Legal
The cloud-cost anomaly agent we run on Kortix — connected to AWS Cost Explorer and Slack. Every day it keeps a running spend baseline per service and account, flags whatever breaks out of that baseline, attributes the likely driver, and alerts with the delta. Read-only and alert-only; it never touches a resource or a budget.
Cloud bills surprise people because nobody is watching spend as it accrues. Cost Explorer shows the truth eventually, but by default a spike surfaces at the end of the month, in the invoice, long after the resource that caused it has been running for weeks. A new instance type left on overnight, a service that started scaling past its usual ceiling, a region nobody meant to deploy to — each one is a small decision that turns into a line item nobody recognizes.
We run a cloud-cost anomaly agent on Kortix that watches AWS spend every day, one persistent session that remembers what "normal" looks like per service and per account. It only reads billing data; the single output is a Slack alert with the delta and its best guess at what caused it. This is how we catch a cost problem while it's still one day old, not one invoice old.
Cloud spend is easy to see and hard to watch. Cost Explorer will answer "how much did we spend" for any window you ask about, but it won't tell you, unprompted, that yesterday's spend on one service was 40% above its normal range. Nobody opens the console every morning to eyeball forty line items across a dozen accounts, so a spike sits there accruing until someone notices the invoice.
The common approaches don't close the gap. A monthly budget alert fires only after the month's total crosses a threshold, by which point the overspend has already happened many times over. A flat per-service alert threshold treats a service that normally costs $50/day the same as one that normally costs $5,000/day, so it's either too noisy or too blind. And none of it tells you why — a dashboard shows the number moved, not what moved it.
On Kortix, a daily cron re-prompts one persistent agent session with read-only access to AWS Cost Explorer. It pulls the prior day's spend broken out by service and by linked account, updates its running baseline for each, and flags anything that breaks out of its own normal range — not a flat threshold, but a deviation from what that specific service in that specific account usually costs. For each anomaly it works out the likely driver — a newly launched resource, a traffic surge, a region the spend wasn't previously in — and posts one alert to Slack with the delta and the suspected cause. It writes nothing back to AWS: no resource is touched, no budget is changed.
Open your Kortix workspace, start a new session, paste this prompt and send it. The agent writes the agent file, the cost-anomaly-detection skill and the daily trigger, and opens a change request for you to review. Prefer clicks? Choose Use this template instead.
Set up a daily cloud-cost anomaly agent in this workspace.
Create the agent agents/cloud-cost-anomaly.md. Its job is to compare each day's AWS spend with its baseline and alert on anomalies. It may use the AWS and Slack connectors. It only reads AWS.
Create the skill skills/cost-anomaly-detection/SKILL.md with these rules:
Add a cron trigger daily-cost-anomaly-scan to kortix.yaml. It runs the cloud-cost-anomaly agent every day at 07:00 UTC with the prompt "Load the cost-anomaly-detection skill and run today's cloud-cost anomaly sweep."
Tell me which of these connectors are not connected yet.
Open a change request with all of it. Do not merge it.
Open Connectors in your workspace and connect AWS with read-only access to Cost Explorer, and Slack. Credentials are brokered server-side and never enter the agent's machine.
Reads daily spend by service and account from Cost Explorer.
Posts each anomaly with its suspected driver.
Merge the change request, then start a session with the cloud-cost-anomaly agent and send this prompt. The first run builds the baseline, so check it before you let the schedule take over.
Run one cloud-cost anomaly sweep on AWS. Read only.
The change request added this trigger to kortix.yaml. From now on the agent
runs every day at 07:00 UTC and picks up from its ledger in memory/. To change the time, edit the cron line, or open
Triggers in the workspace.
triggers:- slug: daily-cost-anomaly-scan name: Daily cloud-cost anomaly scan on: cron: "0 0 7 * * *" run: agent: cloud-cost-anomaly prompt: Load the cost-anomaly-detection skill and run today's cloud-cost anomaly sweep.The AWS connector is read-only. The agent never launches, resizes, stops or deletes a resource, and never changes a budget. It posts the delta and the suspected driver, and an engineer decides what to do.
A run with an anomaly ends with one message in the channel. This is what a run looks like in the session:
Found 1 anomaly. EC2 spend in one linked account is up $412 (62%) over its baseline, and 6 new instances appeared in a region with no prior spend. The likely driver is a new deployment in that region, not a traffic surge.
Once it works, paste any of these into the same session.
When I tell you a spike is planned, add it to the known patterns in the ledger with an end date, and stop alerting on it until then.
Every Monday, post the 5 services with the largest week-over-week spend change to #cloud-costs.
For each anomaly, read the owner tag on the resources behind it and mention that team in the alert.
The agent reads across every linked AWS account's billing data, so its access is scoped and strictly one-directional:
A cost problem that used to surface as a surprising line item at the end of the month now surfaces the next morning, with the service, the account, the size of the spike, and a suspected cause already attached. The agent only reads and alerts; the engineering team decides what to do about each one.