Overview

S3-compatible buckets for files, backups, and static assets — create a bucket from the console, or use any S3 SDK or CLI.

Object Storage gives you S3-compatible buckets for anything you'd put in a blob store — user uploads, backups, exports, static assets. Create a bucket from the console in a few seconds, then use the built-in file browser or any S3-compatible SDK, CLI, or tool (AWS CLI, boto3, rclone, the AWS SDKs) to work with it.

A bucket is priced by a storage tier — a fixed monthly price for a fixed amount of space — rather than metered per gigabyte, so the cost is known upfront. See Tiers.

The mental model

• Bucket — a named container for objects, created in a specific region, on a specific storage tier, with a visibility of Private or Public read.
• Object — a file stored inside a bucket, addressed by a key (its path, e.g. avatars/user-42.png). Folders are a display convenience over /-delimited keys — S3-compatible storage has no real folders.
• Storage tier — a fixed amount of space for a fixed monthly price, picked when you create the bucket and changeable later. It's a hard cap: uploads are rejected once a bucket is full, same as it would be on any fixed-size disk.
• Access key — an S3-compatible access key ID + secret pair, scoped to one, several, or all of your buckets, used to authenticate SDK/CLI requests the same way you would against any S3-compatible provider.
• Visibility — Private (the default; every request needs a signed request or a presigned link) or Public read (anyone with an object's URL can fetch it, no credentials needed).

Two ways to work with a bucket

The console's Files tab is a full file browser — drag and drop to upload, click to download, select and delete — good for occasional use and for checking on what's actually in a bucket. For anything programmatic (an app uploading user files, a backup job, a CI pipeline pushing build artifacts) use an access key with any S3-compatible tool; nothing about the API surface is proprietary.

Explore