Work with Buckets

To store your data in Oort DSS, 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 DSS, 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.

What is a bucket?

A bucket is a container for objects stored in Oort DSS. 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

Manage buckets

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


To upload your data (photos, videos, documents, etc.) to Oort DSS, you must first create a bucket in one of the Oort Regions.
Oort DSS creates buckets in the Region of your choosing. To optimize latency, minimize costs, or address regulatory requirements, choose the Oort Region that is geographically close to you. For a list of Oort Storage Regions, see Regions and Endpoints in the Oort General Reference.

Bucket names

Each bucket on Oort DSS must be given a unique name, meaning a bucket's name cannot be used by another Oort Cloud 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.


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)

Create a bucket

-> Sign in to Oort DSS Console
-> Click Create bucket: this will open the Create bucket wizard
-> Under Bucket name, enter a DNS-compliant name for your bucket. The bucket name must:
  • Be unique
  • Be between 3 and 63 characters long
  • Not contain uppercase letters
  • Start with a number or a lowercase letter
You cannot change a bucket's name once you create it. For information about naming buckets, see Bucket naming rules
-> Under Storage provider, choose the storage provider for the files you're uploading
-> To add a tag to the objects that you're uploading, click Add tag. Name the tag in the Key field. Type a value for the tag. You can add up to 10 tags per object
Object tagging allows you to categorize your storage. Each tag is a key-value pair. Key and tag values are case sensitive. A tag key can be up to 128 Unicode characters in length and tag values can be up to 255 Unicode characters long. Learn more about tagging.
-> Click Upload to upload your objects
Oort DSS will upload your object. Once the upload is complete, you'll see a "success" notification on the Upload: status page
-> Click Exit

Other ways to create a bucket

You can use the Oort DSS console, Oort DSS 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 DSS S3-Compatible API Reference.

Who owns the buckets?

The Oort account that creates the bucket owns it. You can upload any number of objects to the bucket. By default, you can create up to 100 buckets in each of your Oort accounts. You can store any number of objects in a bucket.
Object Ownership is an Oort DSS bucket-level setting that you can use to take ownership of every object in your bucket, simplifying access management for data stored in Oort DSS. When you create a bucket, you own it. By extension, you automatically own every object in that bucket. As a result, access to your data is based on policies.

Types of bucket tags

Oort provides two types of cost allocation tags, an Oort-generated tag and user-defined tags. The definitions are quite straightforward.
  • Oortech-generated tags: defined, created, and applied by Oort
  • User-defined tags: defined, created, and applied by users

Tag set

Each DSS bucket has a tag set. A tag set contains all of the tags that are assigned to that bucket. A tag set can contain as many as 50 tags, or it can be empty. Keys must be unique within a tag set, but values in a tag set don't have to be unique. For example, you can have the same value in tag sets named project/Trinity and cost-center/Trinity.
Within a bucket, if you add a tag that has the same key as an existing tag, the new value overwrites the old value.
Oort doesn't apply any semantic meaning to your tags. We interpret tags strictly as character strings.

Manage tags

To add, list, edit, or delete tags, you can use the Oort DSS console, the AWS Command Line Interface (AWS CLI), or the Oort S3-Compatible API.

Tag restrictions

  • Maximum number of tags per resource – 50
  • For each resource, each tag key must be unique, and each tag key can have only one value.
  • Maximum key length – 128 Unicode characters in UTF-8
  • Maximum value length – 256 Unicode characters in UTF-8
  • Allowed characters
    • The allowed characters across services are: letters (a-z, A-Z), numbers (0-9), and spaces representable in UTF-8, and the following characters: + - = . _ : / @.
    • If you enable instance tags in instance metadata, instance tag keys can only use letters (a-z, A-Z), numbers (0-9), and the following characters: + - = . , _ : @. Instance tag keys can't contain spaces or /, and can't comprise only . (one period), .. (two periods), or _index.
  • Tag keys and values are case-sensitive.
  • The user: prefix is reserved for Oort use.
You can't terminate, stop, or delete a resource based solely on its tags; you must specify the resource identifier. For example, to delete snapshots that you tagged with a tag key called DeleteMe, you must use the DeleteSnapshots action with the resource identifiers of the snapshots, such as snap-1234567890abcdef0.
When you tag public or shared resources, the tags you assign are available only to your Oort Cloud account; no other Oort account will have access to those tags. For tag-based access control to shared resources, each Oort account must assign its own set of tags to control access to the resource.