Skip to navigation

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

  1. Your organization has one or more workspaces. Each workspace has its own buckets and its own S3 endpoint.
  2. A bucket lives in one location (for example Amaravati, VGA) and holds objects.
  3. Each object is one file plus its details (size, type, date), found by its key — its full name inside the bucket.
  4. 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

You want to…UseWho can get inFor how long
Let your app or backup tool read and writeS3 credentialPrograms that have the keysUntil you revoke the credential
Share one private file, or accept one uploadPresigned URLAnyone with the link1 second to 7 days
Serve files to everyone (website, public downloads)Public Access + custom domainAnyoneUntil you turn it off

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:

PartExampleNotes
Keyreports/2026/may.pdfThe full name inside the bucket. Up to 1,024 bytes of UTF-8. Case-sensitive.
Datathe file’s bytesUp to 5 GiB in one upload; larger files are uploaded in parts (see Limits).
Content typeapplication/pdfTells browsers how to open the file. Set when you upload.
ETag"9b2cf535f27731c974343645a3985328"A fingerprint of the content, used by tools to check the upload.
Last modified2026-10-30 10:15When the object was last written.

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.

LocationCodeStatus for Object Storage
Amaravati, IndiaVGAAvailable
Hyderabad, IndiaHYDPre-order (Talk to Sales)

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:

https://WORKSPACE-ID.blob.ibeestorage.com

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:

SettingValue
Endpointhttps://WORKSPACE-ID.blob.ibeestorage.com
Regionauto
Addressing stylepath — the bucket name goes in the path (…/my-bucket/file.txt), not in the hostname
  • 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.

Glossary

TermMeaning
BucketA named container for objects, in one location and one workspace.
ObjectOne stored file plus its metadata.
KeyAn object’s full name inside its bucket, such as logs/app.log.
PrefixThe start of a key, such as logs/. Used as a “folder” and in rules.
S3 APIThe protocol Amazon S3 uses; IBEE implements the common parts of it.
EndpointThe address S3 tools connect to: https://WORKSPACE-ID.blob.ibeestorage.com.
Signing regionPart of every S3 request signature. Always auto for IBEE.
SigV4AWS Signature Version 4, the way S3 tools sign each request with your secret key. Tools do this for you.
Path-style addressingPutting the bucket name in the URL path rather than the hostname. Required by IBEE.
Multipart uploadUploading a large file in parts, which tools do automatically.
ETagA fingerprint of an object’s content.
Presigned URLA link with a built-in signature and expiry time.
Public Access URLA blob.dev address that serves a public bucket; meant for testing.
Class A / Class B operationsBilling groups of requests: writes and lists (A) and reads (B). See Pricing.
WORMWrite once, read many: data that can’t be changed after it is written.

Troubleshooting common misunderstandings

You expect…What actually happensWhat to do
Renaming a folder in one stepFolders are prefixes, so each object must be copiedCopy with aws s3 mv s3://bucket/old/ s3://bucket/new/ --recursive.
A new bucket to be readable by a linkBuckets are privateUse a presigned URL or turn on Public Access.
The region to be VGA or us-east-1 in toolsRequests fail with Invalid region scopeUse auto.
An overwritten file to be recoverableWithout Object Lock, the old content is replacedCreate buckets that need recovery with Object Lock, or keep your own copies.