# Maintaining a DB instance
Periodically, Amazon RDS performs maintenance on Amazon RDS resources. The following topics describe these maintenance actions and how to apply them.
## Overview of DB instance maintenance updates
Maintenance most often involves updates to the following resources in your DB instance:
+ Underlying hardware
+ Underlying operating system (OS)
+ Database engine version
Updates to the operating system most often occur for security issues. We recommend that you do them as soon as possible. For more information about operating system updates, see [Applying updates to a DB instance ](#USER_UpgradeDBInstance.OSUpgrades).
**Topics**
+ [
### Offline resources during maintenance updates
](#USER_UpgradeDBInstance.Maintenance.Overview.offline)
+ [
### Deferred DB instance modifications
](#USER_UpgradeDBInstance.Maintenance.Overview.Deferred)
+ [
### Eventual consistency for the DescribePendingMaintenanceActions API
](#USER_UpgradeDBInstance.Maintenance.Overview.eventual-consistency)
### Offline resources during maintenance updates
Some maintenance items require that Amazon RDS take your DB instance offline for a short time. Maintenance items that require a resource to be offline include required operating system or database patching. Required patching is automatically scheduled only for patches that are related to security and instance reliability. Such patching occurs infrequently, typically once every few months. It seldom requires more than a fraction of your maintenance window.
### Deferred DB instance modifications
Deferred DB instance modifications that you have chosen not to apply immediately are applied during the maintenance window. For example, you might choose to change the DB instance class or parameter group during the maintenance window. Such modifications that you specify using the **pending reboot** setting don't show up in the **Pending maintenance** list. For information about modifying a DB instance, see [Modifying an Amazon RDS DB instance](Overview.DBInstance.Modifying.md).
To see the modifications that are pending for the next maintenance window, use the [describe-db-instances](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/rds/describe-db-instances.html) AWS CLI command and check the `PendingModifiedValues` field.
### Eventual consistency for the DescribePendingMaintenanceActions API
The Amazon RDS `DescribePendingMaintenanceActions` API follows an eventual consistency model. This means that the result of the `DescribePendingMaintenanceActions` command might not be immediately visible to all subsequent RDS commands. Keep this in mind when you use `DescribePendingMaintenanceActions` immediately after using a previous API command.
Eventual consistency can affect the way you managed your maintenance updates. For example, if you run the `ApplyPendingMaintenanceActions` command to update the database engine version for a DB instance, it will eventually be visible to `DescribePendingMaintenanceActions`. In this scenario, `DescribePendingMaintenanceActions` might show that the maintenance action wasn't applied even though it was.
To manage eventual consistency, you can do the following:
+ Confirm the state of your DB instance before you run a command to modify it. Run the appropriate `DescribePendingMaintenanceActions` command using an exponential backoff algorithm to ensure that you allow enough time for the previous command to propagate through the system. To do this, run the `DescribePendingMaintenanceActions` command repeatedly, starting with a couple of seconds of wait time, and increasing gradually up to five minutes of wait time.
+ Add wait time between subsequent commands, even if a `DescribePendingMaintenanceActions` command returns an accurate response. Apply an exponential backoff algorithm starting with a couple of seconds of wait time, and increase gradually up to about five minutes of wait time.
## Viewing pending maintenance updates
View whether a maintenance update is available for your DB instance by using the RDS console, the AWS CLI, or the RDS API. If an update is available, it is indicated in the **Maintenance** column for the DB instance on the Amazon RDS console, as shown in this figure.
![\[Maintenance action is available and will be applied at the next maintenance window.\]](http://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/images/offlinepatchavailable.png)
If no maintenance update is available for a DB instance, the column value is **none** for it.
If a maintenance update is available for a DB instance, the following column values are possible:
+ **required** – The maintenance action will be applied to the resource and can't be deferred indefinitely.
+ **available** – The maintenance action is available, but it will not be applied to the resource automatically. You can apply it manually.
+ **next window** – The maintenance action will be applied to the resource during the next maintenance window.
+ **In progress** – The maintenance action is being applied to the resource.
If an update is available, you can do one of the following:
+ If the maintenance value is **next window**, defer the maintenance actions by choosing **Defer upgrade** from **Actions**. You can't defer a maintenance action that has already started.
+ Apply the maintenance actions immediately.
+ Apply the maintenance actions during your next maintenance window.
+ Take no action.
**To take an action by using the AWS Management Console**
1. Choose the DB instance to show its details.
1. Choose **Maintenance & backups**. The pending maintenance actions appear.
1. Choose the action to take, then choose when to apply it.
![\[Pending maintenance items for an RDS DB instance.\]](http://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/images/pending_maintenance_rds.png)
The maintenance window determines when pending operations start, but doesn't limit the total run time of these operations. Maintenance operations aren't guaranteed to finish before the maintenance window ends, and can continue beyond the specified end time. For more information, see [Amazon RDS maintenance window](#Concepts.DBMaintenance).
You can also view whether a maintenance update is available for your DB instance by running the [describe-pending-maintenance-actions](https://docs.aws.amazon.com/cli/latest/reference/rds/describe-pending-maintenance-actions.html) AWS CLI command.
For information about applying maintenance updates, see [Applying updates to a DB instance ](#USER_UpgradeDBInstance.OSUpgrades).
### Maintenance actions for Amazon RDS
The following maintenance actions apply to RDS DB instances:
+ `server-certificate-rotation` – Rotate the Amazon RDS server certificate for the DB instance.
**Note**
Engines that support rotation without restart don't receive this notification. Amazon RDS for Oracle DB instances will receive this notification, but they don't require restart. Only the database listener is restarted during the server certificate rotation. Existing database connections are unaffected, but new connections will encounter errors for a brief period while the listener is restarted. See [Automatic server certificate rotation](UsingWithRDS.SSL-certificate-rotation.md#UsingWithRDS.SSL-certificate-rotation-server-cert-rotation) for details.
+ `db-upgrade` – Upgrade the DB engine version for the DB instance.
+ `hardware-maintenance` – Perform maintenance on the underlying hardware for the DB instance.
+ `system-update` – Update the operating system for the DB instance.
## Maintenance for Multi-AZ deployments
Running a DB instance as a Multi-AZ deployment can further reduce the impact of a maintenance event. This result is because Amazon RDS applies operating system updates by following these steps:
1. Perform maintenance on the standby.
1. Promote the standby to primary.
1. Perform maintenance on the old primary, which becomes the new standby.
If you upgrade the database engine for your DB instance in a Multi-AZ deployment, Amazon RDS modifies both primary and secondary DB instances at the same time. In this case, both the primary and secondary DB instances in the Multi-AZ deployment are unavailable during the upgrade. This operation causes downtime until the upgrade is complete. The duration of the downtime varies based on the size of your DB instance.
If there are underlying operating system patches that need to be applied, a short Multi-AZ failover is required to apply the patches to the primary DB instance. This failover typically lasts less than a minute.
If your DB instance runs RDS for MySQL, RDS for PostgreSQL, or RDS for MariaDB, you can minimize the downtime required for an upgrade by using a blue/green deployment. For more information, see [Using Amazon RDS Blue/Green Deployments for database updates](blue-green-deployments.md). If you upgrade an RDS for SQL Server or RDS Custom for SQL Server DB instance in a Multi-AZ deployment, then Amazon RDS performs rolling upgrades, so you have an outage only for the duration of a failover. For more information, see [Multi-AZ considerations](USER_UpgradeDBInstance.SQLServer.Considerations.md#USER_UpgradeDBInstance.SQLServer.MAZ).
For more information about Multi-AZ deployments, see [Configuring and managing a Multi-AZ deployment for Amazon RDS](Concepts.MultiAZ.md).
## Amazon RDS maintenance window
The maintenance window is a weekly time interval during which any system changes are applied. Every DB instance has a weekly maintenance window. The maintenance window is an opportunity to control when modifications and software patching occur. For more information about adjusting the maintenance window, see [Adjusting the preferred DB instance maintenance window](#AdjustingTheMaintenanceWindow).
RDS consumes some of the resources on your DB instance while maintenance is being applied. You might observe a minimal effect on performance. For a DB instance, on rare occasions, a Multi-AZ failover might be required for a maintenance update to complete.
If a maintenance event is scheduled for a given week, it's initiated during the 30-minute maintenance window you identify. Most maintenance events also complete during the 30-minute maintenance window, although larger maintenance events may take more than 30 minutes to complete. The maintenance window is paused when the DB instance is stopped.
The 30-minute maintenance window is selected at random from an 8-hour block of time per region. If you don't specify a maintenance window when you create the DB instance, RDS assigns a 30-minute maintenance window on a randomly selected day of the week.
The following table shows the time blocks for each AWS Region from which default maintenance windows are assigned.
****
[\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.Maintenance.html)
**Topics**
+ [
### Adjusting the preferred DB instance maintenance window
](#AdjustingTheMaintenanceWindow)
### Adjusting the preferred DB instance maintenance window
The maintenance window should fall at the time of lowest usage and thus might need modification from time to time. Your DB instance is unavailable during this time only if the system changes, such as a change in DB instance class, are being applied and require an outage. Your DB instance is unavailable only for the minimum amount of time required to make the necessary changes.
In the following example, you adjust the preferred maintenance window for a DB instance.
For this example, we assume that a DB instance named *mydbinstance* exists and has a preferred maintenance window of "Sun:05:00-Sun:06:00" UTC.
#### Console
**To adjust the preferred maintenance window**
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**, and then select the DB instance that you want to modify.
1. Choose **Modify**. The **Modify DB instance** page appears.
1. In the **Maintenance** section, update the maintenance window.
**Note**
The maintenance window and the backup window for the DB instance cannot overlap. If you enter a value for the maintenance window that overlaps the backup window, an error message appears.
1. Choose **Continue**.
On the confirmation page, review your changes.
1. To apply the changes to the maintenance window immediately, select **Apply immediately**.
1. Choose **Modify DB instance** to save your changes.
Alternatively, choose **Back** to edit your changes, or choose **Cancel** to cancel your changes.
#### AWS CLI
To adjust the preferred maintenance window, use the AWS CLI [https://docs.aws.amazon.com/cli/latest/reference/rds/modify-db-instance.html](https://docs.aws.amazon.com/cli/latest/reference/rds/modify-db-instance.html) command with the following parameters:
+ `--db-instance-identifier`
+ `--preferred-maintenance-window`
**Example**
The following code example sets the maintenance window to Tuesdays from 4:00-4:30AM UTC.
For Linux, macOS, or Unix:
```
aws rds modify-db-instance \
--db-instance-identifier mydbinstance \
--preferred-maintenance-window Tue:04:00-Tue:04:30
```
For Windows:
```
aws rds modify-db-instance ^
--db-instance-identifier mydbinstance ^
--preferred-maintenance-window Tue:04:00-Tue:04:30
```
#### RDS API
To adjust the preferred maintenance window, use the Amazon RDS API [https://docs.aws.amazon.com/AmazonRDS/latest/APIReference/API_ModifyDBInstance.html](https://docs.aws.amazon.com/AmazonRDS/latest/APIReference/API_ModifyDBInstance.html) operation with the following parameters:
+ `DBInstanceIdentifier`
+ `PreferredMaintenanceWindow`
## Applying updates to a DB instance
With Amazon RDS, you can choose when to apply maintenance operations. You can decide when Amazon RDS applies updates by using the AWS Management Console, AWS CLI, or RDS API.
### Console
**To manage an update for a DB instance**
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**.
1. Choose the DB instance that has a required update.
1. For **Actions**, choose one of the following:
+ **Patch now**
+ **Patch at next window**
**Note**
If you choose **Patch at next window** and later want to delay the update, you can choose **Defer upgrade**. You can't defer a maintenance action if it has already started.
To cancel a maintenance action, modify the DB instance and disable **Auto minor version upgrade**.
### AWS CLI
To apply a pending update to a DB instance, use the [apply-pending-maintenance-action](https://docs.aws.amazon.com/cli/latest/reference/rds/apply-pending-maintenance-action.html) AWS CLI command.
**Example**
For Linux, macOS, or Unix:
```
aws rds apply-pending-maintenance-action \
--resource-identifier arn:aws:rds:us-west-2:001234567890:db:mysql-db \
--apply-action system-update \
--opt-in-type immediate
```
For Windows:
```
aws rds apply-pending-maintenance-action ^
--resource-identifier arn:aws:rds:us-west-2:001234567890:db:mysql-db ^
--apply-action system-update ^
--opt-in-type immediate
```
**Note**
To defer a maintenance action, specify `undo-opt-in` for `--opt-in-type`. You can't specify `undo-opt-in` for `--opt-in-type` if the maintenance action has already started.
To cancel a maintenance action, run the [modify-db-instance](https://docs.aws.amazon.com/cli/latest/reference/rds/modify-db-instance.html) AWS CLI command and specify `--no-auto-minor-version-upgrade`.
To return a list of resources that have at least one pending update, use the [describe-pending-maintenance-actions](https://docs.aws.amazon.com/cli/latest/reference/rds/describe-pending-maintenance-actions.html) AWS CLI command.
**Example**
For Linux, macOS, or Unix:
```
aws rds describe-pending-maintenance-actions \
--resource-identifier arn:aws:rds:us-west-2:001234567890:db:mysql-db
```
For Windows:
```
aws rds describe-pending-maintenance-actions ^
--resource-identifier arn:aws:rds:us-west-2:001234567890:db:mysql-db
```
You can also return a list of resources for a DB instance by specifying the `--filters` parameter of the `describe-pending-maintenance-actions` AWS CLI command. The format for the `--filters` command is `Name=filter-name,Value=resource-id,...`.
The following are the accepted values for the `Name` parameter of a filter:
+ `db-instance-id` – Accepts a list of DB instance identifiers or Amazon Resource Names (ARNs). The returned list only includes pending maintenance actions for the DB instances identified by these identifiers or ARNs.
+ `db-cluster-id` – Accepts a list of DB cluster identifiers or ARNs for Amazon Aurora. The returned list only includes pending maintenance actions for the DB clusters identified by these identifiers or ARNs.
For example, the following example returns the pending maintenance actions for the `sample-instance1` and `sample-instance2` DB instances.
**Example**
For Linux, macOS, or Unix:
```
aws rds describe-pending-maintenance-actions \
--filters Name=db-instance-id,Values=sample-instance1,sample-instance2
```
For Windows:
```
aws rds describe-pending-maintenance-actions ^
--filters Name=db-instance-id,Values=sample-instance1,sample-instance2
```
### RDS API
To apply an update to a DB instance, call the Amazon RDS API [https://docs.aws.amazon.com/AmazonRDS/latest/APIReference/API_ApplyPendingMaintenanceAction.html](https://docs.aws.amazon.com/AmazonRDS/latest/APIReference/API_ApplyPendingMaintenanceAction.html) operation.
To return a list of resources that have at least one pending update, call the Amazon RDS API [https://docs.aws.amazon.com/AmazonRDS/latest/APIReference/API_DescribePendingMaintenanceActions.html](https://docs.aws.amazon.com/AmazonRDS/latest/APIReference/API_DescribePendingMaintenanceActions.html) operation.
## Operating system updates for RDS DB instances
RDS for Db2, RDS for MariaDB, RDS for MySQL, RDS for PostgreSQL, RDS for SQL Server, RDS for Oracle and RDS Custom for SQL Server DB instances occasionally require operating system updates. Amazon RDS upgrades the operating system to a newer version to improve database performance and customers’ overall security posture. Typically, the updates take about 10 minutes. Operating system updates don't change the DB engine version or DB instance class of a DB instance.
Operating system updates can be either optional or mandatory:
+ An **optional update** can be applied at any time. While these updates are optional, we recommend that you apply them periodically to keep your RDS fleet up to date. RDS *does not* apply these updates automatically.
To be notified when a new, optional operating system patch becomes available, you can subscribe to [RDS-EVENT-0230](USER_Events.Messages.md#RDS-EVENT-0230) in the security patching event category. For information about subscribing to RDS events, see [Subscribing to Amazon RDS event notification](USER_Events.Subscribing.md).
**Note**
`RDS-EVENT-0230` doesn't apply to operating system distribution upgrades.
+ A **mandatory update** is required and has an apply date. Plan to schedule your update before this apply date. After the specified apply date, Amazon RDS automatically upgrades the operating system for your DB instance to the latest version during one of your assigned maintenance windows.
**Note**
Staying current on all optional and mandatory updates might be required to meet various compliance obligations. We recommend that you apply all updates made available by RDS routinely during your maintenance windows.
You can use the AWS Management Console or the AWS CLI to get information about the type of operating system upgrade.
### Console
**To get update information using the AWS Management Console**
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**, and then select the DB instance.
1. Choose **Maintenance & backups**.
1. In the **Pending maintenance** section, find the operating system update, and check the **Status** value.
In the AWS Management Console, an optional update has its maintenance **Status** set to **available** and doesn't have an **Apply date**, as shown in the following image.
![\[Optional operating system update.\]](http://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/images/os-update-optional.png)
A mandatory update has its maintenance **Status** set to **required** and has an **Apply date**, as shown in the following image.
![\[Required operating system update.\]](http://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/images/os-update-required.png)
### AWS CLI
To get update information from the AWS CLI, use the [describe-pending-maintenance-actions](https://docs.aws.amazon.com/cli/latest/reference/rds/describe-pending-maintenance-actions.html) command.
```
aws rds describe-pending-maintenance-actions
```
A mandatory operating system update includes an `AutoAppliedAfterDate` value and a `CurrentApplyDate` value. An optional operating system update doesn't include these values.
The following output shows a mandatory operating system update.
```
{
"ResourceIdentifier": "arn:aws:rds:us-east-1:123456789012:db:mydb1",
"PendingMaintenanceActionDetails": [
{
"Action": "system-update",
"AutoAppliedAfterDate": "2022-08-31T00:00:00+00:00",
"CurrentApplyDate": "2022-08-31T00:00:00+00:00",
"Description": "New Operating System update is available"
}
]
}
```
The following output shows an optional operating system update.
```
{
"ResourceIdentifier": "arn:aws:rds:us-east-1:123456789012:db:mydb2",
"PendingMaintenanceActionDetails": [
{
"Action": "system-update",
"Description": "New Operating System update is available"
}
]
}
```
### Availability of operating system updates
Operating system updates are specific to DB engine version and DB instance class. Therefore, DB instances receive or require updates at different times. When an operating system update is available for your DB instance based on its engine version and instance class, the update appears in the console. It can also be viewed by running the [describe-pending-maintenance-actions](https://docs.aws.amazon.com/cli/latest/reference/rds/describe-pending-maintenance-actions.html) AWS CLI command or by calling the [DescribePendingMaintenanceActions](https://docs.aws.amazon.com/AmazonRDS/latest/APIReference/API_DescribePendingMaintenanceActions.html) RDS API operation. If an update is available for your instance, you can update your operating system by following the instructions in [Applying updates to a DB instance ](#USER_UpgradeDBInstance.OSUpgrades).
# Using AWS Organizations upgrade rollout policy for automatic minor version upgrades
Amazon RDS supports AWS Organizations upgrade rollout policy to manage automatic minor version upgrades across multiple database resources and AWS accounts. This policy helps you implement a controlled upgrade strategy for your instances by:
**How upgrade rollout policy works**
When a new minor engine version becomes eligible for automatic upgrade, the policy controls the upgrade sequence based on defined orders:
+ Resources marked as [first] (typically development environments) become eligible for upgrades during their maintenance windows.
+ After a designated bake time, resources marked as [second] become eligible.
+ After another designated bake time, resources marked as [last] (typically production environments) become eligible.
+ Monitoring upgrade progress through AWS Health notifications.
You can define your upgrade orders by:
+ Account-level policies – Apply to all eligible resources in specified accounts.
+ Resource tags – Apply to specific resources based on tags.
**Note**
Resources not configured with an upgrade policy or excluded from the policy automatically receive an upgrade order of [second].
**Prerequisites**
+ Your AWS account must be part of an organization in Organizations with upgrade rollout policy enabled
+ Enable automatic minor version upgrades for your instances
+ Tags are not strictly required for upgrade rollout policy. If you want to define specific upgrade orders for different environments (for example, development, test, QA, production), you can use tags. If you don't include tag settings in your policy, all resources under that policy follow the default upgrade order.
**Prerequisites**
+ Your AWS account must be part of an organization in Organizations with upgrade rollout policy enabled
+ Enable automatic minor version upgrades for your instances
+ Tag your resources to identify their environment (for example, development, test, production)
**To tag your resources**
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**.
1. Choose the instance you want to tag.
1. Choose **Actions**, then choose **Manage tags**.
1. Choose **Add tag**.
1. Enter your tag key (for example, 'Environment') and value (for example, 'Development')
1. Choose **Add tag**, then **Save**.
You can also add tags using the AWS CLI:
```
aws rds add-tags-to-resource \
--resource-name arn:aws:rds:region:account-number:db:instance-name \
--tags Key=Environment,Value=Development
```
## Upgrade order and phases
The upgrade rollout policy supports three upgrade orders:
+ [first] - Typically used for development or testing environments
+ [second] - Typically used for QA environments. Default order for resources not specifically configured
+ [last] - Usually reserved for production environments
When a new minor engine version becomes eligible for automatic upgrade:
+ Resources with upgrade order [first] become eligible for upgrades during their configured maintenance windows.
+ After a designated bake time, resources with upgrade order [second] become eligible for upgrades during their maintenance windows.
+ After another designated bake time, resources with upgrade order [last] become eligible for upgrades during their maintenance windows.
+ The automatic minor version upgrade campaign closes after all eligible resources with upgrade orders [first], [second], and [last] have been upgraded, or when the campaign reaches its scheduled end date, whichever comes first.
**Note**
All automatic minor version upgrades are performed during each instance's configured maintenance window to minimize potential impact to your applications.
## Observability
### AWS Health and monitoring
You receive AWS health notifications:
+ Before the start of an automatic minor version upgrade campaign
+ Between each phase transition to help track and monitor upgrade progress
+ Progress updates showing the number of resources upgraded across your fleet in the AWS Health console
Amazon RDS event notifications:
+ Notifications for resources enabled for automatic minor version upgrades, including:
+ When your resource becomes eligible for upgrade based on its upgrade order ([first], [second], or [last])
+ Scheduled upgrade timeline during the maintenance window
+ Individual database upgrade start and completion status
+ Subscribe to these events through Amazon EventBridge0 for automated monitoring
### Considerations
Some considerations to keep in mind:
+ The policy applies to all future automatic minor version upgrade campaigns, including policy changes made during active campaigns.
+ If you join an ongoing upgrade campaign, your resources follow the current running upgrade order and do not wait for a configured policy.
+ Resources not configured with an upgrade policy automatically receive an upgrade order of [second].
+ The policy provides validation periods between upgrade phases before proceeding to the next phase.
+ Changes to either the policy or resource tags require time to propagate before the new upgrade order is applied.
+ The policy applies only to Amazon RDS resources with automatic minor version upgrades enabled.
+ If you detect an issue within an environment, you can turn off automatic minor version upgrades for subsequent environments or use the validation period to resolve issues before upgrades proceed to the next upgrade order.
**Note**
This feature supports automatic minor version upgrades for Oracle Database engine versions released after January 2026.
For more information about tagging RDS resources, see [Tagging Amazon RDS resources](USER_Tagging.md). For detailed instructions on setting up and using upgrade rollout policy, see [ Getting started with AWS Organizations](https://docs.aws.amazon.com/organizations/latest/userguide/orgs_getting-started.html) in the *AWS Organizations User Guide*.