Graph

Amazon Neptune

Amazon Neptune runs Gremlin and openCypher through the AWS Neptune Data SDK and signs SPARQL with SigV4, while explicit custom endpoints can use unsigned HTTP.

Available for AWS IAM queries; some cloud diagnostics are limited12 minDesktop

Prerequisites

  • Install the current DataPad++ desktop pre-release on Windows, macOS, or Linux.
  • Have the endpoint, database file, or cloud account details for a Amazon Neptune datastore you are authorized to use. Start with least-privileged, read-only access.
  • Keep an independent backup before enabling edits, administration, restore, or transfer execution.

Connect and run a safe query

  1. 1

    Create the connection

    Open Library, choose Create connection, and select Amazon Neptune and a supported Connection method tab.

  2. 2

    Test and save

    Complete the applicable fields and enable Read-only connection. Test connection when available; new local files and pending secondary credential changes must be saved first. Review runtime limitations and warnings.

    Amazon Neptune connection setup. The Amazon Neptune connection dialog with supported method tabs and illustrative, non-secret settings. Expand optional sections and review runtime limitations before saving.
    Amazon Neptune connection setup. The Amazon Neptune connection dialog with supported method tabs and illustrative, non-secret settings. Expand optional sections and review runtime limitations before saving. Open full size
  3. 3

    Open the native explorer

    Use Save Connection, or Create Database and Save Connection for a new local file, then open the Amazon Neptune Explorer where supported.

  4. 4

    Select a scope

    Select the graph / database scope that should be attached to the new tab.

  5. 5

    Run a bounded read

    Open a query tab, paste the bounded read-only sample below, and choose Run or press Ctrl/Cmd+Enter.

    Amazon Neptune native workflow. A representative Amazon Neptune explorer and bounded read-only workflow. Replace the example objects with names from your datastore.
    Amazon Neptune native workflow. A representative Amazon Neptune explorer and bounded read-only workflow. Replace the example objects with names from your datastore. Open full size
  6. 6

    Inspect the result

    Inspect Results, Messages, History, and Details; dock the panel on the bottom or right as needed.

  7. 7

    Export when needed

    Export only the required rows after reviewing format, destination, and redaction options.

  8. 8

    Open diagnostics or transfers

    Open Diagnostics or Transfers from the drawer/status bar and treat disabled reasons as capability boundaries, not transient errors.

Connection fields

FieldRequiredPurposeSafe example
NameYesA clear profile name, without credentials.Amazon Neptune development
Connection methodYesChoose a supported tab. The fields below apply only to the selected method and deployment.Connection fields / Connection string
EnvironmentNoAttach the intended variable and safety context.Local development
Read-only connectionNoEnable for initial exploration. This does not make pre-release software safe for production workloads.Enabled
Host / PortNoEndpoint for a fields-based connection. Follow the selected deployment and runtime limitations; MongoDB SRV does not use an explicit port.localhost / engine default
Database / default scopeNoInitial scope for browsing, where supported.catalog
Complete connection stringYesRequired in Connection string mode only. Saved unchanged as one vault secret with Save Connection. Blank keeps an existing stored value.Paste your complete provider string; do not share it
UsernameNoAuthentication identity for the selected method.catalog_reader
PasswordNoRequired only when the chosen authentication needs it. Save Connection stores changes; blank preserves an existing value, and Reveal… explicitly discloses it.Stored in the desktop OS vault
ProtocolNoGeneral. Optional, depending on the method and server. Review runtime limitations before overriding the driver default.neptune-http / neptune-iam
AWS regionNoAuthentication. Optional, depending on the method and server. Review runtime limitations before overriding the driver default.Driver default
AWS profileNoAuthentication. Optional, depending on the method and server. Review runtime limitations before overriding the driver default.Driver default
EndpointNoGeneral. Optional, depending on the method and server. Review runtime limitations before overriding the driver default.Driver default
Database / graphNoGeneral. Optional, depending on the method and server. Review runtime limitations before overriding the driver default.Driver default
Traversal sourceNoGeneral. Optional, depending on the method and server. Review runtime limitations before overriding the driver default.Driver default
Path prefixNoAdvanced. Optional, depending on the method and server. Review runtime limitations before overriding the driver default.Driver default
Use TLSNoTLS & certificates. Optional, depending on the method and server. Review runtime limitations before overriding the driver default.Driver default
Verify certificatesNoTLS & certificates. Optional, depending on the method and server. Review runtime limitations before overriding the driver default.Driver default
CA certificateNoTLS & certificates. Optional, depending on the method and server. Review runtime limitations before overriding the driver default.Driver default
Client certificateNoTLS & certificates. Optional, depending on the method and server. Review runtime limitations before overriding the driver default.Driver default
Client keyNoTLS & certificates. Optional, depending on the method and server. Review runtime limitations before overriding the driver default.Driver default
Connect timeout (ms)NoAdvanced. Optional, depending on the method and server. Review runtime limitations before overriding the driver default.Driver default
Query timeout (ms)NoAdvanced. Optional, depending on the method and server. Review runtime limitations before overriding the driver default.Driver default

