We have Savings Plans and RIs but no idea if we really use them
Reservation utilization < 90 percent is throwing money away. Every cloud has a standard report showing monthly what's unused and what your commitment coverage is.
Try this first
- 1AWS: Cost Explorer > Reservations Utilization Report and Coverage Report. Aim for utilization > 95 percent and coverage > 70 percent for steady-state.
- 2Azure: Cost Management > Reservations with utilization and recommendation. Same pattern.
- 3GCP: Committed Use Discounts (CUDs) report in Billing. What's locked, what's used, where's the gap.
- 4Low utilization (< 80 percent): likely too much or wrong type committed. With Savings Plan you can flex across families, with RI not, then exchange or sell on Marketplace.
- 5Low coverage (< 50 percent): on-demand spend is high, that's where commitment savings sit. Next cycle, more Savings Plan or RI.
When to bring us in
For commitments above 5K per month or considering a first RI purchase, an hour of analysis with someone with FinOps routine usually pays back inside a month.
See also
- Everyone logs in with the AWS root accountRoot is for emergencies and billing. Day-to-day work belongs in IAM users or SSO.
- Every developer has AdministratorAccessAdministratorAccess everywhere is convenient now, painful later. Start with role-based policies.
- Everyone has individual IAM users with their own passwordIdentity Center (formerly AWS SSO) links to your IdP and issues temporary credentials per session.
None of the above fits?
Describe your situation below. We pass your input plus the steps you already saw to our AI and return tailored next-step advice. If it's too risky to DIY, we'll say so.
Or skip the DIY entirely
Our Managed IT clients do not look these things up. One point of contact, a fixed monthly price, resolved within working hours.