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

Amazon Neptune Limits

Regions

Amazon Neptune is available in the following regions:

  • US East (N. Virginia)

  • US East (Ohio)

  • US West (Oregon)

  • EU (Ireland)

  • EU (London)

Instance Sizes

Neptune supports the db.r4.large , db.r4.xlarge, db.r4.2xlarge, db.r4.4xlarge, and db.r4.8xlarge DB instance classes.

Instance Limit

Amazon Neptune shares a DB instance limit with Amazon RDS.

For certain management features Neptune uses operational technology that is shared with Amazon RDS. The default limit for Neptune and Amazon RDS instances is 40.

You can request an increase on this limit. For more information, see https://aws.amazon.com/support.

Account Limits

The following are per-account limits.

Item Limit
Clusters 20
DB Subnet Groups 50
DB Snapshots 100
VPC Security Groups 5

You can request an increase on some limits. For more information, see https://aws.amazon.com/support.

Console Access Required

Creating and modifying Amazon Neptune instances and clusters must be done through the AWS Management Console.

VPC Required

Amazon Neptune is a virtual private cloud (VPC)–only service. Additionally, instances do not allow access from outside the VPC.

Availability Zones and DB Subnet Groups

Amazon Neptune requires a DB subnet group for each cluster that has subnets in at least two supported Availability Zones. We recommend using three or more subnets in different Availability Zones.

HTTP Request Payload Maximum (150MB)

Gremlin and SPARQL HTTP requests must be less than 150 MB total size. If a request exceeds this size, Neptune will return HTTP 400: BadRequestException. This limit does not apply to Gremlin WebSockets connections.

Gremlin Implementation

The Amazon Neptune Gremlin implementation has specific implementation details. For more information, see Neptune Gremlin Implementation Differences.

SPARQL UPDATE LOAD

SPARQL UPDATE LOAD from URI works only with resources that are within the same VPC. This includes Amazon S3 URLs in the same region as the cluster with an Amazon S3 VPC endpoint created. For information about creating a VPC endpoint, see Amazon S3 VPC Endpoint.

The Amazon S3 URL must be HTTPS, and any authentication must be included in the URL. For more information, see Authenticating Requests: Using Query Parameters.

If you need to load data from a file, we recommend that you use the Amazon Neptune loader API. For more information, see Loading Data into Neptune.

Note

The Amazon Neptune loader API is non-ACID.

Authentication and Access

IAM authentication and access control are not supported for Gremlin, SPARQL. It is only supported at the DB Cluster level. See IAM Database Authentication for Neptune

The Amazon Neptune console requires NeptuneReadOnlyAccess permissions. You can restrict access to IAM users by revoking this access. For more information, see AWS Managed (Predefined) Policies for Amazon Neptune

Amazon Neptune does not support user name/password–based access control.