From Amazon RDS Custom for Oracle to what’s next: A technical guide to Oracle migration paths on AWS
Public Sector Blog
This article provides a technical migration guide for AWS customers transitioning from RDS Custom for Oracle, which reaches end of support on March 31, 2027, to alternative Oracle deployment options on AWS.
- RDS for Oracle now supports up to 256 TiB storage (increased from 64 TiB), addressing the primary reason many customers used RDS Custom
- Three migration paths available: RDS for Oracle (managed, low overhead), Oracle on EC2 (full OS access, high complexity), or ODB@AWS (Oracle-managed Exadata, RAC support)
- Migration approaches include physical methods (RMAN, Data Guard) for near-zero downtime or logical methods (Data Pump, AWS DMS, GoldenGate) for schema flexibility
- Use case examples: Oracle E-Business Suite to ODB@AWS, PeopleSoft to EC2, Oracle APEX to RDS for Oracle
- Key assessment questions cover OS customizations, Oracle versions, third-party agents, HA/DR requirements, and licensing arrangements
Organizations should evaluate their workload dependencies now to select the optimal migration path and begin planning their transition before the March 2027 deadline.
The AWS News Feed is currently looking for gold sponsors. If you want to support the AWS community and reach a large audience of AWS professionals, consider sponsoring the AWS News Feed.
Related articles
2026
2026
2026
2026
The AWS News Feed is currently looking for silver sponsors. If you want to support the AWS community and reach a large audience of AWS professionals, consider sponsoring the AWS News Feed.