# Amazon RDS Extended Support with Amazon RDS
RDS Extended Support allows you to continue running a database on a major engine version past the RDS end of standard support date for an additional cost.
You can only enroll a database in RDS Extended Support by enabling RDS Extended Support when you first [create](extended-support-creating-db-instance.md) or [restore](extended-support-restoring-db-instance.md) a DB instance. You can't update your RDS Extended Support enrollment status on existing DB instances unless you are restoring them.
If you enabled RDS Extended Support during the creation or restoration of a DB instance, then after the RDS end of standard support date, Amazon RDS will automatically enroll the DB instance in RDS Extended Support. Automatic enrollment into RDS Extended Support doesn't change the database engine and doesn't impact the uptime or performance of your DB instance.
RDS Extended Support provides the following updates and technical support:
+ Security updates for [critical and high CVEs](https://nvd.nist.gov/vuln-metrics/cvss) for your DB instance or DB cluster, including the database engine
+ Bug fixes and patches for critical issues
+ The ability to open support cases and receive troubleshooting help within the standard Amazon RDS service level agreement
This paid offering gives you more time to upgrade to a supported major engine version. For example, the RDS end of standard support date for RDS for MySQL version 5.7 is February 29, 2024. However, you aren't ready to manually upgrade to RDS for MySQL version 8.0 before that date. In this case, Amazon RDS automatically enrolls your databases in RDS Extended Support on February 29, 2024, and you can continue to run RDS for MySQL version 5.7. Starting March 1, 2024, Amazon RDS automatically charges you for RDS Extended Support.
RDS Extended Support is available for up to 3 years past the RDS end of standard support date for a major engine version. After this time, if you haven't upgraded your major engine version to a supported version, then Amazon RDS will automatically upgrade your major engine version. We recommend that you upgrade to a supported major engine version as soon as possible.
For more information about the RDS end of standard support dates and the RDS end of Extended Support dates, see [Supported MySQL major versions on Amazon RDS](MySQL.Concepts.VersionMgmt.md#MySQL.Concepts.VersionMgmt.ReleaseCalendar) and [Release calendar for Amazon RDS for PostgreSQL](https://docs.aws.amazon.com/AmazonRDS/latest/PostgreSQLReleaseNotes/postgresql-release-calendar.html#Release.Calendar).
**Topics**
+ [
# Overview of Amazon RDS Extended Support
](extended-support-overview.md)
+ [
# Amazon RDS Extended Support charges
](extended-support-charges.md)
+ [
# Versions with Amazon RDS Extended Support
](extended-support-versions.md)
+ [
# Amazon RDS and customer responsibilities with Amazon RDS Extended Support
](extended-support-responsibilities.md)
+ [
# Creating a DB instance or a Multi-AZ DB cluster with Amazon RDS Extended Support
](extended-support-creating-db-instance.md)
+ [
# Viewing the enrollment of your DB instances or Multi-AZ DB clusters in Amazon RDS Extended Support
](extended-support-viewing.md)
+ [
# Viewing support dates for engine versions in Amazon RDS Extended Support
](extended-support-viewing-support-dates.md)
+ [
# Restoring a DB instance or a Multi-AZ DB cluster with Amazon RDS Extended Support
](extended-support-restoring-db-instance.md)
# Overview of Amazon RDS Extended Support
After the RDS end of standard support date, if you didn't disable RDS Extended Support during the [creation](extended-support-creating-db-instance.md) or [restoration](extended-support-restoring-db-instance.md) of your DB instances, then Amazon RDS will automatically enroll them in RDS Extended Support. Amazon RDS automatically upgrades your DB instance to the last minor version released before the RDS end of standard support date, if you aren't already running that version. Amazon RDS won't upgrade your minor version until *after* the RDS end of standard support date for your major engine version.
You can create new databases with major engine versions that have reached the RDS end of standard support date. RDS automatically enrolls these new databases in RDS Extended Support and charges you for this offering.
If you upgrade to an engine that's still under RDS standard support *before* the RDS end of standard support date, Amazon RDS won't enroll your engine in RDS Extended Support.
If you attempt to restore a snapshot of a database compatible with an engine that's past the RDS end of standard support date but isn't enrolled in RDS Extended Support, then Amazon RDS will attempt to upgrade the snapshot to be compatible with the latest engine version that is still under RDS standard support. If the restore fails, then Amazon RDS will automatically enroll your engine in RDS Extended Support with a version that's compatible with the snapshot.
You can end enrollment in RDS Extended Support at any time. To end enrollment, upgrade each enrolled engine to a newer engine version that's still under RDS standard support. The end of RDS Extended Support enrollment will be effective the day that you complete an upgrade to a newer engine version that's still under RDS standard support.
For more information about the RDS end of standard support dates and the RDS end of Extended Support dates, see [Supported MySQL major versions on Amazon RDS](MySQL.Concepts.VersionMgmt.md#MySQL.Concepts.VersionMgmt.ReleaseCalendar) and [Release calendar for Amazon RDS for PostgreSQL](https://docs.aws.amazon.com/AmazonRDS/latest/PostgreSQLReleaseNotes/postgresql-release-calendar.html#Release.Calendar).
# Amazon RDS Extended Support charges
You will incur charges for all engines enrolled in RDS Extended Support beginning the day after the RDS end of standard support date. For the RDS end of standard support date, see [Major versions](MySQL.Concepts.VersionMgmt.md#MySQL.Concepts.VersionMgmt.ReleaseCalendar) and [Release calendar for Amazon RDS for PostgreSQL](https://docs.aws.amazon.com/AmazonRDS/latest/PostgreSQLReleaseNotes/postgresql-release-calendar.html). RDS Extended Support charges apply to standby instances in Multi-AZ deployments.
The additional charge for RDS Extended Support automatically stops when you take one of the following actions:
+ Upgrade to an engine version that's covered under standard support.
+ Delete the database that's running a major version past the RDS end of standard support date.
The charges will restart if your target engine version enters RDS Extended Support in the future.
For example, RDS for PostgreSQL 11 enters Extended Support on March 1, 2024, but charges don't start until April 1, 2024. You upgrade your RDS for PostgreSQL 11 database to RDS for PostgreSQL 12 on April 30, 2024. You will only be charged for 30 days of Extended Support on RDS for PostgreSQL 11. You continue running RDS for PostgreSQL 12 on this DB instance past the RDS end of standard support date of February 28, 2025. Your database will again incur RDS Extended Support charges starting on March 1, 2025.
For more information, see [Amazon RDS for MySQL pricing](https://aws.amazon.com/rds/mysql/pricing/) and [Amazon RDS for PostgreSQL pricing](https://aws.amazon.com/rds/postgresql/pricing/).
## Avoiding charges for Amazon RDS Extended Support
You can avoid being charged for RDS Extended Support by preventing RDS from creating or restoring a DB instance or a Multi-AZ DB cluster past the RDS end of standard support date. To do this, use the AWS CLI or the RDS API.
In the AWS CLI, specify `open-source-rds-extended-support-disabled` for the `--engine-lifecycle-support` option. In the RDS API, specify `open-source-rds-extended-support-disabled` for the `LifeCycleSupport` parameter. For more information, see [Creating a DB instance or a Multi-AZ DB cluster](extended-support-creating-db-instance.md) or [Restoring a DB instance or a Multi-AZ DB cluster](extended-support-restoring-db-instance.md).
# Versions with Amazon RDS Extended Support
RDS Extended Support is only available for major versions. It isn't available for minor versions.
RDS Extended Support is available for RDS for MySQL and for RDS for PostgreSQL. For more information, see [Major versions](MySQL.Concepts.VersionMgmt.md#MySQL.Concepts.VersionMgmt.ReleaseCalendar) and [Release calendar for Amazon RDS for PostgreSQL](https://docs.aws.amazon.com/AmazonRDS/latest/PostgreSQLReleaseNotes/postgresql-release-calendar.html) in the *Amazon RDS for PostgreSQL Release Notes*.
You can also view information about support dates for engine versions by using the AWS CLI or the RDS API. For more information, see [Viewing support dates for engine versions in Amazon RDS Extended Support](extended-support-viewing-support-dates.md).
## Amazon RDS Extended Support version naming
Amazon RDS will release new minor versions with fixes and CVE patches for engines on RDS Extended Support. For more information, see [Amazon RDS Extended Support versions for RDS for MySQL](MySQL.Concepts.VersionMgmt.md#mysql-extended-support-releases) and [Amazon RDS Extended Support updates for RDS for PostgreSQL](https://docs.aws.amazon.com/AmazonRDS/latest/PostgreSQLReleaseNotes/postgresql-extendedsupport.html) in the *Amazon RDS for PostgreSQL Release Notes*.
The names of these minor releases will be in the form *major.minor-RDS.YYYYMMDD.patch.YYYYMMDD*, for example, 5.7.44-RDS.20240208.R2.20240210 (for RDS for MySQL) or 11.22-RDS.20240208.R2.20240210 (for RDS for PostgreSQL).
**major**
For MySQL, the major version number is both the integer and the first fractional part of the version number, for example, 8.0. A major version upgrade increases the major part of the version number. For example, an upgrade from 5.7.44 to 8.0.33 is a major version upgrade, where *5.7 *and *8.0* are the major version numbers.
For PostgreSQL, the major version number is the integer, for example, 11.
**minor-RDS.YYYYMMDD**
For MySQL, the minor version number is the third part of the version number, for example, the 44-RDS.20240208 in 5.7.44-RDS.20240208.
For PostgeSQL, the minor version number is the second part of version number, for example, the 22-RDS.20240208in 11.22-RDS.20240208.
The date is when Amazon RDS created the Amazon RDS minor version.
**patch**
The patch version is what follows the date when Amazon RDS created the Amazon RDS minor version, for example, the R2 in 5.7.44-RDS.20240208.R2 or 11.22-RDS.20240208.R2.
An Amazon RDS patch version includes important bug fixes added to an Amazon RDS minor version after its release.
**YYYYMMDD**
The date is when Amazon RDS created the patch version, for example, the 20240210 in 5.7.44-RDS.20240208.R2.20240210 or 11.22-RDS.20240208.R2.20240210.
An Amazon RDS dated version is a security patch that includes important security fixes added to a minor version after its release. It doesn't include any fixes that might change an engine's behavior.
# Amazon RDS and customer responsibilities with Amazon RDS Extended Support
The following content describes the responsibilities of Amazon RDS and your responsibilities with RDS Extended Support.
**Topics**
+ [
## Amazon RDS responsibilities
](#extended-support-rds-responsibilities)
+ [
## Your responsibilities
](#extended-support-customer-responsibilities)
## Amazon RDS responsibilities
After the RDS end of standard support date, Amazon RDS will supply patches, bug fixes, and upgrades for engines that are enrolled in RDS Extended Support. This will occur for up to 3 years, or until you stop using the engines, whichever happens first.
The patches will be for Critical and High CVEs as defined by the National Vulnerability Database (NVD) CVSS severity ratings. For more information, see [Vulnerability Metrics](https://nvd.nist.gov/vuln-metrics/cvss#).
## Your responsibilities
You're responsible for applying the patches, bug fixes, and upgrades given for DB instances or Multi-AZ DB clusters enrolled in RDS Extended Support. Amazon RDS reserves the right to change, replace, or withdraw such patches, bug fixes, and upgrades at any time. If a patch is necessary to address security or critical stability issues, Amazon RDS reserves the right to update your DB instances or Multi-AZ DB clusters with the patch, or to require that you install the patch.
You're also responsible for upgrading your engine to a newer engine version *before* the RDS end of Extended Support date. The RDS end of Extended Support date is typically 3 years after the RDS standard support date. For the RDS end of Extended Support date for your database major engine version, see [Major versions](MySQL.Concepts.VersionMgmt.md#MySQL.Concepts.VersionMgmt.ReleaseCalendar) and [Release calendar for Amazon RDS for PostgreSQL](https://docs.aws.amazon.com/AmazonRDS/latest/PostgreSQLReleaseNotes/postgresql-release-calendar.html).
If you don't upgrade your engine, then after the RDS end of Extended Support date, Amazon RDS will attempt to upgrade your engine to a newer engine version that's supported under RDS standard support. If the upgrade fails, then Amazon RDS reserves the right to delete the DB instance or Multi-AZ DB cluster that's running the engine past the RDS end of standard support date. However, before doing so, Amazon RDS will preserve your data from that engine.
# Creating a DB instance or a Multi-AZ DB cluster with Amazon RDS Extended Support
When you create a DB instance or a Multi-AZ DB cluster, select **Enable RDS Extended Support** in the console, or use the Extended Support option in the AWS CLI or the parameter in the RDS API. When you enroll a DB instance or a Multi-AZ DB cluster in Amazon RDS Extended Support, it is permanently enrolled in RDS Extended Support for the life of the DB instance or Multi-AZ DB cluster.
If you use the console, you must select **Enable RDS Extended Support**. The setting isn't selected by default.
If you use the AWS CLI or the RDS API and don't specify the RDS Extended Support setting, Amazon RDS defaults to enabling RDS Extended Support. When you automate by using [CloudFormation](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-rds-dbinstance.html#aws-resource-rds-dbinstance-return-values:~:text=EngineLifecycleSupport) or other services, this default behavior maintains the availability of your database past the RDS end of standard support date.
You can prevent enrollment in RDS Extended Support by using the [AWS CLI](#extended-support-creating-db-instance-create-cli) or the [RDS API](#extended-support-creating-db-instance-create-api) to create a DB instance or a Multi-AZ DB cluster.
**Topics**
+ [
## RDS Extended Support behavior
](#extended-support-creating-db-instance-behavior)
+ [
## Considerations for RDS Extended Support
](#extended-support-creating-db-instance-considerations)
+ [
## Create a DB instance or a Multi-AZ DB cluster with RDS Extended Support
](#extended-support-creating-db-instance-create)
## RDS Extended Support behavior
The following table summarizes what happens when a major engine version reaches the RDS end of standard support.
| RDS Extended Support status\$1 | Behavior |
| --- | --- |
| Enabled | Amazon RDS charges you for RDS Extended Support. |
| Disabled | Amazon RDS upgrades your DB instance or Multi-AZ DB cluster to a supported engine version. This upgrade takes place on or shortly after the RDS end of standard support date. |
\$1 In the RDS console, the RDS Extended Support status appears as Yes or No. In the AWS CLI or RDS API, the RDS Extended Support status appears as `open-source-rds-extended-support` or `open-source-rds-extended-support-disabled`.
## Considerations for RDS Extended Support
Before creating a DB instance or a Multi-AZ DB cluster, consider the following items:
+ *After* the RDS end of standard support date has passed, you can prevent the creation of a new DB instance or a new Multi-AZ DB cluster and avoid RDS Extended Support charges. To do this, use the AWS CLI or the RDS API. In the AWS CLI, specify `open-source-rds-extended-support-disabled` for the `--engine-lifecycle-support` option. In the RDS API, specify `open-source-rds-extended-support-disabled` for the `LifeCycleSupport` parameter. If you specify `open-source-rds-extended-support-disabled` and the RDS end of standard support date has passed, creating a DB instance or a Multi-AZ DB cluster will always fail.
+ RDS Extended Support is set at the cluster level. Members of a cluster will always have the same setting for RDS Extended Support in the RDS console, `--engine-lifecycle-support` in the AWS CLI, and `EngineLifecycleSupport` in the RDS API.
For more information, see [MySQL versions](MySQL.Concepts.VersionMgmt.md) and [Release calendars for Amazon RDS for PostgreSQL](https://docs.aws.amazon.com/AmazonRDS/latest/PostgreSQLReleaseNotes/postgresql-release-calendar.html).
## Create a DB instance or a Multi-AZ DB cluster with RDS Extended Support
You can create a DB instance or a Multi-AZ DB cluster with an RDS Extended Support version using the AWS Management Console, the AWS CLI, or the RDS API.
### Console
When you create a DB instance or a Multi-AZ DB cluster, in the **Engine options** section, select **Enable RDS Extended Support**. This setting isn't selected by default.
The following image shows the **Enable RDS Extended Support** setting:
![\[\]](http://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/images/extended-support-enable.png)
### AWS CLI
When you run the [create-db-instance](https://docs.aws.amazon.com/cli/latest/reference/rds/create-db-instance.html) or [create-db-cluster](https://docs.aws.amazon.com/cli/latest/reference/rds/create-db-cluster.html) (Multi-AZ DB cluster) AWS CLI command, select RDS Extended Support by specifying `open-source-rds-extended-support` for the `--engine-lifecycle-support` option. By default, this option is set to `open-source-rds-extended-support`.
To prevent the creation of a new DB instance or a Multi-AZ DB cluster after the RDS end of standard support date, specify `open-source-rds-extended-support-disabled` for the `--engine-lifecycle-support` option. By doing so, you will avoid any associated RDS Extended Support charges.
### RDS API
When you use the [CreateDBInstance](https://docs.aws.amazon.com/AmazonRDS/latest/APIReference/API_CreateDBInstance.html) or [CreateDBCluster](https://docs.aws.amazon.com/AmazonRDS/latest/APIReference/API_CreateDBCluster.html) (Multi-AZ DB cluster) Amazon RDS API operation, select RDS Extended Support by setting the `EngineLifecycleSupport` parameter to `open-source-rds-extended-support`. By default, this parameter is set to `open-source-rds-extended-support`.
To prevent the creation of a new DB instance or a Multi-AZ DB cluster after the RDS end of standard support date, specify `open-source-rds-extended-support-disabled` for the `EngineLifecycleSupport` parameter. By doing so, you will avoid any associated RDS Extended Support charges.
For more information, see the following topics:
+ To create a DB instance, follow the instructions for your DB engine in [Creating an Amazon RDS DB instance](USER_CreateDBInstance.md).
+ To create a Multi-AZ DB cluster, follow the instructions for your DB engine in [Creating a Multi-AZ DB cluster for Amazon RDS](create-multi-az-db-cluster.md).
# Viewing the enrollment of your DB instances or Multi-AZ DB clusters in Amazon RDS Extended Support
You can view the enrollment of your DB instances or Multi-AZ DB clusters in RDS Extended Support using the AWS Management Console, the AWS CLI, or the RDS API.
**Note**
The **RDS Extended Support** column in the console, the -`-engine-lifecycle-support` option in the AWS CLI, and the `EngineLifecycleSupport` parameter in the RDS API only indicate enrollment in RDS Extended Support. Charges for RDS Extended Support only start when your DB engine version has reached the RDS end of standard support. For more information, see [Major versions](MySQL.Concepts.VersionMgmt.md#MySQL.Concepts.VersionMgmt.ReleaseCalendar) and [Release calendar for Amazon RDS for PostgreSQL](https://docs.aws.amazon.com/AmazonRDS/latest/PostgreSQLReleaseNotes/postgresql-release-calendar.html) in the *Amazon RDS for PostgreSQL Release Notes*.
For example, you have an RDS for MySQL 5.7 database that is enrolled in RDS Extended Support. On March 1, 2024, Amazon RDS started charging you for RDS Extended Support for this database. On July 31, 2024, you upgraded this database to RDS for MySQL 8.0. The RDS Extended Support status for this database remains enabled. However, the RDS Extended Support charges for this database stopped because RDS for MySQL 8.0 hadn't reached RDS end of standard support yet. Amazon RDS won't charge you for RDS Extended Support for this database until August 1, 2026, which is when RDS standard support ends for RDS for MySQL 8.0.
## Console
**To view the enrollment of your DB instances or Multi-AZ DB clusters in RDS Extended Support**
1. Sign in to the AWS Management Console and open the Amazon RDS console at [https://console.aws.amazon.com/rds/](https://console.aws.amazon.com/rds/).
1. In the navigation pane, choose **Databases**. The value under **RDS Extended Support** indicates if a DB instance or Multi-AZ DB cluster is enrolled in RDS Extended Support. If no value appears, then RDS Extended Support isn't available for your database.
**Tip**
If the **RDS Extended Support** column doesn't appear, choose the **Preferences** icon, and then turn on **RDS Extended Support**.
![\[The Databases section with the RDS Extended Support setting for each database in the RDS console.\]](http://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/images/extended-support-view-db-list.png)
1. You can also view the enrollment on the **Configuration** tab for each database. Choose a database under **DB identifier**. On the **Configuration** tab, look under **Extended Support** to see if the database is enrolled or not.
![\[The Configuration tab on a database details page that shows the RDS Extended Support status.\]](http://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/images/extended-support-view-details.png)
## AWS CLI
To view the enrollment of your databases in RDS Extended Support by using the AWS CLI, run the [describe-db-instances](https://docs.aws.amazon.com/cli/latest/reference/rds/describe-db-instances.html) or [describe-db-clusters](https://docs.aws.amazon.com/cli/latest/reference/rds/describe-db-clusters.html) (Multi-AZ DB clusters) command.
If RDS Extended Support is available for a database, then the response includes the parameter `EngineLifecycleSupport`. The value `open-source-rds-extended-support` indicates that a DB instance or Multi-AZ DB cluster is enrolled in RDS Extended Support. The value `open-source-rds-extended-support-disabled` indicates that enrollment of the DB instance or Multi-AZ DB cluster in RDS Extended Support was disabled.
**Example**
The following command returns information for all of your DB instances:
```
aws rds describe-db-instances
```
The following response shows that a PostgreSQL engine running on the DB instance `database-1` is enrolled in RDS Extended Support:
```
{
"DBInstanceIdentifier": "database-1",
"DBInstanceClass": "db.t3.large",
"Engine": "postgres",
...
"EngineLifecycleSupport": "open-source-rds-extended-support"
}
```
## RDS API
To view the enrollment of your databases in RDS Extended Support by using the Amazon RDS API, use the [DescribeDBInstances](https://docs.aws.amazon.com/AmazonRDS/latest/APIReference/API_DescribeDBInstances.html) or [DescribeDBClusters](https://docs.aws.amazon.com/AmazonRDS/latest/APIReference/API_DescribeDBClusters.html) operation.
If RDS Extended Support is available for a database, then the response includes the parameter `EngineLifecycleSupport`. The value `open-source-rds-extended-support` indicates that a DB instance or Multi-AZ DB cluster is enrolled in RDS Extended Support. The value `open-source-rds-extended-support-disabled` indicates that enrollment of the DB instance or Multi-AZ DB cluster in RDS Extended Support was disabled.
# Viewing support dates for engine versions in Amazon RDS Extended Support
You can view information about support dates for engine versions for your DB instances or Multi-AZ DB clusters in Amazon RDS Extended Support by using the AWS CLI or the RDS API. This information can help you plan for upgrades.
AWS CLI commands and RDS API operations return start and end dates for RDS standard support and RDS Extended Support. These dates can also be found in the major engine version tables. For more information, see [Supported MySQL major versions on Amazon RDS](MySQL.Concepts.VersionMgmt.md#MySQL.Concepts.VersionMgmt.ReleaseCalendar) and [Release calendar for Amazon RDS for PostgreSQL](https://docs.aws.amazon.com/AmazonRDS/latest/PostgreSQLReleaseNotes/postgresql-release-calendar.html) in the *Amazon RDS for PostgreSQL Release Notes*.
## AWS CLI
To view the start and end dates for RDS standard support and RDS Extended Support for your major engine versions by using the AWS CLI, run the [describe-db-major-engine-versions](https://docs.aws.amazon.com/cli/latest/reference/rds/describe-db-major-engine-versions.html) command.
This command returns the following relevant parameters for open source engines (MariaDB, MySQL, and PostgreSQL). It doesn't return these parameters for commercial engines (Db2, SQL Server, and Oracle).
+ `SupportedEngineLifecycles` – This parameter is an array of objects that include `LifecycleSupportName`, `LifecycleSupportStartDate`, and `LifecycleSupportEndDate`.
+ `LifecycleSupportName` – This parameter indicates the type of support the engine version is in: RDS standard support (`open-source-rds-standard-support`) or RDS Extended Support (`open-source-rds-extended-support`). For MariaDB, this parameter only returns RDS standard support (`open-source-rds-standard-support`).
+ `LifecycleSupportStartDate` – This parameter lists the start date for either RDS standard support or RDS Extended Support for the major engine version, depending on the value of `LifecycleSupportName`.
+ `LifecycleSupportEndDate` – This parameter lists the end date for either RDS standard support or RDS Extended Support for the major engine version, depending on the value of `LifecycleSupportName`.
**Example**
The response example shows the following information:
+ The start and end dates for the supported engine lifecycles `open-source-rds-standard-support` and `open-source-rds-extended-support` for MySQL 5.7. RDS Extended Support is available for MySQL 5.7.
+ The start and end dates for the supported engine lifecycle `open-source-rds-standard-support` for MariaDB 10.6. RDS Extended Support isn't available for MariaDB 10.6.
+ No information about supported engine lifecycles for SQL Server Enterprise Edition 13 because SQL Server is a commercial engine.
```
{
"DBMajorEngineVersions": [
{
"Engine": "mysql",
"MajorEngineVersion": "5.7",
"SupportedEngineLifecycles": [
{
"LifecycleSupportName": "open-source-rds-standard-support",
"LifecycleSupportStartDate": "2016-02-22T00:00:00+00:00",
"LifecycleSupportEndDate": "2024-02-29T23:59:59.999000+00:00"
},
{
"LifecycleSupportName": "open-source-rds-extended-support",
"LifecycleSupportStartDate": "2024-03-01T00:00:00+00:00",
"LifecycleSupportEndDate": "2027-02-28T23:59:59.999000+00:00"
}
]
},
{
"Engine": "mariadb",
"MajorEngineVersion": "10.6",
"SupportedEngineLifecycles": [
{
"LifecycleSupportName": "open-source-rds-standard-support",
"LifecycleSupportStartDate": "2022-02-03T00:00:00+00:00",
"LifecycleSupportEndDate": "2026-07-31T23:59:59.999000+00:00"
}
]
},
{
"Engine": "sqlserver-ee",
"MajorEngineVersion": "13.00"
},
...
]
}
```
## RDS API
To view the start and end dates for RDS standard support and RDS Extended Support for your major engine versions by using the RDS API, use the [DescribeDBMajorEngineVersions](https://docs.aws.amazon.com/AmazonRDS/latest/APIReference/API_DescribeDBMajorEngineVersions.html) operation.
If RDS Extended Support is available for an engine version, then the response includes the parameter `SupportedEngineLifeCycles` as an array with two objects. One object includes the start and end dates for RDS standard support. The second object includes the start and end dates for RDS Extended Support.
If RDS Extended Support isn't available for an open source engine version (MariaDB, MySQL, and PostgreSQL), then the response only includes the parameter `SupportedEngineLifeCycles` as an array with a single object. This object includes the start and end dates for RDS standard support.
If the engine version is for a commercial engine (Db2, SQL Server, and Oracle), then the response doesn't include the parameter `SupportedEngineLifeCycles`.
# Restoring a DB instance or a Multi-AZ DB cluster with Amazon RDS Extended Support
When you restore a DB instance or a Multi-AZ DB cluster, select **Enable RDS Extended Support** in the console, or use the Extended Support option in the AWS CLI or the parameter in the RDS API. When you enroll a DB instance or Multi-AZ DB cluster in RDS Extended Support, it is permanently enrolled in RDS Extended Support for the life of the DB instance or Multi-AZ DB cluster.
The default for the RDS Extended Support setting depends on whether you use the console, the AWS CLI, or the RDS API to restore your database. If you use the console, you don't select **Enable RDS Extended Support**, and the major engine version you are restoring is past the RDS end of standard support, then Amazon RDS automatically upgrades your DB instance to a newer engine version. If you use the AWS CLI or the RDS API and you don't specify the RDS Extended Support setting, then Amazon RDS defaults to enabling RDS Extended Support. When you automate by using [CloudFormation](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-rds-dbinstance.html#aws-resource-rds-dbinstance-return-values:~:text=EngineLifecycleSupport) or other services, this default behavior maintains the availability of your database past the RDS end of standard support date. You can disable RDS Extended Support by using the AWS CLI or the RDS API.
**Topics**
+ [
## RDS Extended Support behavior
](#extended-support-restoring-db-instance-behavior)
+ [
## Considerations for RDS Extended Support
](#extended-support-restoring-db-instance-considerations)
+ [
## Restore a DB instance or a Multi-AZ DB cluster with RDS Extended Support
](#extended-support-restoring-db-instance-restore)
## RDS Extended Support behavior
The following table summarizes what happens when a major engine version of a DB instance or a Multi-AZ DB cluster that you are restoring has reached the RDS end of standard support.
| RDS Extended Support status\$1 | Behavior |
| --- | --- |
| Enabled | Amazon RDS charges you for RDS Extended Support. |
| Disabled\$1\$1 | After the restore finishes, Amazon RDS automatically upgrades your DB instance or Multi-AZ DB cluster to a newer engine version (in a future maintenance window). |
\$1 In the RDS console, the RDS Extended Support status appears as Yes or No. In the AWS CLI or RDS API, the RDS Extended Support status appears as `open-source-rds-extended-support` or `open-source-rds-extended-support-disabled`.
\$1\$1 This option is only available when restoring a DB instance or a Multi-AZ DB cluster running PostgreSQL 12 and higher or MySQL 8 and higher.
## Considerations for RDS Extended Support
Before restoring a DB instance or a Multi-AZ DB cluster, consider the following items:
+ *After* the RDS end of standard support date has passed, if you want to restore a DB instance or a Multi-AZ DB cluster from Amazon S3, you can only do so by using the AWS CLI or the RDS API. Use the `--engine-lifecycle-support` option in the [restore-db-cluster-from-s3](https://docs.aws.amazon.com/cli/latest/reference/rds/restore-db-cluster-from-s3.html) AWS CLI command or the `EngineLifecycleSupport` parameter in the [RestoreDBClusterFromS3](https://docs.aws.amazon.com/AmazonRDS/latest/APIReference/API_RestoreDBClusterFromS3.html) RDS API operation.
+ If you want to prevent RDS from restoring your databases to RDS Extended Support versions, specify `open-source-rds-extended-support-disabled` in the AWS CLI or the RDS API. By doing so, you will avoid any associated RDS Extended Support charges.
If you specify this setting, Amazon RDS will automatically upgrade your restored database to a newer, supported major version. If the upgrade fails pre-upgrade checks, Amazon RDS will safely roll back to the RDS Extended Support engine version. This database will remain in RDS Extended Support mode, and Amazon RDS will charge you for RDS Extended Support until you manually upgrade your database.
For example, if you restore a MySQL 5.7 snapshot without using RDS Extended Support, Amazon RDS will attempt to automatically upgrade your database to MySQL 8.0. If this upgrade fails because of an issue that you need to resolve, Amazon RDS will roll back the database to MySQL 5.7. Amazon RDS will keep the database on RDS Extended Support until you can fix the issue. For example, an upgrade might fail because of insufficient storage space. After you fix the issue, you must initiate the upgrade. After the first attempt to upgrade your database, Amazon RDS won't attempt to upgrade it again.
+ RDS Extended Support is set at the cluster level. Members of a cluster will always have the same setting for RDS Extended Support in the RDS console, `--engine-lifecycle-support` in the AWS CLI, and `EngineLifecycleSupport` in the RDS API.
For more information, see [MySQL versions](MySQL.Concepts.VersionMgmt.md) and [Release calendars for Amazon RDS for PostgreSQL](https://docs.aws.amazon.com/AmazonRDS/latest/PostgreSQLReleaseNotes/postgresql-release-calendar.html).
## Restore a DB instance or a Multi-AZ DB cluster with RDS Extended Support
You can restore a DB instance or a Multi-AZ DB cluster with an RDS Extended Support version using the AWS Management Console, the AWS CLI, or the RDS API.
### Console
When you restore a DB instance or a Multi-AZ DB cluster, select **Enable RDS Extended Support** in the **Engine options** section. If you don't select this setting and the major engine version that you are restoring is past the RDS end of standard support, then Amazon RDS automatically upgrades your DB instance or Multi-AZ DB cluster to a version under RDS standard support.
The following image shows the **Enable RDS Extended Support** setting:
![\[\]](http://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/images/extended-support-enable.png)
### AWS CLI
When you run the [restore-db-instance-from-db-snapshot](https://docs.aws.amazon.com/cli/latest/reference/rds/restore-db-instance-from-db-snapshot.html) or [restore-db-cluster-from-snapshot](https://docs.aws.amazon.com/cli/latest/reference/rds/restore-db-cluster-from-snapshot.html) AWS CLI command, select RDS Extended Support by specifying `open-source-rds-extended-support` for the `--engine-lifecycle-support` option.
If you want to avoid charges associated with RDS Extended Support, set the `--engine-lifecycle-support` option to `open-source-rds-extended-support-disabled`. By default, this option is set to `open-source-rds-extended-support`.
You can also specify this value using the following AWS CLI commands:
+ [restore-db-cluster-from-s3](https://docs.aws.amazon.com/cli/latest/reference/rds/restore-db-cluster-from-s3.html)
+ [restore-db-cluster-to-point-in-time](https://docs.aws.amazon.com/cli/latest/reference/rds/restore-db-cluster-to-point-in-time.html)
+ [restore-db-instance-from-s3](https://docs.aws.amazon.com/cli/latest/reference/rds/restore-db-instance-from-s3.html)
+ [restore-db-instance-to-point-in-time](https://docs.aws.amazon.com/cli/latest/reference/rds/restore-db-instance-to-point-in-time.html)
### RDS API
When you use the [RestoreDBInstanceFromDBSnapshot](https://docs.aws.amazon.com/AmazonRDS/latest/APIReference/API_RestoreDBInstanceFromDBSnapshot.html) or [RestoreDBClusterFromSnapshot](https://docs.aws.amazon.com/AmazonRDS/latest/APIReference/API_RestoreDBClusterFromSnapshot.html) Amazon RDS API operation, select RDS Extended Support by setting the `EngineLifecycleSupport` parameter to `open-source-rds-extended-support`.
If you want to avoid charges associated with RDS Extended Support, set the `EngineLifecycleSupport` parameter to `open-source-rds-extended-support-disabled`. By default, this parameter is set to `open-source-rds-extended-support`.
You can also specify this value using the following RDS API operations:
+ [RestoreDBClusterFromS3](https://docs.aws.amazon.com/AmazonRDS/latest/APIReference/API_RestoreDBClusterFromS3.html)
+ [RestoreDBClusterToPointInTime](https://docs.aws.amazon.com/AmazonRDS/latest/APIReference/API_RestoreDBClusterToPointInTime.html)
+ [RestoreDBInstanceFromS3](https://docs.aws.amazon.com/AmazonRDS/latest/APIReference/API_RestoreDBInstanceFromS3.html)
+ [RestoreDBInstanceToPointInTime](https://docs.aws.amazon.com/AmazonRDS/latest/APIReference/API_RestoreDBInstanceToPointInTime.html)
For more information about restoring a DB instance or a Multi-AZ DB cluster, follow the instructions for your DB engine in [Restoring to a DB instance](USER_RestoreFromSnapshot.md).