What Oracle versions and editions does Amazon RDS support?

Amazon RDS for Oracle currently supports Oracle Database 19c and 21c, and supports editions including Enterprise Edition and Standard Edition Two.

What is the difference between License Included and BYOL on Amazon RDS for Oracle?

License Included bundles Oracle licensing into the service price and is mainly associated with Oracle SE2. BYOL allows you to use your existing Oracle licenses and is supported for Enterprise Edition and SE2 when licensing requirements are met.

How many PDBs can I create in the multitenant architecture on Amazon RDS for Oracle?

Amazon RDS for Oracle supports a single-tenant multitenant model and limits a CDB instance to one PDB.

Amazon RDS for Oracle Guide | Licensing, Editions, Multi-AZ, Data Guard Read Replicas, Upgrades & Best Practices

Q: Does Amazon RDS for Oracle support read replicas?

Yes. Amazon RDS for Oracle supports Data Guard read replicas for Oracle 19c and 21c CDBs, including single-tenant and multitenant configurations.

What is Amazon RDS for Oracle?

Amazon RDS for Oracle is the AWS managed Oracle database offering for teams that need Oracle compatibility but do not want to self-manage the full database server platform. It lets organizations keep Oracle-based applications while moving much of the infrastructure management burden into AWS.

In practice, you still own schema design, application compatibility, SQL behavior, access controls, operational runbooks, and upgrade decisions. AWS manages major portions of the platform layer such as provisioning, storage handling, automated backups, failover orchestration, and baseline maintenance workflows. :

Simple memory trick: Oracle stays Oracle, but the host and service plumbing become managed.

Managed Oracle operations

Useful when enterprises want Oracle without fully managing the underlying database host fleet themselves.

Cloud migration continuity

Helps organizations migrate Oracle-backed workloads into AWS while maintaining application compatibility.

Enterprise-grade patterns

Supports licensing flexibility, Multi-AZ deployments, backups, and Data Guard read replicas for Oracle-specific operational designs. :

Why Use Amazon RDS for Oracle?

RDS for Oracle is usually chosen by enterprises with existing Oracle workloads, Oracle-skilled teams, or vendor applications that depend on Oracle behavior and supportability. It is often less about “choosing a new database” and more about modernizing how an existing Oracle estate is operated.

              Keep Oracle compatibility
              Retain Oracle-backed application compatibility while moving the platform to AWS.
            
              Reduce infrastructure burden
              Let AWS manage much of the repetitive platform work around provisioning, storage, failover, and backups.
            
              Use enterprise HA patterns
              Choose Multi-AZ and Data Guard read replica strategies depending on resilience and read needs.
            
              Modernize operations
              Shift from host-centric Oracle administration toward service-centric Oracle operations.

Typical reasons teams choose RDS for Oracle

They already run Oracle-backed enterprise applications
They need Oracle compatibility for vendor software or internal systems
They want managed backups, storage, and failover rather than self-running Oracle hosts
They need clear licensing paths for cloud deployment
They want disaster recovery or read-only replica options based on Oracle Data Guard patterns

Supported Oracle Versions and Editions on Amazon RDS

AWS currently documents support for Oracle Database 21c and Oracle Database 19c on Amazon RDS for Oracle. AWS also documents support for Oracle Database Enterprise Edition and Oracle Database Standard Edition Two in the current offering. :

Oracle Database 21c

Available on Amazon RDS for Oracle and relevant for teams working with newer Oracle feature sets and lifecycle planning. :

Oracle Database 19c

A widely used Oracle long-term support release that AWS specifically documents for RDS for Oracle. :

Area	What AWS documents	Why it matters
Supported versions	Oracle 19c and 21c	Version support affects upgrade planning and application lifecycle
Editions	Enterprise Edition and Standard Edition Two	Edition choice affects licensing, features, and cost
Version planning	Major and minor version upgrades are documented separately	Upgrade strategy should be part of enterprise rollout planning

For enterprise planning, think in three layers: Oracle version, Oracle edition, and license model.

Oracle Licensing Models on Amazon RDS

Oracle licensing is one of the most important parts of RDS for Oracle design. AWS documents two licensing models for Amazon RDS for Oracle: License Included and Bring Your Own License (BYOL). :

License Included

In the License Included model, Oracle licensing is bundled into the service price. AWS prescriptive guidance notes that License Included is supported only on Amazon RDS for Oracle Database SE2. This can be attractive for non-production or teams that want simpler licensing administration. :

Bring Your Own License (BYOL)

In the BYOL model, you bring existing Oracle licenses into AWS. AWS documents BYOL support for Oracle Enterprise Edition and Oracle Standard Edition Two on Amazon RDS, provided you meet Oracle licensing requirements and support obligations. :

