Choose a node plan for the workload you intend to host with PD AWS ElastiCache. A node type sets compute and memory capacity. It is separate from application data-retention policy, backup planning and the number of nodes; this module’s normal provisioning creates one primary node.

Review the offered node types

The curated catalogue includes T3 Micro, Small and Medium; T4g Medium; R6g Large; and R7g Large and X-Large. T3 and T4g are burstable families, while the R families are memory-optimised. Check the actual cache node-type identifier alongside its friendly label rather than judging suitability by the label alone.

AWS documents supported ElastiCache node types. Review working-set memory, connection load and sustained CPU demand. The module uses a curated list; check availability for the intended region and engine version with the AWS administrator.

Save a matching offering

1. Open the package’s Module settings.
2. Review Plan, Region, Engine and Engine version together.
3. Confirm that the intended combination is available for the account.
4. Save and review the actual accepted customer selections before provisioning.

There is no separate disk size to enlarge for an in-memory cache. Changing a default for new orders is different from resizing an existing service. A larger node also does not create a standby or remove an application-level problem.

If a plan is refused

Keep the original service and recorded request. Ask the AWS administrator to check capacity, engine compatibility and the exact provider response before repeating creation. Review Activity and service readiness rather than deleting the billing record as a repair.

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