Db2 on Cloud and BYOL Considerations
Moving Db2 to a public cloud and bringing your own license looks like a way to simplify spend, but the license travels with its original rules. The workload changes address; the metric, the entitlement, and the reporting duty do not. BYOL moves the database, not the compliance burden.
What bring your own license actually carries
Bring your own license means you apply an entitlement you already hold to an instance running in a cloud you do not own. The entitlement keeps its metric, its edition, and its quantity. A PVU entitlement remains a PVU entitlement, where value units per core times the cores allocated to Db2 set the count, and a VPC entitlement remains tied to virtual processor cores. The cloud provider supplies the infrastructure, but IBM still measures the license the way it always did. The mistake buyers make is treating BYOL as if the cloud absorbed the licensing question. It did not.
Counting cores you do not control
On premises you can see the host, the sockets, and the cores. On cloud you see a virtual machine shape, and the mapping from that shape to chargeable cores is where findings appear. IBM publishes how virtual cores on eligible cloud platforms map to its metrics, and sub-capacity terms can apply, but only when the conditions are met. That means an approved reporting tool capturing the cloud instances continuously, just as on premises. A BYOL Db2 on cloud with no reporting behind it carries the same exposure as an unreported on premises instance: the period without evidence defaults to the larger count.
- The metric travels: PVU stays PVU, VPC stays VPC, regardless of the cloud
- Sub-capacity still needs a tool: cloud instances must be captured continuously to hold the virtual count
- Instance shape is not entitlement: the chargeable cores come from IBM rules, not the provider console
- Elastic scaling is a trap: instances that grow or multiply can exceed the entitlement quietly
How buyers keep BYOL Db2 defensible
We reconcile the cloud Db2 footprint to the entitlement it draws on, confirm the metric mapping for each instance shape, and verify that the reporting tool sees every BYOL instance for the whole period. Where scaling pushed the deployment above the entitlement, we size the true gap rather than accept a full-capacity sweep. Where the provider platform is eligible for sub-capacity and the reporting exists, the virtual count holds, and a finding that ignored it is challenged with the report data.
BYOL does not reset the clock or the rules. The entitlement you moved to cloud still answers to its metric and still needs continuous reporting to hold a sub-capacity position. Treat every cloud Db2 instance as if it were on a host you must report: map the shape to the right count, capture it in an approved tool, and reconcile the footprint to the entitlement before IBM does the counting for you.