Amazon Neptune
User Guide (API Version 2017-11-29)

Maintaining an Amazon Neptune DB Cluster

Periodically, Neptune performs maintenance on Neptune resources. Maintenance most often involves updates to the DB cluster's underlying operating system (OS) or database engine version. Updates to the operating system most often occur for security issues and should be done as soon as possible.

Maintenance items require that Neptune take your DB cluster offline for a short time. Maintenance that require a resource to be offline include scale compute operations, which generally take only a few minutes from start to finish, and 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) and seldom requires more than a fraction of your maintenance window.

DB instances are not automatically backed up when an OS update is applied, so you should back up your DB instances before you apply an update.

You can view whether a maintenance update is available for your DB cluster by using the Neptune console, the AWS CLI, or the Neptune API. If an update is available, it is indicated by the word Available or Required in the Maintenance column for the DB cluster on the Neptune console.

If an update is available, you can take one of the actions.

  • Defer the maintenance items.

  • Apply the maintenance items immediately.

  • Schedule the maintenance items to start during your next maintenance window.

  • Take no action.


Certain OS updates are marked as Required. If you defer a required update, you receive a notice from Neptune indicating when the update will be performed. Other updates are marked as Available, and these you can defer indefinitely.

The maintenance window determines when pending operations start, but does not limit the total execution time of these operations. Maintenance operations are not guaranteed to finish before the maintenance window ends, and can continue beyond the specified end time. For more information, see The Neptune Maintenance Window.

The Neptune Maintenance Window

Every DB cluster has a weekly maintenance window during which any system changes are applied. You can think of the maintenance window as an opportunity to control when modifications and software patching occur, in the event either are requested or required. If a maintenance event is scheduled for a given week, it is 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 30-minute maintenance window is selected at random from an 8-hour block of time per region. If you don't specify a preferred maintenance window when you create the DB cluster, then Neptune assigns a 30-minute maintenance window on a randomly selected day of the week.

Neptune will consume some of the resources on your DB cluster 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.

Following, you can find the time blocks for each region from which default maintenance windows are assigned.

Region Time Block
US West (Oregon) Region 06:00–14:00 UTC
US West (N. California) Region 06:00–14:00 UTC
US East (Ohio) Region 03:00–11:00 UTC
EU (Ireland) Region 22:00–06:00 UTC

Adjusting the Preferred DB Cluster Maintenance Window

The Neptune DB cluster maintenance window should fall at the time of lowest usage and thus might need modification from time to time. Your DB cluster is unavailable during this time only if the updates that are being applied require an outage. The outage is for the minimum amount of time required to make the necessary updates.

AWS Management Console

To adjust the preferred DB cluster maintenance window

  1. Sign in to the AWS Management Console, and open the Amazon Neptune console at

  2. Choose Clusters on the left of the console.

  3. Choose the DB cluster for which you want to change the maintenance window.

  4. From Actions, choose Modify cluster.

  5. In the Maintenance section, update the maintenance window.

  6. Choose Continue.

    On the confirmation page, review your changes.

  7. To apply the changes to the maintenance window immediately, select Apply immediately.

  8. Choose Modify cluster to save your changes.

    Alternatively, choose Back to edit your changes, or choose Cancel to cancel your changes.