Oracle Licensing on AWS RDS: Best Practices and Recommendations

2 vCPUs= 1 Oracle processor licence on AWS (with hyper-threading)

8 vCPUsmaximum allowed for Oracle SE2 on AWS RDS

SE2 OnlyLicence Included model — Enterprise Edition requires BYOL

2×licence requirement for Multi-AZ deployments under BYOL

Understanding the Cloud Licensing Challenge

Running an Oracle Database in a cloud environment such as AWS RDS introduces complexity beyond on-premises licensing. Oracle treats AWS as an "Authorised Cloud Environment" with specific rules governing the counting of processor licences.

Unlike on-premises — where physical cores and Oracle's core factor table determine licence needs — in AWS, each virtual CPU (vCPU) has a defined licensing value. For AWS RDS (and EC2), Oracle's policy counts two vCPUs as one Oracle processor licence (assuming hyper-threading is enabled). This effectively halves the licence requirement compared to physical core counts, but the standard core factor discounts do not apply in the cloud.

Standard Edition 2 limits: Oracle SE2 on AWS counts up to 4 vCPUs as one socket (one licence), and every additional 4 vCPUs as another socket. However, Oracle imposes a hard limit — SE2 can only be licensed on instances with up to 8 vCPUs in AWS. Large RDS instances (more than 8 vCPUs) cannot use SE2, forcing those workloads to Enterprise Edition or requiring architectural changes.

Licence Included vs BYOL: Two Models on AWS RDS

Amazon RDS for Oracle offers two licensing options, and choosing the right one has major cost and compliance implications:

Simple

📦 Licence Included (LI)

Oracle licence bundled into the RDS hourly price
Available for Standard Edition 2 (SE2) only
No need to procure licences from Oracle
Pay-as-you-go — no upfront licence investment
AWS handles licence and support in background
Internal use only — no third-party hosting rights
Ideal for dev/test, short-term, or variable workloads

Flexible

🔑 Bring Your Own Licence (BYOL)

Use your existing Oracle Database licences on RDS
Required for Enterprise Edition (EE) on RDS
Lower AWS hourly cost (excludes licence fees)
You bear licence ownership and Oracle Support costs
Access to all features you're licensed for (including EE options)
Must licence standby instances in Multi-AZ deployments
Ideal for stable production workloads with existing licences

Detailed Comparison

Aspect	Licence Included (LI)	Bring Your Own Licence (BYOL)
Oracle Editions	Standard Edition 2 only	SE2 or Enterprise Edition
Licence Cost	Included in RDS hourly price	Use existing licences or purchase from Oracle
Cost Model	Pay-as-you-go (no upfront)	Sunk licence cost + Oracle support annually
Support & Patching	AWS handles support	You maintain Oracle Support contract
Feature Usage	Limited to SE2 features	All Oracle features you're licensed for
Multi-AZ/DR	Standby covered by AWS service	Must licence primary and standby instances
Usage Restrictions	Internal business use only	Subject to your Oracle agreement terms

Many enterprises use a mix: deploy Standard Edition workloads on LI for convenience, while using BYOL for Enterprise Edition or steady production loads where they already own licences. Always evaluate total cost of ownership — depending on your Oracle contract and usage duration, one model can be substantially cheaper than the other.

Oracle's Cloud Licensing Rules on AWS RDS

When using BYOL on AWS RDS, enterprises must follow Oracle's cloud licensing policy to remain compliant. Key rules include:

Processor Licence Calculation

For AWS, each pair of vCPUs counts as one Oracle processor licence (because AWS instances use hyper-threaded cores). For example, a DB instance with 8 vCPUs requires 4 Oracle processor licences (8 ÷ 2 = 4). If an instance type does not use hyper-threading (unusual in AWS), then one vCPU = 1 licence.

No Core Factor

Oracle's standard Core Factor table (which gives discounts for certain CPUs on-prem) does not apply in cloud environments. In AWS, it's a flat rule (0.5 licence per vCPU for EE) regardless of CPU type.

Standard Edition Socket Licensing

Instances with up to 4 vCPUs count as 1 socket (1 SE2 licence), and each additional 4 vCPUs is another socket. Oracle limits SE2 usage to a maximum of 8 vCPUs on AWS. Exceeding this puts you out of compliance.

In an RDS Multi-AZ deployment, AWS keeps a standby database in a different AZ. Oracle considers that standby as "installed and running" — so if you BYOL, you must have a licence for the standby as well. Multi-AZ effectively doubles the licence requirement. The same applies to read replicas. A backup snapshot does not require a licence until restored and running.

Named User Plus (NUP) Minimums

