As the hosting operator, plan your customer’s cache recovery before a PD AWS ElastiCache service needs it. Establish what the application must recover, which snapshot contains it and how the application will connect to the destination. The customer Snapshots page does not provide an in-place Restore control.

Verify the recovery point

Identify the original service, AWS region, cache and snapshot name. Ask the administrator to verify the actual snapshot time and available status in AWS; do not rely only on a displayed date, particularly if several snapshots show the same old time. Normal module provisioning requests one-day automated retention, but confirm the actual retained backups on an existing service.

Keep the source service and recovery points intact while planning. Do not assume that cancellation preserves backups or that an empty customer list proves no recovery point exists. Avoid deleting the original resource merely to make a replacement easier to configure.

Plan a new destination

AWS restores an ElastiCache backup into a new cache. Restoration is not a rollback of the existing service in place. The administrator must check the intended engine, compatible version and node type, private network access, encryption and authentication for the destination.

The module’s customer actions do not expose Restore or point-in-time recovery. A snapshot does not establish a recovery point later than the data it captured. Use the administrator’s supported AWS recovery workflow and confirm the actual destination settings before testing the application.

Coordinate service tracking and cutover

A separately restored cache is not automatically attached to the original billing service. Record the source and destination separately and establish how the restored cache will be managed before changing module settings or retiring the source. Another Create request is not a way to attach a separately restored cache. Privately verify the recovered data, TLS, current token and application connection. Then plan the endpoint change and check the application’s result. Keep the original service, snapshot name and required recovery time alongside the observed destination result.

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