Set the intended AWS region before PD AWS MySQL creates a database. The choice determines where the resource is provisioned; editing a billing product later does not migrate an existing database.

Review default and checkout selection

1. Open the product’s Module Settings tab.
2. Choose the intended Region and backing service.
3. Review a matching plan and engine version, then save.
4. If Region is visible at checkout, inspect the accepted selection.
5. After provisioning, compare the service’s region, backing and endpoint with the intended destination.

A hidden generated Region dimension uses the saved product default. Check what is actually offered before orders rather than assuming every region has the same plans, versions, quotas or network prerequisites.

Verify account and network readiness

An account connection test is a limited RDS read; it does not prove provisioning permission or service availability in every region. Have the AWS administrator review the intended regional permissions and network requirements before a controlled provisioning test.

For RDS, the module needs to establish the service’s dedicated firewall group in a suitable network. An error mentioning a default VPC should be investigated alongside permissions and the original AWS result; it is not automatic proof that a VPC must be created.

Plan an existing-service move separately

Use an appropriate backup, restore or migration process to establish a destination database, confirm tracking and test application access before retiring the original. Review the endpoint, credentials and network rules after any move.

Do not terminate the old service just to change location. Use recovery planning and compare the original order with the resource in your AWS account before changing an existing service.

See the PD AWS MySQL WHMCS guide for related tasks, or explore PD AWS MySQL.