Next platform deadline: Amazon EKS Nov 26, 2026  

All 14 deadlines

Oracle & Middleware

Amazon RDS Custom for Oracle retires on March 31, 2027. Your options, compared

AWS is discontinuing RDS Custom for Oracle. What the notice says, the two migration methods AWS documents, and how to pick a target.

By the SRASH team · · 6 min read

Key facts

  • AWS will end support for Amazon RDS Custom for Oracle on March 31, 2027.
  • After that date you can no longer access the RDS Custom for Oracle console or its resources.
  • AWS recommends migrating to self-managed Oracle on Amazon EC2 and documents two methods: RMAN active duplication and Oracle Data Guard.
  • AWS's guidance suggests keeping the RDS Custom instance through a validation period, typically 1 to 2 weeks.

What AWS has announced

AWS has decided to discontinue Amazon RDS Custom for Oracle, effective March 31, 2027. From March 31, 2026 to March 31, 2027, AWS recommends migrating to Oracle on Amazon EC2 while you continue to use the service with its existing features and support. After March 31, 2027, AWS states you will no longer be able to access the RDS Custom for Oracle console or RDS Custom for Oracle resources.

The two migration methods AWS documents

 RMAN active duplicationOracle Data Guard
DowntimeMinutes, at final cut-overSeconds to minutes, at switchover
ComplexityLowerHigher
Continuous sync before cut-overNoYes
FallbackManual: keep the sourceBuilt in: old primary becomes standby
Best forPlanned cut-overs, dev and testProduction and mission-critical systems

Summarized from AWS's prescriptive guidance for this exit.

Choosing a target

AWS's own guidance targets self-managed Oracle on Amazon EC2, which keeps full control of the operating system and Oracle home, the reason most teams chose RDS Custom in the first place. Depending on edition, features and how much operations work you want to keep, Amazon RDS for Oracle (fully managed) or Oracle Database@AWS can also be worth comparing. That choice is per database, not per estate.

What RDS Custom did that you now own

On EC2 the automation goes away. Plan for:

  • Backups: RMAN schedules, copies to Amazon S3 and AWS Backup snapshots, with restore tests.
  • Monitoring: CloudWatch metrics and alarms for tablespace, archive logs, sessions and waits.
  • Patching: match Release Updates exactly between source and target before you migrate, then run a regular patch cycle.
  • High availability: a Data Guard standby in another Availability Zone if the workload needs it.
  • Security: least-privilege security groups, EBS encryption and network encryption.

A practical sequence

  1. Inventory every RDS Custom instance: version, Release Update, CDB or non-CDB, size and dependencies.
  2. Pick a target and method per database, and agree the downtime each application can accept.
  3. Build the target with infrastructure as code, and match patch levels.
  4. Rehearse in non-production, then migrate production with the source kept as fallback.
  5. Validate for one to two weeks, take a final snapshot, and decommission.

Sources

Checked on November 15, 2026. Vendors can change dates and terms, so confirm against the source before you rely on them.

Start with a free 30-minute review.

Databases, cloud or AI: talk to a senior engineer about what you run and what is coming. We reply within one business day and sign your NDA on request.