Licensing should be reviewed with your Oracle licensing specialists, procurement team, or legal/compliance stakeholders before production commitment. BYOL is not just a technical choice; it is a governance and cost-management decision. :

Model	Typical fit	Important note
License Included	Teams wanting simpler cloud-side Oracle licensing management	Mainly associated with Oracle SE2 on Amazon RDS
BYOL	Enterprises with existing Oracle license estate and support contracts	Supported for EE and SE2 when licensing requirements are met

Architecture Models for Amazon RDS for Oracle

One Oracle-specific topic that matters on Amazon RDS is database architecture. AWS documents support for Oracle multitenant in a limited form called a single-tenant configuration. In this model, an RDS for Oracle CDB instance is limited to one PDB. You cannot add more PDBs with RDS APIs. :

Non-CDB style

Useful when the workload does not require multitenant packaging assumptions.

CDB single-tenant style

AWS supports a subset of Oracle multitenant, but limits an RDS CDB to one PDB. :

Enterprise implication

Teams migrating large Oracle estates should validate whether this model fits their Oracle architecture assumptions before committing.

A common enterprise mistake is assuming Amazon RDS for Oracle matches every on-prem Oracle pattern one-for-one. It does not. Architecture compatibility should be checked early.

High Availability with Multi-AZ

AWS documents Multi-AZ deployments for Amazon RDS as an availability and failover pattern. In a Multi-AZ DB instance deployment with one standby, Amazon RDS maintains a synchronous standby replica in another Availability Zone, and that standby provides failover support but does not serve read traffic. :

What Multi-AZ is for

Use Multi-AZ when resilience, failover, and minimizing downtime matter more than adding read capacity. :

What Multi-AZ is not for

Do not treat a traditional standby-only Multi-AZ design as a read-scaling pattern. That is a different problem with a different solution. :

Clean interview answer: Multi-AZ is for availability and failover, not primary read scaling.

Data Guard Read Replicas for Amazon RDS for Oracle

AWS documents Oracle read replicas separately because they rely on Oracle Data Guard patterns. Amazon RDS for Oracle supports Data Guard read replicas for Oracle Database 19c and 21c CDBs in both single-tenant and multitenant configurations, and these replicas can be created, managed, and promoted. AWS also documents mounted replicas and cross-Region replica capabilities. :

Read-only access

Useful for workloads that need read access or disaster recovery-oriented replica design. :

Managed DR pattern

AWS positions Data Guard replicas as useful for disaster recovery, high availability, and managed replica workflows. :

Cross-Region support

Cross-Region Oracle replica design is supported and can be valuable for enterprise resiliency planning. :

Read replicas for Oracle are not the same thing as generic read replicas in every other engine family. Data Guard expectations, architecture compatibility, and operational runbooks should be understood clearly before rollout.

Security and Networking for RDS for Oracle

Oracle on RDS should still be treated as part of your AWS network and security architecture. In most enterprise environments, the database sits in tightly controlled VPC subnets and is exposed only to approved application tiers, jump patterns, or management paths.

Private placement

Oracle database services should usually be private rather than broadly exposed.

Security group control

Use least-privilege access patterns so only approved workloads and teams can connect.

Enterprise segmentation

Think about application tiers, DR topology, management access, and compliance boundaries together.

Managed database service does not remove the need for disciplined network design. It simply changes where responsibility begins and ends.

Upgrade Planning for Amazon RDS for Oracle

AWS documents major and minor engine upgrades for RDS for Oracle separately, and Oracle 19c and 21c are treated as major releases. For enterprise teams, upgrade planning should include version support timelines, application certification, replica coordination, backup strategy, and maintenance window planning. :

Major version planning

Major upgrades need application validation, Oracle feature compatibility review, and change-management planning. :

Replica coordination

AWS database guidance notes that source DB instances and read replicas must share the same Oracle engine version during upgrade activities. :

Good enterprise mindset: treat Oracle upgrades like coordinated application-and-platform changes, not simple patch events.

Migration Strategies for Oracle to Amazon RDS for Oracle

Oracle migrations are rarely just “copy the database.” Enterprises usually need to think about cutover windows, application dependency analysis, licensing implications, network routing, and data synchronization patterns. AWS blogs and guidance show migration approaches such as Oracle Data Pump for initial load and Oracle GoldenGate-based change data capture patterns for continuous sync scenarios. :

Simple migration

Suitable when downtime windows are acceptable and the database can be moved in a more straightforward cutover pattern.

Staged migration

Useful when teams need initial bulk load plus synchronization before final switch-over. :

Enterprise migration program

Required when multiple Oracle environments, licensing review, DR design, and application validation all need coordination.

