Amazon Neptune parameters - Amazon Neptune

Amazon Neptune parameters

You manage your database configuration in Amazon Neptune by using parameters in parameter groups. The following parameters are available for configuring your Neptune database:

neptune_enable_audit_log (cluster-level parameter)

This parameter toggles audit logging for Neptune.

Allowed values are 0 (disabled) and 1 (enabled). The default value is 0.

neptune_lab_mode (cluster-level parameter)

When set, this parameter enables specific experimental features of Neptune. See Neptune Lab Mode for the experimental features currently available.

To enable or disable an experimental feature, include (feature name)=enabled or (feature name)=disabled in this parameter. You can enable or disable multiple features by separating them with commas, like this:

(feature #1 name)=enabled, (feature #2 name)=enabled

Lab mode features are typically disabled by default. An exception is the DFEQueryEngine feature, which became enabled by default for use with query hints (DFEQueryEngine=viaQueryHint) starting in Neptune engine release 1.0.5.0.

neptune_query_timeout (cluster-level parameter)

Specifies a specific timeout duration for graph queries, in milliseconds.

Allowed values range from 10 to 2,147,483,647 (231 - 1). The default value is 120,000 (2 minutes).

neptune_streams (cluster-level parameter)

Enables or disables Neptune Streams.

Allowed values are 0 (disabled, which is the default), and 1 (enabled).

neptune_lookup_cache (cluster-level parameter)

Disables or re-enables the Neptune lookup cache. on R5d instances.

Allowed values are enabled and disabled. The default value is disabled, but whenever an R5d instance is created in the DB cluster, the neptune_lookup_cache parameter is automatically set to enabled and a lookup cache is created on that instance.

neptune_autoscaling_config (cluster-level parameter)

Sets configuration parameters for the read-replica instances that Neptune auto-scaling creates and manages.

Using a JSON string that you set as the value of the neptune_autoscaling_config parameter, you can specify:

  • The instance type that Neptune auto-scaling uses for all the new read-replica instances that it creates.

  • The maintenance windows assigned to those read-replicas.

  • Tags to be associated with all the new read-replicas.

The JSON string has a structure like this:

"{ \"tags\": [ { \"key\" : \"reader tag-0 key\", \"value\" : \"reader tag-0 value\" }, { \"key\" : \"reader tag-1 key\", \"value\" : \"reader tag-1 value\" }, ], \"maintenanceWindow\" : \"wed:12:03-wed:12:33\", \"dbInstanceClass\" : \"db.r5.xlarge\" }"

Note that the quotation marks within the string must all be escaped with a backslash character (\).

Any of the three configuration settings not specified in the neptune_autoscaling_config parameter are copied from the configuration of the DB cluster's primary writer instance.

neptune_ml_iam_role (cluster-level parameter)

Specifies the IAM role ARN used in Neptune ML. The value can be any valid IAM role ARN.

You can specify the default IAM role ARN for machine learning on graphs.

neptune_ml_endpoint (cluster-level parameter)

Specifies the endpoint used for Neptune ML. The value can be any valid SageMaker endpoint name.

You can specify the default SageMaker endpoint for machine learning on graphs.

neptune_query_timeout (instance-level parameter)

This DB instance parameter specifies a timeout duration for graph queries, in milliseconds, for one instance.

Allowed values range from 10 to 2,147,483,647 (231 - 1). The default value is 120,000 (2 minutes).

neptune_result_cache (instance-level parameter)

neptune_result_cache   –   This DB instance parameter enables or disables Caching query results.

Allowed values are 0, (disabled, which is the default), and 1 (enabled).

neptune_enforce_ssl (DEPRECATED cluster-level parameter)

(Deprecated) There used to be regions that permitted HTTP connections to Neptune, and this parameter was used to force all connections to use HTTPS when it was set to 1. This parameter is no longer relevant, however, since Neptune now only accepts HTTPS connections in all regions.