Skip to content
Black Friday

20% off for every Pro licenses

BLACKFRIDAYClaim the Offer
Contact us

Configure: S3-Compatible Object Storage

Many storage providers offer an API compatible with Amazon S3, for example Wasabi, Backblaze B2, Linode/Akamai Object Storage, Vultr Object Storage, Scaleway, IDrive e2, Contabo, Oracle Cloud, Storj, and self-hosted MinIO or Ceph. Media Cloud Sync works with any of them through the S3 Compatible option.

What is S3-compatible storage?

S3-compatible services implement the same API as Amazon S3, so one connection method works across all of them. You only need your provider’s endpoint URL and a pair of access keys; the rest of the setup is the same for every provider.

Using Cloudflare R2 or DigitalOcean Spaces? They have their own provider options with extra checks. Use the Cloudflare R2 or DigitalOcean Spaces guide instead.

You’ll need: an account with your provider, an existing bucket, and Media Cloud Sync installed and activated (installation guide).

Step 1: Collect the details from your provider

Get these four values from your provider’s dashboard:

ValueExampleWhere to find it
Storage Endpointhttps://s3.eu-central-1.wasabisys.comYour provider’s “S3 endpoint” or “S3 API URL” for your bucket’s region. See Common endpoint URLs
Access KeyAKIA… / 0051a2…Access keys / application keys section
Secret KeywJalr…Shown once when you create the key
Regioneu-central-1Usually part of the endpoint; optional for some providers

Also create a bucket in your provider’s dashboard first. The wizard can’t create buckets on S3-compatible services.

Make the bucket publicly readable if you’ll serve media straight from it. If you deliver through a CDN, set up the CDN’s access to the bucket instead.

Step 2: Choose S3 Compatible and name it

  1. Go to Media Cloud Sync → Dashboard, click Configure, then Get started. (New to the wizard? See Connecting Your Cloud Storage.)
  2. Select S3 Compatible.
  3. Enter a Provider label, such as “Wasabi” or “Backblaze B2”. This name appears throughout the plugin.
  4. Click Next.

Step 3: Enter credentials

Choose where to keep your credentials:

  • Use wp-config.php Constant (recommended; see Storing Credentials in wp-config.php):
    define( 'WPMCS_CONFIG', [
    'endpoint' => 'https://s3.eu-central-1.wasabisys.com',
    'access_key' => 'YOUR_ACCESS_KEY',
    'secret_key' => 'YOUR_SECRET_KEY',
    'region' => 'eu-central-1'
    ] );
  • Store in Database: enter Storage Endpoint, Access Key, Secret Key, and Region.

The endpoint must be a full URL starting with https:// (or http://) and use a domain name, such as https://minio.example.com:9000. Bare IP addresses and localhost aren’t accepted.

Click Verify credentials.

Step 4: Enter the bucket name

Type the name of the bucket you created in Step 1 and click Verify bucket. The plugin checks that it can read, write, and delete in that bucket. If a check fails, see Provider Permissions and Troubleshooting.

Click Save and continue.

Step 5: Choose how media is delivered

Click Finish setup, then use Recheck on the Delivery card in Settings to confirm files can be read publicly (Checking delivery).

Common endpoint URLs

Use the endpoint for the region your bucket is in. Some providers show an account-specific endpoint in their dashboard; if yours differs from this list, use the one from your dashboard.

ProviderRegionStorage Endpoint
WasabiUS East 1https://s3.wasabisys.com
US East 2https://s3.us-east-2.wasabisys.com
US West 1https://s3.us-west-1.wasabisys.com
EU Central 1https://s3.eu-central-1.wasabisys.com
AP South 1 (India)https://s3.ap-south-1.wasabisys.com
AP Southeast 1https://s3.ap-southeast-1.wasabisys.com
AP Northeast 1https://s3.ap-northeast-1.wasabisys.com
Backblaze B2Your bucket’s regionhttps://s3.REGION.backblazeb2.com, e.g. https://s3.us-west-004.backblazeb2.com
ScalewayFrance (FR-PAR)https://s3.fr-par.scw.cloud
Netherlands (NL-AMS)https://s3.nl-ams.scw.cloud
Poland (PL-WAW)https://s3.pl-waw.scw.cloud
Linode / AkamaiUS East (Newark)https://us-east-1.linodeobjects.com
US Central (Dallas)https://us-central-1.linodeobjects.com
EU Central (Frankfurt)https://eu-central-1.linodeobjects.com
AP South (Mumbai)https://ap-south-1.linodeobjects.com
IDrive e2US Easthttps://s3.us-east-1.idrivee2-22.com
US Westhttps://s3.us-west-1.idrivee2-22.com
EU Centralhttps://s3.eu-central-1.idrivee2-22.com
Oracle Cloud (OCI)Your regionhttps://NAMESPACE.compat.objectstorage.REGION.oraclecloud.com
StorjGlobal (S3 gateway)https://gateway.storjshare.io
MinIO (self-hosted)Your serverhttps://minio.example.com:9000
Ceph (self-hosted)Your serverhttps://ceph.example.com:7480
OpenStack SwiftYour serverThe URL of your S3 gateway (s3api)

Endpoint format: the endpoint must start with https:// (or http://), use a domain name (an optional :port is fine), and be at most 100 characters. localhost and bare IP addresses aren’t accepted, so give a self-hosted server a domain name. The plugin always connects using path-style addressing, so for Oracle Cloud use the path-style compat endpoint shown above, not the virtual-hosted one.

Provider notes

In every case: files must be readable by visitors, either through a public bucket or through your CDN. The wizard can’t make the bucket public for you, because uploaded files don’t carry a public ACL.

Wasabi

Backblaze B2

  • Endpoint: shown next to your bucket on the Buckets page, as https://s3.REGION.backblazeb2.com.
  • Keys: create an Application Key. The master key doesn’t work with the S3 API. The key ID is your Access Key, and the application key is your Secret Key.
  • Limited to one bucket? Turn on Allow List All Bucket Names on the key. See Getting started with the S3 API.
  • Public access: set the bucket’s privacy to Public.

MinIO and self-hosted

Give the server a domain name. The endpoint must be reachable from your WordPress server, and from visitors’ browsers if you serve files from it. Set the bucket’s anonymous access to allow downloads.

Others

Linode/Akamai, Vultr, Scaleway, IDrive e2, Contabo, Oracle Cloud, Storj, and Ceph work the same way: find the S3 endpoint and region for your bucket, create an access key with read, write, and delete on it (Provider Permissions), and make the bucket publicly readable in your provider’s panel.

Note: Private Media PRO isn’t available for S3-compatible providers.

If your provider doesn’t work with these steps, contact us through dudlewebs.com and we’ll look into it.

Next steps