Bucket Policies
Bucket access is about who can read and write the files in a bucket. Every bucket starts private: only S3 credentials from its workspace can read or write it. You open it up in one of three ways:
- Public Access: a switch on the bucket that lets anyone on the internet read every file in it, through a Public Access URL or a custom domain.
- S3 credentials: keys for your own apps and tools, each with a permission level and a list of buckets.
- Presigned URLs: links that let someone download or upload one file, until the link expires.
Which option should I use?
Public Access applies to the whole bucket: every file in it becomes public. To share some files publicly and keep others private, use two buckets, or presigned URLs for the private files.
For browser-based cross-origin access, see CORS. For Object Lock retention, see Objects → Locking.
Before you begin
- A bucket. See Create a bucket.
- Permission to change the bucket’s settings in the portal. The Public Access switch needs write access to the bucket.
Public access
Enabling Public Access allows objects in the bucket to be served unauthenticated via a Public Access URL.
Enable Public Access
Toggle Public Access from Disabled to Enabled. A confirmation toast appears: “Bucket access changed to public”.
Enable the Public Access URL
The Public Access URL section becomes active but no URL is assigned automatically — it shows “No Public Access URL is assigned to this bucket.”
Click Enable in the top-right of the Public Access URL card to assign a URL to the bucket.
Copy the URL. Objects are then accessible at:
The Public Access URL is rate-limited and not recommended for production. For production traffic, connect a custom domain to the bucket. To turn the URL off, click Disable on the Public Access URL card.
Enabling Public Access makes all objects in the bucket readable without authentication. Only enable this for buckets intended for public content.
If Public Access is disabled, the Public Access URL section shows: “Please enable public access in General to use the Public Access URL.”
To serve from your own hostname instead of the assigned Public Access URL, see Custom Domains — the bucket must be public to register a custom domain.
API Credential access
For programmatic access via the AWS CLI, rclone, or any S3-compatible tool, use an S3 credential, created under Organization → API Tokens → S3 Credentials. Each credential belongs to one workspace and provides:
- Access Key ID + Secret Access Key — for S3-compatible tools
- S3 Endpoint —
https://{workspaceId}.blob.ibeestorage.com
Permission levels
Each credential is created with one Object Storage permission level:
Bucket scoping
Admin credentials always apply to every bucket in the credential’s workspace. Object Read & Write and Object Read only credentials can apply to:
- Apply to all buckets in this organization (including newly created buckets): the simplest option for application-wide access.
- Apply to specific buckets only: pick one or more buckets the credential can access.
This is the bucket-level access boundary: a credential scoped to bucket A cannot read or write to bucket B.
Troubleshooting
Best practices
- Default to private. Only enable Public Access on buckets that genuinely serve public content (websites, media, downloads).
- Use one credential per application or environment with the narrowest permission level and bucket scope that works.
- Rotate credentials by creating a new credential, switching applications to use it, then revoking the old one. The Secret Access Key is shown only once — store it securely.
- Separate buckets for prod / staging / dev rather than relying on prefix-based separation alone.
