Set the intended placement before PD Object Storage creates a bucket. The available choice depends on the product’s backend, and changing an offering does not relocate existing data.

Review the saved product and order

1. Open the product’s Module Settings.
2. Confirm the saved Backend and server group.
3. Review Default region / data location.
4. Inspect any Region or Data Location checkout choice and the accepted order value.
5. Compare the created service’s placement and issued endpoint with the intended destination.

Known values belonging to a different backend are discarded, but do not use arbitrary typed values or assume every input is validated against provider availability. A hidden option can still submit a saved selection. Use the actual current module choices and inspect the provisioned result.

Distinguish regions, hints and jurisdiction

Amazon S3 and Spaces use their selected region. R2 location hints are placement preferences, whereas its EU jurisdiction is a separate boundary requiring the corresponding endpoint. MinIO uses its deployment’s API endpoint and has no generated region choice.

Use the service’s issued endpoint, particularly for R2 jurisdiction-specific storage. A custom public hostname or CDN address is not automatically a substitute for the S3 API endpoint. Cloudflare explains R2 location and jurisdiction separately.

Treat a location change as a move

An existing bucket keeps its placement. Provision the intended destination through your controlled process, copy the required data and versions appropriately, then verify application recovery before retiring the original. Keep required backups and review retention/purge state first.

Changing the product default, server credentials or Backend does not perform that migration.

See the PD Object Storage WHMCS guide for related tasks, or explore PD Object Storage.