Oracle ULA (Unlimited License Agreement) offers a flexible, yet complex, licensing model for deploying Oracle software. Understanding the intricacies of ULA deployment on AWS is crucial for maximizing benefits and minimizing risks.
Deploying Oracle ULA on AWS requires careful contract management and strategic planning to maximize benefits and mitigate risks. Regularly review your contract terms and plan your deployments accordingly to ensure compliance and optimize your Oracle investments.
Initial Setup: One-time license fee plus 22% support fee.
Existing Licenses: Included in the ULA contract.
ULA Term: 1-5 years of unlimited software deployment on processors.
End of ULA Term: Renew with a new fee or exit with annual support.
Certification: Report deployment numbers to Oracle for verification to determine granted licenses.
Deployment on AWS: Deployments on AWS might not receive licenses, necessitating ULA renewal or new licenses.
Scalability: Unlimited deployment capability during the ULA term.
Flexibility: Potential to optimize costs and infrastructure.
Certification Complexity: Navigating the certification process to ensure accurate license counting.
Compliance Issues: Managing deployment within the terms of the ULA to avoid penalties.
Unlimited Deployment
During the ULA term, unlimited Oracle software deployment is allowed.
Territory Clause
Check which countries your software can be deployed in and select an AWS region accordingly.
End-of-Term Concerns
AWS deployments may not count towards ULA exit numbers, posing a risk of zero licenses if deployed 100% on AWS.
No Public Cloud - Standard Option
Deployments in third-party clouds do not count towards exit numbers.
Standard in 90% of Oracle ULA contracts.
Last 365 Average - Option
Certification counts the average number of deployments over the last 365 days.
Potential compliance challenges with recent high deployment rates.
Restricted Use Option
Certifications split into public cloud and on-premises licenses.
Complexity in managing Oracle software post-ULA.
Before you decide to utilise your ULA on AWS it is recommended to complete these steps to avoid getting caught out by licensing compliance issues.
Contract Review: Carefully review and negotiate the certification clause in your Oracle ULA or PULA contract.
Deployment Planning: Plan deployments to optimize licensing benefits and reduce compliance risks.
We have assessed 5,769 Oracle databases running on 3,163 hosts and 15,629 CPU cores in the last twelve months. The total license value - database and options used - exceeds $690 million, with $150 million in annual support fees (based on list prices).
Read moreManaging Oracle licenses on Amazon Web Services (AWS) can be complex. Whether you're looking to migrate existing systems or scale new deployments on AWS, it’s important to understand how Oracle’s licensing works to avoid compliance issues and unexpected costs. Here’s a breakdown of the options and considerations you need to be aware of when using Oracle on AWS.
Read more