← CloudScale Plugin Help/CloudScale Backup & Restore, Free WordPress Backup Plugin with One-Click Restore & Cloud Sync
AWS S3 and S3-compatible


The AWS S3 Remote Backup card uploads backup zips to an S3 bucket after every local backup. The plugin talks to the S3 API directly from PHP using signed HTTPS requests, the AWS CLI is not needed and nothing has to be installed on the server. It needs AWS credentials with s3:PutObject, s3:ListBucket, and s3:DeleteObject permissions on the target bucket.
S3 Bucket name, bucket name only, no s3:// prefix (e.g. my-wp-backups).
Key prefix (folder), path prefix applied to all uploaded objects. Trailing slash required (e.g. backups/). Use / to store at the bucket root.
AWS Access Key ID / AWS Secret Access Key, the IAM access key the plugin signs requests with. Once saved, the fields show only the last characters; leave them blank to keep the current key. Leave both empty on EC2 to use the instance’s IAM role instead (see Option A below).
AWS Region (optional), the bucket’s region (e.g. af-south-1). Leave blank on EC2 to use the instance’s region; set it when the site is not on EC2.
Test Connection, writes a small test file, lists the folder and deletes the file again. Retention needs list and delete as well as write, so a key that can only upload is reported with the missing permission named, rather than passing and then failing every prune.
Diagnose, shows the S3 client (requests are signed by the plugin itself), bucket, prefix, which credentials are in use (access keys saved in the card first, otherwise the EC2 instance role), last sync, and whether AWS S3 is ticked under Include in cloud backup.
Copy Last Backup to AWS S3, immediately copies the most recent local backup zip to S3, outside of any schedule. Does not create a new backup, it copies whatever zip is already on the server. S3 has no practical storage quota for most accounts, so no pre-flight space check is performed.
When configured, the card shows the full S3 destination path (s3://bucket/prefix/), number of objects in the bucket, and time of last upload. A part that fails on a dropped connection, a timeout or an S3 server error is retried on its own, so one slow part does not cost the whole upload.
AWS S3 Setup Guide
Step 1, Grant AWS credentials
Both options use this IAM policy, scoped to your bucket:
{
"Version": "2012-10-17",
"Statement": [{
"Effect": "Allow",
"Action": ["s3:PutObject","s3:ListBucket","s3:DeleteObject","s3:GetObject"],
"Resource": [
"arn:aws:s3:::YOUR-BUCKET-NAME",
"arn:aws:s3:::YOUR-BUCKET-NAME/*"
]
}]
}
Option A, IAM Instance Role (EC2 only, recommended, no keys stored)
- AWS Console → IAM → Roles → Create role
- Trusted entity: AWS service → EC2 → Next
- Skip managed policies → Create role (e.g. name it
ec2-s3-backup) - Open the new role → Add permissions → Create inline policy → JSON tab → paste the policy above
- Name the policy (e.g.
ec2-s3-backup-policy) → Create policy - EC2 Console → select your instance → Actions → Security → Modify IAM role → select the role → Update IAM role
- Leave the Access Key ID and Secret Access Key fields on the card empty. The plugin reads short-lived role credentials from the EC2 Instance Metadata Service.
Option B, IAM User with access keys (any server)
- AWS Console → IAM → Users → Create user (e.g.
cloudscale-s3) - Attach the policy above as an inline policy
- Open the user → Security credentials → Create access key → copy the Access Key ID and Secret Access Key (the secret is shown once only)
- Paste both into the AWS Access Key ID and AWS Secret Access Key fields on the card, and set AWS Region if the site is not on EC2
Step 2, Save settings in the plugin
Enter your bucket name and prefix, click Save, then Test Connection. Then tick AWS S3 Remote Backup under Include in cloud backup in Cloud Backup Settings and click that card’s Save, otherwise uploads are skipped.
S3-compatible storage (R2, B2, Wasabi and others)
The same card works with any storage that speaks the S3 API. Choose it in the Provider list at the top of the card: Cloudflare R2, Backblaze B2, Wasabi, DigitalOcean Spaces, Google Cloud Storage, Hetzner Object Storage, or S3-compatible (other) for MinIO and the rest. Everything else stays the same: multipart upload, parallel download, resume, retention, golden backups and restore.
- Endpoint, shown for every provider except Amazon S3. Most providers fill it in from the region. For Cloudflare R2 paste the address from your R2 bucket settings (
https://<account-id>.r2.cloudflarestorage.com); for other, the address your provider gives you, including a port if it uses one. - Region, the region your provider shows for the bucket. R2 and Google Cloud Storage use
auto. - Access Key ID / Secret Access Key, the S3 API key your provider issues (in Google Cloud Storage, an HMAC key). The EC2 instance role is only used for Amazon S3.
The key needs permission to write, list, read and delete in the bucket. Test Connection checks all of them and names any that is missing.
Setup, provider by provider
Each one ends the same way: choose the provider on the card, enter the bucket, region (and endpoint where asked) and the two keys, click Save, then Test Connection, then tick the card under Include in cloud backup. Keep the bucket private. Copy the secret as soon as it is shown; every provider shows it once only.
Cloudflare R2
- Dashboard → R2 Object Storage → Create bucket.
- Manage API tokens → Create API token, permission Object Read & Write, limited to that bucket.
- Copy the Access Key ID, Secret Access Key and the endpoint
https://<account-id>.r2.cloudflarestorage.com(a bucket in the EU jurisdiction uses<account-id>.eu.r2.cloudflarestorage.com). Region:auto.
Backblaze B2
- Buckets → Create a Bucket, set to Private. Note its Endpoint, for example
s3.us-west-004.backblazeb2.com. - Application Keys → Add a New Application Key, access to that bucket only, type Read and Write. The master application key does not work with the S3 API.
- Access Key ID is the keyID, secret is the applicationKey. Region is the middle of the endpoint:
us-west-004.
Wasabi
- Buckets → Create Bucket, choosing a region such as
eu-central-1. - Policies → Create Policy allowing
s3:ListBucketon the bucket ands3:GetObject,s3:PutObject,s3:DeleteObjecton its contents. - Users → Create User with programmatic access, attach the policy, and copy the keys. Region is the bucket’s region.
- Wasabi bills every object for at least 90 days, so a backup deleted sooner by retention is still charged. Set retention with that in mind.
DigitalOcean Spaces
- Spaces Object Storage → Create Bucket in a datacenter such as
nyc3orfra1. - Access Keys → Create Access Key, Limited Access to that bucket with Read/Write/Delete.
- Region is the datacenter slug, for example
fra1.
Google Cloud Storage
- Cloud Storage → Buckets → Create, storage class Standard (Nearline, Coldline and Archive charge minimum storage periods).
- IAM & Admin → Service Accounts → create one. On the bucket’s Permissions, grant it Storage Object Admin.
- Cloud Storage → Settings → Interoperability → Create a key for a service account, pick that account, and copy the access key and secret. Region:
auto.
Hetzner Object Storage
- Cloud Console → your project → Object Storage → Create Bucket in
fsn1,nbg1orhel1, private. - Security → S3 Credentials → Generate credentials. Region is the location code, for example
fsn1. - Hetzner credentials reach every bucket in the project, so keep backups in a project of their own.
MinIO and other S3-compatible servers
- Create a bucket, then a user or access key with a policy allowing
s3:ListBucketon the bucket and get, put and delete on its contents. - Choose S3-compatible (other) and enter the S3 API address with its port, for MinIO usually
https://your-host:9000(9001 is the web console and will not work). Region:us-east-1unless the server sets another.