Amazon Relational Database Service for Oracle is a managed Oracle database offering in the Amazon Web Services cloud. The service runs the Oracle database engine on Amazon managed infrastructure and removes the database administration overhead from the buyer. The migration of an Oracle database from an on premises environment to Amazon RDS changes the licensing model, the cost structure, and the negotiation leverage with Oracle. The decision between the two RDS licensing paths, bring your own licence and licence included, determines how the migration affects the Oracle relationship and the future negotiation position.
The two licensing paths.
Amazon RDS for Oracle offers two licensing models. The bring your own licence model allows the buyer to use existing Oracle licences on the RDS instances subject to the Oracle licensing policy for authorised cloud environments. The licence included model bundles the Oracle licence into the hourly RDS rate so the buyer pays a single hourly price that includes the database licence and the infrastructure.
The choice between the two paths depends on the buyer existing licence position and on the workload profile. A buyer with surplus perpetual licences may prefer bring your own licence to use the existing licence asset. A buyer with no surplus licences or with a variable workload may prefer licence included to avoid a new perpetual licence purchase. See the BYOL deal type page for the full bring your own licence structure.
The Oracle cloud policy.
The bring your own licence path on Amazon RDS is governed by the Oracle policy for licensing in authorised cloud environments. The policy defines how Oracle processor and named user licences are counted on the virtual CPUs of the cloud instance. The policy treats two virtual CPUs as equivalent to one Oracle processor licence where hyper threading is enabled. The buyer must size the licence count to the virtual CPU count under this policy.
The Oracle cloud policy is a policy document rather than a contractual term and Oracle has revised it over time. The buyer should confirm the current policy at the point of migration and should document the licence count against the policy in force. See the soft partitioning note for the related virtualisation counting issues.
The cost comparison.
The cost comparison between the on premises Oracle database, the bring your own licence RDS path, and the licence included RDS path depends on the workload profile and on the existing licence position. The on premises database carries the perpetual licence and the twenty two percent support stream. The bring your own licence RDS path carries the same licence and support plus the RDS infrastructure cost. The licence included RDS path carries a single hourly rate.
The licence included path can be more economical for a variable or seasonal workload because the hourly rate scales with usage and avoids the perpetual licence and the compounding support stream. The bring your own licence path can be more economical for a steady high utilisation workload where the existing licence is already a sunk cost. The buyer should model both paths over the planned workload profile.
The migration leverage.
The credible option to migrate an Oracle database to Amazon RDS changes the negotiation leverage with Oracle. A buyer that can demonstrate a viable migration path holds a genuine alternative to the Oracle on premises renewal and to the Oracle cloud. The alternative gives the buyer a walk away position that strengthens the renewal negotiation.
The leverage is strongest when the migration is genuinely viable rather than a negotiating bluff. Oracle account teams are experienced at distinguishing a real migration plan from a bluff. The buyer should develop the migration plan to the point of credibility and should be prepared to execute it. See the Database Negotiation pillar for the leverage context and the data egress note for the cloud exit considerations.
The technical constraints.
The migration to Amazon RDS for Oracle carries technical constraints that the buyer must evaluate. RDS supports a defined set of Oracle database versions and editions and does not support every Oracle database option. Features that depend on operating system access or on options not available in RDS will not migrate without redesign. The buyer should map the application dependencies against the RDS feature set before committing to the migration.
The migration also requires a data migration approach that minimises the downtime. The approach may use the Oracle Data Pump utility, the AWS Database Migration Service, or a replication based cutover. The migration approach should be tested in a non production environment that mirrors the production data volume and the production workload.
The decision framework.
The decision framework for the Amazon RDS migration should weigh the cost comparison, the licensing path, the technical constraints, and the negotiation leverage. The framework should produce a defensible business case that supports the migration decision and that can be presented to the internal stakeholders. The framework should also model the residual Oracle relationship after the migration because a partial migration leaves an ongoing Oracle footprint.
For the wider cluster see Database Negotiation. For the service see Cloud Migration Advisory. For the deal structure see BYOL. For the Oracle product see Oracle Database. For the full research read the Oracle Negotiation Playbook.
Engaging an independent advisor.
The Amazon RDS migration decision benefits from independent modelling of the cost comparison and from independent review of the licensing path under the Oracle cloud policy. An independent advisor can model the bring your own licence and the licence included paths, confirm the licence count under the current Oracle policy, and quantify the negotiation leverage the migration creates. The advisor can also coordinate the migration plan with the Oracle renewal timeline to maximise the leverage.
A North American insurer engaged an advisor to evaluate a partial migration of its Oracle estate to Amazon RDS in 2024. The advisor modelled the cost comparison, confirmed the bring your own licence count under the Oracle cloud policy, and used the credible migration plan to negotiate the on premises renewal. The renewal settled approximately twenty nine percent below the Oracle opening position and the insurer migrated the variable workloads to the licence included path.