AWS RDS & Database Licensing Costs: What to Negotiate

The Two RDS Licensing Models

AWS RDS database licensing costs split into two models that look like a checkbox but behave like two different contracts. Under License Included, AWS bundles the commercial database licence into the hourly instance rate — you buy nothing separately and AWS holds the licensing relationship. Under Bring Your Own License (BYOL), you apply licences you already own and pay AWS only for the underlying infrastructure. Storage is charged identically either way, at provisioned GiB per month, so the entire cost difference sits in the compute line.

That difference is not marginal. On the same vCPU count, the open-source versus commercial gap runs from roughly $0.016/hr to $0.977/hr — and within the commercial engines, the BYOL compute rate strips the licence premium out of the hourly charge entirely. The decision is therefore the single largest lever on any managed-database bill, and it is one most procurement teams never see because engineering makes it silently at provisioning time.

Oracle on RDS: the BYOL maths and the SE2 trap

For Oracle, the maths usually favours BYOL whenever you already own licences and pay annual support. Take a db.r5.2xlarge Multi-AZ instance: the License Included compute rate sits near $0.98/hr, while the BYOL rate drops to roughly $0.48/hr — cutting the compute line from about $1,388 to $691 per month, or close to $8,400 a year for a single instance. Because you are already paying Software Update Licence & Support (typically 22% of the net licence fee per year) on those licences regardless of where they run, the marginal cost of redeploying idle on-premises licences onto RDS BYOL is effectively zero.

The trap is editions. On RDS, License Included covers only Oracle Database Standard Edition 2. Oracle Enterprise Edition is not available under License Included at all — it requires BYOL, and Oracle counts two AWS vCPUs as one processor licence. Teams that select an Enterprise Edition workload assuming AWS will "include" the licence create an immediate, unfunded compliance gap. From September 2025 AWS added bare-metal RDS instances for Oracle Enterprise Edition BYOL, extended to Standard Edition 2 BYOL in January 2026, priced about 25% below the equivalent virtualised instances — a genuine saving, but only if your licence position already covers the deployment. The same discipline that governs an on-premises estate applies here; our AWS cost optimization contract levers guide treats licence-position proof as a precondition, not an afterthought.

SQL Server on RDS: vCPU pricing and Optimize CPU

SQL Server on RDS is licensed per vCPU, and the pricing depends on the instance family. With License Included, the licence is bundled into a single hourly rate across Enterprise, Standard, Web and Express editions. On the newer unbundled families — M7i, R7i, M8i, R8i, M8a and R8a — AWS splits the bill into a per-CPU-hour instance charge and a separate per-vCPU-hour licence charge, which makes the licence cost visible and therefore manageable.

That visibility unlocks the most underused SQL Server lever on RDS: Optimize CPU. Because Enterprise and Standard editions are charged per active vCPU, reducing the vCPU count on a memory-bound instance cuts the licence bill directly without changing the instance size or its memory. Combined with the December 2025 new-generation M7i and R7i instances — which AWS prices up to 55% below the previous generation — a memory-heavy SQL Server estate can shed a large share of its licence cost through configuration alone, before any contract conversation begins.

The Commitment Levers: RIs, Savings Plans and EDP

Once the per-instance model is right, the commitment layer compounds the saving. RDS Reserved Instances and the newer database-scoped Savings Plans discount the infrastructure rate — up to about 69% off on-demand for a three-year all-upfront commitment on stable production databases, tapering to roughly 42% for no-upfront terms. These two mechanisms can run side by side across different workloads, and they sit underneath, not instead of, your enterprise agreement. Our AWS Reserved Instances and Savings Plans portfolio strategy sets out how to blend coverage without over-committing.

Above that, RDS and Aurora are qualifying spend under an AWS Enterprise Discount Program, so every database dollar counts toward your committed amount and draws the EDP discount. For a database-heavy estate, the move is to negotiate broad service coverage and then test whether a service-specific Private Pricing Agreement on database consumption beats the blended rate — a choice we unpack in EDP vs Private Pricing Agreement. The structural context for all of this lives in our pillar on multi-year cloud discount structures and the wider cloud contract complete guide, which map how commitment term and spend tier set the discount you can actually reach.

The Audit Exposure Nobody Prices In

BYOL on RDS carries exactly the same audit risk as on-premises Oracle — and the cloud makes the exposure easier to create. Oracle's LMS scripts read RDS deployments, and AWS's own Oracle Optimisation and Licensing Assessment programme gives Oracle visibility into BYOL instance counts. In estates we review, BYOL deployments without a verified licence position created audit exposure in four of ten cases. The recurring causes are predictable: unlicensed Enterprise Edition options such as Partitioning or Advanced Security switched on by default, and Standard Edition 2 instances scaled past their socket limits.

There is a second, quieter enforcement pattern. Oracle has been contacting customers who run Oracle under RDS License Included terms in ways its policy does not permit — for instance, hosting an Oracle-based SaaS product — and using the breach as the opening for a licence sale. Reusing a licence you cannot prove covers the deployment is not a saving; it is a deferred audit bill. If Oracle has already made contact, treat it as a negotiation, not a compliance errand, and read our AWS enterprise agreement negotiation guide before you respond.

What to Negotiate

Three things move the number. First, get the per-instance model right: prove your BYOL position, right-size vCPUs with Optimize CPU, and convert idle on-premises licences before buying anything new. Second, layer Reserved Instances or Savings Plans under the workloads you are confident will persist. Third, fold database spend into the broader commercial conversation — RDS and Aurora belong inside your EDP coverage and your minimum-commitment maths, not bolted on afterwards.

The mistake we see most often is treating the database bill as an engineering line item rather than a negotiable contract position. It is both. To pressure-test your own RDS estate against current benchmarks and model the BYOL versus License Included decision across your portfolio, request a confidential briefing or download the AWS EDP Negotiation Playbook.