Oracle Database Licensing on AWS: Complete Guide for Procurement and IT Leaders

Oracle Database on AWS: The Two Licensing Models

Oracle Database on AWS is available under two distinct licensing approaches. The first is Licence Included (LI), where the cost of the Oracle Database licence is bundled into the AWS service price. The second is Bring Your Own Licence (BYOL), where you supply existing Oracle licences you have purchased directly from Oracle, and AWS charges only for the underlying compute and infrastructure.

The choice between these models is not purely financial. It also determines your ongoing relationship with Oracle, your Oracle support obligations, and the edition and version of Oracle Database you can deploy. Each model has a different cost profile at different scales and deployment patterns.

Licence Included on RDS

The licence-included model is available on Amazon RDS for Oracle Standard Edition 2 on specific instance classes. Under this model, AWS holds the Oracle licence on your behalf and charges you an all-in hourly rate that covers both the compute infrastructure and the Oracle software licence. You do not need an active Oracle support contract because AWS manages the Oracle licence relationship.

The tradeoff is that the hourly rate for licence-included instances is significantly higher than the equivalent BYOL rate, and the licence-included model is not available for Oracle Enterprise Edition at all. Any organisation requiring Enterprise Edition on AWS must use BYOL. This means that the majority of enterprise Oracle Database deployments on AWS, which typically require EE for advanced features such as Partitioning, RAC, Advanced Compression, or Advanced Security, must be on BYOL.

BYOL on RDS and EC2

BYOL is the standard model for enterprise Oracle Database deployments on AWS. Under BYOL, you maintain your own Oracle licences purchased from Oracle, keep your Oracle support contract active, and pay AWS only for the compute, storage, and infrastructure elements of the service. The AWS hourly rate for BYOL instances is meaningfully lower than for licence-included instances.

BYOL is supported on both Amazon RDS for Oracle and Amazon EC2. The two platforms have different licence counting mechanics, which is one of the most important distinctions to understand when planning an AWS deployment.

How Oracle Counts Licences on AWS

Oracle's official cloud licensing policy specifies that in authorised cloud environments, including AWS, two vCPUs are counted as one Oracle Processor licence when hyper-threading is enabled. This is the foundational rule that governs all BYOL deployments on both EC2 and RDS when hyper-threading is active, which is the standard configuration on all mainstream EC2 instance types.

If hyper-threading is disabled, the counting ratio changes to one vCPU per one Oracle Processor licence. Because disabling hyper-threading reduces the effective compute capacity of the instance without reducing costs, the standard practice is to keep hyper-threading enabled and use the two-to-one counting rule.

EC2 Processor Counting in Practice

On Amazon EC2, you have visibility into the vCPU count of your instance from the EC2 console. For a db.r6i.8xlarge instance with 32 vCPUs, the licence count is 16 Oracle Processor licences. For a db.r6i.16xlarge with 64 vCPUs, the count rises to 32 Oracle Processor licences.

At Oracle's current Enterprise Edition list price of $47,500 per processor, a single 64-vCPU instance requires $1,520,000 in licence value before annual support is added. Annual support is charged at 22 percent of the net licence fee, and Oracle increases this support fee by 8 percent per year. The combination of high per-processor pricing and compounding support costs makes instance right-sizing the single most effective cost management action before any Oracle workload moves to AWS.

RDS Processor Counting

On Amazon RDS for Oracle, the same two-to-one vCPU rule applies under BYOL. RDS does not expose the physical host to you, so the only permissible counting method on RDS is Oracle's cloud licensing policy. You cannot use physical core-based counting on RDS, regardless of whether you are on a Multi-AZ, read replica, or standard deployment.

The vCPU count for your RDS instance is visible in the RDS console under the DB instance class details. Selecting an RDS instance class before checking the vCPU-to-licence ratio is a common mistake that results in over-deployment against available licences.

Amazon RDS for Oracle: Deployment Considerations

Amazon RDS for Oracle is the managed database service path for Oracle on AWS. RDS handles patching, backups, monitoring, and failover automation, reducing administrative overhead relative to self-managed Oracle on EC2. For licensing purposes, the key RDS-specific considerations are Multi-AZ requirements and the restrictions on licence-included availability.

Multi-AZ and Licence Doubling

An RDS Multi-AZ deployment automatically provisions a synchronous standby replica in a separate Availability Zone. The standby runs active Oracle Database software and requires Oracle licences under BYOL, doubling the licence count relative to a single-AZ deployment. Organisations planning Multi-AZ deployments must factor this doubling into their total licence position before deployment.

For a production RDS instance requiring 16 processor licences, a Multi-AZ deployment requires 32 processor licences total. At Enterprise Edition list prices, this additional standby instance represents $760,000 in licence value that must be either held already or purchased before the Multi-AZ deployment goes live.

RDS Read Replicas

RDS read replicas run Oracle Database software and require licences under BYOL. Each read replica must be independently licenced at the same vCPU-based count as the primary instance. Deploying read replicas without accounting for the additional licence requirement is a frequent source of compliance gaps in AWS Oracle environments.

Under the licence-included model on RDS for SE2, read replicas are covered by the AWS-managed licence. Under BYOL, each replica is your responsibility.

Amazon EC2 for Oracle Database

Running Oracle Database on EC2 gives you more control than RDS, including the ability to use Oracle features that RDS does not support, manage the database software directly, and choose between standard instances, Dedicated Hosts, and bare metal instances for different licensing approaches.

