Bring Your Own License (BYOL) for Oracle on AWS
Bring Your Own License (BYOL) allows you to use Oracle software licenses you already own on AWS infrastructure. In this scenario, AWS is another data center environment where you deploy Oracle products under your existing licensing agreements.
This article outlines key points, provides practical examples, and helps you understand licensing obligations and compliance requirements when choosing the BYOL model for Oracle on AWS.
Read Oracle on AWS Licensing FAQs 1 of 4
What is BYOL for Oracle on AWS?
Definition:
- BYOL refers to deploying Oracle software on AWS using licenses you have previously purchased from Oracle or acquired through enterprise agreements.
- AWS provides the infrastructure (EC2, RDS), but the license entitlements remain your responsibility.
Key Points for Oracle BYOL on AWS
1. Licensing Based on vCPU Counting Rules
To determine how many licenses you need on AWS, Oracle applies a specific cloud-based licensing formula:
- 2 AWS vCPUs = 1 Oracle Processor license (when hyper-threading is enabled, as is typical).
Practical Example:
- Deploying Oracle Database Enterprise Edition on an EC2 instance with 8 vCPUs:
- Calculation: 8 vCPUs ÷ 2 = 4 Oracle Processor licenses required.
Why It Matters:
- You must account for vCPU-based licensing to maintain compliance.
- Miscounting can lead to significant licensing shortfalls and audit risks.
2. BYOL is Applicable to All Oracle Software
BYOL is the standard licensing model for most Oracle products on AWS, including:
- Oracle Database Enterprise Edition (EE)
- Oracle Middleware (WebLogic Server, SOA Suite, etc.)
- Oracle Applications (E-Business Suite, PeopleSoft, Siebel, JD Edwards, etc.)
Important Note:
- AWS does not provide bundled licenses for Oracle Enterprise Edition or Oracle Middleware products—BYOL is required.
- The License-Included model (provided by AWS) is limited to specific services, such as Oracle Standard Edition 2 on Amazon RDS.
Practical Example:
- Deploying Oracle WebLogic Server on AWS EC2:
- Requires BYOL—you must own licenses before deployment.
3. Oracle Support Requirements for BYOL Licenses
When using Oracle software via BYOL on AWS:
- You must maintain active Oracle Support contracts for your licenses.
- Oracle explicitly requires active support agreements for licenses deployed in cloud environments (for updates, patches, and compliance).
Practical Example:
- You deploy Oracle Database EE on AWS:
- You must maintain Oracle support contracts for these licenses.
- No special “cloud-specific” license is required beyond standard licensing agreements with Oracle.
Read the Oracle “License Included” Model on AWS.
4. No Separate Oracle “License Mobility” Program Required
Unlike some vendors (such as Microsoft), Oracle does not require special “license mobility” programs to move licenses to AWS:
- Your existing valid Oracle license agreements already grant rights to deploy on AWS (treated as an “Authorized Cloud Environment”).
- However, documenting this deployment internally is strongly recommended to avoid any ambiguity during audits.
Important Consideration:
- Check older Oracle contracts carefully for “outsourcing” or “third-party data center” clauses—older agreements might have limitations requiring Oracle’s consent.
- Most recent Oracle agreements explicitly recognize AWS as an authorized deployment environment.
Best Practice:
- Maintain internal documentation indicating license allocations to AWS instances.
- If uncertain, proactively inform Oracle or obtain written confirmation for older contract clauses.
Read Oracle Licensing Models on AWS.
Practical Summary: Oracle BYOL on AWS—Key Points
| Aspect of BYOL Licensing | Key Point | Recommended Action |
|---|---|---|
| vCPU-Based Licensing | 2 AWS vCPUs = 1 Oracle Processor license | Verify product and use BYOL |
| Applicable Products | All Oracle products (EE, Middleware, Apps) | Verify product and clearly use BYOL |
| Oracle Support Contracts | Active support required | Maintain active Oracle Support |
| License Mobility | No special mobility program required | Document AWS license allocation clearly |
Oracle BYOL Compliance Checklist on AWS
✅ Verify you own sufficient Oracle licenses for AWS deployments based on vCPU counts.
✅ Ensure Oracle Support contracts are active for all licenses deployed on AWS.
✅ document license allocations internally, linking licenses to specific AWS instances.
✅ Review older Oracle contracts for third-party data center clauses and proactively address if necessary.
Common Misunderstandings Corrected
- Misconception: “AWS provides bundled Oracle licenses for Enterprise Edition or Middleware.”
- Reality: BYOL is required for Oracle EE and Middleware; AWS offers bundled licenses only for specific cases (Oracle SE2 on RDS).
- Misconception: “Oracle requires a special license mobility program to deploy on AWS.”
- Reality: Oracle licenses inherently allow AWS deployments; no special mobility program is needed.
- Misconception: “No support contracts needed for Oracle BYOL licenses on AWS.”
- Reality: Active Oracle Support contracts remain required for all BYOL deployments.
Conclusion: Understanding Oracle BYOL Licensing on AWS
Grasping Oracle’s BYOL licensing model on AWS ensures you leverage existing Oracle investments effectively and maintain compliance. BYOL offers flexibility, cost efficiency, and ease of transition to AWS if it is carefully managed through proper license counting, documentation, and support maintenance.
