License-included pricing combines cloud resource charges with the right to use specified licensed software. For example, a virtual machine offering can include a Windows Server license, and a managed database offering can include a commercial database license. The customer pays the published price for that configuration rather than supplying a separate license for the covered product. The license is included in the price, not provided at no cost, and its usage rights generally apply only within the selected cloud offering.
In practice, engineers choose a supported machine image, database engine, software edition, or pricing option that explicitly includes licensing. The provider supplies the covered licensing arrangement, while the customer remains responsible for using the software within the offering's terms. Billing can depend on running time, instance size, user count, subscription period, or another service-specific measure. License inclusion does not guarantee per-second billing, the absence of minimum charges, or the ability to stop every charge by stopping a resource.
The main alternative is Bring Your Own License, or BYOL. With BYOL, the customer supplies qualifying software licenses and must verify that the vendor permits their use in the target cloud environment. Eligibility can depend on the license agreement, purchase date, active maintenance or subscription benefits, deployment architecture, and tenancy requirements. Owning an on-premises license does not automatically make it eligible for cloud use. License-included pricing avoids bringing an existing entitlement for the covered software, but it does not remove all compliance obligations.
Consider a team that needs a Windows Server test environment for two weeks and has no eligible licenses. A license-included virtual machine can let the team provision the environment without a separate license purchase. However, installing a commercial database on that machine does not make the database license included. The team must select an offering that explicitly covers both products or arrange the database licensing separately.
For a database example, Amazon RDS offers license-included pricing for SQL Server and for supported Oracle Database Standard Edition 2 configurations. These offerings combine the applicable database licensing with the database instance charge. Amazon RDS also offers BYOL for supported Oracle configurations, illustrating that a service can support different licensing strategies depending on the engine and edition. Engineers must check the exact configuration rather than assume every engine uses the same licensing model.
The economic trade-off is convenience and flexibility versus potential savings from existing entitlements. License-included pricing can reduce procurement delays and avoid buying licenses solely for a temporary workload. BYOL can be financially attractive when an organization already has eligible licenses, but maintenance, subscription commitments, license administration, and infrastructure restrictions still affect total cost. Compare equivalent software editions, capacity, availability requirements, and workload duration rather than comparing only headline compute rates.
Common misconceptions are that license-included software is free, that every installed application is covered, and that included licenses can be transferred elsewhere. None of these follows from the pricing model. Storage, backups, network transfer, support plans, and additional software can incur separate charges. For certification questions, distinguish the licensing strategy from the purchasing option: On-Demand pricing, reservations, and other commitments address payment or capacity economics, while license-included versus BYOL determines how the software entitlement is supplied.
Amazon EC2
Amazon RDS