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

Amazon Neptune Limits

Preview Release    Amazon Neptune Preview is available only to whitelisted customers. To request access to Neptune, see the information on the Amazon Neptune Preview page.

Instance Limit

Amazon Neptune has a limit of three instances per account.

You can request an increase on this limit. For more information, see

Account Limits

The following are per-account limits.

Item Limit
Clusters 20
DB Subnet Groups 50
DB Snapshots 100
DB Security Groups (Per VPC) 25

You can request an increase on some limits. For more information, see

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.

Amazon Neptune is not supported in every Availability Zone. If you receive the console error DB Subnet Group doesn't meet availability zone coverage requirement, try adding subnets in additional Availability Zones to the DB subnet group.

Gremlin Implementation

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


SPARQL UPDATE LOAD from URI only works with resources within the same VPC. This includes Amazon S3 URLs in the us-east-1 Region 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 using the Amazon Neptune loader API. For more information, see Loading Data into Neptune.


The Amazon Neptune loader API is non-ACID.

Authentication and Access

IAM authentication and access control are not supported for Gremlin, SPARQL, or cluster/instance level.

The Amazon Neptune console requires AmazonRDSFullAccess permissions. You can restrict access to IAM users by revoking this access.

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