Quick answer
When and where do I get my PrivateS3 access keys?
After payment, a person at PrivateS3 creates your bucket and one access key pair within 24 hours, and they appear in the client area. You then have five values: endpoint, region, bucket name, access key and secret key. Put them in restic, rclone or the AWS CLI. A bucket not ready in 24 hours is credited back in full.
In brief
- When: within 24 hours of the order, made by a person, not by a script.
- Where: in the client area, shown with your order.
- What: endpoint, region (eu-central-1), bucket name, access key and secret key.
- Changes: a new key pair or Object Lock is asked for by ticket.
What does each value do, and where does it go?
| Value | Example in this guide | restic | rclone |
|---|---|---|---|
| Endpoint | https://s3.privates3.com | Part of the repository URL | endpoint = |
| Region | eu-central-1 | AWS_DEFAULT_REGION | region = |
| Bucket | BUCKET | End of the repository URL | After the remote name |
| Access key | ACCESS_KEY | AWS_ACCESS_KEY_ID | access_key_id = |
| Secret key | SECRET_KEY | AWS_SECRET_ACCESS_KEY | secret_access_key = |
Why does it take up to 24 hours?
Because a person creates each bucket and key pair today; the client area has no bucket dashboard yet. One access key and secret key per bucket, created by a person within 24 hours of the order and shown in the client area. PrivateS3 says so before you pay, rather than promise a ready bucket at checkout.
If the bucket is not ready in time, the rule is simple: A bucket PrivateS3 cannot deliver within 24 hours is credited back to the balance in full; an outage longer than 24 hours gets the lost days credited back. Order a day before you plan to start a large upload. The top-up guide covers the payment that starts the clock.
What do I type into restic?
restic needs the keys as environment variables and the endpoint and bucket in the repository URL. restic's documentation gives the form s3:https://server/bucket_name for S3-compatible storage, with AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY for the keys. The region goes in AWS_DEFAULT_REGION. The endpoint and region are shown with the keys in the client area; the block uses example values.
restic asks for a repository password at init. That password encrypts everything. Store it apart from the keys: lose it and the backup cannot be read. Full setup and checks sit on the restic storage page.
export AWS_ACCESS_KEY_ID=ACCESS_KEY
export AWS_SECRET_ACCESS_KEY=SECRET_KEY
export AWS_DEFAULT_REGION=eu-central-1
restic -r s3:https://s3.privates3.com/BUCKET init
restic -r s3:https://s3.privates3.com/BUCKET backup /homeWhat do I type into rclone and the AWS CLI?
rclone takes the five values in one remote; the AWS CLI takes the keys once and the endpoint on each command. In rclone, use provider Other. With the AWS CLI, run aws configure for the keys and region, then add --endpoint-url to each call. A first ls that returns without an error proves the keys work.
To encrypt plain files with rclone, wrap the remote in a crypt remote. The rclone page shows that step.
[privates3]
type = s3
provider = Other
access_key_id = ACCESS_KEY
secret_access_key = SECRET_KEY
endpoint = https://s3.privates3.com
region = eu-central-1
# rclone check:
# rclone lsd privates3:
# AWS CLI check (after aws configure):
# aws s3 ls s3://BUCKET --endpoint-url https://s3.privates3.comHow do I keep the keys safe?
Treat the secret key like a password: one place, never in a ticket, never in a public repository. Anyone with both keys can read and delete the bucket. Without client-side encryption, the operator can technically read stored files, file names and sizes; with it, the operator sees only encrypted blobs, their sizes and upload times, so client-side encryption also limits what a leaked key exposes.
If a key leaks, open a ticket under Technical help and ask for a new pair and for the old one to be disabled. PrivateS3 checked on 17 November 2026 that the client area offers no self-serve key reset yet, so the ticket is the only way.
Access key questions
Can I have more than one key pair?
Not yet. No S3 Select, no bucket website hosting, no event notifications, no IAM policies beyond one key pair per bucket. One key pair per bucket is created by a person.
Which region do I enter?
eu-central-1. It is the name S3 clients expect; One data center in the European Union; the city is shown on the order page once the owner confirms it.
Do path-style and virtual-hosted URLs both work?
Yes. The bucket answers both. Most tools pick one on their own.
Can I turn on Object Lock myself?
No. Object Lock (immutable backups) is set on a new bucket on request through a support ticket.
My tool says SignatureDoesNotMatch. What is wrong?
Usually a copied key with a space or a missing character, or a wrong region. Copy both keys again and set the region to eu-central-1.
Verdict
- Expect the keys within 24 hours, in the client area, made by a person.
- Five values, one test: set them in your tool and run a listing before the first backup.
Sources (3)
- restic: preparing a new repository — restic (read 2026-11-17)
- rclone S3 backend documentation — rclone (read 2026-11-17)
- AWS CLI command reference (global --endpoint-url option) docs.aws.amazon.com/cli/latest/reference/s3api/put-bucket-lifecycle-configuration.html — Amazon Web Services (read 2026-11-17)
Order today, back up tomorrow
5 TB for 12 months at $133.87. Bucket and keys within 24 hours.
- Bucket and keys within 24 hours
- Encrypt before upload: the keys stay yours
- Pay in BTC, XMR, USDT, USDC, ETH, SOL or LTC
- DomaineGoat LLC · Panama