Choose placement before provisioning a PD Cloudflare R2 service. Regional hints and the European Union only jurisdiction are different settings, and neither is an AWS region to paste into an S3 client.

Choose the intended placement

1. Review Default data location on the product’s Module Settings tab.
2. If customers should choose, review the generated Data Location option and its saved values.
3. Confirm the intended selection on the order before provisioning.
4. After provisioning, inspect the service’s location and endpoint in its client information.

The module offers Automatic, North America East/West, Europe West/East, Asia Pacific, Oceania and European Union only. Regional choices are placement preferences. The EU choice sets the bucket’s jurisdiction. Consult Cloudflare’s data-location reference for the distinction, rather than treating a preference as an exact physical-location guarantee.

Use the issued endpoint

EU-jurisdiction buckets use the EU S3 endpoint. Use the complete endpoint shown for the service; do not remove its jurisdiction portion or replace it with a custom website domain. For S3 tools, use the region value auto where required and path-style addressing as shown in the connection guide.

Plan changes as data moves

Changing the product default or a billing option does not relocate an existing bucket. Jurisdiction is fixed at bucket creation. Arrange a separate destination, copy and verification process when a move is required, and keep the original until recovery has been checked.

Additional buckets stay in the service’s jurisdiction. Do not assume that creating an extra bucket repeats the primary bucket’s regional location hint; verify the result before promising an identical placement.

See the PD Cloudflare R2 WHMCS guide for related tasks, or explore the module.