Modifying a Neptune DB Instance (and Applying Immediately) - Amazon Neptune
Settings and Downtime Effects
Services or capabilities described in Amazon Web Services documentation might vary by Region. To see the differences applicable to the China Regions, see Getting Started with Amazon Web Services in China (PDF).

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

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

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 Downtime notes

DB instance class

An outage occurs during this change, whether it is applied immediately or during the next maintenance window.

DB instance identifier

The DB instance is rebooted and an outage occurs during this change, whether it is applied immediately or during the next maintenance window.

Subnet group

The DB instance is rebooted and an outage occurs during this change, whether it is applied immediately or during the next maintenance window.

Security group

The change is applied asynchronously as soon as possible, regardless of when you specify changes should take place, and no outage results.

–

Certificate Authority

By default, the DB instance is restarted when you assign a new Certificate Authority.

Database Port

The change always occurs immediately, causing the DB instance to be rebooted, and an outage occurs.

DB parameter group

Changing this setting doesn't result in an outage. The parameter group name itself is changed immediately, but the actual parameter changes are not applied until you reboot the instance without failover. In this case, the DB instance isn't rebooted automatically, and the parameter changes aren't applied during the next maintenance window. However, if you modify dynamic parameters in the newly associated DB parameter group, these changes are applied immediately without a reboot.

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

DB cluster parameter group

The DB parameter group name is changed immediately.

Backup retention period

If you specify that changes should occur immediately, this change does occur immediately. Otherwise, if you change the setting from a nonzero value to another nonzero value, the change is applied asynchronously, as soon as possible. Any other 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.

Audit log

Select Audit log if you want to use audit logging through CloudWatch Logs. You must also set the neptune_enable_audit_log parameter in the DB cluster parameter group to enable (1) for audit logging to be enabled.

Auto minor version upgrade

Select Enable auto minor version upgrade if you want to enable your Neptune DB cluster to receive minor engine version upgrades automatically when they become available.

The Auto minor version upgrade option only applies to upgrades to minor engine versions for your Amazon Neptune DB cluster. It doesn't apply to regular patches applied to maintain system stability.