Connect the AWS account that will hold the caches you sell through PD AWS ElastiCache. The module manages node-based ElastiCache replication groups. Your AWS access key authorises infrastructure management and is separate from the cache AUTH token an application uses.

Prepare the connection

Install PD Modules, connect the account holding your licence, then install PD AWS ElastiCache from its Store. Ask the AWS administrator for a dedicated IAM access key with the permissions required for the cache operations you intend to offer. Keep its key and secret out of customer applications, screenshots and support tickets.

Review ElastiCache replication-group, node, snapshot and cache-subnet-group permissions alongside CloudWatch reads and EC2 network permissions. Creating a cache can need network creation, not just permission to describe existing resources. The AWS administrator should also check service-linked-role prerequisites for the account’s first use.

Save the account

Open Settings → Company → Modules, find PD AWS ElastiCache under Installed and choose Manage. Add an account with a recognisable name, Access Key ID and Secret Access Key, then save. Select that account on the package. Leaving an unchanged secret blank when editing retains its stored value.

Open PD Modules → PD AWS ElastiCache → Settings → Test Connection. Read what the connection test checks before treating a passing result as proof that all operations will work.

Review the dependent offering

Confirm that the package uses the intended account and region. Review private application access before accepting orders: the AWS management connection is not an application network route. When rotating a key, verify the intended dependent operations before retiring the previous pair. If an earlier creation outcome is uncertain, preserve the original service and investigate it before asking for another cache.

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