If you licence Oracle by NUP (instead of per processor), cloud instances must still meet Oracle's minimum user counts. For SE2 in the cloud, Oracle requires at least 10 NUP licences per 8 vCPUs. However, most enterprises use processor licensing for server environments like RDS.

Use AWS's Licence Manager service to track your Oracle BYOL usage. It can help discover RDS instances, track vCPU counts against your licence pool, and alert you if you exceed purchased licences or if an instance is out of policy (e.g., an oversised SE2 instance). This is not a substitute for Oracle audits, but helps maintain ongoing visibility.

Need Help with Oracle Licensing on AWS?

Redress Compliance provides completely vendor-independent Oracle advisory services. We help enterprises navigate cloud licensing rules, optimise costs across LI and BYOL models, and ensure audit readiness.

Oracle Licence Management 📅 Book a Meeting

Cost Considerations and Optimisation

Licence Included for Flexibility: The LI model's biggest advantage is no upfront cost. You pay a higher hourly rate, but can turn off or scale down the database at any time. This is economically efficient for short-term, unpredictable, or dev/test workloads. AWS also offers reserved instance pricing for RDS — a 1-year or 3-year reserved instance can significantly reduce the hourly cost including the licence portion.

BYOL for Long-Term Savings: If you already own Oracle licences (or plan to run a workload for many years), BYOL can be more cost-effective. The AWS hourly rate is lower because you're only paying for infrastructure and management. Enterprises with an Oracle Enterprise Agreement or ULA often leverage BYOL to extend on-premises licences into the cloud. Be cautious: if your ULA doesn't explicitly allow cloud use, clarify with Oracle first.

Edition Downgrade for Savings: Many workloads running Oracle Enterprise Edition on-premises can potentially switch to Standard Edition 2 in the cloud if they don't use EE-only features. This can be a huge cost saver — for instance, an 8-core EE deployment (potentially $380,000 in licence fees) could be migrated to SE2 on AWS RDS using LI pricing.

Hidden cost pitfall: Some Oracle features (Spatial, Advanced Security, Diagnostic/Tuning packs) are separately licensed in Enterprise Edition. On RDS, these can be enabled, but if you're BYOL, you must own the proper licences. Another pitfall: it's easy to spin up multiple RDS instances for QA/testing that each consume a licence. Use Licence Included for ephemeral non-production databases and BYOL only for production or long-running systems.

Compliance Risks and Best Practices

Oracle licensing compliance is as important on AWS as it is on-premises. Moving to AWS can draw Oracle's attention in audits. Here are common pitfalls:

Overlooking Support Policies

Ensure any Oracle licences you bring to AWS are fully backed by active Oracle support contracts. Oracle requires that licences used in the cloud follow the same rules as on-prem — including having a current support subscription.

Neglecting Licence Tracking

AWS won't prevent you from launching an oversised instance or extra copies you aren't licensed for. Use tagging, AWS Licence Manager, and internal record-keeping to map each BYOL instance to an Oracle licence allocation. Implement a quarterly internal audit of Oracle deployments on AWS.

Assuming Audits Won't Happen

Your Oracle licence agreement likely gives Oracle the right to audit your use of their software anywhere, including in AWS. Oracle has taken legal action in cases of suspected cloud licence misuse. Keep detailed records of each RDS instance (edition, vCPUs, usage duration) and how they map to licences.

Ignoring Multi-AZ Implications

If you deploy Multi-AZ or have read replicas with BYOL, your licence needs effectively double. A common mistake is treating the standby as "free." Always budget for additional licences if you plan for high availability.

Not Restricting Instance Sizes

An engineer can accidentally launch a large DB instance exceeding what your SE2 licence allows. Enforce policies or AWS IAM permissions to prevent this. Consider AWS Config rules to flag non-compliant setups.

Recommendations (Expert Tips)

✅ 10 Expert Recommendations

