- Industry
- Banking
- Department
- Engineering
- Team
- Platform and Reliability
- Kind
- Decision-maker
- Approver
- Head of Technology Operations
- Code
- ENG-13
It finds wasted cloud spend in the bank's estate (idle and oversized resources, unattached storage, untagged spend, test environments left running, commitments that no longer fit) and estimates the monthly saving of each action. It never touches production resources tagged as part of a critical business service or disaster-recovery capacity.
How it works
7 steps, and a person signs off before step 7.
- 01Looks it up
Finds the record the request is about in the cloud billing export: the cloud billing and usage data by resource, tag and cost centre..
- 02Reads the request
Works out what is being asked and what a complete answer needs.
- 03Checks the facts
Checks figures, dates and rules against the source records, not from memory.
- 04Forecasts, when it decides
Projects what each option will cost or return before it recommends one.
- 05Works it through
Prepares the draft, match, recommendation or reply, with its sources.
- 06Asks a person
Hands the work to Head of Technology Operations with its reasoning before anything goes out.
- 07Acts
Once approved, it acts in the CI pipeline: it applies the approved cost actions through infrastructure-as-code. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The cloud cost policy: tagging and chargeback to cost centres, protected resources (critical business services, DR standby capacity, regulatory retention stores), commitment purchase rules and the saving threshold.
Reads from
the cloud billing export: the cloud billing and usage data by resource, tag and cost centre.
Acts in
the CI pipeline: it applies the approved cost actions through infrastructure-as-code.
Hands back
A list of actions, each with resource, action (stop, resize, delete, schedule or commit), monthly_saving_usd, risk, environment and reason.
Asks a person when
An action touches production, buys or changes a commitment, deletes storage, or saves more than ten times 100 USD a month.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Idle CPU (%) | 5 | Below this a resource is idle. |
| Lookback (days) | 30 | Usage measured over this. |
| Smallest saving (USD a month) | 100 | Smaller savings are grouped. |
| May act on | non_production_only | Where it may act without approval. |
| Protected tags | critical-business-service, dr-standby, regulatory-retention | Never stopped or resized. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- A resource below 5 percent CPU over 30 days is idle.
- Never stop, resize or delete anything tagged critical-business-service, dr-standby, regulatory-retention, including DR standby that looks idle by design.
- Act without approval only in non_production_only.
- Report actions saving at least 100 USD a month.
- Commitment purchases always need approval.
See the Cloud Cost Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.