Oracle Database@AWS Exadata Licensing Explained in 2026 - ECPU, BYOL, Audit Surface, Contract Levers

What Database@AWS Exadata actually is, and what is licensed

Oracle Database@AWS - the renamed and expanded Database@hyperscaler product line - reached general availability for the Exadata Cloud@AWS service in late 2025 and is now sold across 12 AWS regions in 2026. The headline is that AWS customers can run Oracle Database Enterprise Edition (EE) on Exadata-class infrastructure deployed inside an AWS Availability Zone, billed via the AWS marketplace, and consumed under either License-Included or BYOL economics. The mechanics, and the licensing, are not what most AWS-side architects expect.

Oracle Database@AWS Exadata licensing uses the same underlying entitlements as ExaCC and ExaCS - Oracle Database EE on Exadata-class hardware, billed in ECPU - but the contractual surface is split between an AWS marketplace SKU (compute, storage, network) and an Oracle ordering document (the Oracle software, Universal Credits and Support Rewards). The split matters because each side carries a separate audit posture, a separate contract structure and a separate renewal timeline. Mis-modelling the split is the single most expensive mistake AWS Oracle customers make in 2026.

This article unpacks the full picture: the ECPU and OCPU pricing on AWS in 2026, the LI versus BYOL break-even maths, the options that ship included versus those that require separate entitlements, the audit surface, and the seven contract clauses to negotiate before signing. The wider Database@hyperscaler framework is in the Oracle Cloud Licensing Guide and the Database@AWS overview.

Architecture - the AWS side vs the Oracle side

Database@AWS deploys Exadata X10M or X11M infrastructure inside AWS Availability Zones, owned and operated by Oracle but priced through the AWS marketplace. The architectural split:

• AWS marketplace side: the Exadata infrastructure SKU, the compute (ECPU or OCPU), the storage allocation, intra-region networking, the VPC peering, and the AWS Direct Connect / PrivateLink that connects customer VPCs to the Oracle-managed subnet. Billed in USD by AWS, drawn down from the AWS Enterprise Discount Program (EDP) commit.
• Oracle side: the Oracle Database EE software, the database options (Partitioning, Advanced Security, Diagnostics Pack, Tuning Pack and the rest), the GoldenGate cross-region replication, the technical support entitlement, the Support Rewards earn rate, and the audit-defence carve-outs in the Oracle Master Agreement (OMA). Billed in Oracle Universal Credits or via the ordering document depending on the deal structure.

The two contractual surfaces interact at the SKU level: the AWS-side ECPU SKU includes the right to run Oracle Database EE on that ECPU footprint, but the rate is set by Oracle through the Oracle Master Agreement, not by AWS. The customer signs an OMA addendum that authorises Database@AWS consumption, and the Universal Credits draw down at the contract-negotiated rate.

The audit posture follows the same split. AWS audits the AWS-side billing (commit drawdown, marketplace usage). Oracle LMS audits the Oracle-side option footprint (DBA_FEATURE_USAGE_STATISTICS, V$OPTION, Multitenant PDB counts). Both audits can fire concurrently and they pull different evidence sets. The customer needs an audit-defence pack that covers both.

2026 Database@AWS Exadata pricing - ECPU, OCPU and storage

The 2026 published rate card for Database@AWS Exadata - on the License-Included path - is the same as Database@Azure ECPU pricing with a small AWS marketplace administration uplift. The headline rates (US East / US West regions):

The minimum-activation rule mirrors ExaCC: 8 ECPUs per cluster on the Quarter Rack. A Half Rack activates from 16 ECPUs. A Full Rack from 32 ECPUs. The cluster runs continuously and bills 24x7 unless explicitly stopped via the API - and stop/start does interrupt running connections, so most production workloads run continuously.

The Universal Credits drawdown is interesting: customers with Oracle Universal Credits can spend Universal Credits against Database@AWS, but the AWS marketplace SKU is billed at AWS's commercial rate plus the Oracle software charge. The Universal Credits cover the Oracle software charge; AWS bills the infrastructure separately. Customers without OCI Universal Credits pay the full retail Database@AWS rate via the AWS bill.

BYOL vs License-Included on Database@AWS Exadata - the break-even

The BYOL economics on Database@AWS follow the standard Oracle BYOL ratio: 1 Oracle Database EE Processor entitlement = 4 ECPUs of compute. That converts a Processor-licensed BYOL pool into Database@AWS ECPU coverage at a 1:4 ratio. The break-even between BYOL and LI is the price differential between the two SKU lines.

Worked example - 32 ECPU Exadata X11M Quarter Rack, 24x7 production workload, 5-year horizon:

• License-Included path: 32 ECPU x $2.40/hr x 8,760 hrs/year = $672,768 annual. 5-year = $3,363,840. No BYOL pool required.
• BYOL path: 32 ECPU / 4 = 8 Oracle Database EE Processors required. List price $47,500 / Processor = $380,000 BYOL pool acquisition. Plus annual 22% support = $83,600/year. Plus Database@AWS BYOL rate at $0.99/ECPU-hr x 32 x 8,760 = $277,452/year. 5-year total = $380,000 + (83,600 + 277,452) * 5 = $380,000 + $1,805,260 = $2,185,260.
• Saving on BYOL: $1.18M over 5 years on a single Quarter Rack. The break-even crosses at 14-18 months depending on the discount achieved on the BYOL Processor pool acquisition.

