As the hosting operator, compare PD AWS ElastiCache’s service state and Activity when your customer’s cache has not appeared or an operation seems unfinished. The billing status, a recorded request and provider readiness describe different stages; compare them before deciding what to do next.

Find the original request

1. Open PD Modules → PD AWS ElastiCache → Clients & Caches.
2. Identify the original service and its intended AWS region.
3. Open Activity and match its service reference and action time.
4. Read the operation, status and redacted result before requesting another change.

Activity shows recent operations rather than a complete audit archive. If an earlier attempt is no longer listed, compare the original service reference, account and region with the replication groups and member nodes in your AWS account. Record what exists and its state before requesting creation again. A missing recent entry alone does not establish that no earlier request reached AWS.

Check the relevant stage

Queued or in-progress work still needs processing. A Done entry can mean AWS accepted a request while its replication group or member node is not yet ready. Confirm the resulting resource state and application network path before telling the customer the cache is usable.

Check paid-pending-service automation, applicable client-group settings and the running cron. Staff activating a pending service must use the module when a cache should be provisioned. Payment alone does not prove AWS readiness.

Check the replication group and application separately

Review the original account, region, node plan and engine/version with your AWS administrator. If AWS reports a specific permission or configuration refusal, check that requirement alongside the original module result. Follow an operation still processing rather than placing another order for your customer.

Compare the replication group’s state with its member-node readiness and intended endpoint. If the resources are available but the application cannot connect, investigate its private route, TLS and cache authentication separately from resource creation. Preserve the original service instead of deleting its record as a reset.

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