Create a bucket

A bucket is the basic unit of storage — the "root folder" that holds all objects. Each account can create multiple buckets with independent names, and each bucket has its own configuration (Policy, CORS, Lifecycle, Versioning).

Prerequisites

• The LANIT Cloud account is active.
• You're signed in to the Portal.
• You have enough balance or a Simple Storage plan.

Steps

Step 1. Open the Buckets page

Left menu → Simple Storage → Buckets.

Step 2. Open the Create bucket form

Click + Create bucket in the top right.

Step 3. Fill in the form

Bucket Name

The bucket name must follow these rules:

• Only lowercase letters (a–z), digits (0–9) and hyphens (-).
• Length 3–63 characters.
• Must not start/end with -.
• Unique across the entire LANIT Cloud system — can't clash with another tenant's bucket.

Bucket name is permanent

The bucket name is fixed once created — you cannot rename it. To change it, you must delete the old bucket and create a new one (you'll lose data if you don't copy first).

Region

LANIT Cloud currently offers the HN (Hanoi) region. Pick the region closest to end users to lower latency.

Access Policy

Policy	Who can access?	When to use
Private (recommended default)	Only the owner and principals granted by Policy	Backups, internal data, sensitive data
Public Read	Anyone on the Internet can read	Static images, CDN files, static websites

Step 4. Create

Click Create bucket. The bucket shows up in the list with status Active, ready to receive uploads.

Naming convention

Recommended pattern: <org>-<service>-<env> or <domain>:

Purpose	Example
Account backup	acme-backup-prod
Web assets	acme-cdn-static
Static website for a domain	images.example.com
Internal logs	acme-logs-app

Matching the bucket name to a domain is required when you use the bucket for static website hosting with a custom domain.

See the bucket list

The Simple Storage → Buckets page shows:

• Bucket name + Region
• Created date
• Object count + storage used
• Current Access Policy

Next steps

• Upload an object — put files into the bucket.
• Bucket Policy — fine-grained access control.
• Bucket Versioning — keep previous versions of overwritten objects.
• Access Key — create keys for API/CLI/SDK use.