.png)
Before purchasing an RI, compare it with Database Savings Plans and check whether BYOM changes your licensing economics. AWS currently advertises Database Savings Plans savings of up to 35% across eligible database usage, while BYOM lets qualifying customers use existing SQL Server licenses instead of paying the AWS SQL Server license charge.
For the general mechanics across engines, see the RDS Reserved Instances guide.
Why SQL Server RIs are different
An RDS Reserved Instance is a billing discount rather than a separate database server. AWS offers one-year and three-year terms, and the discount applies only while usage matches the reservation.For RDS SQL Server, AWS requires matching Region, DB engine, instance type and exact size, edition, and license type. The engine version number does not need to match. AWS explicitly excludes SQL Server from RDS RI size flexibility. See the AWS Reserved DB instance guidance.
That last rule changes the risk profile.
Eligible size-flexible engines can normalize RI coverage across sizes in the same family. SQL Server cannot. If you resize outside the matching specification, the database keeps running but the RI discount stops applying, while the commitment continues billing.
AWS offers No Upfront, Partial Upfront, and All Upfront RIs. No Upfront is available only for one-year reservations, while availability of specific offerings can vary by instance class.
Licensing changes the RI decision
RDS for SQL Server supports License Included and Bring Your Own Media, or BYOM.With License Included, AWS supplies the SQL Server license and includes the software licensing cost in RDS pricing. Enterprise, Standard, Web, and Express editions are available under this model.
BYOM lets eligible customers use existing SQL Server licenses. For Standard and Enterprise, this requires Microsoft License Mobility through active Software Assurance. AWS does not charge the SQL Server license fee under BYOM, although customers still pay applicable infrastructure, Windows Server, storage, I/O, data transfer, and other RDS charges.
BYOM also adds checks that matter before an RI purchase:
Supply valid SQL Server Release to Manufacturing, or RTM, installation media as an ISO file in Amazon S3.
For Standard and Enterprise, maintain Microsoft licensing compliance through License Mobility and active Software Assurance. Developer Edition has separate non-production licensing requirements.
Confirm the AWS Region and DB instance type support BYOM.
Remember that BYOM engine versions are account- and Region-specific.
Plan migrations because in-place major version upgrades are not currently supported.
If your organization already owns qualifying SQL Server licenses, finish the BYOM evaluation before locking into License Included RI economics. A reservation must match the applicable license type, so changing the licensing model later can leave the existing reservation unmatched.
For more context on reducing commitment exposure before purchase, see how to save on RDS Reserved Instances.
Edition and Multi-AZ choices matter
Edition affects licensing, features, pricing, and RI matching.| Edition | Licensing model | Production use | RI planning concern |
|---|---|---|---|
| Web | License Included | Yes, restricted | Intended for qualifying public internet-facing workloads |
| Standard | LI or BYOM | Yes | Confirm the workload will not require an edition change |
| Enterprise | LI or BYOM | Yes | Higher licensing cost increases the impact of sizing mistakes |
| Express | License Included | Yes, limited workloads | Often a weaker long-term commitment candidate |
| Developer | BYOM | No | Development and testing only; Multi-AZ is not supported |
Changing from Standard to Enterprise can create the same problem. A Standard Edition reservation does not automatically become an Enterprise Edition reservation, so expected edition changes should be modeled before a long-term purchase.
What SQL Server RIs actually cost
RDS SQL Server pricing varies by Region, size, edition, license model, deployment option, and bundled versus unbundled pricing. Under unbundled pricing, AWS separates instance and licensing charges, which matters when comparing Database Savings Plans.Use the current AWS RDS for SQL Server pricing page for purchase decisions and the Usage.ai RDS pricing calculator guide to structure the comparison.
Illustrative example only
Assume a SQL Server configuration costs $2.00 per hour On-Demand, $1.50 per hour under a one-year RI, and an amortized $1.20 per hour under a three-year RI. These are teaching assumptions, not current AWS quotes.
| Scenario | Illustrative hourly rate | Annual instance cost | Difference vs On-Demand |
|---|---|---|---|
| On-Demand | $2.00 | $17,520 | Baseline |
| 1-year RI | $1.50 | $13,140 | $4,380 |
| 3-year RI, amortized | $1.20 | $10,512 | $7,008 |
RDS SQL Server T3 CPU credits cost $0.144 per vCPU-hour when Unlimited-mode usage exceeds the baseline and credits are exhausted. These charges are not covered by Reserved Instances.
Right-size before you commit
For SQL Server, right-sizing is part of commitment-risk controlReview utilization. Check CPUUtilization, FreeableMemory, DatabaseConnections, storage latency, and application performance. Do not resize from the CPU alone.
Confirm the edition. Model any likely Standard-to-Enterprise move before a long-term purchase.
Confirm the license model. For Standard and Enterprise BYOM, validate Software Assurance, License Mobility, Region, instance type, RTM media, and compliance ownership. For Developer Edition, confirm its separate non-production licensing requirements.
Confirm deployment design. Decide on Single-AZ or Multi-AZ before purchase.
Choose the term last. One year limits exposure to change exposure. Three years fits only configurations expected to remain useful.
Before buying a SQL Server RI, confirm the Region, edition, license model, exact DB instance class, and deployment type against the AWS purchase screen.A mismatch in any of these attributes can leave the reservation unused while the commitment continues.
RI vs Database Savings Plans
Database Savings Plans are now a meaningful alternative to SQL Server RIs.AWS says Database Savings Plans can reduce eligible database costs by up to 35% in exchange for a consistent one-year usage commitment with no upfront payment. They automatically apply to eligible serverless and provisioned database usage regardless of engine, instance family, size, deployment option, or AWS Region.
For RDS SQL Server, there is an important limitation: the Database Savings Plan discount applies only to the instance price. Microsoft Windows Server and SQL Server licensing charges remain billed at On-Demand rates and are not eligible for the Database Savings Plan discount. See the AWS Database Savings Plans pricing page.
| Choice | Best fit | Flexibility | Main limitation |
|---|---|---|---|
| SQL Server RI | Stable exact SQL Server configuration | Low | No size flexibility |
| Database Savings Plan | Eligible database spend likely to move across configurations | High | One-year commitment; SQL Server license charges excluded |
| On-Demand | Temporary or uncertain workloads | Highest | No commitment discount |
Compare the eligible instance portion, licensing charges, expected configuration changes, and utilization. A stable exact SQL Server configuration can favor an RI. Usage likely to move across eligible services, Regions, sizes, or deployment options can favor a Database Savings Plan.
See the Usage.ai Database Savings Plans guide for a broader commitment-sizing framework.
Final purchase checklist
Right-size the database first.
Confirm edition and license model.
For Standard or Enterprise BYOM, validate License Mobility and active Software Assurance.
For Developer Edition BYOM, confirm the separate non-production licensing requirements and remember that Multi-AZ is not supported.
Confirm Single-AZ or Multi-AZ for supported editions.
Verify the exact DB instance class and Region.
Compare current RI and Database Savings Plan economics.
Model licensing, storage, I/O, backups, data transfer, and T3 CPU credits separately where applicable.
Check the supported SQL Server version and upgrade path.
How Usage.ai handles RDS SQL Server Reserved Instances
Usage.ai applies SQL Server-specific checks before recommending an RI, including instance class, edition, licensing model, Multi-AZ configuration, Region, and recent configuration stability. This helps reduce the risk of stranded commitments because SQL Server RIs have no size flexibility.Recommendations also match the exact edition, license model, and deployment type, so Standard, Enterprise, LI, BYOM, Single-AZ, and Multi-AZ workloads are treated separately.
Through our Flex Insured Commitment Program, teams can achieve up to 50% savings on covered cloud spend, on average, without taking on a three-year commitment risk. Our fee is a percentage of realized savings, and eligible commitments include cashback protection for underutilization.
The cloud provider still controls the underlying commitment products, pricing, eligibility rules, and billing mechanics. We operate the optimization and management layer around eligible commitments.
Frequently asked questions
Do RDS SQL Server Reserved Instances have size flexibility?
No. AWS explicitly excludes RDS for SQL Server from RDS RI size flexibility. The running instance must match the required reservation specifications, including the exact instance size, for the discount to apply.
Can I use BYOM with RDS SQL Server?
Yes. BYOM supports Enterprise and Standard Edition for customers using License Mobility through active Software Assurance, and Developer Edition for development and testing without License Mobility. You must provide valid RTM installation media and use a supported Region and instance type. For Standard and Enterprise, you remain responsible for Microsoft licensing compliance.
Do Database Savings Plans cover RDS SQL Server?
Yes. Eligible RDS SQL Server instance usage can receive Database Savings Plan rates. AWS states that Windows Server and SQL Server licensing charges remain at On-Demand rates and are not eligible for the discount.
Should I choose a one-year or three-year SQL Server RI?
Choose based on configuration stability, not only the nominal discount. One year reduces exposure when size, edition, licensing, deployment, or architecture could change. Three years is better suited to configurations expected to remain useful throughout the longer term.
What costs are not covered by a SQL Server RI?
RDS RI pricing does not discount storage, backups, or I/O. Data transfer and other applicable RDS charges also remain separate. T3 CPU credit charges, where applicable, are not covered by Reserved Instances.
