Define the Neptune cluster a customer should receive through PD AWS Neptune. Connect AWS first, then configure a new package 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 Packages → Packages → Add Package.
2. Select PD AWS Neptune and the intended module account.
3. Review Region, Plan, Neptune version and Resource name prefix on Module.
4. Keep the network configuration private. If an older form offers Publicly accessible, leave it off; this module does not configure a public graph endpoint.
5. Review customer controls, package name, pricing and package group, then save.
6. Add the group to the intended form under Packages → Order Forms. Check Provision Paid Pending Services under Settings → Company → Automation, applicable client-group settings and the running cron. Staff activation must use the module when a cluster should be created.

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

Set the dimensions on the package’s own Module settings. The Products panel can direct you back to the package rather than offering a generator. Use the controls offered by that installation; do not assume a generator described in an older example is present. Keep the saved defaults consistent with what the order form promises.

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 Blesta guide for related tasks, or explore PD AWS Neptune.