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, conforming to the API Commons Rate Limits specification.
It captures 4 rate-limit definitions, measuring varies, concurrent_requests, seconds, and count.
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.
Limits
Policies
Sources
- https://docs.aws.amazon.com/neptune/latest/userguide/limits.html
- https://docs.aws.amazon.com/general/latest/gr/api-retries.html
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.