Core Concepts
Object storage is a way to keep files as whole units, called objects, inside named containers called buckets. This page explains each idea you meet in the IBEE Object Storage docs, how they fit together, and the numbers that apply. If you want to try it first, start with Upload Your First Object.
How the pieces fit together
- Your organization has one or more workspaces. Each workspace has its own buckets and its own S3 endpoint.
- A bucket lives in one location (for example Amaravati,
VGA) and holds objects. - Each object is one file plus its details (size, type, date), found by its key — its full name inside the bucket.
- Programs reach your buckets through the S3 endpoint with an S3 credential. People on the internet reach them only if you share a presigned URL or turn on Public Access.
When to use which access method
Buckets
A bucket is a named container for objects. Every object lives in exactly one bucket.
- Names are 3 to 63 characters: lowercase letters, numbers and hyphens, starting and ending with a letter or number. Example:
invoices-2026. - Names are unique within a workspace. Two workspaces can each have a bucket called
assets. - Location is fixed. You pick it when you create the bucket. To move data to another location, create a new bucket there and copy the objects.
- Private by default. Only S3 credentials from the bucket’s workspace can read or write it.
Use separate buckets to separate environments (production and staging) or anything that needs different access, because Public Access and credential scopes apply to a whole bucket. See Buckets.
Objects and keys
An object is one file plus its metadata. Each object has:
Uploading to a key that already exists replaces the object. Unless the bucket was created with Object Lock (which turns on versioning), the old content is gone.
Folders are name prefixes
There are no real folders. A key such as photos/2026/beach.jpg is one name that happens to contain /. The portal shows the part before each / as a folder so you can browse, and Create Folder makes an empty placeholder object whose key ends in /.
This matters when you:
- Rename a folder: there is nothing to rename; each object must be copied to a new key and the old one deleted.
- Write lifecycle rules: a rule’s prefix (for example
logs/) selects every key that starts with it. - List files: S3 tools list keys by prefix, with
/as the separator.
Locations
A location is the data center where a bucket’s data is stored.
When you create a bucket, Automatic location picks an available location for you. Click Need a specific location? click here to choose one yourself. See Regions & Locations.
The location is not the same as the S3 signing region: S3 tools always use the region auto, whatever the bucket’s location.
The S3 endpoint
The endpoint is the web address S3 tools send requests to. Each workspace has its own:
It is set up when the workspace’s first S3 credential is created, and shown as S3 Endpoint in that dialog. Every S3 tool needs three settings:
Access: credentials, links and public buckets
- An S3 credential is an access key pair — an Access Key ID (like a username) and a Secret Access Key (like a password) — for one workspace, with one permission level: Object Read only, Object Read & Write, Admin Read only or Admin Read & Write. Object-level credentials can be limited to chosen buckets. See API Credentials.
- A presigned URL is a link to one object that works without keys until it expires (1 second to 7 days). See Presigned URLs.
- Public Access makes every object in a bucket readable by anyone, through the bucket’s Public Access URL (for testing; rate-limited) or a custom domain (for production). See Bucket Policies.
Versioning and Object Lock
- Versioning keeps the previous copy when an object is overwritten or deleted. Today it is turned on only together with Object lock (WORM) at bucket creation; the Versioning switch on its own isn’t applied yet.
- Object Lock stops objects from being deleted or overwritten until a retention date passes. WORM means “write once, read many”. It can only be turned on when the bucket is created, and a bucket with it can never be deleted. See Object Locking.