Run the sample query

Amazon Neptune read-only example
SELECT ?product ?name
WHERE { ?product a :Product ; :name ?name . }
LIMIT 25

Explore and inspect

  • Browse graph names, labels, relationship types, properties, indexes, constraints where available, access/IAM posture, metrics, and diagnostics.
  • Inspect graph rows, paths, node/edge properties, raw JSON, CloudWatch-style metrics, profile payloads, and access diagnostic panels.

Diagnose, administer, and transfer

  • Review metrics, IAM/access posture, endpoint health, traversal posture, profile boundaries, CloudWatch-style payloads, and SigV4 disabled reasons.
  • Preview access checks, metrics review, explain/profile, index/constraint-like operations where supported, and graph import/export workflows.
  • Import — Plan only. Neptune imports through its S3 bulk loader and exports bounded graph queries. Formats: GraphSON (native), RDF (native), CSV (portable-lossy). Destinations: cloud uri. Live Neptune transfer requires a SigV4-authenticated S3 bulk-loader runtime and opt-in validation against a real Neptune cluster.
  • Export — Plan only. Neptune imports through its S3 bulk loader and exports bounded graph queries. Formats: GraphSON (native), RDF (native), CSV (portable-lossy). Destinations: cloud uri. Live Neptune transfer requires a SigV4-authenticated S3 bulk-loader runtime and opt-in validation against a real Neptune cluster.
  • Backup — Plan only. Neptune uses managed cluster snapshots and restore. Formats: Native managed backup (native). Destinations: managed restore, cloud uri. Neptune snapshot and restore require a SigV4-authenticated control-plane runtime, an isolated destination cluster, and opt-in validation against a real AWS account.
  • Restore — Plan only. Neptune uses managed cluster snapshots and restore. Formats: Native managed backup (native). Destinations: managed restore, cloud uri. Neptune snapshot and restore require a SigV4-authenticated control-plane runtime, an isolated destination cluster, and opt-in validation against a real AWS account.
Transfers Center. Transfers Center shows a failed example transfer with its warning count, failure detail, retry control, and dismiss action.
Transfers Center. Transfers Center shows a failed example transfer with its warning count, failure detail, retry control, and dismiss action. Open full size

Capabilities and availability

CapabilityStatusNotes
Native explorerAvailableBrowse graph names, labels, relationship types, properties, indexes, constraints where available, access/IAM posture, metrics, and diagnostics.
Read queriesAvailableRun Gremlin, openCypher, and SPARQL with language-specific live metadata, bounded normalized graph results, guarded mutations, and profile requests.
Inline editingUnavailableUse a reviewed statement or the engine-native tool instead.
Diagnostics / administrationGuardedPreview access checks, metrics review, explain/profile, index/constraint-like operations where supported, and graph import/export workflows.
Import / export / transferGuardedAvailability follows the authoritative runtime transfer manifest and shows a disabled reason when execution is not implemented.

Safety and limitations

Troubleshooting

SymptomResolution
Test connection fails or times outVerify endpoint, port, TLS mode, proxy settings, service health, firewall rules, and network access. Keep the profile unsaved until the test explains the failure.
Explorer branches are empty or disabledConfirm the selected graph / database, refresh the branch, and grant the minimum metadata permissions described in the connection warning.
Run, edit, admin, or transfer is disabledRead the visible disabled reason. Select a compatible target, turn off read-only only when authorized, or use the documented preview/export fallback.
The sample query fails or returns different columnsReplace the example names with objects from your Amazon Neptune datastore, confirm the selected graph / database, and keep the query bounded while you validate the result.