Amazon Neptune Engine Updates 2019-09-19 - Amazon Neptune

Amazon Neptune Engine Updates 2019-09-19


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

Existing clusters can be upgraded to this release immediately using the DB cluster operations on the console or by using the SDK. You can use the following CLI command to upgrade a DB cluster:

aws neptune apply-pending-maintenance-action \ --apply-action system-update \ --opt-in-type immediate \ --resource-identifier arn:aws:rds:<region>:<account number>:<resourcetype>:<name>

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 downtime ranging from 20–30 seconds to several minutes, after which you can resume using your DB cluster or clusters. You can view or change your maintenance window settings on the Neptune console.

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

Neptune DB clusters currently running engine release will be upgraded to engine release automatically during system maintenance windows. The timing of when updates are applied depends on the Region and maintenance-window setting for the DB cluster, as well as on the type of update.


The instance maintenance window does not apply to engine updates.

IMPORTANT: because release can introduce breaking changes for some customers, any engine versions other than will NOT be upgraded automatically. If you want to upgrade any engine version other than to, use the CLI command above to upgrade manually.

Defects Fixed in This Engine Release

  • Fixed a Gremlin correctness issue introduced in the previous engine release ( by removing the performance improvement to conjunctive predicate handling that caused it.

  • Fixed a SPARQL bug that caused queries with DISTINCT and a single pattern wrapped into OPTIONAL to generate an InternalServerError.