> ## Documentation Index
> Fetch the complete documentation index at: https://docs.komodor.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Cloud Cost

> Track cloud vendor spend, catch the anomaly the week it happens, and convert waste into remediation actions with an owner attached.

Cloud Cost owns your cloud vendor bill: what it is made of, why it moved, and what to do
about the parts that buy nothing. It breaks spend down by service, account, and tag, detects spend
anomalies as new billing data arrives, and turns findings into remediation you approve. This page covers the outcome the
module owns, the three workflows inside it, and what it needs connected.

## 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

| Step                    | What happens                                                                                                                                                    |
| ----------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **1 · CUR ingest**      | Pulls the AWS Cost & Usage Report.                                                                                                                              |
| **2 · Spend breakdown** | Attributes spend by service, account, and tag, and identifies the top movers.                                                                                   |
| **3 · Recommendation**  | Proposes right-sizing or commitment coverage with projected savings — commitment advice where the baseline is steady, right-sizing where the workload is spiky. |
| **4 · Act**             | Executes reversible cleanup within scope, and opens a remediation ticket for anything customer-facing.                                                          |

### S3 optimization

| Step                        | What happens                                                                                               |
| --------------------------- | ---------------------------------------------------------------------------------------------------------- |
| **1 · Bucket scan**         | Inventories buckets, sizes, storage classes, and access patterns.                                          |
| **2 · Cold data detection** | Flags cold, idle, or unused data with a waste estimate.                                                    |
| **3 · Recommendation**      | Proposes lifecycle rules or storage-class transitions.                                                     |
| **4 · Apply**               | Applies the policy within autonomy scope — approve-then-run for anything that deletes or transitions data. |

### Cost anomaly detection

| Step                      | What happens                                                                                                  |
| ------------------------- | ------------------------------------------------------------------------------------------------------------- |
| **1 · Billing ingest**    | Pulls daily cost and usage across vendors.                                                                    |
| **2 · Anomaly detection** | Detects statistically significant spend spikes and rates their severity.                                      |
| **3 · Triage**            | Attributes the anomaly to a service, team, or change, and names an owner where it can.                        |
| **4 · Recommend / alert** | Alerts the owner and proposes containment — alert-only for an expected ramp, an action for a sustained spike. |

<Note>
  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.
</Note>

## What it needs connected

| Requirement               | Why                                                                                     | Where to set it up                                                       |
| ------------------------- | --------------------------------------------------------------------------------------- | ------------------------------------------------------------------------ |
| Cloud billing export      | Every workflow here starts from your own cost and usage data                            | [Built-in integrations](/manage-your-agents/build/built-in-integrations) |
| Cloud read access         | So a finding can be verified against the resource itself, not just the invoice line     | [Built-in integrations](/manage-your-agents/build/built-in-integrations) |
| A scoped write credential | Cleanup and lifecycle changes are writes, bound to the agent allowed to make them       | [Credentials & secrets](/manage-your-agents/build/credentials-secrets)   |
| A ticketing target        | So customer-facing remediation lands as a ticket with an owner rather than as an action | [Built-in integrations](/manage-your-agents/build/built-in-integrations) |

## Enabling it

<Steps>
  <Step title="Open Modules → Overview">
    Cloud Cost appears in the Cost Optimization family with the three workflows it contains.
  </Step>

  <Step title="Turn it on">
    Enabling the module adds Cloud Cost to your sidebar, with its waste findings list.
  </Step>

  <Step title="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.
  </Step>
</Steps>

## 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

<CardGroup cols={2}>
  <Card title="Kubernetes Cost" href="/modules-and-workflows/cost-optimization/k8s-cost">
    The cluster layer of the same bill.
  </Card>

  <Card title="Observability Cost" href="/modules-and-workflows/cost-optimization/observability-optimization">
    Attribute and reduce spend in your monitoring stack.
  </Card>

  <Card title="Approvals" href="/security-and-governance/controls/approvals">
    How a deletion waits for a human decision.
  </Card>
</CardGroup>


## Related topics

- [Kubernetes Cost](/modules-and-workflows/cost-optimization/k8s-cost.md)
- [Observability Cost](/modules-and-workflows/cost-optimization/observability-optimization.md)
- [AWS Cost Analyzer](/manage-your-agents/build/catalog/aws-cost-analyzer.md)
- [Agent catalog](/manage-your-agents/build/catalog/overview.md)
- [Google Cloud Investigator](/manage-your-agents/build/catalog/gcp-investigator.md)