> For the complete documentation index, see [llms.txt](https://docs.influxtechnology.com/support_guides/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.influxtechnology.com/support_guides/rexgen-series-product-manuals/rexgen-air-cloud-usage-guides/cloud-usage-guides-for-rexgen-air-device/self-hosting-with-rexgen-air-minio/step-3-create-bucket.md).
# Step 3 - Create Bucket
Click the 'Buckets' option and then the 'Create a Bucket' tab.
\
Specify the Bucket details.
* Bucket Name: Name the bucket (as desired) after reading the bucket naming rules.
* Versioning: allows multiple versions of the same object to be kept under the same key.
* Object Locking: prevents objects from being deleted. Required to support retention and legal hold. It can only be enabled at bucket creation.
* Quota: limits the amount of data in the bucket.
* Retention imposes rules to temporarily prevent object deletion. Versioning must be enabled to set bucket retention policies.
After entering all the details, click 'Create Bucket'.
Once the bucket is created, its properties can be accessed by simply clicking on its name.
Click on the bucket name to add/upload a file to the bucket.
Click the 'Upload' tab to upload any file/folder to the bucket.
---
# 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.influxtechnology.com/support_guides/rexgen-series-product-manuals/rexgen-air-cloud-usage-guides/cloud-usage-guides-for-rexgen-air-device/self-hosting-with-rexgen-air-minio/step-3-create-bucket.md?ask=&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.
