Use PD Object Storage to offer storage from Amazon S3, Cloudflare R2, DigitalOcean Spaces or your own MinIO deployment. Choose the backend for each product and keep its account connection consistent with that choice.

Match the offering to its backend

• Amazon S3: connect an AWS account and choose the intended AWS region.
• Cloudflare R2: connect the intended Cloudflare account and review its data-location or jurisdiction choice.
• DigitalOcean Spaces: connect a DigitalOcean account and choose the intended Spaces region.
• MinIO: connect your own deployment’s API endpoint; the deployment determines the location.

Review required application operations and actual module capabilities as well as location. An S3-compatible API does not make every backend’s versioning, CORS, lifecycle or access-policy behaviour identical. Do not promise a feature merely because another backend offers it.

Keep account connections separate

Give each backend its own PD Object Storage WHMCS server record and server group. On the product’s Module Settings, save the matching Backend and server group. Do this before running an account test that needs to identify the backend.

Several products can use the same backend connection, but do not assign different backend types to one server record. Its credentials have different meanings for each provider, and later service operations depend on the recorded association.

Add a different backend as a new offering

For an existing live offering, keep its account and backend wiring. Add a separate connection and product when introducing another backend. Changing an existing product’s Backend or replacing its credentials is not a data migration.

Before the first order on a new product, save its backend, generate matching options, then review the order form. Use the product setup guide and placement guide to verify what customers will receive.

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