Oracle on AWS BYOL: Licensing Rules, Dedicated Host Requirements, and the True Cost of Oracle in AWS

Running Oracle software on Amazon Web Services is attractive in principle: the operational benefits of cloud, combined with existing Oracle licence investments. In practice, Oracle's BYOL rules for AWS introduce licensing complexity that catches enterprises off-guard — typically at ULA certification time or during an Oracle LMS audit. The gap between how IT teams assume Oracle BYOL works and how Oracle's licensing policy actually requires it to work is one of the most consistent sources of large Oracle compliance claims we encounter.

This guide covers Oracle's BYOL rules for AWS as they stand in 2026, the dedicated host requirements that drive significant compliance risk, the AWS services where Oracle BYOL is and isn't supported, and how to conduct a genuine cost comparison between Oracle on AWS BYOL and Oracle Cloud Infrastructure as the two primary options for cloud-hosted Oracle workloads.

This article is part of our Complete Oracle Licensing Guide. For Oracle partitioning policy in on-premises virtualised environments, see Oracle Partitioning Rules. For AWS contract strategy, see our AWS practice page and AWS EDP Negotiation Guide.

Oracle BYOL on AWS: The Fundamental Rules

Oracle's authorised cloud environments policy (published on Oracle's website) defines the terms under which existing Oracle on-premises licences can be used in cloud environments. For AWS, the core BYOL rules are:

