Amazon RDS Extended Support vs Standard Support Explained

Image shows Piyush kalra with a lime green background

Piyush Kalra

Jun 2, 2025

    Table of contents will appear here.
    Table of contents will appear here.
    Table of contents will appear here.


Relational databases sit at the core of both digital commerce and enterprise applications, quietly powering transactions and analytics. Thanks to Amazon RDS, administrators can offload much of the heavy lifting while still working with familiar systems such as MySQL, PostgreSQL, Oracle, SQL Server, and MariaDB.

Legacy database engines, however, rarely receive fresh security updates, and that shortfall can expose companies to breaches, regulatory fines, or unexpected outages. A single lapse in patching might alienate customers or cripple high-traffic periods, underscoring the need for a proactive maintenance strategy. The good news is that Amazon RDS support offers built-in mechanisms to shield users from those very threats.

Included with every Amazon RDS deployment, Standard Support covers routine patches, configuration advice, and round-the-clock access to cloud engineers; Extended Support handles older versions that have reached their mainstream release end-of-life and requires a separate, usage-based fee. Both options deliver timely software fixes and expert recommendations, yet they differ significantly in duration and scope, as every database manager quickly discovers.

Selecting a database support plan will, almost immediately, affect performance characteristics, influence overall system stability, and reshape the expense ledger. This article outlines each plan's design, the prescribed advantages, and the operational scenarios where one choice cof ourts favors over another so that you can settle on the option best suited to your institution. By engaging with RDS Support on a proactive cadence, you condition the environment to endure fewer interruptions and edge the company toward a forward-looking posture.

What is Amazon RDS Standard Support?

RDS Standard Support is the baseline help contract that comes bundled with Amazon RDS; it supplies the minimum safeguards needed to keep cloud-hosted databases reliable and secure.

What’s Included in Standard Support:

  • Timely security updates push critical patches as soon as vulnerabilities are confirmed.

  • Routine bug fixes and maintenance updates for each supported engine version prevent reliability gaps.

  • Automated lifecycle management chores, backups, minor version upgrades, and maintenance windows reduce manual overhead.

  • Guaranteed availability and operational continuity within specified SLAs.

Who Benefits from Standard Support?

  • Companies running current major engine releases get full protection because the necessary patches and fixes are in scope.

  • Teams that schedule updates at regular intervals find it easier to avoid end-of-life cliffs.

Limitations of Standard Support:

  • End-of-Life Constraints: Moving from one major release to its successor can trigger API incompatibilities, deprecated features, or delayed query plans. Thorough regression testing keeps surprise outages out of production.

  • Upgrade Requirements: Maintaining compatibility during upgrades can require significant planning.

  • No Coverage for Unsupported Versions: Standard Support does not apply to older database versions outside the supported lifecycle.

What is Amazon RDS Extended Support?

Amazon RDS Extended Support is a premium, subscription-based service that safeguards databases whose engine versions have officially reached end-of-life. By paying for Extended Support, a team can defer the immediate shock of a major version jump while organizing a migration roadmap.

What’s Included:

  • Customers receive critical security patches that address CVE-flagged vulnerabilities, plus bug fixes for issues proven to degrade stability or performance.

  • Compatibility with the retired engine remains intact; many releases do not force an immediate major version change

  • Technical Support within Amazon RDS’s standard SLA.

Who Should Use Extended Support?

  • Legacy enterprises dependent on a specific engine release can postpone disruptive updates without sacrificing security.

  • Teams engaged in intricate, multi-step migration projects find the breathing room essential for thorough testing.

  • Regulated financial and healthcare firms welcome the ongoing patch coverage that meets compliance audit requirements.

Key Features

  • The plan covers widely used engines such as MySQL 5.7, PostgreSQL 12, and their corresponding Aurora variants.

  • Availability by Region and multi-AZ configurations for advanced deployments.

  • Cost occurs at the usual per-vCPU rate, so costs rise or fall directly with daily consumption.

Comparing RDS Extended Support and Standard Support

Selecting the right Amazon RDS support plan begins with a close look at what each tier actually delivers. Below is a side-by-side comparison:

