Backup destinations
Cloudflare R2
R2 is the right pick if you'll be downloading your backups often. Zero egress fees, S3-compatible API, account-specific endpoint URL.
R2 is Cloudflare's object storage. Storage pricing is competitive with B2, and R2's defining feature is zero egress fees. You pay to store and to write, not to read. For backups you'll restore from often (active project archives, drives you swap out monthly), this changes the math significantly.
R2 speaks S3. Setup in Tusk is the same form as AWS or B2, with two differences: the endpoint URL includes your Cloudflare account ID, and you generate API tokens rather than creating IAM users.
Create a bucket
1
Open the R2 dashboard
2
Create a bucket
tusk-backups) and pick a location hint near you. Default automatic region is fine for most setups.3
Note your endpoint URL
<account-id>.r2.cloudflarestorage.com where <account-id> is your Cloudflare account ID. Copy it.Create an API token
R2 lets you create API tokens scoped to specific buckets and permissions. Create one for Tusk that only has access to your backup bucket.
1
Open R2 → Manage R2 API Tokens
2
Create a new token
tusk-backup. Set permissions to Object Read & Write. Under Specify bucket(s), pick your Tusk bucket. Leave TTL empty (no expiry) unless you want to rotate tokens.3
Save the Access Key ID and Secret Access Key
R2 tokens look like S3 keys
Connect Tusk
1
Add an S3 destination in Tusk
- Endpoint URL:
<account-id>.r2.cloudflarestorage.com - Bucket: your R2 bucket name
- Folder: a subfolder for this project
- Access key ID and Secret access key from the API token you just created
2
Test and save
Related