Offer a DigitalOcean managed OpenSearch cluster through PD DigitalOcean OpenSearch. Define its resource defaults and customer controls before accepting orders for search or log-analytics workloads.

Connect the intended account

Install PD DigitalOcean OpenSearch through PD Modules and connect the provider account that will own the clusters. In PD Modules, connect the account holding your licence first; entering a licence key is the alternative activation method. The provider account test is separate from proving database-write permissions or cluster capacity.

Set the OpenSearch defaults

Open System Settings → Products/Services → Products/Services, create an Other product and choose PD DigitalOcean OpenSearch on Module Settings. Assign the intended server group, whose server stores your DigitalOcean API token in Password.

Review Region, Plan, Engine version and High availability on Module Settings. OpenSearch is the fixed engine. Leave Engine version blank only when you intend DigitalOcean to choose its default for a new cluster; this does not define an automatic upgrade policy for existing clusters.

Choose the availability layout

With High availability enabled, this module requests a three-node cluster rather than the base single-node layout. These are OpenSearch cluster members; do not describe every extra node as a database standby or an arbitrary customer-selectable node count.

Review the plan, region and provider costs for the intended layout. Catalogue choices can be cached, stale or from fallback data; a displayed combination is not proof of account capacity. More nodes do not establish that index replicas, backups or application recovery have been configured and tested.

Review customer controls and activation

Set Client: Firewall and Client: Connection details explicitly. The module shows a client Backups page only for supported database engines; it does not expose an OpenSearch backup list or restore control through that generic switch. Do not treat this interface limitation as proof that the provider has no recovery facilities.

Set product prices and the automatic-setup policy, including whether cluster creation should follow the first payment. An Active billing service alone does not prove that the module created a cluster.

After an intended activation, check the service, normal cron progress, connection details and provider result. A running cluster does not prove the customer has ingested data or configured dashboards. Creating real resources incurs provider charges; reconcile an uncertain create outcome before retrying.

See the PD DigitalOcean OpenSearch WHMCS guide for related setup, or explore PD DigitalOcean OpenSearch.