.png)
If you are weighing RDS Custom Reserved Instances, two facts drive the decision: RDS Custom for SQL Server offers Reserved Instances on a one-year term only, and RDS Custom for Oracle reaches end of support on March 31, 2027. Everything else in this guide CEV mechanics, licensing, and pricing is about how you act on those two constraints.
Important: AWS will end support for Amazon RDS Custom for Oracle on March 31, 2027. After that date, customers will no longer be able to access RDS Custom for Oracle resources, including DB instances, snapshots, and custom engine versions. AWS recommends migrating existing RDS Custom for Oracle workloads to Oracle on EC2. RDS Custom for SQL Server is not affected.
Key takeaways
1
RDS Custom SQL Server supports only one-year RIs, so commitment planning stays on a shorter renewal cycle.
2
RDS Custom Oracle ends on March 31, 2027, making migration timing more important than long-term RI savings.
3
CEVs customize the software baseline, but they do not change Reserved Instance terms or eligibility.
4
RDS Custom is worth the premium only when OS-level access or host customization is actually required.
RDS Custom is for Oracle and SQL Server workloads that need access to the operating system or database environment that standard RDS manages for you. SQL Server Custom Reserved Instances are available only for a one-year term.
AWS still lists one-year and three-year RDS Custom Oracle RIs, but the service itself ends March 31, 2027, so migration timing now matters more than headline discount depth.
AWS still lists one-year and three-year RDS Custom Oracle RIs, but the service itself ends March 31, 2027, so migration timing now matters more than headline discount depth.
What RDS Custom and CEVs mean
RDS Custom sits between standard RDS and a self-managed database on EC2. AWS automates parts of database operations, while you can access and customize the host operating system and database environment. It is designed for legacy, packaged, or specialized applications that cannot run inside standard RDS boundaries.
A custom engine version, or CEV, is the baseline used to launch an RDS Custom database. For Oracle, AWS defines a CEV as a binary volume snapshot of the database engine combined with a specific AMI either the AWS-managed default AMI or an eligible AMI previously used by an RDS Custom for Oracle CEV using installation files supplied for the environment.
For SQL Server, a CEV is based on an AMI containing SQL Server and can preserve OS-level customizations such as third-party agents or drivers.
A CEV does not create a separate discount product. RI eligibility comes from the RDS Custom engine, licensing model, deployment, instance class, Region, term, and payment structure.
A custom engine version, or CEV, is the baseline used to launch an RDS Custom database. For Oracle, AWS defines a CEV as a binary volume snapshot of the database engine combined with a specific AMI either the AWS-managed default AMI or an eligible AMI previously used by an RDS Custom for Oracle CEV using installation files supplied for the environment.
For SQL Server, a CEV is based on an AMI containing SQL Server and can preserve OS-level customizations such as third-party agents or drivers.
A CEV does not create a separate discount product. RI eligibility comes from the RDS Custom engine, licensing model, deployment, instance class, Region, term, and payment structure.
Decision point
| Decision point | Standard RDS SQL Server | RDS Custom SQL Server | RDS Custom Oracle |
|---|---|---|---|
| OS-level customization | Limited | Yes | Yes |
| Custom engine baseline | BYOM engine versions available | CEV supported | CEV supported |
| RI term | 1 or 3 years | 1 year only | 1 or 3 years currently listed |
| Licensing | LI or BYOM | LI or BYOM | BYOM |
| Lifecycle | Active | Active | Ends March 31, 2027 |
For broader commitment mechanics, see the RDS Reserved Instances complete guide.
How RDS Custom pricing works
RDS Custom pricing is not a universal percentage premium over standard RDS. The 54% figure is too broad because the difference changes with engine, edition, licensing model, Region, deployment type, and instance class.
AWS says RDS Custom customers pay for the DB instance, storage, data transfer, and other resources provisioned for the environment. SQL Server Custom supports License Included and BYOM. Oracle Custom uses BYOM.
AWS currently gives a pricing example under the SQL Server Custom section for a db.m5.xlarge Single-AZ instance in US East (N. Virginia) at $0.410 per hour. At 730 hours, that is $299.30 for the instance portion of one month.
Calculation block:
AWS says RDS Custom customers pay for the DB instance, storage, data transfer, and other resources provisioned for the environment. SQL Server Custom supports License Included and BYOM. Oracle Custom uses BYOM.
AWS currently gives a pricing example under the SQL Server Custom section for a db.m5.xlarge Single-AZ instance in US East (N. Virginia) at $0.410 per hour. At 730 hours, that is $299.30 for the instance portion of one month.
Calculation block:
Monthly instance cost
Hourly rate
×
730
$0.410 × 730 = $299.30
Annual on-demand baseline
Hourly rate
×
8,760
$0.410 × 8,760 = $3,591.60
These calculations are illustrative applications of AWS’s published example rate, not universal RDS Custom pricing.
For an RI, use the exact effective hourly rate for your edition, licensing model, instance class, deployment, and Region. AWS renders those rows by configuration, so copying a rate from another setup can create a false comparison.
For an RI, use the exact effective hourly rate for your edition, licensing model, instance class, deployment, and Region. AWS renders those rows by configuration, so copying a rate from another setup can create a false comparison.
Reserved Instance options by engine
The most important purchasing difference is term length.
| RDS option | RI availability | Term options | Payment options | Practical decision |
|---|---|---|---|---|
| RDS Custom SQL Server | Yes | 1 year only | No Upfront, Partial Upfront, All Upfront | Model the one-year renewal cycle |
| RDS Custom Oracle | Yes | 1 or 3 years currently listed | No Upfront for 1 year; Partial or All Upfront for 1 or 3 years | Prioritize migration and verify commitment treatment |
| Standard RDS SQL Server | Yes | 1 or 3 years | No Upfront for 1 year; Partial or All Upfront for 1 or 3 years | Compare one- versus three-year coverage |
For RDS Custom SQL Server, AWS explicitly states that Reserved Instances can be reserved for a one-year term and are available for both License Included and BYOM pricing. Standard RDS Reserved Instances can use one-year or three-year terms, with No Upfront limited to one year.
Oracle needs a different interpretation. AWS still lists one-year and three-year Oracle Custom RIs, but AWS has also announced the service ends March 31, 2027.
AWS’s general RDS Reserved Instances guidance limits No Upfront to one-year terms, while the RDS Custom for Oracle pricing page lists all three payment options without restating that limit, so confirm the currently available RDS Custom for Oracle offerings in your account before purchase.
Any commitment that extends beyond the product’s remaining service life needs careful review. Verify current purchase availability in your account and model the migration date before committing.
Oracle needs a different interpretation. AWS still lists one-year and three-year Oracle Custom RIs, but AWS has also announced the service ends March 31, 2027.
AWS’s general RDS Reserved Instances guidance limits No Upfront to one-year terms, while the RDS Custom for Oracle pricing page lists all three payment options without restating that limit, so confirm the currently available RDS Custom for Oracle offerings in your account before purchase.
Any commitment that extends beyond the product’s remaining service life needs careful review. Verify current purchase availability in your account and model the migration date before committing.
Oracle RI risk: AWS still lists one- and three-year RDS Custom for Oracle Reserved Instances, but the service reaches end of support on March 31, 2027. Before buying any Oracle RDS Custom RI whose term approaches or passes that date, obtain current purchasing availability and post-retirement commitment treatment directly from AWS.
“Before you reserve: verify these 5 things”
An RDS Reserved Instance applies only when a running database matches the reservation’s attributes, so confirm each dimension before you reserve:
Account and Region confirm the AWS account and Region where the database actually runs.
Engine and edition match the exact RDS Custom engine and edition (for example, SQL Server Standard versus Enterprise).
Licensing model License Included versus BYOM.
Deployment Single-AZ versus Multi-AZ, which carry separate reservations.
Instance class, payment option, and term select the instance class, payment option (No Upfront, Partial Upfront, or All Upfront), and term, then confirm the expected workload duration justifies the commitment.
For deeper engine-specific guidance, see the RDS SQL Server Reserved Instances guide.
What an automation pause changes
AWS says full RDS Custom automation includes monitoring and instance recovery. When you need to make supported host changes, you can pause automation, perform the customization, and resume it.
The current pause window is 60 minutes by default and can be configured up to 1,440 minutes, or 24 hours. During the pause, RDS Custom pauses monitoring and instance recovery. The original 72-hour timeout and the statement that backups and Multi-AZ failover are universally suspended during a pause should not be published as written.
A pause is not a cheaper billing state. The DB instance remains provisioned, so normal instance billing continues.
The current pause window is 60 minutes by default and can be configured up to 1,440 minutes, or 24 hours. During the pause, RDS Custom pauses monitoring and instance recovery. The original 72-hour timeout and the statement that backups and Multi-AZ failover are universally suspended during a pause should not be published as written.
A pause is not a cheaper billing state. The DB instance remains provisioned, so normal instance billing continues.
Which option fits your workload
The first question is not “How much can an RI save?” It is “Do I actually need RDS Custom?”
| Workload need | Best starting point | Commitment implication |
|---|---|---|
| No host access or third-party host software | Standard RDS | 1- or 3-year RI options |
| SQL Server needs host access, custom drivers, or persistent agents | RDS Custom SQL Server | One-year RIs only |
| Existing Oracle workload on RDS Custom | Plan migration to EC2 | March 31, 2027 deadline |
| Full control beyond RDS Custom boundaries | Self-managed database on EC2 | You own more operations |
Operational constraints: OS and database access do not mean every change is supported. RDS Custom monitors a defined support perimeter, and an unsupported change can move the instance into an unsupported-configuration state that you must fix manually.
Responsibilities also differ by engine and CEV/RPEV model. Before committing, map who owns each task requires agents and drivers, OS and database patching, filesystem changes, and backups and confirm your customization stays inside the support perimeter.
Responsibilities also differ by engine and CEV/RPEV model. Before committing, map who owns each task requires agents and drivers, OS and database patching, filesystem changes, and backups and confirm your customization stays inside the support perimeter.
If standard RDS meets the application requirement, it is usually the simpler managed option. If standard RDS blocks a required host or database customization, the meaningful comparison may be RDS Custom versus self-managed EC2.
Choose RDS Custom only when the required customization is compatible with the AWS support perimeter and your team accepts the engine-specific operational responsibilities; otherwise, compare against self-managed EC2.
For the operating-cost tradeoff, see RDS vs self-managed database on EC2.
Choose RDS Custom only when the required customization is compatible with the AWS support perimeter and your team accepts the engine-specific operational responsibilities; otherwise, compare against self-managed EC2.
For the operating-cost tradeoff, see RDS vs self-managed database on EC2.
How to reduce RDS Custom cost
Do the architecture work before the commitment work.
- Confirm that OS-level access is genuinely required. If the application can run on standard RDS, you can remove Custom complexity and reopen standard RDS commitment choices.
- Right-size before reserving. Review CPU, memory, storage, I/O, and database-specific performance signals over a representative period. Avoid a generic CPU threshold as an automatic resize rule.
- Confirm the licensing model. SQL Server now supports BYOM on both standard RDS and RDS Custom, so BYOM no longer forces you onto RDS Custom. AWS launched BYOM for standard RDS for SQL Server on June 2, 2026, letting you reuse eligible SQL Server licenses through Microsoft’s License Mobility on the fully managed service; RDS Custom remains the right choice only when you also need OS-level customization or host-side software.
- Match the RI to a stable configuration. For RDS Custom SQL Server, the one-year term still requires the correct edition, licensing, deployment, Region, and instance selection.
- Treat Oracle Custom as a migration program. The March 31, 2027 shutdown date is more important than maximizing a long-term RI discount.
Protect your CEV baseline before production: A CEV preserves a specific engine and OS image, but deleting an AMI that a CEV depends on can cause operations that require host replacement such as compute scaling to fail. Retain source AMIs, version your CEVs, document dependencies, and test upgrade or replacement procedures before production rollout.
Bottom line
Work through these three actions in order:
Validate that the customization you need actually requires RDS Custom and is compatible with the AWS support perimeter.
Confirm the eligible AWS commitment offerings for your exact configuration before you reserve.
For SQL Server Custom, set a one-year renewal review; for Oracle Custom, start the March 31, 2027 migration plan.
For RDS Custom SQL Server, model the one-year renewal cycle. For Oracle Custom, prioritize the March 31, 2027 exit plan.
How Usage.ai helps optimize RDS Custom costs
We help optimize stable RDS Custom spend by identifying workloads that are eligible for Reserved Instance pricing. RDS Reserved Instances are billing discounts applied to matching database usage rather than separate physical resources.
With our Flex Reserved Instances, teams can get 30–40% savings on eligible RDS Custom spend with none of the commitment risk. Learn more about Flex Reserved Instances.
We identify reservation opportunities while accounting for AWS requirements such as Region, engine, licensing model, deployment type, and available commitment terms. For RDS Custom SQL Server, this means working within the one-year Reserved Instance term.
For RDS Custom Oracle, the March 31, 2027 end-of-support deadline should remain a hard constraint before making any commitment decision.
For eligible Flex Commitments, we provide cashback protection according to the Flex Commitment Program terms, with pricing tied to realized savings.
With our Flex Reserved Instances, teams can get 30–40% savings on eligible RDS Custom spend with none of the commitment risk. Learn more about Flex Reserved Instances.
We identify reservation opportunities while accounting for AWS requirements such as Region, engine, licensing model, deployment type, and available commitment terms. For RDS Custom SQL Server, this means working within the one-year Reserved Instance term.
For RDS Custom Oracle, the March 31, 2027 end-of-support deadline should remain a hard constraint before making any commitment decision.
For eligible Flex Commitments, we provide cashback protection according to the Flex Commitment Program terms, with pricing tied to realized savings.
Frequently asked questions
Does RDS Custom support Reserved Instances?
Yes. RDS Custom for SQL Server supports Reserved Instances for a one-year term with No Upfront, Partial Upfront, and All Upfront payment options. AWS also currently lists one-year and three-year Reserved Instances for RDS Custom for Oracle, although Oracle Custom support ends March 31, 2027.
What is a custom engine version in RDS Custom?
A CEV is the engine baseline used to create RDS Custom instances. For Oracle, it combines database installation content with an AMI. For SQL Server, it is based on an AMI containing SQL Server and can preserve approved OS-level customizations.
Is RDS Custom always about 54% more expensive than standard RDS?
No. There is no universal 54% premium. The difference depends on engine, licensing, edition, Region, deployment type, and instance class. Compare current AWS pricing for the exact configurations you are considering.
Can I buy a three-year RI for RDS Custom SQL Server?
No. AWS currently documents RDS Custom for SQL Server Reserved Instances as one-year only. Standard RDS SQL Server supports one-year and three-year RIs.
What should existing RDS Custom Oracle customers do?
Plan a migration before March 31, 2027. AWS recommends transitioning RDS Custom for Oracle workloads to Oracle on Amazon EC2 and provides prescriptive migration guidance.
Share
Facebook
X
LinkedIn
Reddit
