# Work with Buckets

To store your data in OORT Storage, you work with resources known as buckets and objects. A *bucket* is a container for objects. An object is a file and any metadata that describes that file.

To store an object in OORT Storage, you create a bucket and then upload an object to the bucket. Once an object is in a bucket, you can open it, download it, and move it. You can delete objects and buckets when you no longer need them.

{% tabs %}
{% tab title="Intro" %}

### What is a bucket?

A bucket is a container for objects stored in OORT Storage. You can store any number of objects in a bucket and can have up to 100 buckets in your account. 

Every object is contained in a bucket. For example, if the object named `photos/puppy.jpg` is stored in the `DOC-EXAMPLE-BUCKET` bucket in the US East Region, then it is addressable using the URL `https://DOC-EXAMPLE-BUCKET.dss.us-east-1.oortech.com/photos/puppy.jpg`. 

### Manage buckets

OORT Storage provides APIs for you to manage your buckets and objects. For example, you can create a bucket and upload objects using the OORT Storage S3-Compatible API or the OORT Storage console. The console uses the OORT S3-Compatible APIs to send requests to OORT Storage .

{% content-ref url="/spaces/Nn5zebxnzyzrzQhb979k/pages/d8dkEd9xbQ6HPbPiEH53" %}
[Work with Objects](/oort/oort-storage/manage-storage/work-with-objects.md)
{% endcontent-ref %}
{% endtab %}

{% tab title="Names" %}

### Bucket names

Each bucket on OORT Storage must be given a unique name, meaning a bucket's name cannot be used by another OORT account until the bucket is deleted. You should not depend on specific bucket naming conventions for the sake of availability or security.

### Bucket naming rules

* Bucket names must be between 3 (min) and 63 (max) characters long.
* Bucket names can consist only of lowercase letters, numbers, and hyphens (-).
* Bucket names must begin and end with a letter or number.
* Bucket names must be unique.
* A bucket name cannot be used by another OORT account until the bucket is deleted.

### Examples <a href="#bucket-names" id="bucket-names"></a>

The following example bucket names are valid and follow the recommended naming guidelines:

* `docexamplebucket1`
* `log-delivery-march-2020`
* `my-hosted-content`

The following example bucket names are *not* valid:

* `doc_example_bucket` (contains underscores)
* `my.example.s3.bucket` (contains dots)
* `DocExampleBucket` (contains uppercase letters)
* doc-example-bucket- (ends with a hyphen)
  {% endtab %}

{% tab title="Manage" %}

<figure><img src="/files/aSJV2xCoJq3z81GEphEv" alt=""><figcaption></figcaption></figure>

Managing your buckets in OORT Storage is quick and easy, thanks to our intuitive user interface. Simply right-click on the bucket you want to manage, and a menu of options will appear, allowing you to edit the bucket's properties, transfer data in and out of the bucket, and more.

###

{% endtab %}

{% tab title="Create a Bucket" %}

### Create a bucket

{% content-ref url="/pages/JMy1Udb7JM9zEw3FijQ4" %}
[Create a Bucket](/oort/oort-storage/getting-started/user-guide/create-a-bucket.md)
{% endcontent-ref %}

### Other ways to create a bucket

You can use the OORT Storage console, S3-Compatible APIs, AWS CLI, or AWS SDKs to create a bucket. For more information about the permissions required to create a bucket, see Create Bucket in the OORT S3-Compatible API Reference.
{% endtab %}
{% endtabs %}


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.oortech.com/oort/oort-storage/manage-storage/work-with-buckets.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.