Storage destinations

Backups need a destination: a named connection to a bucket you control. Credentials are encrypted with your organization’s key. Backup bytes go from WordPress to the provider; they do not pass through ConstellaWP.

Open Storage in the ConstellaWP sidebar (owners and admins). Members cannot view destinations.

Choose a provider

Provider	ConstellaWP type	Guide
Amazon S3	s3	Amazon S3
Cloudflare R2	r2	Cloudflare R2
Backblaze B2	b2	Backblaze B2
DigitalOcean Spaces	spaces	DigitalOcean Spaces

Each guide follows the same pattern: prerequisites, numbered steps, a field-mapping table, then common errors.

Fields every destination shares

ConstellaWP field	Purpose
Name	Label in the UI (for example “Production backups”)
Bucket	Bucket / Space / B2 bucket name
Path prefix	Object prefix, default backups. Required. Changing it does not move existing archives

Provider-specific secrets (access keys, application keys) are write-only on edit: leave them blank to keep the stored value. You cannot change the provider on an existing destination — create a new one instead.

After you save

1. Click Test connection. ConstellaWP writes and deletes a probe object under the path prefix.
2. Attach the destination to a site backup policy, or run a manual backup.

Tip

Grant the key read, write, and delete on the prefix you use. Listing-only keys pass a bucket list but fail backups and retention deletes.

Deleting a destination

Only owners can delete a destination. Objects already in the bucket are not removed. Policies that pointed at it will need a new destination before scheduled backups run again.