As the hosting operator, help your customer choose the endpoint shown on their active PD AWS Neptune service for the graph interface their application expects. The interface, data model, network access and authentication must agree; a hostname alone is not a complete connection setup.

Customer steps: find the service endpoints

1. Open the intended active service and confirm its Neptune cluster and AWS region.
2. Open Overview and find its connection details.
3. Review the labelled Gremlin, openCypher and SPARQL endpoint values.
4. Use Copy beside the required endpoint where offered, retaining its scheme, hostname, port and path.
5. Keep the endpoint in the application’s private configuration and confirm the intended driver and graph model.

The module shows Gremlin over secure WebSocket, and openCypher and SPARQL over HTTPS. They use the same cluster host and normally port 8182. Use the service’s current values rather than an old screenshot or another service’s endpoint.

Match the graph model

AWS explains Neptune’s query interfaces. Gremlin and openCypher query property-graph data; SPARQL queries RDF data. Copying a different endpoint does not convert the graph data model. Check the application’s query language and the engine/instance requirements before interpreting an empty result as missing data.

Confirm access before querying

Arrange the private network path first and use TLS with certificate verification. The module creates no database username or password. If the administrator enabled IAM database authentication, the application needs authorised signed requests; a copied URL does not supply that authorisation. Keep the module’s AWS management keys out of customer applications.

If connection details are unavailable, compare the original service and cluster/compute state using your own AWS access. For a query failure, have your application and AWS administrators check the private route, current endpoint, TLS, enabled IAM setting and query-language compatibility. Identify which layer fails; do not broaden firewall access or repeat cluster creation as a connection repair.

See the PD AWS Neptune WHMCS guide for related tasks, or explore PD AWS Neptune.