Oracle migration planning should involve database, application, cloud, security, and licensing stakeholders together. Treating it as a purely technical DBA task is a common failure pattern.

Amazon RDS for Oracle Pricing Factors

RDS for Oracle pricing depends on far more than instance size. AWS documents different pricing implications based on licensing model, edition, compute class, storage, and deployment design. Oracle-specific cost questions often become material in enterprise cloud programs. :

License model

License Included and BYOL can create very different cost structures. :

Oracle edition

Edition choice influences both technical capabilities and cost expectations.

Compute class

DB instance class affects recurring cost and performance baseline.

Storage

Storage size and performance profile directly affect total spend.

Multi-AZ

Availability-focused designs increase cost but may be necessary for production resilience. :

Replica strategy

Read replica and DR design add resilience and capability, but also add cost.

A simple pricing summary is: license + edition + instance + storage + HA + replica strategy.

Important Limitations and Enterprise Realities

Amazon RDS for Oracle is managed, but it is not a full one-to-one replacement for every on-prem Oracle pattern. Architecture, licensing, multitenant assumptions, feature availability, and operational expectations must all be validated carefully before standardization.

Architecture constraints

RDS multitenant support is limited to a single-tenant configuration with one PDB per CDB. :

Licensing complexity

Oracle licensing remains a high-stakes enterprise governance topic even in cloud-managed deployments. :

Operational tradeoffs

You gain managed service convenience, but you give up some of the unrestricted flexibility of fully self-managed Oracle infrastructure.

Good enterprise Oracle design starts with fit assessment, not with provisioning. Validate compatibility first, then automate.

Real-World Use Cases for Amazon RDS for Oracle

ERP and core business systems

Useful for enterprise applications that depend on Oracle-specific behavior and supportability.

Banking and financial workloads

Relevant where Oracle-backed transaction systems need strong availability and cloud modernization planning.

Legacy Oracle estate migration

Useful when organizations move Oracle databases from on-premises into AWS managed services.

Disaster recovery improvement

Data Guard read replicas and cross-Region patterns can help strengthen DR posture. :

Production systems needing HA

Multi-AZ is relevant where downtime and failover behavior matter. :

Controlled Oracle cloud operations

Useful for organizations that want Oracle under a managed service model rather than host-managed operations.

Best Practices for Amazon RDS for Oracle

Review Oracle licensing and support obligations before production commitment
Choose license model and edition deliberately, not by habit
Use Multi-AZ for availability needs, not as a generic read-scaling assumption
Understand Data Guard read replica behavior before designing DR around it
Validate Oracle architecture compatibility, especially around multitenant expectations
Plan major upgrades as enterprise change events with application validation
Keep production databases private and tightly controlled in the VPC
Build migration runbooks that include cutover, fallback, and licensing review
Test backup, restore, and failover assumptions instead of only enabling them
Document where managed-service limits change your traditional Oracle runbook

Good RDS for Oracle design is not only about creating an Oracle endpoint. It is about licensing strategy, architecture fit, HA model, migration method, and operational clarity.

Amazon RDS for Oracle FAQ

What Oracle versions does Amazon RDS support?

AWS currently documents support for Oracle Database 19c and 21c on Amazon RDS for Oracle. :

What Oracle editions are supported on Amazon RDS?

AWS documents support for Oracle Enterprise Edition and Oracle Standard Edition Two. :

What is the difference between License Included and BYOL?

License Included bundles licensing into the service price and is mainly associated with SE2, while BYOL lets enterprises bring their existing Oracle licenses and is supported for EE and SE2 when licensing requirements are met. :

Does Amazon RDS for Oracle support read replicas?

Yes. AWS documents Data Guard read replicas for Oracle 19c and 21c CDBs, including single-tenant and multitenant configurations. :

How many PDBs can I create in RDS for Oracle multitenant architecture?

AWS documents that an RDS for Oracle CDB instance is limited to one PDB. :

Is Multi-AZ the same as read scaling?

No. Traditional Multi-AZ DB instance deployments are for availability and failover, while read access patterns should be designed separately. :

Related Pages & Official AWS References

Official AWS reference	Why it matters
Amazon RDS for Oracle official page	Product overview and licensing overview
Amazon RDS for Oracle User Guide	Core Oracle-specific service behavior and features
RDS for Oracle licensing	Licensing model rules and edition coverage
Amazon RDS for Oracle pricing	Current pricing and licensing-cost planning
RDS for Oracle read replicas overview	Data Guard read replica behavior and DR planning
RDS for Oracle architecture models	Single-tenant multitenant architecture limits
RDS for Oracle engine upgrades	Major and minor version upgrade planning