Connect the module to the Google Cloud project that will hold your customers’ VMs. Keep the provider account separate from the product or package that describes each server.

Prepare the approved project credential

Ask the Google Cloud administrator to confirm the intended project has billing and the Compute Engine API enabled. The module expects the complete service-account JSON key; it identifies the target project from that key.

The module documents Compute Admin and Service Account User for its provisioning identity. Have the administrator review the actual permissions and their scope, including permission to use the intended VM service account. A suggested role name is not proof of every required permission or every VM’s attached identity. Google explains Compute Engine access roles.

Create an approved JSON key under IAM & Admin → Service accounts → the intended account → Keys → Add key → Create new key → JSON, following your organisation’s credential process. Keep it private. If organisation policy blocks key creation, ask the organisation administrator to review the module’s requirement and any appropriate project exception; do not broadly disable a security policy to clear the error.

Save the provider account

1. Open Settings → Company → Modules.
2. Find PD Google Compute Engine under the installed modules and choose Manage.
3. Add a recognisable account and paste the complete approved service-account JSON key into the credential field. Save it.

Blesta calls this account a module row. Select the intended account when configuring the package. When editing later, leaving its credential field blank retains the saved value.

Interpret the connection test

Open PD Modules → GCE → Settings and use Test Connection after saving the account. The module-level action selects the first active account for this module. It does not automatically test every account or follow the last offering viewed.

The check reads the project and attempts read-only permission and quota probes. It does not create a VM, firewall rule or test credential. Read the full result: an unreachable permission probe can be skipped without failing the connection, and a quota read can be unavailable.

The module-level quota detail uses the module’s default test region, europe-west2, rather than automatically following the zone selected on each product or package. Confirm quota for the region you intend to sell in separately.

Verify before accepting orders

Success does not prove all write permissions, billing readiness, a working guest login or available zonal capacity. Have the project administrator confirm the intended account, quota and resource configuration before normal activation.

Do not send the JSON key, private key or full account details.

See the PD Google Compute Engine Blesta guide for related setup, or explore PD Google Compute Engine.