Recently, AWS announced it will discontinue support for Amazon RDS Custom for Oracle Database effective March 31, 2027. This represents a key milestone for organizations that rely on this service today, establishing a defined timeline to rethink their approach going forward.
It’s important to note that AWS has provided options to transition away from this service in the form of EC2 or AWS RDS. However, Oracle Database customers have just 9 months to plan and execute their database move to the alternative hosting strategy of their choice. Taking a proactive approach now can help organizations make the best decisions, minimize disruption and allow sufficient time for testing.
The early promise of AWS RDS Custom for Oracle
AWS introduced Amazon RDS Custom for Oracle Database in October 2021, then announced the release of RDS Custom for SQL Server just two months later. The idea behind the Amazon RDS Custom offering was straightforward: to provide a more customizable managed database environment. With it, Oracle Database administrators gained greater control over patching, configuration and the underlying operating system — something traditional RDS environments intentionally restrict.
This flexibility was a significant benefit for experienced Oracle DBAs. Under standard Amazon RDS, in contrast:
- Database patching is required for all customers
- Administrative access is limited
- Oracle support contracts are still required under BYOL models
Amazon RDS Custom addressed some of these constraints, enabling organizations to run Oracle Database in AWS with fewer compromises — particularly for serious production environments that exceed the practical limits of Oracle Database Standard Edition 2.
The update: RDS Custom for Oracle Database is being retired
AWS has now confirmed that Amazon RDS Custom for Oracle will be fully desupported on March 31, 2027. After that date, customers will:
- No longer have access to RDS Custom environments
- Need to move their databases elsewhere
For those with multiple Oracle Database instances, custom configurations or compliance-driven environments, this transition requires careful planning across infrastructure, operations and cost considerations.
What options do Oracle Database customers have?
Organizations that are evaluating their next steps in light of AWS’s announcement can choose from several options:
Move back to standard Amazon RDS
If workloads can run on Oracle Database SE2, the simplest option is to move back to the licensed version of Amazon RDS. For more complex production systems, additional evaluation may be needed to ensure feature and scalability requirements are met.
Migrate to Amazon EC2
For those who want to remain in an AWS environment, another option is to move to Amazon EC2. That said, migrating may introduce more administrative work for teams managing the environment, including installation, patching and OS and networking management.
Move to another cloud or hosting model
Some organizations may consider exploring other hosting options, such as Microsoft Azure or Google Cloud. Alternatively, they could bring systems back on-site or relocate them to a shared, physical hosting environment — known as a colocation facility (CoLo).
Why this event calls for a broader support conversation
Though this announcement is specific to Amazon RDS Custom for Oracle Database, it’s not a unique situation. Enterprise technology environments are constantly evolving, with platform updates and lifecycle milestones affecting IT roadmaps.
Organizations that delay in making their own business-driven decisions can end up pushed into:
- Unplanned migrations
- Accelerated timelines
- Higher costs
- Increased operational risk
That’s why Oracle Database customers should use this moment to reassess not only where their databases run but how they’re supported.
How Rimini Street helps organizations navigate forced change
Rimini Street is here to help organizations turn the discontinuation of Amazon RDS Custom for Oracle Database into an opportunity.
As the global leader of third-party support for Oracle, Rimini Street works with Oracle Database customers in all major industries to navigate complexity and regain control — all while maintaining security, compliance and operational stability.
By partnering with Rimini Street, organizations affected by this change can:
- Extend the life and value of their database investments for up to 15 additional years, avoiding rushed migrations
- Lower annual maintenance fees by up to 50%, freeing up budget for higher-priority initiatives
- Strengthen security posture and decrease database risk exposure, even as environments evolve
- Leverage senior-level expertise on Oracle systems to guide complex migration and hosting decisions
Most importantly, Rimini Street enables organizations to move on their own terms and timeline.
With the March 31, 2027, deadline approaching, now is the time to reassess your Oracle Database strategy. Learn how Rimini Street can help you stabilize your Oracle Database environment, reduce costs and take control of your next move.
Key takeaways
AWS’s decision to discontinue Amazon RDS Custom for Oracle Database forces organizations to make complex infrastructure and database decisions on an accelerated timeline. Options exist, but each introduces trade‑offs in cost, risk and operational burden. This moment also presents an opportunity to rethink an organization’s long-term Oracle Database support strategy. Explore third-party support and solutions for Oracle Database to learn how Rimini Street helps organizations stabilize their environments, reduce costs and regain control — no matter where they run their databases.
