What this module owns
A cloud bill is discovered rather than managed. Finance forwards the invoice, someone opens the cost console the week after, deletes the three most obvious things, and does not come back for a quarter. Nothing about that is difficult — it is perpetual, and perpetual work loses to whatever is currently on fire. What accumulates in the gap is boring and expensive: a volume that detached when its instance was terminated and has billed ever since, a gateway in a development network charging by the hour with nothing routed through it, a load balancer that outlived the service behind it, a storage tier full of data nobody has read in two years. None of it pages anyone, because paying too much is not an outage. Good looks like most spend attributable to a named owner, a spend jump traced to its cause within a day rather than on the next invoice, and a reversible action attached to every finding.The workflows inside it
This module contains 3 workflows.AWS spend analyzer
S3 optimization
Cost anomaly detection
Anomaly triage is the same investigation shape as an incident: a signal moved, something changed,
correlate the two, produce the evidence. Only the trigger and the evidence store differ.
What it needs connected
Enabling it
1
Open Modules → Overview
Cloud Cost appears in the Cost Optimization family with the three workflows it contains.
2
Turn it on
Enabling the module adds Cloud Cost to your sidebar, with its waste findings list.
3
Connect billing and set the autonomy you want
Point the ingest steps at your billing export, then decide which cleanups may run in scope and
which must become a ticket.
What you see when it runs
The module lists waste findings and anomalies together, each with the spend it explains, the evidence behind it, the recommendation and its projected savings, and whatever was done about it — an executed cleanup, an applied policy, or a ticket with an owner. Because every conclusion is a run, you can open any finding and read what the agent read: the billing lines, the resource state, and the reasoning that connected them.Next steps
Kubernetes Cost
The cluster layer of the same bill.
Observability Cost
Attribute and reduce spend in your monitoring stack.
Approvals
How a deletion waits for a human decision.