The Math Behind Database Reserved Instances: When to Wait
The biggest mistake in Cloud FinOps isn’t failing to buy Reserved Instances—it’s buying them before you’ve optimized the architecture.
Situation
A company completes a massive “lift and shift” migration to the cloud. To hit their first-year cost reduction targets, the FinOps team immediately purchases 3-year Reserved Instances (RIs) for all their newly provisioned AWS RDS and Azure SQL databases.
The Problem
Lift-and-shift migrations almost always result in oversized infrastructure. On-premises databases are sized for 5-year peak capacity. When you move those identical instance sizes to the cloud and immediately lock them in with a 3-year RI, you are signing a contract to pay for idle CPU and RAM for the next 36 months. How do you balance the pressure for immediate RI discounts against the need for architectural right-sizing?
The Right-Sizing Buffer
Database workloads require a stabilization period.
- The 90-Day Rule: Never purchase a database RI within the first 90 days of a cloud migration.
- P95 Profiling: Use those 90 days to capture the 95th percentile CPU and memory utilization.
- Scale Down: Reduce the instance sizes to match the P95 load, leaning on the cloud’s ability to scale up dynamically if needed.
- Commit: Only then should you execute the 1-year or 3-year RI purchase on the right-sized footprint.
In Practice
The documented pattern shows that a 50% discount on a $10,000/month oversized instance ($5,000 effective) is worse than right-sizing the instance to $4,000/month on-demand and then applying a 30% 1-year discount ($2,800 effective).
Where It Breaks
| Scenario | Tradeoff |
|---|---|
| Database Modernization | If engineering plans to migrate from RDS MySQL to Aurora Serverless within 18 months, a 3-year RI on the legacy RDS instances will become sunk-cost waste. |
| Engine Flexibility | Standard RIs are often locked to a specific database engine. You cannot easily transfer an Oracle RI to a PostgreSQL instance. |
What to Do Next
- Problem: Buying RIs on unoptimized database infrastructure locks in waste.
- Solution: Enforce a 90-day waiting period post-migration to profile and right-size instances before committing.
- Proof: Right-sizing followed by RIs yields a dramatically lower TCO than applying RIs to legacy sizes.
- Action: Model your break-even points using our Database Reserved Instance ROI Calculator.