Buckets
A bucket is a container for objects. Every object lives in exactly one bucket, and a bucket lives in a single location (chosen at creation).
What you can do with a bucket
Naming rules
Bucket names must:
- Be 3 to 63 characters long.
- Contain only lowercase letters, numbers, and hyphens (
-) — dots (.) and underscores (_) are not allowed. - Start and end with a lowercase letter or number.
- Be globally unique within IBEE Object Storage.
Create a bucket
1. Go to Object Storage
In the IBEE Solutions portal, click Object Storage in the left sidebar under Infrastructure.
The page lives at portal.ibee.ai/organizations/{orgId}/workspaces/{workspaceId}/object-storage.
2. Open the create-bucket page
Click Create Bucket in the top right. The create page has four sections:
Choose a location
The Location section has two tabs:
- Automatic — Automatic location (the default) picks the best available region for the bucket. To choose yourself, click Need a specific location? click here and pick a site from the grid. Available sites are labelled with their country; pre-order sites are labelled Talk to Sales.
- Specify jurisdiction — coming soon. For jurisdiction-based placement, talk to sales.
If you pick a pre-order site or the jurisdiction tab, the footer button changes from Create Bucket to Talk to Sales.
Versioning and Object Lock
With Object lock (WORM) on, pick a default retention mode — None, Governance, or Compliance — and, for Governance or Compliance, a Retention period in days (default 30, minimum 1). You can change the default retention later on the Lock Settings tab. See Objects → Locking.
API placement
For public API requests, omit site_id. It is internal placement metadata,
not a value users should guess or copy from another product. The region
field is required and must be the Object Storage region identifier configured
for the target environment. Do not send a compute site ID or a display name.
The public API does not currently provide a region-discovery endpoint. Use the
region identifier provided for your environment; if it is not available in
your account configuration, contact support before creating the bucket.
Bucket creation requires the object-storage.write scope.
List buckets
The Object Storage page lists every bucket in the organization with these columns:
The usage panel at the top shows Buckets, Objects, Storage Used, and Bandwidth Egress for the organization.
Bucket detail page
Click a bucket name to open it. The bucket page has three tabs:
Settings tabs
Settings opens a sub-navigation with these tabs:
The General tab fields:
Empty a bucket
Empty bucket permanently removes every object in a bucket while keeping the bucket and its settings. It runs as a background job, so you don’t have to delete objects one by one.
Open the Danger Zone
Open the bucket → Settings → General. The Danger Zone card at the bottom holds Empty bucket and Delete bucket.
Start the job
Click Empty bucket. In the dialog, type the bucket name to confirm and click Empty bucket. This action cannot be undone.
Track progress
A status strip replaces the button while the job runs — for example Emptying bucket…, Finalizing empty bucket…, or Retrying empty bucket…. Click Cancel to stop a running job. When it finishes, the strip shows the outcome (Bucket contents were deleted, Bucket partially emptied, Some objects are protected, Couldn’t empty bucket, or Empty bucket cancelled) and can be dismissed.
Empty bucket isn’t available for every bucket. It is blocked for buckets with Object Lock enabled, and for buckets with Versioning enabled. Delete objects in those buckets with an S3-compatible client instead.
Delete a bucket
Delete bucket sits in the Danger Zone on the General tab. You can also delete an empty bucket from the bucket list.
Only empty buckets can be deleted. If the bucket still contains objects, Delete bucket is disabled and the card reads “This bucket contains X objects. Empty it first to delete.” — use Empty bucket first.
Click Delete bucket, then confirm with Delete. This action cannot be undone.
Buckets with Object Lock enabled can’t be deleted — even when empty. If you enabled Object Lock at creation, the bucket is permanent and cannot be deleted, regardless of whether it contains any objects. See Objects → Locking.