Create a bucket

A bucket is the container where you store your objects in OtterStorage. Buckets are created and configured from the console, using a guided form. In this guide you'll see how to do it step by step, the naming rules, and the options worth deciding on when you create the bucket.

Before you begin

All you need is an OtterStorage account. When you create a bucket you'll issue its credentials, since access keys are per bucket: each bucket has its own access key + secret key pair, which lets you isolate permissions per project without sharing a global key.

• S3 endpoint: https://es-mad-1.s3.otterstorage.io
• Example region: eu-mad
• Credentials: access key + secret key, issued per bucket.

Good news for your day-to-day: at OtterStorage we don't charge for requests or deletes, so listing, writing, and cleaning up objects adds no operation cost.

Bucket naming rules

The bucket name is part of the address of your objects, so it must follow S3 conventions. Before creating it, make sure your name:

• Uses only lowercase letters, numbers, hyphens (-), and periods (.).
• Contains no spaces, uppercase letters, or underscores (_).
• Is between 3 and 63 characters long.
• Starts and ends with a lowercase letter or a number.
• Is not formatted as an IP address (for example, 192.168.0.1).
• Is unique within your OtterStorage account.

Valid examples: mi-primer-bucket, backups-2026, fotos-eu-mad. Invalid examples: Mi_Bucket (uppercase and underscore), backup prod (space), ab (too short).

Create a bucket from the web console

This is the fastest route if you prefer a visual interface. Sign in to the console and follow these steps.

1. Open the creation form

In the Buckets section, click the Create bucket button. A form will open with the options described below.

2. Bucket name

Enter a name that follows the rules in the previous section. The console validates the name on the spot and warns you if it contains disallowed characters or if it already exists.

3. Choose the region

Select the region where the data will be stored. In this guide we use eu-mad (Madrid, European Union). Choosing the region closest to your users reduces latency and helps you meet data residency requirements.

4. Choose the disk technology

OtterStorage lets you choose the type of storage to match your use case. Choose based on the access pattern and the performance you need:

• HDD — the most economical option. Ideal for backups, archiving, and data you access infrequently.
• SSD — a balance between cost and performance. A good choice for web assets, images, and regularly accessed workloads.
• NVMe — maximum performance and the lowest latency. Designed for hot data, analytics, and speed-sensitive applications.

5. Versioning and Object Lock options

Before confirming, you can enable two protections directly at creation time:

• Versioning: keeps previous copies of each object, protecting you against accidental overwrites and deletes. You can enable or disable it later. More details in lifecycle.
• Object Lock: applies a WORM model (write once, read many) that prevents objects from being deleted or modified before a given date. It must be enabled when you create the bucket and it also enables versioning automatically. See the retention and Object Lock guide.

6. Create the bucket and issue the keys

Click Create. The console will create the bucket and offer to generate the access key pair. Copy the secret key somewhere safe: it is shown only once. With those keys you can now operate the bucket from any S3 client.

What about the command line?

Bucket creation is done from the console, not via the CLI. Because your access keys are scoped to a specific bucket, with AWS CLI, MinIO Client, rclone, or any S3 client you can work with objects (upload, download, list, sync), but not create buckets. Versioning and Object Lock are also chosen in the console when you create the bucket.

Once the bucket is created in the console and you have its keys, connect with the tool you prefer:

# Upload an object to the bucket (already created in the console)
aws --profile otter s3 cp ./datos.zip s3://mi-primer-bucket/

# List the objects in the bucket
aws --profile otter s3 ls s3://mi-primer-bucket/

You'll find the full per-tool configuration in AWS CLI, MinIO Client, and Rclone.

Check that the bucket exists

You'll see the newly created bucket in the Buckets section of the console, along with its usage, region, and technology. From the CLI you can list its contents (since we don't bill for requests, list it as often as you need):

# List the objects in the bucket with AWS CLI
aws --profile otter s3 ls s3://mi-primer-bucket/

# With MinIO Client
mc ls otter/mi-primer-bucket

Summary

• Choose a valid name: lowercase, no spaces, unique, 3 to 63 characters.
• From the console: name, region (eu-mad), technology (HDD/SSD/NVMe), and, if applicable, versioning and Object Lock at creation time.
• Buckets are created in the console, not via the CLI: your keys are scoped to a single bucket and are used to work with objects (upload, list, sync).
• Object Lock can only be enabled when you create the bucket, and it also enables versioning.
• Access keys are per bucket; store the secret key securely. And remember: we don't charge for requests or deletes.

Ready to upload your first object? Continue with the AWS CLI guide or go back to the documentation.