To explain Oracle licensing on AWS, we need to talk about how Oracle licensing works in cloud. Oracle has defined 2 public cloud platforms as authorized as public cloud providers and have granted its Oracle customer special licensing rules. These 2 providers are Azure and AWS. If you are using any other public cloud provider, then normal on-premises Oracle licensing rules apply. It is important to note that Google or GCP is not authorized cloud provider and there is no difference in how to license Oracle in Google Cloud as it would be with any traditional hosting provider. This article is here to help you with licensing Oracle on AWS, we will cover both AWS EC2 Oracle licensing and AWS RDS for Oracle
If you run your Oracle database on an AWS EC2 instance, you must license the Oracle software based on the number of occupied sockets on the instance. Oracle’s Core Factor Table describes the number of Oracle licenses required for different CPU architectures. Oracle’s Cloud Licensing Policy does not apply to this table, so each core counts toward the number of Oracle licenses required. This policy applies to EC2 instances running Oracle applications and databases that are licensed according to their number of vCPUs.
If you have an existing Oracle license, you can transfer it to AWS instances and avoid the cost of buying new licenses. Keep in mind that Oracle often changes its licensing policy without notice, so you should always download the latest version of the policy document. Oracle representatives often claim that your license is incompatible with AWS EC2 instances, and that you must have Enterprise Edition licensing to use SE2 RDS instances.
While AWS has a number of different licensing options for Oracle on AWS, you can use this flexible licensing option to run your Oracle database on a single instance. As long as you use Oracle Standard Edition, you should only count one CPU per virtual core. In contrast, Oracle Enterprise Edition requires four-processor licenses for each eight vCPU. In addition, you can roll the RDS license costs into your hourly cost with Amazon. You can then scale RDS up or down depending on the needs of your workload.
AWS RDS for Oracle is a service that allows you to run your database on Amazon EC2. The advantages of this service include full control of your infrastructure, database environment, and operating system. You can choose which tools you use to manage your database and select all optional modules. However, you will need to be knowledgeable about all components and how to tune them to optimize performance. It can also be expensive, so you need to plan carefully.
Fortunately, AWS is in the approved list of cloud vendors for Oracle, so your existing Oracle licenses will work just fine on your Amazon RDS instances. The licensing documentation for each product contains the latest rules and regulations regarding licensing. For more information about the rules for your specific product, see the AWS RDS for Oracle licensing documentation. To get started, sign up for a free trial of AWS RDS for Oracle.
AWS RDS also provides a variety of options for tuning and diagnosing your Oracle database. Instances are backed by different physical CPU models. Each instance type offers preconfigured configurations of vCPUs and memory. They also vary in storage and networking capacity. You can choose from Compute Optimized, Memory Optimized, or Compute Optimized instance types. We recommend the Memory Optimized instance type. The R5B model is especially beneficial for performance monitoring, because it provides higher I/O throughput.
Amazon Web Services offers customers the option of running Oracle on Amazon EC2 Bare Metal. This allows customers to take advantage of the same support and scalability offered by AWS while providing an option for high-end performance. Generally, this option is advantageous for customers operating on a massive scale. It also provides licensing advantages over AWS. However, it is important to note that Oracle on AWS is considered a hosting partner, not a cloud provider.
Using Oracle on AWS and EC2 requires special licensing and compliance requirements. These requirements can be complicated and can bog down even the most well-intentioned Cloud migration efforts. TekStream can help enterprise organizations navigate the Oracle licensing process and find cost-saving opportunities. To help organizations choose the right cloud computing solution for their needs, our expert team will walk you through Oracle licensing on AWS and EC2.
Oracle Standard Edition One can be licensed on AWS and EC2 environments with four or more virtual cores, and for instances with eight or more virtual cores. AWS Optimize CPU program also allows customers to choose which number of vCPUs they would like. Customers can decide upfront how many vCPUs they need. However, customers must remember that Oracle databases require an Oracle license, which they need to purchase before setting up the EC2 environment.
You can use the License Manager API to manage Oracle licensing across your AWS accounts. This dashboard enables you to create licensing rules and attach them to resources in your member accounts. It also helps you track the usage of Oracle licenses across all of your AWS accounts. You can use the License Manager API to count the number of Oracle licenses that you currently have and to assign them to EC2 instances. This article will cover the basic steps to manage Oracle licensing on AWS.
Oracle is known for auditing their customers to ensure that they are following their license terms. The contract with Oracle does not permit running Oracle software in cloud environments without special licensing. The licensing is based on an extra-contractual policy document called the Cloud Policy. There are two public clouds that are defined by the Cloud Policy: Amazon Web Services (AWS) and Microsoft Azure. Oracle also provides VMs with licenses based on vCPU, not per-user licenses.
For the bare metal hosts, Oracle uses processor-based licensing. If your server has vCPUs that are multi-threading enabled, Oracle will count these vCPUs as one processor. However, if you’re running Oracle software on bare metal hosts, you need to buy a processor license for each physical host. If you don’t want to buy an additional license for a bare metal host, you can use the named user plus licensing method.
Amazon RDS services provide access to an enterprise edition of Oracle databases. Oracle has been a popular relational database for years and has been supported in RDS since version 11.2. The latest versions of Oracle are available on the RDS platform. You can leverage most of the features of Oracle in RDS and AWS EC2 without any hassles. You can select between two types of Oracle licenses: License Included and Bring Your Own License. Here’s a quick rundown of the two options.
For Oracle Standard Edition One, you can use the instance with four or more virtual cores. You can also license the instance with fewer than eight virtual cores. However, you must check the minimum CPU configuration. The minimum CPU usage for Oracle Standard Edition is four. For higher amounts of CPU usage, you should select the Oracle Standard Edition. If you want to use more than eight virtual cores, you can use the Oracle Enterprise Edition.
Several options exist for obtaining Oracle licenses on Amazon Web Services. The license-included-service model provides support for Oracle software without the need for an individual license. In the case of Oracle Database specific issues, you can use an active Oracle support account. Otherwise, you can contact the premium support team of Amazon Web Services for help. Similarly, the company has a multi-vendor support model that makes it easy to resolve issues.
If you’re using Oracle in your applications on the Amazon Web Services (AWS), you may want to know about the RDS Oracle License. Unless you are planning on using the service for commercial purposes, you may not be in compliance with the license. To avoid having to pay thousands of dollars in fines and penalties, you should check with Oracle first. Oracle has been using the RDS Oracle License for over a decade, and it’s one of the most common forms of commercialization today.
The Amazon Relational Database Service supports a variety of databases, but primarily focuses on Oracle Database. This fully managed commercial database makes Oracle deployment in the cloud simple. By using Oracle RDS, you can provision a database instance in minutes, instead of hours or days. AWS RDS supports multiple Oracle versions, including Enterprise Edition. For your RDS license, you can choose between two options: License Included and Bring Your Own License.
When comparing vCPUs to processors, Oracle recommends using the SPARC processor. Oracle Enterprise Edition requires four four-processor licenses per eight vCPUs. AWS RDS fully supports Oracle database, which means you can roll the RDS license into your hourly cost. In addition, you can scale your RDS instance when your workload requires it. You can also use Oracle database-assisted compute instances if you need them.
While Oracle on Amazon EC2 (AWS) instances provide the same benefits, they are not equivalent in terms of license terms. Dedicated hosts, on the other hand, offer significantly more flexible licensing terms. For customers who need to license Oracle extensively, and don’t need the benefits of AWS’s elasticity, the EC2 dedicated host is the best option. This article discusses some of the differences between EC2 and Dedicated Host licensing and how to determine which one is best for your needs.
The Cloud Policy for Oracle products is specific to the AWS EC2 environment. For the current Oracle Cloud Policy, this policy applies to any licensed Oracle product on an AWS EC2 environment. Oracle may change this policy in the future, however, so be sure to read the fine print before you make a purchase. Oracle offers various license options and has made it easy to determine which one will be most appropriate for your needs.
AWS bare metal servers are allocated without any EC2 OS or hypervisor installed on them. The end customer is responsible for installing the OS. This can be any OS that supports the hardware. Windows and Linux servers can be configured as physical servers on an AWS bare metal server. Oracle’s Partitioning Policy is compatible with AWS bare metal servers. Oracle’s bare metal instances are also compatible with the EC2 license.
Oracle has defined AWS as an Authorized Public cloud platform in their policy document for how to license Oracle software in public cloud. You can use AWS under 2 different models, License included or BYOL (Bring your own license) Bring your own license means that you purchase your own license from Oracle and brings it to AWS. AWS then acts as any outsourcing or hosting provider, the difference is that they have negotiated the right to license on vCPU and does not face the challenge of virtualization as a traditional hosting provider would do. License Included is quite limited and covers only Oracle Database Standard Edition One and Two products.
You need to calculate the number of vCPUs that you deploy the Oracle software upon. 2x vCPU count as one processor license if multi-threading is enabled. For example, if you are going to deploy Oracle Database Enterprise Edition on 8x vCPU instance – you will need to license that environment with 4 processor licenses. If you do not enable multi-threading one vCPU counts as one Oracle processor license. This calculate applies to all core based Oracle software products.
Amazon RDS for Oracle is when Amazon is managing your Oracle database. AWS is taking care of databse management tasks such as hardware provisioning, software patching, setup and backups. You must follow Oracle licensing policies for software products in public cloud environments. The document is called “Licensing Oracle software in the cloud computing environment”. AWS RDS for Oracle is split up into 2 different options, either license included or bring your own license.
What about Oracle licensing AWS DR Site? It is important to remember as you will need to license all Oracle instances, if you AWS DR sites, both sites needs to be fully licensed.
1# Oracle licensing on AWS – Oracle Database Standard Edition One and Two.
Deploying Oracle Database Standard Edition One or Two on an AWS instance that has more than 8 vCPUs. Oracle cloud licensing policy puts a cap on how large the AWS instance can be to run Oracle Database SE1 or SE2. You can only run those versions on instances with maximum 8 vCPU. If you install on an instance with more vCPUs, you need to license with Enterprise Edition.
2# Oracle licensing on AWS – Counting named user plus licenses wrong.
Oracle Database SE2 deployments must have a minimum of 10 user licenses per 8 vCPUs even if you only have 5 users. That is because Oracle for on-premises have user minimums for how few users you can license their software, the same applies for public cloud.
3# Oracle licensing on AWS – You are using Oracle Enterprise Management options on SE
Diagnostic and Tuning pack options are Enterprise Edition Options and are not available for Oracle Standard Edition databases. However, there are no technical limitations for using those products to manage your Oracle standard edition database. When Oracle audits your company, any current and historical usage is detected and you will be required to license with Oracle Database Enterprise Edition.
4# Oracle licensing on AWS – Using AWS RDS (license included) for Oracle proprietary application hosting
The Oracle license is only for internal business operations – the license is only for 1 entity, you. You are not allowed to extend usage or access to third party legal entities. One example is if you would purchase an AWS RDS license included and use it as a SaaS solution. That is not allowed, the license included option only includes standard terms.
5# AWS BYOL and not reviewing your Oracle licensing agreements.
If you Bring-Your-Own-License to AWS RDS, the same licensing terms that you have on-premises applies for deployment in AWS. There are sometimes limitations for how you can use and deploy Oracle software. Please review your Oracle Ordering Document to understand if there is any term preventing you from using the licenses in AWS RDS.
If you are not moving to Oracle cloud, you need to pay extra attention to how you license Oracle in AWS as Oracle is looking at ways to persuade you to move to their cloud. That is by finding ways for how to make Oracle licensing on AWS very costly. You should view AWS as any other hosting provider who only have one exception, that is how to license Oracle on the hardware aspect. Carefully review your Oracle licensing terms to understand if there are any restrictions on moving Oracle workloads to AWS. You should verify that you are following all of Oracle licensing rules and policies, by reviewing them they are usually very easy to resolve before there is an Oracle audit.
Read more on our blog
If you would like to be updated on Oracle licensing and recieve more tips follow us on
✔️ Follow us on LinkedIn
✔️ Subscribe to our channel on YouTube
Have you plan to license Oracle workloads on AWS and want to be certain that you are compliant, we can help you with Oracle licensing on AWS. If you want to know more about our services, schedule an consultation.