CoreFinOps Docs
On this page

Savings Radar

Prioritize opportunities without double counting potential savings.

Savings Radar brings together supported optimization candidates, financial effect, confidence, risk and action state. It is a prioritization view — not a realized-value report.

Limitation

Savings Radar is part of commercial hardening. Verify live availability against the deployed environment before making external claims about this feature.

Reading the radar

Opportunities should expose the expected monthly or annual impact in explicit currency, the affected resource/workload, AWS account and region, recommendation provenance, evidence, effort/risk and current next action.

Ranking does not guarantee value

A high estimated saving with weak attribution or a production performance risk may be less actionable than a smaller, well-evidenced change. Prioritization should make tradeoffs visible instead of presenting one opaque savings score as fact.

Non-additive opportunities

Several proposals may depend on the same resource, baseline or time window. A rightsize followed by decommission cannot generally be counted as two independent continuing savings streams. The radar should identify overlap and avoid naive summed totals.

Move to action

Select an opportunity, review evidence, assign an owner and create an Action Center item. Any approval or execution remains a governed, human-controlled process.

Empty-state interpretation

“No estimated opportunity yet” can be legitimate: connect AWS, confirm Cost Optimization Hub/Compute Optimizer eligibility, run refresh and check source coverage before concluding that the workload is already optimized.