Define the Neptune cluster a customer should receive through PD AWS Neptune. Connect AWS first, then configure a new product and its private application access before offering it for sale. This module provisions a Neptune cluster with one compute instance; a larger instance plan does not add a replica or automatic standby failover. The graph has no master database login.

Set the defaults

1. Open System Settings → Products/Services → Products/Services and create a product in the intended group.
2. Choose the Other product type.
3. On Module Settings, select PD AWS Neptune and the intended server group.
4. Review Region, Plan, Neptune version and Resource name prefix.
5. Leave any older Publicly accessible switch off. Neptune needs private network access even if an older form offers that misleading choice.
6. Review the customer controls, name and pricing. Set Automatically setup the product explicitly if automatic provisioning is intended, such as when the first payment is received, then save.

Storage grows automatically, so there is no allocated storage size to choose. The instance plan controls compute and memory. If the form offers a provider-default version choice, use it only when that is intended. Otherwise select a compatible offered Neptune version. Do not treat an old example as the latest available version.

Review customer choices

Open PD Modules → PD AWS Neptune → Products and locate the saved product. Generate options builds its configurable-option group. Review choices and prices under System Settings → Products/Services → Configurable Options; the product’s Configurable Options tab assigns groups. Read rebuild confirmations: rebuilding from AWS resets generated prices to defaults. Check actual accepted service selections as well as visible choices.

Confirm the first service

Review the region and private networking before a controlled first-service check. A real order creates provider resources and can incur charges. Confirm the resulting cluster state and connection details before calling the service ready. Keep the original service record and inspect Activity if the outcome is uncertain; repeated creation is not a repair.

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