Savings Plan Coverage Below 30%
Most committed-shape spend is being billed at on-demand rates, which is the gap a Savings Plan exists to close.
Free to start. No card. The playground just needs your work email.
AWS
Found, explained, handed over.
Findings with a dollar figure attached, idle, oversized, orphaned, unscheduled and undiscounted spend.
Detect
ZopNight checks this automatically across AWS, with read-only access to the account.
Explain
Every finding says exactly what to change: Raise Savings Plan coverage for compute. Where the saving can be proven it is priced; where it cannot, the finding says so.
Fix
The finding opens with the fix already written out, step by step, so it is one ticket, not an investigation.
- Applies to
- EC2 Instances on AWS
- The fix, by hand
- Cost Explorer → Savings Plans → Recommendations → Compute Savings Plan. Review AWS-suggested hourly commitment.
- Confirm the recommended commitment is below the 30-day rolling spend floor (don't over-commit on burst).
- Cost Explorer → Savings Plans → Purchase Savings Plans → Compute SP → enter the hourly commitment → 1-year No-Upfront.
- Within 24h verify utilisation on the SP utilisation report.
- Re-evaluate every quarter as baseline grows.
These are the steps the finding carries in the product.
- Category
- Commitment discounts. Reserved Instance, Savings Plan and Committed Use opportunities, where steady usage justifies a commitment.
- Where it appears
- The Savings tab of Recommendations, with every affected resource listed.
- Rule ID
RC-1508- Full reference
Related checks
See the discount opportunities in your account.
Connect a read-only role and the first pass runs on your own estate. This check, and the rest of the catalogue, with it.
Prefer to talk it through first? Book 20 minutes with the team.
- $30M+annualised cloud spend under management
- 550K+resources tracked since launch
- 20-60%off the bill in the first month
- SOC 2Type II report, plus ISO 27001
Figures published on zop.dev.