Oracle Database Licensing for Oracle E-Business Suite on AWS
You typically do not need separate Oracle Database licenses when running Oracle E-Business Suite (EBS) on AWS—provided you stay within Oracle’s clearly defined restricted-use licensing conditions.
However, to remain compliant, it’s crucial to understand Oracle’s specific guidelines about included Oracle Database licenses.
Here’s a step-by-step explanation of these conditions and practical guidance on when additional Oracle Database licenses may be needed.
Read Oracle on AWS Licensing FAQs 3 of 4.
Step 1: Understanding Restricted-Use Database Licenses Included with EBS
Oracle EBS licensing includes a restricted-use license for Oracle Database Enterprise Edition (EE), specifically for:
- Hosting the EBS database exclusively.
- Limited to EBS-related data and approved integrations only.
This means clearly:
- No additional Database licenses are required for standard EBS database usage.
- It is no use for non-EBS databases, custom schemas, or applications without separate licenses.
Step 2: Identifying Allowed vs. Restricted Database Usage
Allowed (No Extra DB Licenses Required):
✅ Standard EBS database
✅ Minor modifications (reports, standard extensions using Oracle’s interfaces)
✅ Certified integrations allowed by Oracle
Not Allowed (Additional DB Licenses Required):
❌ Non-EBS schemas or applications hosted on the same database
❌ Major schema customizations clearly outside Oracle guidelines
❌ Custom-developed applications running alongside EBS on the same DB instance
Step 3: Clarifying Levels of Database Customizations
Oracle clearly defines allowable customization levels for EBS databases:
| Customization Level | DB License Clearly Needed? | Clearly Explained Example |
|---|---|---|
| No Customizations | ❌ No (Included in EBS) | Standard out-of-the-box EBS |
| Minor Customizations (Reports, standard forms, interfaces) | ❌ No (Included in EBS) | Adding standard EBS reports, forms, or minor configurations |
| Major Customizations (Schema changes, custom tables, triggers) | ✅ Yes (Full DB License required) | Adding custom schemas or non-EBS tables clearly outside Oracle’s guidelines |
Important Clearly Stated:
If you clearly exceed Oracle’s permitted EBS database customization boundaries, Oracle will require you to purchase full-use Oracle Database EE licenses for that AWS instance.
Step 4: Calculating CPU Licensing Requirements (When Full License Required)
If additional Oracle DB EE licenses are required (due to significant customizations or non-EBS use), licensing rules follow Oracle’s standard AWS policy:
- 2 AWS vCPUs (hyper-threaded) = 1 Processor license clearly required
- No Oracle core factor adjustments on AWS apply.
Practical Example Clearly Explained:
- AWS EC2 instance running EBS database with significant custom schemas:
- 16 vCPUs ÷ 2 = 8 Oracle Database EE Processor licenses required separately.
Typical Scenario (Clearly Explained):
- Most standard EBS deployments avoid this scenario and require no separate DB licensing.
Step 5: Understanding Included WebLogic (Oracle IAS) Licenses
Oracle EBS also clearly includes a restricted-use WebLogic Server license (Oracle Internet Application Server):
- Limited to hosting EBS application tiers only.
- No separate WebLogic licensing is required unless non-EBS applications are hosted on the same WebLogic instance.
Clear Example Explained:
- Standard EBS forms/reports running on included WebLogic: no extra license.
- Deploying a custom Java application clearly alongside EBS forms/reports on WebLogic: Additional WebLogic licenses are required.
Read Licensing Oracle E-Business Suite (EBS) on AWS.
Step 6: Sizing and Reasonable Usage of Included Database Licenses
Oracle’s EBS included licenses have no clearly defined upper CPU or capacity limit, but:
- Avoid excessively large database instances beyond reasonable EBS requirements (e.g., using enormous AWS EC2 instances far exceeding standard sizing recommendations).
- While typically not a problem, clearly excessive sizing may trigger scrutiny during an Oracle audit.
Practical Advice Clearly Explained:
- Size your AWS EC2 instance clearly to match typical EBS workloads reasonably.
- Document sizing decisions for audits (performance or workload justification).
Practical Example Scenarios Clearly Illustrated
| Scenario | Additional DB License Clearly Needed? |
|---|---|
| Additional DB License Needed? | ❌ No (Included license sufficient) |
| Adding minor EBS reports or standard custom forms clearly within Oracle guidelines | ❌ No (Included license sufficient) |
| Hosting custom non-EBS schema/application clearly on same DB | ✅ Yes (Separate full DB EE license required) |
| Major schema customizations clearly outside EBS guidelines | ✅ Yes (Separate full DB EE license required) |
Summarized Checklist: Oracle Database Licensing for EBS on AWS
✅ Standard EBS DB usage covered by included licenses
✅ Minor customizations allowed (reports, standard extensions)
❌ No non-EBS schemas/apps without separate DB EE licenses
❌ No major schema changes clearly beyond Oracle guidelines without separate DB EE licenses
✅ The size of the database EC2 instance reasonably (no clearly defined upper limit but justified in audits)
✅ Clearly document deployments and customizations for Oracle audits
Common Misunderstandings Clarified
- Misconception: “AWS always requires separate Oracle DB licenses for EBS.”
Clarification: Included restricted-use DB licenses cover standard EBS deployments—no extra licenses are needed unless extensively customized or non-EBS apps are added. - Misconception: “Minor EBS customizations require separate DB licenses.”
Clarification: Oracle allows standard minor customizations without additional licenses. - Misconception: “WebLogic included with EBS can host any Java app without extra licenses.”
Clarification: Limited to EBS-specific usage; separate licenses are required for non-EBS apps.
Read Licensing PeopleSoft, JD Edwards, Siebel, and Other Oracle Apps on AWS.
Conclusion: Clearly Understanding Oracle DB Licensing for EBS on AWS
Oracle provides restricted-use Oracle Database EE licenses included with your Oracle E-Business Suite license, fully covering standard EBS database deployments on AWS. You do not require additional Oracle Database licenses unless you:
- Significantly customize schemas clearly beyond Oracle-approved guidelines, or
- Host non-EBS applications or schemas on the same database instance.
Adhering to Oracle’s defined restricted-use conditions ensures no additional database licensing costs.
