Running Oracle Software on AWS Outposts
AWS Outposts provides AWS cloud infrastructure directly within your data center. Essentially, it extends the AWS environment to your on-premises location. This offers significant benefits like low latency and data residency but introduces some nuances for Oracle licensing.
Here’s everything you need to know about running Oracle on AWS Outposts, clearly explained.
AWS Outposts and Oracle Licensing
AWS Outposts is physically located in your data center but managed entirely by AWS. Oracle views Outposts as an extension of AWS EC2 infrastructure. As a result, Oracle applies its Authorized Cloud Environment licensing rules to Outposts, not traditional on-premises licensing rules.
Key takeaway:
AWS Outposts does not qualify as traditional on-premises hardware under Oracle licensing policies.
How Oracle Licensing Works on AWS Outposts
Licensing Oracle on Outposts follows the same principles as licensing Oracle software in AWS regions:
- Cloud licensing rules apply:
- Oracle counts vCPUs rather than physical cores.
- Hyper-threading rule: Two vCPUs equal one Oracle Processor license.
- You cannot apply Oracle’s traditional core-factor table when licensing Outposts.
Practical example:
- Suppose you have an on-premises physical server with 16 Intel physical cores. Traditionally, applying Oracle’s 0.5 core factor would mean 8 Processor licenses.
- The equivalent AWS Outposts instance with 32 vCPUs (16 cores, hyper-threaded) would also require 8 Processor licenses under Oracle’s cloud licensing rules.
Thus, the license count may seem consistent, but ensure you always recalculate when moving workloads.
Read Oracle on AWS Licensing FAQs 4 of 4.
Bring Your Own License (BYOL) on AWS Outposts
Currently, Oracle software on AWS Outposts operates exclusively on a BYOL basis:
- No Oracle RDS option:
AWS Outposts does not offer Oracle-managed RDS. It only supports RDS for MySQL and PostgreSQL (as of 2025). - Deployment on EC2 instances:
If you want to run Oracle Database, Middleware, or applications like Oracle E-Business Suite (EBS), you’ll install these directly on Outposts EC2 instances using your own Oracle licenses.
Example:
- If you need Oracle Database on AWS Outposts, provision EC2 instances on Outposts hardware and install Oracle Database software using licenses you already own.
Read Moving Your Existing Oracle Licenses to AWS.
Important Licensing Considerations for AWS Outposts
Here are some critical considerations you should remember:
Hybrid Licensing Misconceptions
- AWS Outposts are physically located on-premises, which could lead to confusion.
- Some may mistakenly assume traditional on-premises licensing (with Oracle core factor) applies.
- Oracle explicitly states that AWS Outposts are licensed like standard cloud environments, not traditional on-premises hardware.
No Cost Advantage for Oracle Licensing
- Outposts can reduce AWS data transfer fees and provide low latency to other on-premises workloads.
- However, Oracle offers no special licensing discounts for Outpost.
- License requirements remain strictly tied to the number of vCPUs used on Outposts.
Support and Certification
- Oracle supports software running on AWS Outposts just as they support software running in AWS cloud regions.
- From Oracle’s support perspective, Outpost is identical to any AWS deployment.
Best practices for ensuring Oracle support compliance:
- Confirm operating system compatibility and supported Oracle software versions.
- When contacting Oracle support, describe your Outpost’s deployment as an AWS EC2 environment.
Read Running Oracle on VMware Cloud on AWS.
Cost and Capacity Planning with AWS Outposts and Oracle
Careful license and capacity planning is crucial when deploying Oracle on Outposts. Keep these factors in mind:
- vCPU Licensing Costs:
Oracle licensing costs directly scale with the number of vCPUs provisioned.
Example: A large Outpost instance with 64 vCPUs requires 32 Oracle Processor licenses under the 2:1 vCPU-to-license rule. - Recalculating Licenses from On-Premises Migrations:
If migrating Oracle workloads from traditional on-premises servers to AWS Outposts, recalculate licenses carefully. Example scenario:- Current on-premises: Intel-based server with 24 physical cores (core factor 0.5) requires 12 licenses.
- Equivalent AWS Outposts server: 48 vCPUs (24 cores, hyper-threaded) also requires 24 ÷ 2 = 12 licenses.
Though this example aligns neatly, verify these calculations each time.
- Document Your Licenses Clearly:
Maintain accurate internal records clearly showing license allocation to specific Outpost EC2 instances.
Accurate documentation is critical during Oracle license audits.
Practical Examples of Licensing Oracle Software on AWS Outposts
Here are clear examples of licensing Oracle products commonly deployed on Outposts:
Example 1: Oracle Database EE
- AWS Outposts EC2 instance with 16 vCPUs (8 cores hyper-threaded).
- Licensing calculation: 16 vCPUs ÷ 2 = 8 Processor licenses required.
Example 2: Oracle WebLogic (Middleware)
- AWS Outposts EC2 with multiple instances totaling 32 vCPUs.
- Licensing calculation: 32 vCPUs ÷ 2 = 16 Processor licenses required.
Example 3: Oracle E-Business Suite (EBS)
- EBS running on Outpost’s instance with eight vCPUs (4 cores).
- Licensing calculation: 8 vCPUs ÷ 2 = 4 Processor licenses required.
Always verify your vCPU count and document license allocation meticulously.
Common Misunderstandings About AWS Outposts and Oracle Licensing
Below are some frequent misconceptions clarified:
- Misconception: “AWS Outposts is in my data center, so on-prem core factor licensing applies.”
Clarification: Outposts explicitly follow cloud licensing rules, not traditional on-premises rules. - Misconception: “Oracle licensing might be cheaper on Outposts.”
Clarification: No special Oracle licensing discount or reduced cost is specific to Outposts. - Misconception: “Outposts might have Oracle license-included options like AWS RDS.”
Clarification: Oracle software on Outposts currently requires BYOL exclusively. RDS Oracle is not available on Outposts.
Best Practices Summary for Oracle Licensing on AWS Outposts
To ensure compliance and cost-effective management, follow these best practices clearly:
- Follow Cloud Licensing Rules: Count vCPUs (two per Oracle Processor license) without applying core factors.
- Maintain Accurate Internal Records: Document clearly which Oracle licenses cover specific AWS Outposts EC2 instances.
- Plan Licensing Costs Precisely: Forecast your Oracle license needs carefully when provisioning Outpost’s capacity.
- Maintain Oracle Support Continuously: Your Oracle software running on Outposts is fully supported; continue regular Oracle support payments and ensure compatibility.
- Communicate to Oracle: When engaging Oracle support, consistently describe Outpost deployments as AWS cloud infrastructure.
Conclusion: Licensing Oracle on AWS Outposts Clearly Defined
AWS Outposts offer valuable flexibility and performance advantages, effectively blending cloud benefits with your on-premises infrastructure. However, Oracle’s licensing model remains strictly tied to AWS cloud rules—meaning licenses are allocated by vCPU count, explicitly without core factors.
Understanding this distinction, clearly documenting license usage, and carefully planning your Oracle software deployments on Outposts will ensure compliance, manage costs effectively, and simplify future license audits.
In short, from Oracle’s perspective, treat AWS Outposts exactly like AWS EC2, clearly plan your Oracle license strategy around this, and leverage the full benefit of AWS infrastructure delivered directly into your data center.
