Amazon Neptune Engine Version (2020-05-05) - Amazon Neptune
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.

Amazon Neptune Engine Version (2020-05-05)


Starting from 2020-05-19, no new instances using this engine version will be created.

This engine version is now superseded by version, which contains all the bug fixes in this version as well as additional features such as full-text search integration, OSGP index support, and database snapshot cluster copy across Amazon Regions.

Starting June 1, 2020, Neptune will automatically upgrade any cluster running this engine version to the latest patch of version during the next maintenance window. You can upgrade manually before then, as described here.

If you have any issues with the upgrade, please contact us through Amazon Support or the Amazon Developer Forums.

Defects Fixed in This Engine Release

  • Fixed a bug where ConcurrentModificationConflictException and TransactionException were reported as generic InternalFailureExceptions.

  • Fixed bugs in health checks that caused frequent restarts of the server during start up.

  • Fixed a bug where data was not visible on replicas because commits were out of order under certain conditions.

  • Fixed a bug in load-status serialization where a load failed from a lack of Amazon S3 access permissions.

  • Fixed a resource leak in Gremlin sessions.

  • Fixed a bug in health check that hid the unhealthy status on start-up of components managing IAM authentication.

  • Fixed a bug where Neptune failed to send a WebSocket close frame before closing the channel.

Query-Language Versions Supported in This Release

Before upgrading a DB cluster to version, make sure that your project is compatible with these query-language versions:

  • Gremlin version: 3.4.1

  • SPARQL version: 1.1

Upgrade Paths to Engine Release

Your cluster will be upgraded to this patch release automatically during your next maintenance window if you are running engine version

You can manually upgrade any earlier Neptune engine release to this release.

Upgrading to This Release

Amazon Neptune is now generally available.

If a DB cluster is running an engine version from which there is an upgrade path to this release, it is eligible to be upgraded now. You can upgrade any eligible cluster using the DB cluster operations on the console or by using the SDK. The following CLI command will upgrade an eligible cluster immediately:

For Linux, OS X, or Unix:

aws neptune modify-db-cluster \ --db-cluster-identifier (your-neptune-cluster) \ --engine-version \ --apply-immediately

For Windows:

aws neptune modify-db-cluster ^ --db-cluster-identifier (your-neptune-cluster) ^ --engine-version ^ --apply-immediately

Updates are applied to all instances in a DB cluster simultaneously. An update requires a database restart on those instances, so you will experience downtime ranging from 20–30 seconds to several minutes, after which you can resume using the DB cluster.

For more information about upgrading your engine version, see Neptune engine updates. If you have any questions or concerns, the Amazon Support team is available on the community forums and through Amazon Premium Support.