Menu
Amazon Relational Database Service
User Guide (API Version 2014-10-31)

Modifying an Amazon RDS DB Instance and Using the Apply Immediately Parameter

Most modifications to a DB instance can be applied immediately or applied during the next maintenance window. Some modifications, such as parameter group changes, require that you manually reboot your DB instance for the change to take effect. Some modifications result in an outage because Amazon RDS must reboot your DB instance for the change to take effect.

Note

When you modify some DB instance settings, an outage occurs because the DB instance is rebooted. Review the impact to your database and applications before modifying your DB instance settings.

When you modify a DB instance, you have the option of applying the changes immediately by selecting the Apply Immediately option in the AWS Management Console, using the --apply-immediately parameter when using the AWS CLI, or setting the ApplyImmediately parameter to true when using the Amazon RDS API.

Common Settings and the Impact of Apply Immediately

The following table contains details about which settings you can modify, when the changes can be applied, the impact of the Apply Immediately setting, and whether the changes cause downtime for the DB instance.

DB Instance SettingDowntime NotesIf Apply Immediately is set to trueIf Apply Immediately is set to false

Allocated Storage

No downtime. Performance may be degraded during the change.

The change occurs immediately.

The change occurs during the next maintenance window.

Auto Minor Version Upgrade

An outage occurs if a newer minor version is available, and Amazon RDS has enabled automatic patching for that engine version.

The change is applied asynchronously, as soon as possible.

The change is applied asynchronously, as soon as possible.

Backup Retention Period

An outage occurs if you change from 0 to a non-zero value, or from a non-zero value to 0.

The change occurs immediately.

If you change the setting from a non-zero value to another non-zero value, the change is applied asynchronously, as soon as possible. In all other cases, the change occurs during the next maintenance window.

Backup Window

The change is applied asynchronously, as soon as possible.

The change is applied asynchronously, as soon as possible.

Database Port

The DB instance is rebooted immediately.

The change occurs immediately.

The change occurs immediately. This setting ignores the Apply Immediately setting.

DB Instance Class

An outage occurs during this change.

The change occurs immediately.

The change occurs during the next maintenance window.

DB Instance Identifier

An outage occurs during this change. The DB instance is rebooted.

The change occurs immediately.

The change occurs during the next maintenance window.

DB Parameter Group

An outage doesn't occur during this change. However, parameter changes only occur when you reboot the DB instance manually without failover.

The parameter group change occurs immediately. However, parameter changes only occur when you reboot the DB instance manually without failover.

The parameter group change occurs immediately. However, parameter changes only occur when you reboot the DB instance manually without failover.

License Model

An outage occurs during this change.

The change occurs immediately.

The change occurs during the next maintenance window.

Maintenance Window

If there are one or more pending actions that cause a outage, and the maintenance window is changed to include the current time, then those pending actions are applied immediately, and an outage occurs.

If you set the window to the current time, there must be at least 30 minutes between the current time and end of the window to ensure pending changes are applied.

The change occurs immediately.

The change occurs immediately.

Multi-AZ Deployment

The change occurs immediately.

The change occurs during the next maintenance window.

New Master Password

The change is applied asynchronously, as soon as possible.

The change is applied asynchronously, as soon as possible. This setting ignores the Apply Immediately setting.

Option Group

If the change results in an option group that enables Oracle OEM, this change can cause a brief (sub-second) period during which new connections are rejected. Existing connections are not interrupted.

The change occurs immediately.

The change occurs during the next maintenance window.

Publicly Accessible

The change occurs immediately.

The change occurs immediately. This setting ignores the Apply Immediately setting.

Security Group

The change is applied asynchronously, as soon as possible.

The change is applied asynchronously, as soon as possible. This setting ignores the Apply Immediately setting.

Storage Type

The following changes all result in a brief outage while the process starts.

  • From General Purpose (SSD) to Magnetic.

  • From General Purpose (SSD) to Provisioned IOPS (SSD), if you are using a custom parameter group.

  • From Magnetic to General Purpose (SSD).

  • From Magnetic to Provisioned IOPS (SSD).

  • From Provisioned IOPS (SSD) to Magnetic.

  • From Provisioned IOPS (SSD) to General Purpose (SSD), if you are using a custom parameter group.

The change occurs immediately.

The change occurs during the next maintenance window.