Skip to content

S3-compatible

Many object stores speak the Amazon S3 API. In ConstellaWP, choose provider S3-compatible when the service is not listed as a named provider (Amazon S3, Cloudflare R2, Backblaze B2, DigitalOcean Spaces).

ConstellaWP uses the same client, presigned URLs, and path-style addressing as the named providers. You supply the endpoint, region, and access keys.

  • A bucket on an S3-compatible service
  • Access keys with read, write, and delete on that bucket (or on the path prefix you will use)
  • ConstellaWP role owner or admin

Prefer a named provider in the ConstellaWP list when one matches: the form and this Help Center then map the fields for you.

  1. In your provider console, create a private bucket. Note the bucket name, the region (or region slug), and the S3 API endpoint. The endpoint is an API hostname such as https://s3.wasabisys.com, not a website or public file URL.

  2. Create access keys (often labelled Access Key ID / Secret Access Key, or equivalent HMAC keys). Restrict them to this bucket when the provider allows it.

  3. In ConstellaWP, go to Storage → Add Destination:

    • Provider: S3-compatible
    • Fill the fields from the table below
    • Save, then Test connection
ConstellaWP field What to paste
Bucket Bucket name
Region Region the bucket lives in. Some providers use a dummy value such as us-east-1 — use whatever their S3 docs specify for SigV4
S3 Endpoint Base API URL, for example https://s3.eu-central-1.wasabisys.com. No trailing path, no bucket name in the host unless the provider documents it that way
Access Key ID S3 access key
Secret Access Key S3 secret key (shown once)
Path prefix Chosen by you; default backups

ConstellaWP talks to the endpoint with path-style URLs (https://endpoint/bucket/key). That is the usual setting for MinIO, Hetzner, OVH, and most self-hosted gateways.

These are starting points from provider docs — always copy the value shown in your console if it differs.

Provider Typical endpoint Region example
Wasabi https://s3.wasabisys.com or https://s3.<region>.wasabisys.com us-east-1, eu-central-1
MinIO https://minio.example.com (the API listen address) often us-east-1
Scaleway Object Storage https://s3.<region>.scw.cloud fr-par, nl-ams
Hetzner Object Storage https://<region>.your-objectstorage.com nbg1, fsn1, hel1
OVH Object Storage https://s3.<region>.io.cloud.ovh.net gra, sbg
Linode / Akamai Object Storage https://<region>.linodeobjects.com eu-central-1
Error Likely cause
Could not connect / cURL error Endpoint hostname is wrong, or it is a website URL instead of the S3 API
PermanentRedirect / 301 Region does not match the bucket
SignatureDoesNotMatch Secret truncated, or region/endpoint pair does not match what the provider expects for SigV4
NoSuchBucket Bucket name typo, or the key is scoped to another bucket
AccessDenied Key cannot PutObject / DeleteObject; the connection test writes then deletes a probe object
InvalidAccessKeyId Pasted a console login, a personal API token, or a public key instead of the S3 access key