Docs
A working key in about two minutes.
Three steps, and the first one is on this screen. Nothing here needs an account.
1. Make a key
Say which space it is for and what it can do, then copy the result. It shows you once and is never shown again — not to you, not to us in plain form.
scopefs keys create \
--space invoices \
--access read-onlyYou should see the key once, then a line saying it was created.
2. Use it
Most people reaching for storage already have this. The endpoint is the only thing that differs.
aws s3 cp report.pdf \
s3://invoices/report.pdf \
--endpoint-url https://files.scopefs.comYou should see the upload succeed and return the key's name.
3. Check it worked
Seeing the file is the moment you become a user.
aws s3 ls s3://invoices/ \
--endpoint-url https://files.scopefs.comYou should see report.pdf listed with its size.
Which way in
I already use S3 toolsPoint
aws-cli or your SDK at the endpoint. Nothing new to learn, and the key still opens one space.I’m uploading from a browserRequest a key for one upload, use it, and it expires on its own. Nothing long-lived ships to the client.
The four things you’ll meet
A spaceA named place files live. The docs call it a scope; it is a bucket underneath.
A keyA credential for one space. The docs call it a client; it is an access key pair underneath.
A serviceWhere your storage actually lives. Any S3-compatible store.
An adminA person who can change keys and spaces. Only invited people.
When it doesn’t work
The key isn’t for that space.It was made for a different one. Check the space on the key record before changing anything else.
The key expired.Links for browser upload are deliberately short-lived. Request a fresh one; there is nothing to rotate.
A read-only key tried to write.Correct behaviour, not a bug. The message tells you which permission it actually holds.
Signature mismatch.Almost always the endpoint. One line fixes it, and it is the first thing to check.
Reference material for keys, the audit log and the console is not written yet. It will hang off this page as plain anchors rather than as a nested section pretending to be a product. How a key behaves →