> For the complete documentation index, see [llms.txt](https://docs.higiocloud.vn/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.higiocloud.vn/hi-gio-s3-storage/bucket-management.md).

# Bucket Management

## <mark style="color:green;">**Overview**</mark> <a href="#overview" id="overview"></a>

The Bucket Management page displays information about your Buckets, including name, size, public and private modes, and operations of that Bucket.

* Rules Bucket names must follow domain name constraints.
  * Bucket names must be unique.
  * Bucket names cannot be formatted as IP addresses
  * Bucket names can be 3 to 63 characters long.
  * Bucket names cannot contain uppercase characters or underscores.
  * Bucket names must start with a lowercase letter or number.
  * Bucket names must be a series of one or more labels.
* The following example bucket names are valid and follow the recommended naming guidelines for general-purpose buckets:
  * docexamplebucket1
  * log-delivery-march-2020
  * my-hosted-content
* The following example bucket names are valid but are not recommended for uses other than static website hosting:
  * [docexamplewebsite.com](http://docexamplewebsite.com/)
  * [www.docexamplewebsite.co](http://www.docexamplewebsite.co/)m
  * my.example.s3.bucket
* The following example bucket names are invalid:
  * doc\_example\_bucket (contains an underscore)
  * DocExampleBucket (contains uppercase letters)
  * doc-example-bucket- (ends with a hyphen)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.higiocloud.vn/hi-gio-s3-storage/bucket-management.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
