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

Amazon Neptune Engine Updates 2018-11-19


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.


  • Added support for Gremlin Query Hints.

  • Improved error messages for IAM authentication. For more information, see IAM Authentication Errors.

  • Improved SPARQL query performance with a high number of predicates.

  • Improved SPARQL property path performance.

  • Improved Gremlin performance for conditional mutations, such as the fold().coalesce(unfold(), …) pattern, when used with addV(), addE(), and property() steps.

  • Improved Gremlin performance for by() and sack() modulations.

  • Improved Gremlin performance for group() and groupCount() steps.

  • Improved Gremlin performance for store(), sideEffect(), and cap().unfold() steps.

  • Improved support for Gremlin single cardinality properties constraints.

    • Improved enforcement of single cardinality for edge properties and vertex properties marked as single cardinality properties.

    • Introduced an error if additional property values are specified for an existing edge property during Neptune Load jobs.

On this page: