Amazon Neptune · Rate Limits

Amazon Neptune Rate Limits

Amazon Neptune has two distinct API surfaces. The control-plane (CreateDBCluster, etc.) is throttled per-account/region under the standard AWS API throttling envelope. The data-plane (Gremlin/SPARQL/openCypher endpoints) accepts queries up to the configured query timeout and concurrent-request limit on each cluster, scaling with instance class. Use exponential backoff with jitter on ThrottlingException and ConcurrentModificationException.

Amazon Neptune Rate Limits is the machine-readable rate-limit profile for Amazon Neptune on the APIs.io network, in the API Commons Rate Limits shape.

It captures 4 rate-limit definitions, measuring varies, concurrent_requests, seconds, and count.

Limit state is signalled in the requestId and retryAfter response headers, and an exhausted limit returns HTTP 400.

This profile was written by API Evangelist and has not been verified against a page the provider published; treat every limit as unconfirmed until a dated transcription replaces it.

The profile also includes 4 backoff/retry policies defined and response codes documented for throttled, quotaExceeded, serviceUnavailable, and queryTimeout.

Tagged areas include Rate Limiting, Database, Graph Database, and Neptune.

4 Limits Exhausted: HTTP 400 Quota: 400 requestIdretryAfter
Method: generated, dated 2026-05-05.
Written by API Evangelist on 2026-05-05 and not verified against a page the provider published. Treat every limit as unconfirmed until a dated transcription replaces it.
View Source
Rate LimitingDatabaseGraph DatabaseNeptune

Limits

Neptune control-plane API throttling account/region
varies
see Service Quotas console for Neptune
Standard AWS API throttling. Limits depend on action.
Concurrent open queries (data-plane) cluster
concurrent_requests
varies by instance class
Approximately 8 to 80 concurrent queries depending on instance type; configurable via DB cluster parameter group.
Default query timeout cluster
seconds · second
120
Configurable via neptune_query_timeout parameter (max 2,147,483,647 ms).
Clusters per account/region account/region
count
40
Soft default; raisable via Service Quotas.

Policies

Backoff with jitter
AWS SDKs default to standard retry mode (truncated exponential backoff with jitter, max 20s, 3 attempts).
Read scaling
Add up to 15 read replicas per cluster to absorb concurrent queries.
Long-running queries
Use the Neptune Status API (/status) and explicit /gremlin/status endpoints to monitor and cancel long-running queries.
Quota increases
Most quotas are soft and can be raised via Service Quotas.

Sources

Work with this as data

Every rate limit here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for rate limits

4 MCP tools reach this
  • find_rate_limitsBrowse and filter every rate limit in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This rate limit 
curl "https://apis.io/api/v1/rate-limits/amazon-neptune-rate-limits"
All rate limits 
curl "https://apis.io/api/v1/rate-limits?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.