BYOL pays off above 50% steady-state utilisation. License-Included pays off below 30% utilisation. Customers with intermittent dev/test consumption should mix - LI for the dev/test ECPUs (start-and-stop to minimise drawdown), BYOL for the 24x7 production ECPUs. The contract needs to permit the mix, which is the first negotiation lever in the BYOL contract section.

The detailed BYOL portability rules across Database@hyperscaler platforms are in the Multi-Cloud BYOL rules article; the AWS-vs-Azure-vs-GCP comparison maths sits in the Exadata OCI vs ExaCC vs Database@Azure decision matrix.

Which options are included on Database@AWS Exadata

Database@AWS License-Included pricing is the most generous Oracle option bundle in the Database@hyperscaler family. The included options under the LI SKU:

• Partitioning
• Advanced Security (Transparent Data Encryption + Database Vault)
• Diagnostics Pack
• Tuning Pack
• Real Application Testing
• Database In-Memory
• Advanced Compression
• Active Data Guard
• Real Application Clusters (RAC) - cell-pair RAC on the Quarter Rack and above
• Multitenant - unlimited PDBs on the platform
• Spatial & Graph
• OLAP

Not included on LI (require separate entitlement):

• GoldenGate cross-region replication
• Application Express (APEX) - included for development, separate licensing for production multi-user APEX deployments
• Oracle Machine Learning extensions beyond the base ADB-native ML set
• Vector Search at extreme scales (the base 23ai Vector Search is included; large dedicated AI workloads need ML add-ons)

On BYOL: the customer brings their own EE Processor entitlements and must separately licence each option they intend to use. The included Diagnostics Pack and Tuning Pack on LI become chargeable BYOL items - $7,500/Processor each at list. The audit posture is identical to on-prem Exadata: a single usage event in DBA_FEATURE_USAGE_STATISTICS triggers full-cluster option scope.

Database@AWS vs RDS for Oracle vs ExaCC - decision matrix

The AWS-resident Oracle options for an enterprise buyer in 2026 are now three: Amazon RDS for Oracle, Database@AWS Exadata, and (for customers retaining on-premise control) ExaCC. The decision matrix:

The pattern: workloads under 10TB and with no Exadata-feature dependency stay on RDS; workloads above 10TB or that need Smart Scan / HCC / In-Memory / RAC move to Database@AWS Exadata; workloads that need on-premise data residency stay on ExaCC. The Database@AWS Exadata sweet spot is the migrate-from-on-prem-Exadata scenario where the customer wants AWS-native ecosystem integration without losing the Exadata feature set.

The detailed RDS vs Database@AWS economics are in the Database@AWS vs RDS comparison; the on-prem-vs-cloud Exadata decision is in the Exadata on-prem vs ExaCC vs ExaCS piece.

Database@AWS audit surface - what Oracle LMS pulls

Oracle LMS's 2026 audit protocol for Database@AWS Exadata pulls the following evidence set:

1. DBA_FEATURE_USAGE_STATISTICS for every PDB on every database on the cluster.
2. V$OPTION showing the option binaries installed (which on Exadata is the full option set).
3. PDB count per CDB - relevant on BYOL where Multitenant is a separate entitlement.
4. The AWS marketplace usage history showing ECPU activation and stop/start patterns.
5. The Oracle ordering document and the OMA addendum that authorises Database@AWS consumption.
6. The Universal Credits drawdown ledger showing the Oracle-software consumption rate.
7. The Support Rewards earn ledger - this surface is new in 2026 and Oracle is auditing the earn-and-burn against the contract terms aggressively.

The cross-audit risk: AWS and Oracle audits can fire concurrently against the same Database@AWS estate. AWS audits the marketplace billing; Oracle audits the option footprint. The combined remediation surface on a $5M annual Database@AWS spend typically nets to $1.2M-$2.8M of exposure if the customer has not run a pre-emptive review. The defensive pattern is the same as ExaCC: pre-audit diagnostic across DBA_FEATURE_USAGE_STATISTICS, option disable where unused, full-pool licensing where used, and contract carve-outs for development-and-testing usage.

The audit-defence framework is in the Oracle Audit Guide; the option-audit specifics are in the Audit Defense service.

Seven Database@AWS contract levers to negotiate

The Database@AWS contract is materially negotiable in 2026. Oracle's cloud-deal team is incentivised on Database@hyperscaler bookings and will trade against a long list of customer asks. The seven highest-impact levers:

