Plan the application’s route and graph access before provisioning a PD AWS Neptune service. This module configures private cluster access inside your AWS network. Its AWS management key is separate from the application’s graph-query access.

Establish the private path

Use an application server in the cluster’s VPC or an established private network path into it. The module does not build an application server, VPN or tunnel for you. Ask the AWS administrator to check the selected region’s default VPC, subnet group, DNS, routing and security-group permissions. The module attempts to create a service-specific firewall group during provisioning; confirm the actual assignment before customer firewall edits.

Review the product’s Module Settings tab. If a newer form shows Network access, retain private access. Leave any older Publicly accessible switch off: that label does not establish that this module configures a public endpoint. These instructions describe the module’s offering, not every network feature Amazon Neptune might support.

Understand graph authorisation

This module creates no database username or password, and normal provisioning does not turn on IAM database authentication. Network access is therefore especially important: permitted application sources can read and write the graph. Allow only the sources that require access. Do not broaden the firewall to all addresses as a timeout test.

If the AWS administrator enabled IAM database authentication, the application also needs authorised signed requests. Do not give customers the module’s stored AWS management credentials. Keep TLS and certificate verification enabled; the module’s graph endpoint normally uses port 8182.

Check the appropriate layer

A timeout calls for a private-path or allowed-source check. An authorisation refusal needs the administrator to review the actual IAM setting and application identity. There is no database-password reset to solve those failures. Keep the original service, observed cluster/compute state and redacted result. Compare any failed module action with AWS separately from an application route or identity problem..

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