Running Oracle Database Enterprise Edition on AWS introduces complex licensing requirements for every database option and management pack. This guide provides definitive licensing rules for Real Application Clusters (RAC), Multitenant, Partitioning, Advanced Security, Advanced Compression, Active Data Guard, and the Diagnostics and Tuning Packs — including processor licence calculations for EC2 instances, RDS and RDS Custom deployment considerations, compliance monitoring with DBA_FEATURE_USAGE_STATISTICS, common audit traps, and a practical optimisation framework.
Every Oracle Database option and management pack is licensed separately, per processor, matching the Enterprise Edition base licence count. There are no bundles, no cloud-specific discounts, and no included options in AWS deployments. If you run Oracle Database Enterprise Edition on an EC2 instance with 8 vCPUs (requiring 4 EE Processor licences), every additional option you enable — RAC, Multitenant, Partitioning, Advanced Security, Diagnostics Pack — requires an additional 4 Processor licences each.
This additive model means the total licensing cost for a fully featured Oracle EE deployment on AWS can be 3–5× the base database licence cost. Understanding which options are genuinely needed — and which have been inadvertently enabled — is the most important cost control lever for Oracle on AWS.
RAC is Oracle’s high-availability clustering technology, available only with Enterprise Edition and licensed separately per processor on every node in the cluster. RAC is not supported on Amazon RDS — it requires manual deployment on EC2 instances or VMware Cloud on AWS (VMC), with third-party shared storage or clustering solutions.
RAC must be licensed on every server node participating in the cluster. Each node requires RAC Processor licences equal to the EE Processor licence count for that node. A 2-node cluster doubles the RAC licence requirement compared to a single instance — and a 3-node cluster triples it. There is no “cluster licence” or “shared” RAC licence pool across nodes.
Amazon RDS does not support RAC. If you need RAC functionality, you must deploy on EC2 instances (with shared storage solutions like Amazon FSx for NetApp ONTAP or third-party clustered storage) or on VMware Cloud on AWS. This means RAC on AWS is always a BYOL deployment — you cannot use AWS’s “Licence Included” option for RAC.
Before committing to RAC on AWS, evaluate whether AWS-native high availability — Multi-AZ RDS, EC2 Auto Scaling with Data Guard, or Aurora (for non-Oracle workloads) — meets your requirements at lower cost. RAC licensing on a 2-node cluster with 8 vCPUs per node costs 8 additional RAC Processor licences. If the goal is HA rather than scale-out performance, Data Guard may achieve the same objective at a fraction of the RAC licensing cost.
| RAC Scenario | Nodes | vCPUs Per Node | EE Licences | RAC Licences | Total |
|---|---|---|---|---|---|
| Small HA cluster | 2 | 4 | 4 (2 per node) | 4 (2 per node) | 8 |
| Standard production | 2 | 8 | 8 (4 per node) | 8 (4 per node) | 16 |
| Large-scale cluster | 3 | 16 | 24 (8 per node) | 24 (8 per node) | 48 |
| Formula: Per node — vCPUs ÷ 2 = EE licences = RAC licences. Total = sum across all nodes. | |||||
Oracle’s Multitenant architecture — Container Databases (CDBs) and Pluggable Databases (PDBs) — is a separately licensed option for Enterprise Edition. However, Oracle provides a free allowance of up to 3 PDBs per CDB starting from Oracle Database 19c, which means many deployments may not require the Multitenant licence at all.
Running 1, 2, or 3 Pluggable Databases within a single Container Database on Oracle 19c or later does not require a separate Multitenant licence. This is included with the base Enterprise Edition licence. For many AWS deployments — particularly where each EC2 instance hosts a small number of databases — this free allowance is sufficient. On standard Amazon RDS for Oracle, AWS restricts you to one user-created PDB per instance, so the Multitenant licence is typically unnecessary for RDS deployments.
Running 4 or more PDBs in a single Container Database requires the Multitenant option licence — licensed per processor, matching the EE base count. On EC2 and RDS Custom, you have full flexibility to create many PDBs, but each additional PDB beyond 3 does not incur an incremental licence — the Multitenant licence is binary: either you have it (unlimited PDBs) or you do not (capped at 3). This means the cost decision is between staying within the 3-PDB free allowance versus licensing Multitenant for unlimited consolidation.
Before licensing Multitenant, evaluate whether your database consolidation objectives can be achieved within the 3-PDB-per-CDB limit. If you have 9 databases to consolidate, deploying 3 CDBs with 3 PDBs each avoids the Multitenant licence entirely. On an 8-vCPU EC2 instance, the Multitenant licence costs the same as 4 additional Processor licences — at Oracle list pricing, this represents approximately $188,000 in licence fees plus ~$41,000 annual support. Consolidation architecture decisions should always consider the licensing cost threshold.
Oracle’s remaining database options — Partitioning, OLAP, Advanced Security, Advanced Compression, Active Data Guard, and others — follow the identical per-processor licensing model. Each option requires Processor licences equal to the EE base count, licensed separately, with no bundles or cloud-specific pricing.
| Oracle Option | Licence Metric | 8-vCPU EC2 Example | Common Audit Trigger |
|---|---|---|---|
| Partitioning | Processor (matches EE count) | 4 Processor licences | Partitioned tables or indexes detected in DBA_PART_TABLES |
| Advanced Security | Processor (matches EE count) | 4 Processor licences | Transparent Data Encryption (TDE) or Network Encryption enabled |
| Advanced Compression | Processor (matches EE count) | 4 Processor licences | OLTP compression, SecureFiles deduplication, or HCC usage |
| Active Data Guard | Processor (matches EE count) | 4 Processor licences (standby server) | Open standby database for read-only queries or reporting |
| OLAP | Processor (matches EE count) | 4 Processor licences | Analytic workspaces or OLAP cube materialised views |
| In-Memory | Processor (matches EE count) | 4 Processor licences | INMEMORY_SIZE parameter set to non-zero value |
| Cumulative impact: An 8-vCPU instance with EE + Partitioning + Advanced Security + Compression = 16 Processor licences (4 × 4 options) | |||
Transparent Data Encryption (TDE): Frequently enabled by default in cloud deployments for data-at-rest encryption — triggers Advanced Security licence requirement.
Network Encryption (SQL*Net): Configuring SQLNET.ENCRYPTION_SERVER = REQUIRED triggers Advanced Security licensing, even if encryption is mandated by your security policy.
Automatic Segment Advisor: Can recommend partitioning — if you act on the recommendation and create partitions, a Partitioning licence is required.
SecureFiles Deduplication: Using LOB deduplication or compression within SecureFiles triggers Advanced Compression licensing.
Data Guard Broker with read-only standby: Opening a standby database for queries (even briefly for reporting) converts it from a free standby to an Active Data Guard deployment requiring additional licensing.
Oracle’s Diagnostics Pack and Tuning Pack are among the most commonly inadvertently used licensed features. DBAs frequently generate AWR reports, use Performance Hub, or run SQL Tuning Advisor without realising these actions trigger a licensing obligation.
Required when using: Automatic Workload Repository (AWR), Active Session History (ASH), Performance Hub, ADDM (Automatic Database Diagnostic Monitor), or any feature that reads from AWR data. Licensed per processor, matching EE count. On an 8-vCPU EC2 instance: 4 Diagnostics Pack Processor licences. This is one of the most common audit findings — AWR reports are a standard DBA troubleshooting tool, and many teams generate them without awareness of the licensing implication.
Required when using: SQL Tuning Advisor, SQL Access Advisor, SQL Profile creation, or Automatic SQL Tuning. Licensed per processor, matching EE count. Often used alongside Diagnostics Pack — together, they add 8 Processor licences to an 8-vCPU instance. Oracle auditors specifically query DBA_FEATURE_USAGE_STATISTICS for “AWR Report” and “SQL Tuning Advisor” entries — these are among the first features checked during compliance reviews.
Oracle’s CONTROL_MANAGEMENT_PACK_ACCESS initialisation parameter controls access to the management packs. Set it to NONE to prevent any usage of Diagnostics or Tuning Pack features. Set it to DIAGNOSTIC to allow only Diagnostics Pack (if licensed). Set it to DIAGNOSTIC+TUNING only if both are licensed. This is a preventive compliance control — it stops DBAs from inadvertently triggering licensing obligations through routine troubleshooting. Implement this as a standard configuration across all Oracle instances on AWS.
AWS does not enforce or monitor Oracle option licensing — compliance responsibility rests entirely with the customer. Oracle auditors will examine your AWS deployments with the same rigour as on-premises environments, querying feature usage statistics and comparing against your licence entitlements.
DBA_FEATURE_USAGE_STATISTICS regularly: This Oracle-provided view shows every licensed feature that has been used, when it was first and last used, and by which database. Run this query quarterly across all Oracle instances on AWS and compare against your licence entitlements.DBA_PART_TABLES and DBA_PART_INDEXES: These views reveal whether Partitioning has been used — even if it was created inadvertently or by an application installer.V$ENCRYPTION_WALLET to determine whether Transparent Data Encryption is active — a common Advanced Security trigger.DBA_HIST_SNAPSHOT to determine if AWR snapshots are being collected (and therefore if Diagnostics Pack is being used).CONTROL_MANAGEMENT_PACK_ACCESS, remove unnecessary init.ora parameters, and educate DBAs about licensing implications of common troubleshooting tasks.Oracle database options receive no special or discounted pricing for cloud deployments. The per-processor licence fee and annual support cost for every option — RAC, Multitenant, Partitioning, Advanced Security, Diagnostics Pack, Tuning Pack — are identical whether deployed on-premises, on EC2, on VMware Cloud on AWS, or on any other authorised cloud platform.
The RDS “Licence Included” model covers Standard Edition 2 (SE2) only. No Enterprise Edition options are included. RAC, Multitenant, Partitioning, Advanced Security, Diagnostics Pack, and Tuning Pack all require BYOL (Bring Your Own Licence) with separately purchased Oracle licences. If you are running EE features on RDS, you must have corresponding Oracle licences — AWS does not provide them.
Licensing and pricing rules are identical to on-premises. The only AWS-specific consideration is the vCPU-to-processor conversion (vCPUs ÷ 2 for hyper-threaded instances on EC2). The option licence counts, metrics, and fees are the same. Oracle’s cloud licensing policy applies the same rules across all authorised cloud environments — AWS, Azure, GCP — with no cloud-specific discounts or bundles for database options.
If a feature is used — even inadvertently — it requires a licence. The Diagnostics and Tuning Packs are installed by default with Enterprise Edition. Generating a single AWR report triggers the Diagnostics Pack requirement. Running SQL Tuning Advisor once triggers the Tuning Pack requirement. Oracle auditors check DBA_FEATURE_USAGE_STATISTICS for any recorded usage, regardless of whether the feature was intentionally or accidentally invoked.
The following table shows the cumulative licensing impact when multiple Oracle options are deployed on a single 8-vCPU EC2 instance:
| Component | Processor Licences Required | Approximate List Price (Licence) | Approximate Annual Support (22%) |
|---|---|---|---|
| Enterprise Edition (base) | 4 | $188,000 | $41,360 |
| + Real Application Clusters | 4 | $92,000 | $20,240 |
| + Multitenant | 4 | $92,000 | $20,240 |
| + Partitioning | 4 | $46,000 | $10,120 |
| + Advanced Security | 4 | $60,000 | $13,200 |
| + Diagnostics Pack | 4 | $30,000 | $6,600 |
| + Tuning Pack | 4 | $20,000 | $4,400 |
| Total (all options) | 28 | $528,000 | $116,160/year |
DBA_FEATURE_USAGE_STATISTICS across every Oracle instance on AWS. Identify which options are actually used versus merely available. Many enterprises discover that Partitioning, Advanced Compression, or Management Packs were enabled by a DBA during troubleshooting or by an application installer — not as a deliberate architectural decision. Disabling unused features eliminates the licensing obligation and can save hundreds of thousands of dollars.The formula is consistent across all options: take the EC2 instance’s vCPU count (with hyper-threading enabled, which is the default), divide by 2, and the result is the Processor licence count for each option. An 8-vCPU instance requires 4 Processor licences for EE and 4 additional Processor licences for each separately licensed option. A 16-vCPU instance doubles these numbers. Every option is licensed independently — there are no bundles where multiple options share a licence pool. The vCPU ÷ 2 conversion applies to standard EC2 instance types; for bare metal or non-hyper-threaded instances, consult Oracle’s cloud licensing policy for the applicable core factor.
Not necessarily. Starting from Oracle Database 19c, you can run up to 3 Pluggable Databases (PDBs) within a single Container Database (CDB) without a Multitenant licence — this is included with the base Enterprise Edition licence. Only when you exceed 3 PDBs in a single CDB do you need the Multitenant option. On standard Amazon RDS for Oracle, AWS restricts you to one user-created PDB per instance, so the Multitenant licence is typically unnecessary. On EC2 and RDS Custom, you have full flexibility but must licence Multitenant if deploying 4+ PDBs per CDB. The Multitenant licence is binary — once licensed, you can create unlimited PDBs.
No. Amazon RDS does not support Oracle Real Application Clusters (RAC). If you need RAC, you must deploy it on EC2 instances with shared storage solutions (such as Amazon FSx for NetApp ONTAP or third-party clustered storage) or on VMware Cloud on AWS (VMC). RAC on AWS is always a BYOL deployment — you must bring your own Oracle licences for both the EE base and the RAC option. For high availability without RAC, consider Multi-AZ RDS (automated failover), Oracle Data Guard on EC2 (included with EE for non-read standby), or AWS-native HA architectures.
Any usage of features that depend on the Automatic Workload Repository (AWR) triggers a Diagnostics Pack requirement — this includes generating AWR reports, using Performance Hub, viewing Active Session History (ASH), or running ADDM reports. For the Tuning Pack, using SQL Tuning Advisor, SQL Access Advisor, creating SQL Profiles, or using Automatic SQL Tuning triggers the requirement. These features are installed by default with Enterprise Edition and can be used inadvertently. Oracle auditors check DBA_FEATURE_USAGE_STATISTICS for any recorded usage. To prevent inadvertent use, set the CONTROL_MANAGEMENT_PACK_ACCESS parameter to NONE (or DIAGNOSTIC if only the Diagnostics Pack is licensed).
No. Oracle database options receive identical pricing and licensing terms whether deployed on-premises, on EC2, on VMware Cloud on AWS, or on any other authorised cloud platform. There are no cloud-specific discounts, bundles, or pricing adjustments for options. The only AWS-specific element is the vCPU-to-processor conversion (vCPUs ÷ 2 for hyper-threaded instances). Oracle’s position is that cloud licensing follows the same rules as traditional deployments — the deployment location does not change the licensing obligation or the price.
Oracle provides several built-in views for compliance monitoring. The primary view is DBA_FEATURE_USAGE_STATISTICS — query it across all Oracle instances to see every feature that has been used, including first and last usage dates. For Partitioning specifically, query DBA_PART_TABLES and DBA_PART_INDEXES. For TDE (Advanced Security), check V$ENCRYPTION_WALLET. For AWR usage (Diagnostics Pack), query DBA_HIST_SNAPSHOT for active snapshots. Run these queries quarterly and compare results against your licence entitlements. Any feature showing as “used” that you have not licensed represents compliance exposure that should be remediated — either by obtaining the licence or by disabling the feature.
The Diagnostics Pack is consistently the most common audit finding — DBAs generate AWR reports as a standard troubleshooting practice without awareness of the licensing implication. The second most common finding is Advanced Security triggered by TDE encryption, which is increasingly enabled by default in cloud environments for data-at-rest protection. The third is Partitioning, where application installers create partitioned tables during deployment. Together, these three inadvertently used options can generate audit exposure of $200,000–$500,000+ per instance (licence fees plus back-support). The most effective prevention is implementing CONTROL_MANAGEMENT_PACK_ACCESS, auditing TDE wallet status, and reviewing application DDL for partitioning before deployment.