• Dedicated infrastructure is required for most Oracle products: Oracle Database, Oracle RAC, Oracle WebLogic, and most Oracle middleware products require deployment on AWS Dedicated Hosts or Dedicated Instances. Shared multi-tenant AWS infrastructure — the default EC2 model — does not qualify for Oracle BYOL for these products.
• vCPU to physical core conversion: On AWS Dedicated Hosts, Oracle counts 2 vCPUs as equivalent to 1 physical core for licensing purposes. Oracle Database Enterprise Edition requires 1 processor licence per 2 vCPUs (with Oracle's standard core factor applied to the physical core count). Oracle Database Standard Edition 2 is licensed per 2 vCPUs regardless of physical core count, capped at 8 vCPUs per instance.
• Annual support must remain current: Oracle BYOL requires that the licences brought to AWS are covered by active Oracle Software Update Licence and Support (annual support). Using lapsed licences voids the BYOL arrangement and creates compliance exposure.
• Licence Mobility rules apply: Oracle's Licence Mobility through Microsoft Azure Licence Mobility program does not apply to Oracle software on AWS — Oracle has its own cloud policy for AWS which is separate from any Microsoft Licence Mobility framework.

AWS Dedicated Hosts: The Compliance Linchpin

The requirement for AWS Dedicated Hosts is the most commercially significant aspect of Oracle BYOL on AWS. A Dedicated Host is a physical EC2 server allocated exclusively to a single AWS account — unlike shared tenancy where multiple customers' VMs co-exist on the same physical hardware. Dedicated Hosts are substantially more expensive than equivalent shared EC2 instances, and the cost model is based on physical host allocation rather than instance size.

Why Dedicated Hosts Are Required

Oracle's requirement for Dedicated Hosts stems from Oracle's position on partitioning. AWS's standard multi-tenant EC2 infrastructure is, in Oracle's view, equivalent to soft partitioning — Oracle cannot determine how many physical processors underlie a standard EC2 instance, and therefore requires customers to either deploy on Dedicated Hosts (where the physical core count is known and fixed) or use Oracle's own cloud (OCI).

Without a Dedicated Host, Oracle's auditors will typically assert that the BYOL arrangement is non-compliant and will calculate licence requirements based on estimated physical server configurations — which can produce claims significantly larger than the actual Oracle footprint.

Dedicated Host Instance Types Supported for Oracle BYOL

Not all EC2 instance families support Oracle BYOL on Dedicated Hosts. Oracle's authorised cloud environments policy specifies which AWS instance types are supported. As of 2026, the key supported families for Oracle Database BYOL are the compute-optimised families (C-series) and memory-optimised families (R and X series) running on Dedicated Hosts. Oracle's vCPU core conversion applies: 2 vCPUs = 1 physical core, with Oracle's core factor then applied to the physical core count.

Oracle Services on AWS: BYOL vs. Licence Included

AWS offers two Oracle deployment models: Bring Your Own Licence (BYOL) for instances where you provide the Oracle licence, and Licence Included (LI) through the AWS Marketplace where Oracle licence and support costs are bundled into the EC2 instance pricing. Understanding the cost and compliance profile of each model is essential for Oracle cloud strategy.

Oracle RDS (Relational Database Service)

Oracle on Amazon RDS is available in both BYOL and Licence Included configurations. RDS BYOL supports Oracle Database Standard Edition 2 and Enterprise Edition. Critically, RDS uses shared infrastructure and is not a Dedicated Host service — Oracle's BYOL rules for RDS require specific licence types (SE2 is generally straightforward; EE requires careful analysis of the RDS multi-AZ and read replica configurations). RDS Licence Included is available for SE2 only — the licence cost is embedded in the RDS instance hourly rate and is generally significantly more expensive per unit than purchasing Oracle licences separately, but removes compliance management overhead.

Oracle on EC2 (Self-Managed)

Running Oracle on EC2 gives maximum control but requires full BYOL compliance management. EC2 BYOL requires Dedicated Hosts for Oracle Database EE and RAC. Standard EC2 shared tenancy is only permissible for Oracle Database SE2 under very specific configurations that Oracle has explicitly endorsed. Any Oracle EE deployment on non-dedicated EC2 infrastructure is a compliance risk regardless of how the vCPU limits are configured.

Amazon RDS Custom for Oracle

RDS Custom is a relatively recent AWS service that provides managed Oracle database infrastructure with administrator-level access — combining some of the automation benefits of RDS with the customisation of self-managed EC2. RDS Custom for Oracle supports BYOL, runs on Dedicated Hosts, and is increasingly the preferred model for enterprise Oracle on AWS deployments that require customisation beyond what standard RDS supports.

Oracle on AWS vs. Oracle Cloud Infrastructure: A Genuine Cost Comparison

Oracle is consistently aggressive in positioning OCI as a superior licensing environment to AWS for Oracle workloads. Oracle's BYOL terms for OCI are materially different from AWS: OCI counts physical cores directly without the 2-vCPU conversion factor, and Oracle's "Bring Your Own Licence" to OCI includes provisions that are not available on AWS, including the ability to use on-premises licences in OCI without the dedicated host requirement for some workloads.

The OCI cost advantage is real but not unconditional. The "2× credit" for bringing on-premises Oracle licences to OCI is a compelling headline, but it entangles your Oracle licence relationship with your cloud commercial relationship in ways that can reduce negotiating leverage at both Oracle licence renewal and OCI contract renewal. Enterprises considering OCI BYOL should engage specialist advisory before committing to understand the full commercial implications — particularly the impact on Oracle licence portability and the exit provisions in OCI agreements.

Oracle BYOL Audit Risk on AWS: What Oracle's Team Looks For

Oracle LMS audit activity on AWS deployments has increased significantly since 2023. Oracle has developed tools and partnerships that give it visibility into patterns consistent with Oracle software deployment in AWS environments — including patch download patterns from licensed IP addresses that resolve to AWS ranges and support ticket submissions referencing AWS infrastructure. When Oracle identifies a customer with significant Oracle deployments in AWS without a commensurate BYOL compliance arrangement, it typically initiates an LMS engagement targeting the cloud deployments specifically.

The most common AWS BYOL audit findings are: Oracle EE deployed on standard (shared) EC2 tenancy without a Dedicated Host arrangement; RDS deployments that the customer has documented as Licence Included but which Oracle believes should be covered by BYOL (typically in EE configurations); and ULA deployments where cloud deployments were not properly disclosed or where the entity scope excludes the AWS deployment.

For comprehensive AWS strategy, see our AWS advisory practice and download our Cloud Contract Framework. For Oracle audit defence if you have received an LMS letter, see our Oracle Audit Defence Guide and Vendor Audit Defence service.