Save the AWS account that will hold your customers’ EC2 resources, then confirm the intended offering uses that account. The provider credential is separate from a customer’s server login or SSH key.

Prepare an approved AWS credential

Ask the AWS administrator to prepare a dedicated IAM identity for the module. PD AWS EC2 uses an Access key ID and Secret access key. Do not use the AWS root user’s access keys, and do not assume a temporary session credential or role-based sign-in is accepted by these two fields.

Review the module-supplied IAM policy with the administrator. It includes instance, key-pair, security-group, address, volume, backup, catalogue, monitoring and pricing actions. Its supplied resource scopes are broad; a named IAM user alone does not restrict access to just this module’s resources. Have the administrator choose the intended account and scope rather than attaching unrelated broad policies to clear an error.

An approved IAM user can obtain its key through IAM → Users → the intended user → Security credentials → Create access key. Store the secret using your credential process: AWS shows it at creation and does not provide a later reveal. AWS explains access-key management.

Save and assign the account

1. Open Settings → Company → Modules.
2. Find PD AWS EC2 under the installed modules and choose Manage.
3. Add a named AWS account with the intended Access key ID and Secret access key, then save it.
4. Select that saved account on the intended package. It is a module account, separate from an individual customer’s service.

Interpret Test Connection correctly

Open PD Modules → PD EC2 → Settings and use Test Connection after checking which account it will select. The module-level action selects the first saved account; it does not test every account. Do not disable working connections merely to influence selection.

The test performs a read-only DescribeRegions request in the module’s Default AWS region. It does not launch an instance or prove all lifecycle, image, pricing, backup or monitoring permissions. It also does not establish quota, available capacity or guest access for every region you intend to offer.

Verify before accepting orders

Confirm the account selected on the intended package, its launch region, resource choices and the permissions those operations need. If a later launch fails, check that service’s recorded operation and your AWS resource state separately from this read-only connection test.

See the PD AWS EC2 Blesta guide for related setup, or explore PD AWS EC2.