E2E Object Storage

View as Markdown

E2E Object Storage holds files as objects inside a bucket, reached over the network rather than attached to a server like a disk. You reach a bucket with an access key or a shared link, from any node, your own laptop, or another cloud. It is built to speak the same S3 API as Amazon S3, so the S3-compatible tools and SDKs you already know work against it too. See S3 compatibility for exactly which ones. A bucket is a good fit for backups, web app uploads, and AI/ML datasets.

How buckets, objects and keys fit together

Diagram as text

flowchart TD
    A[Create a bucket] --> B[Upload and download objects from the dashboard]
    A --> C[Generate an access key]
    C --> D[Connect with the mc client, s3cmd, or an SDK]
    D --> E[Upload and download objects from a script or an app]

What you can do with Object Storage

Set up a bucket and reach it:

Create a bucket in Delhi or Chennai
Generate an access key so an app or a command-line tool can read and write to it
Connect with the mc client
Connect with s3cmd
Connect with CS Browser (formerly S3 Browser)
Use the S3-compatible API from an SDK
Mount a bucket with s3fs to use it as a folder

Work with what is in it:

Upload and download objects from the dashboard
Share an object with a presigned URL without handing out your access key
Make a bucket public for files meant for everyone
Delete a bucket, or empty it and keep it
Track storage usage from the usage dashboard

Protect your data:

Turn on Object Versioning so the earlier copy survives an overwrite or delete
Lock objects with Object Lock to protect them from changes and deletes for a set time
Encrypt objects with your own key
Set a lifecycle rule to delete old objects automatically
Replicate a bucket to another region

Use it with other products and services:

Where to start with Object Storage

Get started with E2E Object Storage creates a bucket and uploads a first file. When something fails, start at Troubleshooting E2E Object Storage.