On this page
Object storage (S3)
Object storage keeps files as objects inside buckets and serves them over an S3-compatible API, so any S3 tool or SDK can read and write your data. It is ideal for backups, media, static sites and application assets.
Unlike a volume, object storage is not mounted to one instance. Objects are addressed by a bucket name and a key over HTTP(S), so many clients can read and write in parallel from anywhere with the right credentials.
Because the API is S3-compatible, you keep using the tools you already know: the AWS CLI, rclone, s3cmd, and the AWS SDKs. The console adds a browser file manager, access-key and sub-user management, bucket policies, CORS, versioning, static website hosting, presigned URLs and per-bucket quotas.
Key concepts
Bucket — A named container for objects; names are unique within the storage service.
Object — A single stored file plus its metadata, identified by its key within a bucket.
Key / prefix — The object's full name; a shared prefix ending in / acts like a folder.
Access key — An access-key-id and secret pair used to sign S3 requests.
Endpoint — The S3 service URL your client connects to; the console shows the exact value for your account.
Presigned URL — A temporary, signed link that grants time-limited access to one object without sharing keys.
Before you start
- A bucket created in the console.
- An S3 access key (access-key-id and secret) generated for your account.
- The S3 endpoint and region shown on the bucket's connection panel.
- An S3 client such as the AWS CLI, rclone or an SDK.
Step by step
- Create a bucket
Go to Storage > Object storage and choose Create bucket. Pick a name that is unique and DNS-friendly.
Screenshot — The Create bucket dialogThe Create bucket dialog - Generate an access key
Open the access-key manager and create a key. Copy the secret now; it is shown only once.
Screenshot — The access-key manager showing a newly created key pairThe access-key manager showing a newly created key pair - Read the connection details
Open the bucket's connection panel to copy the endpoint URL and region. You can also download a ready-made AWS CLI or rclone config.
Screenshot — The bucket connection panel with endpoint, region and a generated CLI configThe bucket connection panel with endpoint, region and a generated CLI config - Upload and manage files
- Drag files into the browser file manager, or
- Use any S3 client with your key and the endpoint.
Screenshot — The browser file manager with a file upload in progressThe browser file manager with a file upload in progress - Add features as needed
- Turn on versioning to keep previous copies of objects.
- Set a bucket policy or CORS rules for controlled access.
- Enable static website hosting to serve a site from the bucket.
- Generate a presigned URL to share one object temporarily.
Examples
patrii s3 cli-config # endpoint, region and keys aws configure # Access Key ID : <your-access-key-id> # Secret Access Key: <your-secret> # Default region : <region-from-console>
# use the endpoint URL shown on the bucket connection panel ENDPOINT=<your-s3-endpoint> aws s3 ls --endpoint-url $ENDPOINT aws s3 mb s3://my-bucket --endpoint-url $ENDPOINT aws s3 cp ./report.pdf s3://my-bucket/ --endpoint-url $ENDPOINT aws s3 sync ./site s3://my-bucket/ --endpoint-url $ENDPOINT
# endpoint and keys: run `patrii s3 cli-config` (or see the bucket connection panel) rclone config create patrii s3 provider Other \ access_key_id <your-access-key-id> \ secret_access_key <your-secret> \ endpoint <your-s3-endpoint> rclone sync ./backups patrii:my-bucket/backups
Limits & specifications
Object-storage features available in the console:
| Feature | What it gives you |
|---|---|
Buckets & objects | Create buckets and upload, list, download and delete objects. |
Access keys | S3 key pairs to authenticate your clients. |
Sub-users | Additional identities with their own keys and permissions. |
Bucket policy | Fine-grained access rules on a bucket. |
Versioning | Keep and restore previous versions of an object. |
CORS | Allow browser apps on other origins to call the bucket. |
Static website | Serve a static site directly from a bucket. |
Presigned URLs | Time-limited links to upload or download one object. |
Per-bucket quota | Cap the size a bucket may grow to. |
Best practices
- Use a separate access key per application so you can rotate or revoke one without affecting others.
- Prefer sub-users with scoped permissions over sharing your main key.
- Enable versioning on buckets that hold important or frequently-overwritten data.
- Share single files with presigned URLs instead of making a bucket public.
- Always pass the endpoint URL from the console; the default AWS endpoints will not reach Patrii object storage.
FAQ
Which endpoint URL do I use?
--endpoint-url (AWS CLI) or the equivalent SDK setting. Requests sent to the default AWS endpoints will not reach your data.I lost my secret access key.
Can I host a website from a bucket?
How do I let a browser app call my bucket?
Learn more
Everything you can do here in the console is also available through the Patrii Cloud API for automation and scripting.