Choose storage placement before PD AWS S3 creates the service’s bucket. Changing a saved default later does not move an existing S3 bucket.

Review the choice order

The module uses an exposed customer Region choice first, then Default Region on the product’s Module Settings tab. Where neither supplies a value, its fallback is US East (N. Virginia). Choose deliberately instead of relying on that fallback.

1. Identify the intended AWS account and new-service offering.
2. Set Default Region on the product’s Module Settings tab.
3. If customers should choose, review the generated Region configurable option and its visibility.
4. Check the order form and saved defaults together.
5. After controlled provisioning, read the service’s actual region and endpoint.

The module offers a curated set of AWS regions, including Europe (London). Use the module’s offered choices rather than treating every region in the wider AWS catalogue as supported.

Keep existing placement separate

All extra buckets created for this service use its existing region. Editing the default or an order option is not a migration process.

For an existing service that needs another region, plan new storage and a verified data copy with the responsible administrator. Keep old data until the destination, application connection and recovery requirements have been checked.

Investigate a mismatch

Compare the customer’s exposed choice, saved module default and actual service information. Use the service’s displayed endpoint in tools; changing the host connection’s descriptive hostname cannot relocate its buckets. See the connection guide before updating applications.

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