Use PD AWS Neptune’s module-panel connection test to check whether it can authenticate to AWS and read Neptune clusters. This is an infrastructure check, separate from connecting an application to a customer database.

Run the test

1. Save the AWS connection using the account guide.
2. Open PD Modules → PD AWS Neptune → Settings.
3. Choose Test Connection and read the result.
4. Confirm separately that the intended package uses the correct account and region.

The module-panel test uses the first configured active account and its default test region. It lists Neptune clusters; it does not test every account or automatically follow every package’s region. The test creates no cluster and changes no firewall. A passing result confirms that read rather than provisioning, snapshots, graph queries or application access.

Investigate a refusal

Check the saved key pair, accidental spaces and whether the key remains active. A lost AWS secret cannot be displayed again: use an approved replacement pair if needed. For an access refusal, ask the AWS administrator to check the permission to describe Neptune clusters. Do not confuse an instance-list permission with the cluster read used here.

A generic failure is not proof of bad credentials alone. Outbound HTTPS access and provider availability also matter. Keep the redacted error and test time rather than sharing the key itself.

Verify readiness separately

Review the offering defaults and private-network prerequisites before a controlled first service. A successful AWS read does not prove that a customer’s database is ready or reachable. If an earlier creation outcome is uncertain, investigate the original service before requesting another cluster.

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