Skip to main content

Manage buckets and users

Our customer interface Cockpit allows you to create and manage our "Object Storage" product in a self service fashion.

Terms​

Bucket: A bucket represents a container in which you store your data.

Bucket User: Each user created can be granted access to multiple buckets. Each user has an "access key" and a "secret key". This information is required to log in to the system.

Which "Location" should I choose?​

The choice of the "Location" plays an important role if you want to use your bucket for backups. In this case, it is advisable not to create the bucket in the same data center where your systems are located.

On the other hand, if you want to mount the bucket directly on your systems via a network protocol, it would be advisable to choose the "Location" where your systems are located due to lower latencies.

Create user​

You create users under the Bucket Users tab in our Self-Service Portal.

A user can only be granted access to those buckets that have been created in the same "Location".

Create buckets​

You create buckets under the Bucket tab in our Self-Service Portal. Mandatorily, you must specify a unique name.

The following settings are optional:

Versioning: The files are stored versioned. This takes up more storage space, but protects the data from being overwritten. Public readable: The bucket's data can be accessed or downloaded without authentication. Public list: A list of the files in the bucket can be retrieved using the specified public URL. The option requires that "Public readable" has been enabled. Location: Defines the location of the data.

All options, except for "Location", can be adjusted later as needed.

After saving, you can specify which users should have access to the new bucket. Users can be granted read access or write access.

Only users from the same "Location" where the bucket was created can be selected.

How do I access my buckets?​

Buckets can be accessed via the S3-compatible API or via HTTP. Various open source tools and framework integrations are available for this purpose.

Pricing​

per GBv1v2
Storage0,09 CHF0,03 CHF
Outbound traffic0,02 CHF0,02 CHF

The storage space is billed per started gigabyte. If you need more than 1 TB of storage, please contact us to adjust your quota.

Bucket v2 Migration​

We are introducing a new and greatly improved S3/Object Storage product, as the previous solution could not fulfil the high demands that both we and our customers place on performance and accessibility. This new version is simply called v2, while the existing solution will be referred to as v1 in Cockpit and documentation.

In order to smoothly migrate from v1 to v2 buckets we offer an automated sync between v1 and v2 buckets. To start syncing two buckets, head to Products, Object Storage and then Migration in Cockpit. There you can choose source and target bucket and configure the interval how often the sync will run. After creation it will execute an initial sync to copy all the data and then it will schedule regular resyncs according to the configured interval.

The full migration process will vary depending on how you use object storage but the most common case should work something like this:

  1. Create a v2 destination bucket.
  2. Create a v2 user and assign write permissions on the destination bucket.
  3. Create a Migration and select the source bucket and user and the newly created destination bucket and user.
  4. Wait until the initial sync completes.
  5. Stop application(s) (if any) that write to the source bucket.
  6. Wait until the next resync has completed.
  7. Configure the application(s) to connect to the new destination bucket.
  8. Stop the sync process by deleting the Migration.
  9. Delete the source bucket and user once you are confident all the data has been migrated to the new bucket and nothing is depending on it anymore.

Besides that, there are some differences in configuring bucket access. These differences are documented here.