RDS Reserved Instance Opportunity
The instance runs continuously, so it pays the on-demand premium for a flexibility it never exercises.
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: Buy a Reserved Instance for the RDS instance. 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
- RDS Instances on AWS
- The fix, by hand
- Confirm the workload is stable (production, long-lived, predictable utilisation over 70%).
- Open RDS → Reserved instances → 'Purchase reserved DB instance'.
- Match the DB engine, license model, instance class and AZ count to this instance.
- Pick a term (1-year No-Upfront is the safest first-time choice).
- Confirm the commitment in Billing → AWS Cost Explorer's RI utilisation report after ~24h.
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-031- 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.