Connect PD Google Cloud MySQL to the project that will hold your managed MySQL instances. The saved provider account supplies access; the product or package separately describes the resource a customer receives.

Prepare the approved project credential

Ask the Google Cloud administrator to confirm the intended project has billing and the Cloud SQL Admin API enabled. The module uses a complete service-account JSON key, including its project, service-account email and private key. It selects the project from this credential, so confirm that it identifies the project you intend to use.

The documented role is Cloud SQL Admin on the intended project. Have the administrator review the service account’s actual role and scope. A connection test reads instance information; passing it does not prove all provisioning permissions.

The administrator can create an approved JSON key from IAM & Admin → Service accounts → the intended account → Keys → Add key → Create new key → JSON. Keep the downloaded key private and follow your organisation’s credential-handling process. Google documents service-account key creation.

If key creation is blocked by organisation policy, ask the organisation administrator to review whether a scoped exception is appropriate for this module. Do not remove a security policy across the organisation merely to make the connection work. The reviewed module expects a JSON key; do not assume it accepts a different sign-in method. Google’s key-management guidance explains the approval and handling considerations.

Save the provider account

1. Open Settings → Company → Modules.
2. Find PD Google Cloud MySQL under the installed modules and choose Manage.
3. Add a recognisable account name and paste the complete approved service-account JSON key into the credential field. Save the account.
4. Open PD Modules → GC MySQL and use Test Connection, observing the account-selection limit below.

Blesta calls this account a module row. Select the intended account when configuring the package. When editing a saved account, leaving the credential field blank keeps the existing credential.

Interpret the connection result

The module-level Test Connection action selects the first active saved account for this module. With several accounts, do not assume it tests the account on the last offering or service you viewed. Review the intended association without disabling working accounts to force selection.

A successful check authenticates and reads the project’s instance list. It does not create an instance, verify every write permission, establish region capacity or prove that an application can connect to a database.

For a rejected credential, review the complete original JSON and intended service account. For a permission or API error, have the project administrator inspect the exact reported condition. Do not send the JSON key, private key or full account identifiers.

See the PD Google Cloud MySQL Blesta guide for related setup, or explore PD Google Cloud MySQL.