Skip to content

Endpoints and regions

Endpoint Hostname
Global (recommended default) https://s3.dockhive.io
us: United States (Los Angeles) https://s3-us.dockhive.io
virginia: United States (Virginia) https://s3-virginia.dockhive.io
eu: Europe (London) https://s3-eu.dockhive.io
de: Germany (Frankfurt) https://s3-de.dockhive.io
asia: Asia (Singapore) https://s3-asia.dockhive.io
mumbai: India (Mumbai) https://s3-mumbai.dockhive.io
africa: South Africa (Johannesburg) https://s3-africa.dockhive.io
ng: Nigeria (Lagos) https://s3-ng.dockhive.io
abuja: Nigeria (Abuja) https://s3-abuja.dockhive.io

Any endpoint can read and write any bucket. You never have to match an endpoint to a bucket for things to work.

A bucket’s region, chosen when you create it, is its home: the bucket’s regional endpoint is its home endpoint and the fastest place to read it from. If your app runs in one region, create its buckets in the same region and use that regional endpoint. If you don’t know where your users or servers are, use the global endpoint.

Sign requests with the region auto. dockhive and us-east-1 are accepted too, which helps with tools that insist on an AWS region name.

Both styles work. Pick the one your tool or framework expects.

Path style puts the bucket in the path, https://s3.dockhive.io/<bucket>/<key>. It works with every endpoint above. Turn it on in your tool:

Tool Setting
AWS CLI aws configure set s3.addressing_style path
boto3 Config(s3={"addressing_style": "path"})
AWS SDK for JavaScript v3 forcePathStyle: true
Laravel 'use_path_style_endpoint' => true
django-storages AWS_S3_ADDRESSING_STYLE = "path"
Other SDKs look for path style, UsePathStyle or s3ForcePathStyle

Virtual-hosted style puts the bucket in the hostname, https://<bucket>.dockhivestore.xyz/<key>. Use the endpoint https://dockhivestore.xyz and leave your tool on its default (virtual-hosted) addressing. It’s the global endpoint under another name, so any bucket in any region works there. Bucket names with dots (my.bucket) need path style.

Each bucket has an optional setting, Faster reads in this region. When it’s on, Hive Buckets keeps an extra copy of the bucket’s files in its home region, so reads from there are quicker.

That extra copy is billed as storage, which roughly doubles the stored size of that bucket. It’s off by default; turn it on in the bucket’s settings for buckets that are read often and where read latency matters. See Pricing and allowances.

Your files are encrypted and stored across multiple regions, so a whole region can go down without losing data.