Endpoints and regions

There is no single global endpoint: each zone (region) exposes its own URL. Choose the zone where the bucket lives and point your S3 client to that endpoint. The disk technology (HDD, SSD, or NVMe) is chosen when you create the bucket and is served from the same zone endpoint: the URL doesn't change.

URL scheme

The endpoint pattern is the zone code as a subdomain of s3.otterstorage.io:

https://<zona>.s3.otterstorage.io

All zones use mandatory HTTPS and path-style addressing (path-style: endpoint/bucket/objeto), not virtual-host.

Available endpoints

The disk technology and the zone are fixed when you create the bucket and cannot be changed afterward. You can see the exact endpoint of each bucket in the console, under Storage → Endpoints or in the bucket's own detail view.

How to use it

Point any S3-compatible client at the zone endpoint and use its region_name. Example with AWS CLI for Madrid:

aws --endpoint-url https://es-mad-1.s3.otterstorage.io \
    --region eu-mad \
    s3 ls

Or set it in your profile so you don't repeat --endpoint-url in every command (~/.aws/config):

[profile otter]
region = eu-mad
endpoint_url = https://es-mad-1.s3.otterstorage.io

The same endpoint serves HDD, SSD, and NVMe buckets in that zone; you decide the technology when you create each bucket. You'll find full per-tool examples in AWS CLI, MinIO Client, and Rclone.

What's next? Create a bucket in the zone you want, generate your access keys, and start operating with the S3 API.