Browse articles Object storage # Creating and managing buckets Create an S3-compatible object storage bucket from the dashboard and understand global bucket naming rules, optional bucket quotas and account quotas, the preparing status, and bucket deletion. 3 min readUpdated: October 23, 2026[Baca dalam Bahasa Indonesia](/docs/bucket) A bucket is a container for objects in Linuxteknosia Cloud S3-compatible object storage. You choose the name of each bucket yourself, every bucket can be given a fixed (hard) quota, and all your buckets are isolated from other accounts: your access keys can only access buckets that belong to your account. ## 1\. Get to know the Object storage page Open **Object storage** in the sidebar. The page shows: - **Used**: the data stored right now. - On a pay-as-you-go account: **Estimated bill this month** (no account quota limit). On an account with a storage plan or an admin-set limit: **Account quota** and its source (_ plan_ or _set by admin_). - **Buckets**: the number of buckets; on a limited account also the quota already allocated and the remaining account quota. - **Active access keys** and **30-day usage** (the chart appears after usage has been sampled for a few hours). - The **S3 endpoint** card: **Endpoint** `https://storage.linuxteknosia.cloud` and **Region** `id-jkt-1`. S3 clients must use path-style addressing. ## 2\. Create a bucket 1. Click **Create bucket**. 2. Enter a **Bucket name** that follows the rules below. Example: `production-assets-example-co`. 3. Fill in **Limit (GB, optional)** on a pay-as-you-go account or **Quota (GB)** on a plan account. On a pay-as-you-go account this field is optional: leave it empty if the bucket does not need a limit, and billing still follows the GB actually stored. On an account with a storage plan, bucket quotas come out of the plan quota: the total quota of all buckets may not exceed the account quota, and if the field is left empty the bucket takes all of the remaining account quota. The remaining account quota is shown below the field. 4. Tick **object lock** (WORM) only if you need objects that cannot be deleted during a retention period. This option can only be chosen when the bucket is created, and versioning is enabled with it. 5. Click **Create bucket**. Bucket naming rules: - Names are global across the service, as in AWS S3, and are used exactly as you type them. - 3–63 characters: lowercase letters, digits, and hyphens. - Start and end with a letter or digit, without two consecutive hyphens (`--`). - Names starting with `lt-` or `linuxteknosia` are reserved for the platform. - If a name is already taken, the dashboard tells you so; choose another name, for example by adding your company or project name. Use the bucket name exactly as shown in the dashboard in every S3 client. Buckets created before these rules took effect keep their existing names and keep working as before. ## 3\. Wait for the ready status A bucket with a quota shows **preparing** while the quota scanner sets it up, for up to about 2 minutes. During that time uploads are rejected with the message `quota check temporarily unavailable`. The page refreshes automatically and the status changes to **ready**. ## 4\. Change the bucket quota 1. Click the bucket name to open its page. 2. In the **Quota & usage** card, enter the **Bucket quota (GB)** and click **Save quota**. On a pay-as-you-go account, clear the field and save to remove the bucket limit. On an account with a storage plan, the quota is required and can be at most the remaining account quota plus the bucket's current quota. The quota cannot be lower than the current usage. The quota is _hard_: uploads that exceed it are rejected. The quota only limits capacity. On pay-as-you-go, billing is based on the average GB actually stored, not on the allocated quota. ## 5\. Delete a bucket On the bucket page, open **Danger zone → Delete bucket**, type the bucket name to confirm, and click **Delete permanently**. Every object in it is deleted and cannot be recovered. ## Account limits The number of buckets per account is limited (shown as _n of max buckets_). Buckets are created from the dashboard or the API, not from S3 clients; tenant access keys cannot create new buckets. ## Troubleshooting - **"nama bucket: 3–63 karakter, huruf kecil, angka, dan tanda hubung"** (invalid bucket name): fix the name according to the rules above. - **"nama bucket berawalan ... dicadangkan"** (reserved name): names starting with `lt-` or `linuxteknosia` cannot be used; choose another name. - **"kuota bucket melebihi sisa kuota akun"** (quota exceeds the remaining account quota): lower the quota, reduce another bucket's quota, or raise the account quota with a storage plan. - **"kuota bucket harus lebih dari 0"** (quota must be greater than 0): accounts with a storage plan must give every bucket a quota; enter a quota within the remaining account quota. - **"batas N bucket per akun tercapai"** (bucket limit reached): delete unused buckets or contact support. - **"nama bucket sudah dipakai"** (name taken): bucket names are global and this one is already in use; choose another name. - **"bucket ... sudah ada di akun Anda"** (bucket already exists in your account): you already own a bucket with that name; use it or choose another name. - **"bucket masih berisi objek"** (bucket not empty): empty the bucket, or delete it permanently from the dashboard. - **"layanan storage ditangguhkan"** (storage suspended): read [Storage suspended](/help/storage-ditangguhkan). ## See also - [Creating access keys](/docs/access-key) - [Bucket settings](/docs/pengaturan-bucket) - [AWS CLI](/docs/aws-cli), [rclone](/docs/rclone) Still need help? Open a support ticket from the dashboard and our team will reply as soon as possible. [Help center](/en/help)[Open a ticket](/app/support/new)