Assess Your Current Licences and Needs: Do a full inventory of Oracle licences. Determine which apps truly require Enterprise Edition vs SE2 to guide BYOL vs LI decisions.
Leverage Licence Included for Non-Critical Systems: Use LI for transient, dev, or variable workloads. Turn off instances when not in use — billing stops when stopped.
Use BYOL Strategically: Allocate owned licences to stable, production RDS instances running 24/7. Document each BYOL deployment in an internal register.
Right-Size and Standardise Instances: Choose the smallest instance meeting performance needs, especially for SE2 with its 8-vCPU limit. Scale out with multiple smaller instances rather than one large one.
Monitor with AWS Licence Manager: Configure it with your Oracle licence entitlements and let it track RDS usage. It catches obvious over-deployments and sends alerts.
Keep Oracle Support Active: Maintain active Oracle support for BYOL licences. Lack of support raises flags in audits and may mean non-compliance.
Plan for Multi-AZ and DR Licensing: Factor in double licence requirements from the start. Consider using LI for standby/DR instances to simplify compliance.
Educate and Govern Cloud Deployments: Train cloud architects on Oracle licensing basics. Establish guardrails via AWS IAM policies to prevent non-compliant instance launches.
Evaluate Oracle's Cloud Programs: Stay informed on Oracle's licensing programs. Understanding ULA certification for AWS or Oracle Cloud alternatives gives negotiation leverage.
Regularly Review Costs and Compliance: Schedule annual or semi-annual reviews. Verify the licensing model remains optimal and catch any compliance drift before Oracle does.

Checklist: 5 Actions to Take

📋 Oracle on AWS RDS Deployment Checklist

Inventory and Classify Workloads: List all Oracle databases planned for AWS RDS. Note required edition (SE2 vs EE), vCPU needs, and whether production/test/DR. This informs the licensing model for each.
Choose the RDS Licensing Model per DB: Use LI for SE2 workloads needing flexibility or short-term use. Use BYOL for EE requirements or when you have existing licences. Record decisions.
Validate Compliance Requirements: For BYOL, calculate required Oracle licences (2 vCPU = 1 licence). Ensure you have enough licences under support. For SE2, verify the instance class doesn't exceed 8 vCPUs.
Implement Governance and Tools: Set up AWS Licence Manager with your Oracle licence counts. Establish tagging conventions. Configure AWS Config rules to detect non-compliant scenarios.
Deploy and Monitor: Launch instances as planned. Continuously monitor via Licence Manager reports, CloudWatch metrics, and monthly bills. Update your internal licence inventory as instances start or stop.

FAQ

Can we run Oracle Enterprise Edition on AWS RDS under the Licence Included model?

No. The Licence Included option on Amazon RDS only covers Oracle Standard Edition (specifically SE2). If you need Oracle Enterprise Edition on RDS, you must use the BYOL model and provide your own EE licences. AWS will let you create RDS instances with EE only if BYOL is selected.

How do I calculate how many Oracle licences I need for an AWS RDS instance?

Oracle's cloud licensing policy for AWS says to count two vCPUs as one Oracle processor licence (with hyper-threading on). For example, a DB instance with 8 vCPUs would require 4 Oracle processor licences. Standard Edition 2 is licensed per socket: up to 4 vCPUs = 1 licence, 5–8 vCPUs = 2 licences (with a maximum of 8 vCPUs allowed for SE2 on AWS RDS).

Which is more cost-effective — Licence Included or BYOL on AWS RDS?

It depends on your situation. Licence Included is generally better for short-term or small deployments where you don't already own licences. BYOL can be more cost-effective for long-running workloads if you already own licences, as the AWS hourly rate is lower. For long-lived production systems, BYOL may cost less over a multi-year period. Always compare the AWS cost difference and factor in Oracle support fees when considering BYOL.

Do I need to licence the standby database in a Multi-AZ RDS deployment?

Yes, if you are using BYOL. Oracle requires that any running instance of its database software be licensed. In a Multi-AZ RDS deployment, the standby is continuously running and synced, so it requires a licence — effectively doubling your licence needs. If you use Licence Included, AWS's pricing already covers both primary and standby.

Can Oracle audit our use of Oracle on AWS RDS?

Absolutely. Oracle can audit your use of their software anywhere, including in AWS. Keep records of each RDS instance (edition, vCPUs, usage duration, licence model). Use AWS Licence Manager reports for an up-to-date picture. Make sure you adhere to Oracle cloud licensing rules. Having documentation and using the tools described will put you in a strong position during an audit.

Ensure Oracle Compliance on AWS

Our independent Oracle licensing experts help enterprises navigate AWS RDS licensing, optimise costs between LI and BYOL models, and prepare for Oracle audits — ensuring full compliance without overspending.

Oracle Licence Management Contact Us

Explore Oracle Advisory Services

📊 Oracle Licence Management 🛡️ Oracle Audit Defence 📋 Oracle Contract Negotiation ☁️ Oracle ULA Optimisation

Fredrik Filipsson

Co-Founder @ Redress Compliance

20+ years in enterprise software licensing. Former IBM, SAP, and Oracle. 11 years as an independent consultant advising hundreds of Fortune 500 companies on Oracle, Microsoft, SAP, IBM, Salesforce, and ServiceNow licensing, contract negotiations, and cost optimisation.

View All Posts