In early 2017, Oracle issued a policy statement dedicated to helping customers better understand how to license Oracle products when the customers access the products via Amazon’s or Microsoft’s cloud services. Increasingly, companies are considering outsourcing datacenter workloads to third-party hosted or cloud environments.

Software publishers like Oracle are not only publishing guidance on how to count licenses that are installed in a third-party cloud environment, Oracle is also offering its own cloud solutions to customers. Although moving the Oracle products to third-party cloud environments may result in initial hardware savings, failing to understand the licensing rules for these environments can ultimately lead to costly licensing mistakes. Licensing Oracle in the Microsoft or Amazon Clouds The primary concern related to licensing Oracle in non-Oracle cloud environments is how many licenses a customer needs to cover the installations in the third-party’s cloud. In early 2017, Oracle issued a policy statement dedicated to helping customers better understand how to license Oracle products when the customers access the products via Amazon’s or Microsoft’s cloud services. You can review Oracle’s policy at. Oracle’s policy document describes these environments as “Authorized Cloud Environments.” Oracle identifies Microsoft’s Azure and Amazon’s Elastic Compute Cloud (“EC2”) and Amazon’ Relational Database Services (“RDS”) as the only Authorized Cloud Environments.

This policy applies to a number of Oracle products, including but not limited to the BI Suite, all editions of Database, Hyperion, and WebLogic. According to the policy, customers are required to license Authorized Cloud Environments as follows: • Amazon EC2 and RDS – count two vCPUs as equivalent to one Oracle Processor license if hyper-threading is enabled, and one vCPU as equivalent to one Oracle Processor license if hyper-threading is not enabled. • Microsoft Azure – count one Azure CPU Core as equivalent to one Oracle Processor license.

Because no other approved cloud vendors are identified in the policy, if a customer is currently accessing Oracle products via the cloud in non-Microsoft, non-Amazon, or non-Oracle environments, that customer should carefully review its licensing terms to determine whether installing in that third-party cloud environment is allowed. Because the published guidance is vendor-specific as outlined above, it may be difficult to determine how to count cores or CPUs on non-approved cloud environments. Ddl and dts connect license activation serial code free. Those who are already familiar with calculating the required Oracle licensing for processor-based products may be wondering which of the core factors from the Core Factor Table would apply to the Authorized Cloud Environments. Oracle’s answer is clear – “the Oracle Processor Core Factor Table is not applicable” to any licenses used for products accessed via Authorized Computing Environments. This could have a potentially significant impact on Database Standard licensing, in particular, because Oracle has indicated that Database Standard can only be licensed on up to 16 Amazon vCPUs or 8 Azure CPU Cores.

Igo8 pna 2010 hyundai. Additionally, Oracle instructs customers that for any product that contains Standard Edition One, Standard Edition 2, or Standard Edition in the product name, that four Amazon vCPUs count as one socket and two Azure CPU Cores also count as one socket. Importantly, Oracle also limits the availability of support services to customers using larger Authorized Computing Environments. Both Basic Limited and Premier Limited Support are not available to customers using Authorized Computing Environments containing more than 8 Amazon vCPUs or 4 Azure CPU Cores. For customers who want to use their Oracle Unlimited License Agreements (“ULA”) to license their Authorized Computing Environments, Oracle expressly grants permission in the policy to use ULA licenses for cloud instances of Oracle products.