Use PD AWS ElastiCache’s module-panel connection test to check an authenticated AWS read. The test lists ElastiCache replication groups; it does not connect to a customer’s cache or test the cache AUTH token.

Run the module-panel check

1. Save the AWS connection using the account connection guide.
2. Open PD Modules → PD AWS ElastiCache → Settings.
3. Choose Test Connection and read the result.
4. Confirm separately that the intended package uses the correct account and region.

This test uses the first configured active account and its default test region. It does not test every account or automatically follow each package’s region. It creates no cache and changes no firewall. A success confirms that read, rather than creation, snapshots, network permissions or application access.

Investigate a failure

For invalid credentials, check the saved key pair, accidental spaces and whether the key remains active. AWS cannot show a lost secret again; use an approved replacement pair where needed. For an access refusal, ask the AWS administrator to check permission to describe replication groups on the intended IAM user.

A generic failure can have several causes. Check outbound HTTPS access and AWS availability as well as the saved key. Keep the test time and redacted result, without sending credentials.

Verify provisioning separately

Review the offering defaults and network prerequisites before a controlled first-service check. A passing read does not prove that the selected node type or engine version can be created. Preserve the original service and Activity, then compare the earlier operation with the replication group and member-node state in your own AWS account before requesting another creation.

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