Modifying a Neptune DB Instance (and Applying Immediately) - Amazon Neptune

Modifying a Neptune DB Instance (and Applying Immediately)

You can apply most changes to an Amazon Neptune DB instance immediately or defer them until 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.

Important

Some modifications result in an outage because Neptune must reboot your DB instance for the change to be applied. Review the impact to your database and applications before modifying your DB instance settings.

Effects of the Apply Immediately Option

When you modify a DB instance, you can apply the changes immediately. To apply changes immediately, choose the Apply immediately option on the AWS Management Console.

If you don't choose to apply changes immediately, the changes are put into the pending modifications queue. During the next maintenance window, any pending changes in the queue are applied.

Important

If you choose to apply the changes immediately, any changes in the pending modifications queue are also applied. If any of the pending modifications require downtime, choosing to apply changes immediately can cause unexpected downtime.

Common Settings and Downtime Implications

The following table contains details about which settings you can change, when the changes can be applied, and whether the changes cause downtime for the DB instance.

DB instance setting When the change occurs Downtime notes

Allocated storage

If Apply immediately is selected, the change occurs immediately.

If Apply immediately is not selected, the change occurs during the next maintenance window.

No downtime. Performance might be degraded during the change.

Auto minor version upgrade

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

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

Backup retention period

If Apply immediately is selected, the change occurs immediately.

If Apply immediately is not selected, and you change the setting from a nonzero value to another nonzero value, the change is applied asynchronously, as soon as possible. Otherwise, the change occurs during the next maintenance window.

An outage occurs if you change from zero to a nonzero value, or from a nonzero value to zero.

Backup window

The change is applied asynchronously, as soon as possible.

DB instance class

If Apply immediately is selected, the change occurs immediately.

If Apply immediately is not selected, the change occurs during the next maintenance window.

An outage occurs during this change.

DB instance identifier

If Apply immediately is selected, the change occurs immediately.

If Apply immediately is not selected, the change occurs during the next maintenance window.

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

DB parameter group

Note: Parameter group can only be changed for an entire cluster.

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

For more information, see Rebooting a DB Instance in Amazon Neptune.

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

Maintenance window

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

If there are one or more pending actions that cause an outage, and the maintenance window is changed to include the current time, 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 that any pending changes are applied.

Security group

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