Skip to Content
vVozoraDocs
Guides

Object storage

Create S3-compatible buckets on Vozora, connect with the AWS CLI, rclone or s3cmd, make a bucket public, keep old versions, and understand how storage is charged.

Object storage keeps files in buckets that you reach over the S3 protocol, with the same tools and libraries that work with Amazon S3. It suits backups, uploads, logs and anything else that does not need to live on a server's disk. Everything stored is encrypted on our disks and kept in three copies on separate machines.

Creating a bucket

On Object storage, under New bucket, give it a name and a size limit, then press Create bucket. You need credit on your account first.

  • The name is 3 to 63 lowercase letters, digits and hyphens. Names are shared by all customers, so it must be one nobody else is using.
  • The size limit stops the bucket growing past a size you choose, from 1 to 1024 GB. You can change it at any time.

An account can hold up to 20 buckets. Buckets can only be created here, not through the S3 API.

Connecting

The Connection details on the Object storage page show the endpoint and your access key; press Show secret key for the secret. One key works for all of your buckets. Use path-style addressing and any region name.

With the AWS CLI:

aws configure set aws_access_key_id <access-key>
aws configure set aws_secret_access_key <secret-key>
aws --endpoint-url <endpoint> s3 cp backup.tar.gz s3://<bucket>/
aws --endpoint-url <endpoint> s3 ls s3://<bucket>/

With rclone, add a remote of type s3 with provider Ceph, your keys and the endpoint, then:

rclone copy ./photos vozora:<bucket>/photos

With s3cmd:

s3cmd --access_key=<access-key> --secret_key=<secret-key> \
  --host=<endpoint-host> --host-bucket=<endpoint-host> put file.txt s3://<bucket>/

Anyone holding the key can read, change and delete everything in your buckets. If it may have leaked, press Make a new key: the old key stops working at once, and everything that used it needs the new one.

Public buckets

A bucket is private unless you press Make public. A public bucket lets anyone on the internet read and list every object in it, without a key, at <endpoint>/<bucket>/<object>. Press Make private to undo it. Do not make a bucket public if anything in it is confidential.

Versioning

With versioning on, changing or deleting an object keeps the old version, which you can list and restore with your S3 tool. Old versions take space and are charged like any other data until you delete them. Turning versioning off stops new versions being kept; it does not remove existing ones.

Charges

Object storage is in preview and is not charged yet. Prices will be announced before charging starts, and will be shown on the Object storage page. Uploads, downloads and requests will not be charged.

You need credit on your account to create a bucket. If your credit runs out, your buckets keep working for 24 hours. After that, access to them is suspended: nothing is lost, but your key is refused until you add credit. Seven days later, the buckets and everything in them are deleted.

Deleting a bucket

Delete bucket removes the bucket and everything in it at once. This cannot be undone.

Not available yet

Object lock (write-once retention), per-bucket encryption keys, lifecycle rules set from the console, and custom domains for public buckets.

On this page

Vozora is a trading name of Bankside Technology Ltd, company no. 17253446.TermsPrivacysupport@vozora.io