Standard EC2 Instances

On standard shared-tenancy EC2 instances, Oracle's two-to-one vCPU rule applies. You cannot use the physical core count of the underlying host because you share the physical host with other AWS customers and do not have visibility into or control over the physical hardware assignment. Oracle's policy requires you to use vCPU-based counting in this scenario.

EC2 Dedicated Hosts

Dedicated Hosts give you a physical server allocated solely to your account. Because you have full visibility into the instance's physical core count, some organisations use Dedicated Hosts to establish a cleaner compliance basis for Oracle licensing. On a Dedicated Host, you can verify the physical core count and apply Oracle's core factor to calculate the precise processor licence requirement.

A Dedicated Host typically carries a 10 to 30 percent cost premium over standard shared-tenancy instances. Whether that premium is justified depends on your organisation's audit risk posture and the importance of a physically bounded licence position.

EC2 Bare Metal Instances

Bare metal EC2 instances are licenced by Oracle exactly as an on-premises physical server. All physical cores must be licenced, adjusted by Oracle's published core factor for the processor type. Bare metal provides the clearest compliance basis but eliminates the flexibility and cost efficiency of virtualised EC2 instances.

Oracle Database Editions on AWS

Oracle supports Enterprise Edition and Standard Edition 2 for AWS deployments. The edition determines which features are available, how licences are counted, and which deployment options are permitted.

Enterprise Edition on RDS is available under BYOL only. SE2 on RDS is available under both BYOL and licence-included models, but SE2 is limited to instance classes with no more than eight vCPUs, reflecting Oracle's on-premises constraint of two sockets per SE2 deployment. When an SE2 workload grows beyond what an eight-vCPU instance can handle, the workload must either be redesigned or migrated to Enterprise Edition, which is a significant cost step-up.

Oracle Options and Management Packs on AWS

The Oracle Database base product does not include Oracle options and management packs. If your database deployment uses any of the following, each requires a separately purchased and tracked licence counted on the same vCPU basis as the database itself.

• Diagnostics Pack: Required for Automatic Workload Repository (AWR) access, Active Session History, and most performance monitoring views. Frequently enabled inadvertently by DBAs who access AWR for troubleshooting without realising it requires a separate licence.
• Tuning Pack: Required for SQL Tuning Advisor, SQL Access Advisor, and Automatic SQL Tuning. Often used alongside Diagnostics Pack in performance-sensitive environments.
• Partitioning: One of the most widely used Oracle options. Any database that uses table or index partitioning requires this option to be licenced.
• Advanced Security: Required for Transparent Data Encryption (TDE) on Enterprise Edition databases running older than Oracle 19c. From Oracle 19c onwards, TDE is included in the base Enterprise Edition licence for on-premises deployments, but must be verified against the specific RDS version in use.
• Real Application Clusters (RAC): Available only on EC2, not on RDS. RAC is an Enterprise Edition option that requires separate licensing on every node in the cluster.

Oracle Support on AWS: Cost Structure and Increase Trajectory

Oracle's annual support fee is set at 22 percent of the net licence fee at the time of purchase. Oracle increases this support fee by 8 percent per year, compounding annually. This means that a $500,000 licence portfolio carries approximately $110,000 in year one support fees, rising to approximately $163,000 by year five and $240,000 by year ten.

For BYOL deployments, active Oracle support is mandatory. Oracle requires all cloud-deployed software to be covered by current Software Update Licence and Support agreements. Allowing support to lapse while continuing to run Oracle on AWS creates a material compliance violation. When support is reinstated after a lapse, Oracle demands back-payment of all lapsed support fees plus interest, retroactively applying the 8 percent compounding increase to each year of the lapse period.

Six Cost Management Strategies for Oracle on AWS

Right-size instances before migration: The largest single cost lever for Oracle on AWS is instance sizing. Every vCPU reduction halves the licence count at that instance. Analysing actual CPU utilisation data from your on-premises environment before choosing an EC2 or RDS instance class can significantly reduce your licence requirement compared to a like-for-like lift-and-shift.

Audit options usage before migration: Identify every Oracle option and management pack in use in your on-premises environment. Options that are not required in the cloud workload should be disabled before migration, reducing the licence footprint on AWS.

Model Multi-AZ licence costs explicitly: Multi-AZ deployments double the licence requirement. Ensure your licence position covers both the primary instance and the standby before enabling Multi-AZ, and factor the doubling into your total cost of ownership model.

Evaluate SE2 for eligible workloads: For workloads that do not require Enterprise Edition features, Standard Edition 2 is licensed by socket rather than by core on-premises, and is restricted to eight vCPUs on cloud instances. This restriction actually provides a cost ceiling. At $17,500 per socket versus $47,500 per processor, SE2 can represent a substantial cost reduction for qualifying workloads.

Negotiate Oracle support within the renewal cycle: Oracle's Q4 (March through May) is the most favourable period for Oracle contract negotiations. Support fee negotiations conducted outside this window typically yield fewer concessions. An independent adviser with visibility into Oracle's discount framework can secure support fee discounts of 15 to 30 percent off Oracle's standard rates.

Maintain a live licence inventory: As EC2 instances are resized, replicated, or added to Multi-AZ configurations, the total Oracle licence requirement changes. A live licence inventory that updates whenever infrastructure changes are made is the only reliable mechanism for maintaining compliance between formal audits.