Object storage

Object storage is S3-compatible storage on Ankra Storage, replicated across the zone's storage hosts. Enabling it in a zone creates a tenant of your own with one access key; buckets live in that tenant, so bucket names never clash with other accounts.

Enabling it#

curl -X POST https://cloud.ankra.app/v1/object-storage \
  -H "Authorization: Bearer $ANKRA_CLOUD_TOKEN" \
  -H 'Content-Type: application/json' \
  -d '{ "zone": "de-fsn1" }'

The answer holds the zone's endpoint and your credentials (access_key_id, secret_access_key). The call is idempotent: enabling an enabled zone returns the current key. Show the key again with GET /v1/object-storage/{zone}/credentials; rotate it with POST /v1/object-storage/{zone}/rotate-keys, after which the old key stops working at once.

Using it#

Any S3 client works. Sign with AWS Signature V4 (any region name) and use path-style URLs, <endpoint>/<bucket>/<key>:

export AWS_ACCESS_KEY_ID=<access_key_id>
export AWS_SECRET_ACCESS_KEY=<secret_access_key>
aws --endpoint-url https://s3.de-fsn1.example s3 mb s3://backups
aws --endpoint-url https://s3.de-fsn1.example s3 cp ./dump.sql.gz s3://backups/

Replace the endpoint with the zone's endpoint from the API. Virtual-hosted-style URLs work where the zone's certificate and DNS cover the wildcard name; path-style always works. When the endpoint's certificate is signed by a private authority, the zone's certificate_authority holds the PEM to pass as --ca-bundle or AWS_CA_BUNDLE.

The endpoint is served by every storage host of the zone behind the zone's gateways, so it stays up when a storage host fails. It is reachable from the internet and from every server with a public address.

Pricing and quota#

Stored data costs €0.006 per GiB-month, billed per started GiB held per hour; an empty tenant costs nothing. Usage is measured every five minutes (used_bytes, object_count). The default quota is 1 TiB per tenant.