Define the cache a customer should receive through PD AWS ElastiCache. Connect AWS and plan application access before offering a new package. 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 Packages → Packages → Add Package.
2. Select PD AWS ElastiCache and the intended module account.
3. Review Region, Plan, Engine, Engine version and Resource name prefix on Module. Use a verified Redis OSS configuration for the initial offering.
4. Review customer controls, package name, pricing and package group, then save.
5. Add the group to the intended form under Packages → Order Forms.
6. 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 cache should be created.

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

Use the package’s own Module settings for its cache dimensions. The module’s Products panel can direct you back to those settings rather than offering an option generator. Follow the controls on your installation, and check the actual accepted service values as well as the order form’s visible choices.

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