PD AWS Lightsail connects to AWS through an account saved in Blesta’s module management screen. Add this connection before creating a Lightsail package, then select the intended account for that package.

This guide is for the hosting operator. Adding the connection does not provision a customer server.

Before you start

Install PD Modules and PD AWS Lightsail, connect the account that holds your licence, and grant the appropriate staff group access. Prepare an AWS access key ID and secret access key with permission for the Lightsail actions your offering needs.

Use dedicated IAM credentials rather than root-account keys. The module’s Setup documentation includes its AWS policy; review the permissions for the controls you will offer. Keep the secret out of tickets, screenshots and package descriptions.

Add the AWS account

1. Open Settings → Company → Modules.
2. Find PD AWS Lightsail under the installed modules and choose Manage.
3. Choose Add AWS Account.
4. Enter an Account name that identifies this provider connection, followed by the AWS Access Key ID and Secret Access Key.
5. Save the account.
6. Open PD Modules → PD AWS Lightsail → Settings and use Test Connection. Review the result for the account you added.

Blesta calls a saved provider account a module row. It can be used by packages that provision through the module. These AWS credentials belong on that account, rather than in the package’s operating-system or plan fields.

Check the result

Confirm that the intended AWS account is available when creating a PD AWS Lightsail package. Check that region, plan and image choices load for the configuration you are preparing.

A successful connection check is not a test of every possible provisioning or networking permission. Verify the IAM permissions needed for your intended service features before accepting orders.

If the connection fails

For an invalid-key result, check that the ID and secret are the intended pair and that the key is still active. For a denied action, review the permissions named by the error rather than changing unrelated package settings.

Keep existing working connections in place while investigating. Correct the identified setting and retest the intended saved connection.

See the PD AWS Lightsail overview for Blesta for the surrounding workflow, or explore the module.