It sounds like a great deal at first. Spin up a fully-managed Oracle database instance with the license cost already baked in. And in a lot of ways, it can be a good deal. Take a look at the cost of managing the database, doing backups & patching. Plus, the hardware and software and Oracle on Amazon RDS can be a great deal. But as always, be careful about the details.
Oracle uses a policy document to allow for licensing in Amazon EC2 and RDS: Licensing Oracle Software in the Cloud Computing Environment. That is in itself a problem because Oracle has and will change the policy without any notice. They just did it again earlier this month. So make sure you download a copy of the policy when you spin up the instances for Oracle.
But the warning for today is around the sizing of the environments. Per the policy:
"Under this cloud computing policy, Oracle Database Standard Edition may only be licensed on Authorized Cloud Environment instances up to 16 Amazon vCPUs or 16 Azure vCPUs. Oracle Standard Edition One and Standard Edition 2 are only licensed on Authorized Cloud Environment instances up to eight Amazon vCPUs or eight Azure vCPUs. If licensing Database Standard Edition 2 by Named User Plus metric, the minimums are 10 NUP licenses per 8 Amazon vCPUs or 8 Azure vCPUs."
In the EC2 environment, customers need to abide by these limits or the limits in place at the creation of the instance. However, the tricky part is that Amazon and Oracle aren't even abiding by these limits in the RDS environments. That's right! Even today, you can go to the AWS console and spin up an SE instance on 8xlarge instances with 32 vCPUs. Or an SE1 or SE2 instance on 4xlarge instances with 16 vCPUs.
The Licensing Trap
Guess what happens when the Oracle License Management Services (LMS) rep comes knocking on the door? They claim that the SE, SE1, or SE2 license doesn't cover this and requires an Enterprise Edition license. So instead of paying $17,500 for the SE2 RDS instance, you're paying $380,000 instead!
This is a massive compliance trap that catches many organizations off guard. AWS allows you to configure instances that violate Oracle's licensing policies—and Oracle will hold you responsible, not Amazon.
What Should You Do Next?
- Audit your AWS Oracle RDS instances immediately: Check all instance sizes against Oracle's published limits.
- Download Oracle's cloud licensing policy: Keep a timestamped copy when you spin up instances.
- Understand the vCPU limits: SE2 is limited to 8 vCPUs; SE is limited to 16 vCPUs.
- Don't trust AWS defaults: Just because AWS lets you configure it doesn't mean Oracle licenses it.
- Get expert help if audited: The jump from $17,500 to $380,000 is negotiable with the right approach.
