Define the cache a customer should receive through PD AWS ElastiCache. Connect AWS and plan application access before offering a new product. The reviewed provisioning model creates one primary node in a cluster-mode-disabled replication group; a larger node type does not add a replica or automatic failover.

Set the offering 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 ElastiCache and the intended server group.
4. Review Region, Plan, Engine, Engine version and Resource name prefix. Use a verified Redis OSS configuration for the initial offering.
5. Review customer controls, product name and pricing.
6. Set Automatically setup the product explicitly if automatic provisioning is intended, such as when the first payment is received, then save.

The node type determines memory capacity. There is no separate disk-storage or Multi-AZ dimension to select in this module. Its provisioning requests encryption in transit and at rest and a cache AUTH token. The application needs a TLS-capable client and the intended private network path.

Review customer choices

Open PD Modules → PD AWS ElastiCache → Products and locate the saved product. Generate options builds the configurable-option group. Review choices and prices under System Settings → Products/Services → Configurable Options; the product’s own tab assigns groups. Rebuilding from AWS resets generated prices to defaults, so read the confirmation before rebuilding.

Before offering Valkey, use the engine and version verification guide. A selected engine name or version list is not proof of the engine that the installed module will provision.

Check the first service

Review the account, region and accepted configuration before a controlled first-service test. A real order creates AWS resources and can incur charges. Check provider readiness and application connectivity before calling the cache ready. If a request has an uncertain result, keep the original record and investigate Activity before trying again.

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