PD AWS ElastiCache for WHMCS: getting started
PD AWS ElastiCache lets you offer Amazon ElastiCache caches through WHMCS, using AWS. It suits Redis- or Valkey-compatible caching, with the resource linked to the customer’s service.
Before you start
Install PD Modules for WHMCS first, connect the account that holds your licence, then install PD AWS ElastiCache from its Store. Allow the administrator role that needs to use it.
You also need an AWS account with the permissions required for the chosen database service. Check the provider account’s permissions, available locations and capacity before enabling automatic provisioning.
Connect the account
Add the provider connection under System Settings → Servers, selecting this module for the server record. Assign the appropriate server group to the product. Keep provider credentials on the connection, separate from the product’s resource defaults.
Define what the customer receives
Create a product using PD AWS ElastiCache and review its Module Settings and configurable options. Start with Region, Plan, Engine and Engine version. Together these describe the resource requested when a service is provisioned; they are not just labels on the order form.
Choose the intended engine deliberately and plan TLS and authentication for the application that will connect. Verify the actual AWS engine and version before offering the configuration broadly; a selected Redis OSS or Valkey label alone is not proof of what was provisioned.
Choose which client controls the product exposes. If you offer configurable options, check that their values match the module’s supported choices and that the defaults describe the service you intend to sell.
Put the service into use
Set the product’s automatic-setup behaviour deliberately. If you want provisioning after payment, select that option rather than leaving setup manual. Keep the normal cron running for subsequent status and usage updates.
Check the first service
Review the instance or cluster state, the connection details and the access controls. A pending resource is not ready for application connections.
Creating a real service creates provider resources and can incur provider charges. Review the configuration first; use your normal controlled test process for the first provisioning rather than making an order solely to browse the settings.
Explore the module
See the PD AWS ElastiCache for WHMCS module page for the current product details.
AWS ElastiCache task guides
- Connect an AWS account to PD AWS ElastiCache in WHMCS
- Test the AWS connection for PD AWS ElastiCache in WHMCS
- Configure a Redis OSS cache product in WHMCS with PD AWS ElastiCache
- Choose an AWS region for PD AWS ElastiCache in WHMCS
- Choose an ElastiCache node plan in WHMCS
- Plan private ElastiCache access with PD AWS ElastiCache in WHMCS
- Check Redis OSS or Valkey engine settings in WHMCS before offering a cache
- Investigate a pending ElastiCache service in WHMCS
