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

Check the Health Status of a Neptune Instance

Amazon Neptune provides a mechanism to check the status of the graph database on the host. It's also a good way to confirm that you are able to connect to an instance.

To check the health of an instance using curl:

curl -G https://your-neptune-endpoint:port/status

If the instance is healthy, the status command returns the following fields:

  • status   –   As long as the instance is not experiencing problems, this field is set to "healthy".

    If the instance is recovering from a crash or from being rebooted and there are active transactions running from the latest server shutdown, the status is set to "recovery".

  • version   –   This field is set to the Neptune engine version.

    If this engine version has been manually patched since it was released, the version number is prefixed by "Patch-".

  • startTime   –   This field is set to the UTC time at which the current server process started.

  • role   –   This field is set to "reader" if the instance is a read-replica or to "writer" if the instance is the primary instance.

  • gremlin   –   This field is set to the current TinkerPop version being used by the engine.

  • sparql   –   This field is set to the current version of SPARQL being used by the engine.

  • labMode   –   This field lists the lab mode settings being used by the engine.

The following is an example:

{ "status": "healthy", "startTime": "Tue Nov 05 22:49:06 UTC 2019", "dbEngineVersion": "development", "role":"writer", "gremlin":{"version":"tinkerpop-3.4.1"}, "sparql":{"version":"sparql-1.1"}, "labMode": { "Streams":"disabled", "ReadWriteConflictDetection":"enabled" } }

If there is a problem with the instance, the status command returns the HTTP 500 error code. If the host is unreachable, the request times out. Ensure that you are accessing the instance from within the virtual private cloud (VPC), and that your security groups allow you access to it.