Feature

Standard Support

Extended Support

Security Updates

Provided for active versions

Available for older versions

Major Version Upgrades Required?

Yes, when support ends

No, allows deferred upgrades

SLA-Backed Support

Yes

Yes

Pricing

Included in RDS pricing

Additional cost per vCPU

Database Engine Versions Supported

Current major versions

Older major versions

Ideal For

Regularly updated systems

Legacy/compatibility-focused systems

Which Support Option is Right for You?

Choosing between Amazon RDS Standard Support and Extended Support depends on your database requirements, upgrade plans, and regulatory needs. Here's a quick guide to help you decide:

Opt for Standard Support If:

  • A production database already runs on a broadly accepted major release and picks up engine patches automatically.

  • The operations team is comfortable moving to successor versions within the pre-announced end-of-life windows.

  • Controlling operational costs is non-negotiable, since Standard Support accompanies every paid RDS provision without extra charge.

Choose Extended Support If:

  • Legacy applications depend on distinctly older database engines that do not share obvious feature parity with newer lines.

  • Auditors in heavily regulated sectors insist on uninterrupted security patching, even if that means locking to one release for twelve months or more.

  • Migration planning demands breathing room for extensive testing; Extended Support simply gives whoever owns the project the time to validate without panic.

Understand RDS Extended Support Costs 

Amazon RDS Extended Support provides security updates and bug fixes for database versions no longer covered by standard support, but it comes at an additional cost. 

Cost Calculation: 

  • Per vCPU per Hour: Costs depend on the number of vCPUs and hours your instances run. 

  • First Two Years: Typically $0.10 per vCPU per hour (region-dependent). 

  • Third Year: Usually increases to $0.20 per vCPU per hour. 

  • Applies to All Instances: Charges include primary, standby (Multi-AZ), and read replicas. 

  • Automatic Enrollment: Eligible instances are automatically enrolled unless disabled, starting the day after standard support ends. 

Example: For a db.r5.large instance with 2 vCPUs at $0.10 per vCPU per hour: 

  • Monthly Cost: $144 

  • Annual Cost: $1,752 

Running 10 such instances would cost $17,520 annually for Extended Support. 

After Three Years: 

The support stream ends after three calendar frames, at which point AWS pushes the database engine to a mainstream variant and trims Extended Support invoices from the sutured billing.

How to Enable or Upgrade to RDS Extended Support

Enabling Extended Support on an Amazon RDS instance is designed to be straightforward. Follow these steps:

  1. Check Compatibility: Ensure your database engine version is eligible for Extended Support. 

  2. Purchase Extended Support: Go to the AWS Management Console and select the Extended Support option. 

  3. Activate Extended Support during Instance Creation: Use the AWS Console or CLI to enable the "Enable Extended Support" option. 

  4. Upgrade Existing Instances: Select eligible instances and enable Extended Support by following the prompts in the AWS Console.

Tips for a Smooth Transition:

  • Schedule upgrades before the fixed date when standard support ceases.

  • Use Amazon RDS automatic failover features to keep downtime brief during the transition.

Conclusion

Long-term planners must weigh the incremental cost of RDS Extended Support against the moral hazard of an unpatched legacy system. Scalable architecture options remain in balance with regulatory compliance; put more simply, the choice maps neatly to organizational risk appetite at any given moment.

Having trouble settling on a database strategy? Take a close look at Amazon RDS Extended Support and steer your database operations with newfound certainty.

Join Pump for Free

If you are an early-stage startup that wants to save on cloud costs, use this opportunity. If you are a start-up business owner who wants to cut down the cost of using the cloud, then this is your chance. Pump helps you save up to 60% in cloud costs, and the best thing about it is that it is absolutely free!

Pump provides personalized solutions that allow you to effectively manage and optimize your Azure, GCP and AWS spending. Take complete control over your cloud expenses and ensure that you get the most from what you have invested. Who would pay more when we can save better?

Are you ready to take control of your cloud expenses?

Similar Blog Posts

1390 Market Street, San Francisco, CA 94102

Made with

in San Francisco, CA

© All rights reserved. Pump Billing, Inc.