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

Amazon Neptune Engine Updates 2018-06-22


Amazon Neptune is generally available. All new Neptune DB clusters, including those restored from snapshots, will be created in Neptune once the engine update is complete for that region.

Updates are applied to Neptune DB clusters during system maintenance windows. The timing when updates are applied depends on the region and maintenance window setting for the DB cluster, as well as the type of update.


The instance maintenance window does not apply to engine updates.

Updates are applied to all instances in a DB cluster simultaneously. An update requires a database restart on all instances in a DB cluster, so you will experience 20 to 30 seconds of downtime, after which you can resume using your DB cluster or clusters. You can view or change your maintenance window settings from the

Should you have any questions or concerns, the AWS Support Team is available on the community forums and through AWS Premium Support.


  • Fixed an issue where a large number of bulk load requests are issued in quick succession results in an error.

  • Fixed a data-dependent issue where a query could fail with an InternalServerError. The following example shows the type of query affected.

    g.V("my-id123").as("start").outE("knows").has("edgePropertyKey1","myedge").inV().as("end").select("start", "end", "myedge").by("vertexPropertyKey1").by("vertexPropertyKey1").by("edgePropertyKey1")
  • Fixed an issue where a Gremlin Java client cannot connect to the server using the same WebSocket connection after the timeout of a long-running query.

  • Fixed an issue where the escaped sequences contained as part of the Gremlin query over HTTP or string-based queries over the WebSocket connection were not handled correctly.

On this page: