Connect a backup, sync or storage application to a customer service supplied by PD DigitalOcean Spaces. Use that service’s scoped key pair and regional endpoint, keeping the host’s administrative token private.

Collect the issued details

1. Open the intended storage service in the client area.
2. Open Connection details from its storage overview.
3. Note the exact bucket, endpoint and access key privately.
4. Use Show or Copy for the saved secret when needed.
5. Open Connect and review the suggested application settings.

Showing a saved secret again does not require rotation. Do not copy credential-bearing snippets into tickets, screenshots or shared notes.

Configure the application

Choose an S3-compatible destination and enter the issued regional endpoint, exact bucket and complete service key pair. Use virtual-host-style addressing where the application offers that choice. The S3 endpoint is separate from a web Console, CDN or custom public download address; rewriting a signed request to another hostname can invalidate it.

Follow the application-specific connection guide for signing and region fields. Different SDKs can distinguish their AWS validation region from the custom endpoint’s region. A client key intended for service buckets is not a host credential for creating arbitrary native buckets.

Verify the required operations

Use a harmless test object and check the operations the application needs. A successful upload alone does not prove a backup can be restored; test the relevant download or recovery path too.

For a signature or access refusal, compare the current complete key pair, exact endpoint and bucket before changing anything. Check the service’s actual access state and whether credentials were recently rotated. Use access troubleshooting if it remains unresolved, supplying the redacted error without secrets or signed object URLs.

See the PD DigitalOcean Spaces WHMCS guide for related tasks, or explore the module.