1. ECPU rate cap. Lock the ECPU LI rate at the contract price for the life of the deal (3-5 years). Standard Oracle behaviour is to walk the rate up 5-8% annually at renewal.
2. BYOL/LI mix permission. Get explicit contract permission to mix BYOL and LI ECPUs on the same Database@AWS cluster, with quarterly reconciliation. Without the clause, Oracle's default is single-mode-per-cluster.
3. Stop/start credit refund. Negotiate a refund clause for stopped-cluster periods. The default contract bills 24x7 regardless. A stop/start refund clause is achievable on multi-million-dollar Database@AWS deals.
4. Support Rewards 35c per $1. The standard rate is 25c per $1 of OCI commit. The 35c rate is achievable on Database@AWS commits above $2M annual.
5. Audit scope carve-out. Limit the LMS audit scope to a defined script set and a defined database list. The carve-out prevents Oracle from expanding the audit to the broader AWS estate or to non-Oracle workloads incidentally on the platform.
6. Exit clause - data-migration credit. Negotiate a one-time data-migration credit usable in the final 6 months of the contract. This funds the egress and the destination-platform compression conversion if the customer decides to exit Database@AWS.
7. Cross-cloud GoldenGate replication carve-out. If the architecture includes GoldenGate from Database@AWS to Database@Azure or to on-prem, get the cross-cloud replication entitled at a reduced rate. Standard Oracle pricing treats this as full GoldenGate Processor licensing on both sides.

The wider negotiation playbook is in the Oracle Negotiation Guide; the Universal Credits framework is in the Oracle Cloud Licensing Guide; cluster-level cost optimisation is in the Dedicated Region cost optimisation piece.

What to do next on Database@AWS Exadata

Database@AWS Exadata is the right platform for AWS-resident enterprise Oracle workloads that need Exadata features and Multi-AZ HA. The economics work if - and only if - the BYOL/LI mix is right-sized for the workload utilisation profile, and the contract carries the seven levers above. The default Oracle quote does not include them; they have to be negotiated in.

The action sequence we recommend for any 2026 Database@AWS evaluation:

1. Run the workload profile - utilisation, peak ECPU, off-peak ECPU, dev/test versus production split.
2. Model BYOL versus LI across the workload mix. Customers without an existing BYOL pool typically buy a starter BYOL pool sized for production and use LI for dev/test.
3. Build the audit-defence pack before signing the OMA addendum. Lock the option scope contractually.
4. Negotiate the seven contract levers as a single package. Oracle's deal team will trade on 4-5 of them at typical enterprise deal sizes.
5. Run a 12-month post-signing review to confirm the BYOL/LI mix is still optimal. Workloads shift; the contract should permit quarterly rebalance.

For deal-specific support, the independent Cloud & OCI Advisory, Contract Negotiation and Licence Optimisation services run this end-to-end. Further reading: Database@AWS guide, Database@Azure pricing benchmarks, Database@Google Cloud guide, Support Cost Reduction Guide.

Frequently asked questions

How is Oracle Database@AWS Exadata licensed differently from Amazon RDS for Oracle?

RDS for Oracle uses the standard 1 Oracle Database EE Processor = 2 AWS vCPU BYOL ratio and does not give Exadata features (Smart Scan, HCC, Storage Indexes). Database@AWS Exadata uses the 1 EE Processor = 4 ECPU ratio, includes the full Exadata feature set, supports up to 1.5PB databases, and earns Support Rewards at 25c per $1 of commit. RDS is for smaller OLTP workloads; Database@AWS is for production-grade workloads that need the Exadata feature set.

What is the Database@AWS ECPU price in 2026?

The 2026 published License-Included rate is $2.40 per ECPU-hour on X11M and $2.19 on X10M, with a 24x7 billing model unless the cluster is explicitly stopped. The BYOL rate is $0.99 / ECPU-hr on X11M and $0.85 on X10M. The minimum activation is 8 ECPUs on a Quarter Rack. Discounts of 20-35% are achievable on Database@AWS deals above $1M annual.

Does Database@AWS earn Oracle Support Rewards?

Yes. The standard rate is 25c per $1 of OCI commit, and Database@AWS Universal Credits drawdowns qualify. Customers with $2M+ Database@AWS commits routinely negotiate the rate to 35c per $1. The Support Rewards offset the on-premise Oracle support invoice up to 100% in some cases - one of the strongest economic levers in the Database@AWS deal model.

Can I bring my existing Oracle Database EE licences to Database@AWS Exadata?

Yes. The BYOL ratio is 1 Oracle Database EE Processor = 4 ECPUs. Each option you intend to use must be separately entitled (Partitioning, Advanced Security, Diagnostics Pack, Tuning Pack, etc.). The Database@AWS BYOL ECPU rate at $0.99/hr is materially cheaper than the LI rate, but you carry the audit exposure of the on-premise option footprint.

What is the audit risk on Database@AWS Exadata?

The audit surface is the standard Oracle LMS option scope - DBA_FEATURE_USAGE_STATISTICS, V$OPTION, PDB counts and the OMA addendum. Concurrently, AWS may audit the marketplace billing. On a $5M Database@AWS spend, the typical unallocated option exposure ranges $1.2M to $2.8M if no pre-emptive review has been done. The defensive pattern is identical to on-prem Exadata: option disable where unused, full-pool licensing where used, and a contract audit carve-out clause.

Related Oracle licensing reading