Skip to content

Objectspaces & S3

An Objectspace is an object storage build on the commonly used S3 protocol. Objectspaces allow you to store large amounts of unstructured blobs of data ( images, videos, text files, HTML files..) or any blob of bytes.

An Objectspace can be connected to one or more Cloudspaces, however, Cloudspaces with overlapping networks cannot connect to the same Objectspace.

When connecting an Objectspace to your cloudspace, it's served over HTTP. You can expose an Objectspace with a reverse-proxy publicly, serving it over HTTPS. You can read more about reverse-proxies in the Ingress Documentation

Before you begin

Objectspaces can only connect to Cloudspaces in the same location. You can manage your buckets (create/delete/edit) in an Objectspace by using a client compatible with S3 such as MinIO or from the whitesky.cloud NV user interface. To access your S3 content, you can use the MinIO client which offers UNIX like commands to manage buckets and objects. Next to MinIO there are tons of other clients and applications that support the S3 protocol.

Creating Objectspaces

Creating an objectspace is a multi-step wizard.

  1. On the left side of the page in the navigation drawer, click Objectspaces. The previously created Objectspaces will be listed.
  2. At the top of the page, click CREATE OBJECTSPACE.
  3. Step 1 — Select location: choose the location where you want to create your Objectspace. A datacenter info table and a map are shown for the selected location. Keep in mind that Objectspaces can only connect to Cloudspaces residing in the same location.
  4. Step 2 — Configuration details: enter your Objectspace's Name, optionally Choose a cloudspace to connect to, and optionally check Make publicly available.
  5. In express/DNS mode, two extra steps appear: a DNS configuration step, then an external network step.
  6. Click CREATE OBJECTSPACE.

Your Objectspace will be created and added to the list of available Objectspaces.

Tip

Checking Make publicly available during creation skips the manual cloudspace/reverse-proxy setup below — see Deploy S3 via the Portal for the manual walkthrough, or Cloudspace DNS for the express, DNS-driven path.

Connecting Objectspaces to Cloudspaces

To connect an existing Objectspace to a Cloudspace

  1. On the left side of the page in the navigation drawer, click Objectspaces. The previously created Objectspaces will be listed.
  2. Click the Objectspace you want to connect to a Cloudspace
  3. At the top of the page, click CONNECT. A list of available Cloudspaces will appear.
  4. Choose a Cloudspace from the list, then click CONNECT.

A message will appear indicating that the Objectspace has been successfully connected to the Cloudspace.

Note: A cloudspace must belong to the same account as the objectspace in order to be connectable.

Accessing Objectspaces with the MinIO Client

In this section, you will learn how to connect to your Objectspace using the MinIO client internally in your connected Cloudspace. If you have exposed you Objectspace using a reverse proxy, keep in mind that you might need to use HTTPS instead of HTTP when your reverse proxy is handling TLS.

  1. Download MinIO client on a VM within your connected Cloudspace.
Function Command Example
To access your Objectspace and give it an alias ./mc alias set <ALIAS> http://<CLOUDSPACE-IP> <ACCESS-KEY> <SECRET>
  • ALIAS is the alias you choose for your Objectspace.
  • You can find CLOUDSPACE-IP, ACCESS-KEY, and SECRET values in the Objectspace details page.
  • CLOUDSPACE-IP is the Cloudspace IP address under the Cloudspace connections tab
./mc alias set mys3 [http://192.168.103.1](http://192.168.103.1/) NVZWGMSDSHQNHJRQHRTO 1QisYhq/mu3jpMOTwpIQi3vstnOuvf86Yt35rLKv
To make a new bucket ./mc mb <ALIAS>/<NEW-BUCKET-NAME> ./mc mb mys3/newbucket
To copy a file to your bucket ./mc cp <FILE-NAME> <ALIAS>/<BUCKET-NAME> ./mc cp myfile.txt mys3/newbucket
To list your buckets ./mc ls <ALIAS> ./mc ls mys3
To list a bucket's content ./mc ls <ALIAS>/<BUCKET-NAME> ./mc ls mys3/newbucket
To remove a bucket and all its content ./mc rb <ALIAS>/<BUCKET-NAME> --force ./mc rb mys3/newbucket --force
To summarize disk usage recursively ./mc du <ALIAS> ./mc du mys3

Tip

If your access key and secret get comprised, you can generate a new pair by clicking RESET CREDENTIALS at the top of the page.

Creating Buckets from whitesky.cloud NV Portal

You can also create a Bucket from the whitesky.cloud NV user interface. The user interface also allows you to set IOPS limitations per bucket.

To create a bucket in the user interface

  1. On the left side of the page in the navigation drawer, click Objectspaces. The previously created Objectspaces will be listed.
  2. Select the Objectspace from the list, and the Objectspace details page will appear.
  3. Select the Buckets tab, then at the top of the page, click ADD BUCKET.
  4. Enter the bucket Name and configure the performance limit in IOPS that is suitable for your application. The portal slider is clamped to 2000–25000 IOPS (default 2000); the API does not enforce a hard range. Optionally check Enable locking to turn on object locking for this bucket.
  5. Click CREATE BUCKET.

The bucket will be added to the list of created buckets.

Managing Buckets from whitesky.cloud NV Portal

You can change the performance limit for a bucket from the bucket details page. Under **Limit (IOPS) ** click and change the value.

To delete a bucket, click DELETE at the top of the bucket details page.

Objectspace Details Page

The details page shows the Name, status, Access key (with a copy icon), Secret (masked), Location and Buffer size, and the notes. The action bar has CONNECT, RESET CREDENTIALS and DELETE. The page has the tabs Cloudspace connections, Buckets, Audits and Roles & permissions.

Buffer Size

On the objectspace details page, the Buffer Size field is editable. Changing it shows a cost-impact confirmation dialog before saving.

Public Domain

When the express/DNS path is used during creation, the objectspace details page shows a Public Domain field with the assigned domain.

Objectspace Notes

On the objectspace details page, you can add, edit, and delete private notes (visible only to you) using the notes icon.

Bulk Bucket Operations

On the Buckets tab, select multiple buckets using row checkboxes. The subtop bar then shows Delete selected buckets and Update selected buckets limit.

Restoring or Permanently Deleting a Bucket from the Recycle Bin

The objectspace details page has no bucket recycle bin tab. Deleting a bucket in the portal is a soft delete: the bucket moves to the Buckets tab of the Recycle Bin, where you can Restore it or delete it permanently.

Deleting an Objectspace

On the objectspace details page, click the DELETE button (enabled when the objectspace status is CREATED). Confirm in the dialog.

Bucket Access Credentials

Beyond the single access key and secret shown on the Objectspace details page, each bucket can have its own set of named access credentials with restricted permissions:

  1. Open the bucket's details page and find the Bucket Access Credentials table.
  2. Click ADD ACCESS KEY, give the credential a name, and choose an access type: read, write, or read + write.
  3. Click CREATE.

The new credential's access key and secret appear in the table (Name / Access type / Access key / Secret key / Actions). Edit a credential's access type, or delete it, from the same table.

Roles & Permissions

An objectspace has its own Roles & permissions tab for granting other users access to it — see Granting access within resources for the full flow.

Audits

An objectspace has its own Audits tab, showing the same request log described in Audits, pre-filtered to this objectspace. See that page for the column and filter reference — everything there applies here, just scoped to one objectspace.

Notice

The Objectspaces server contains code derived from the MinIO Inc. Apache 2.0 licensed MinIO server from commit c4e12dc846ca04c03cab9de69c828b1351631cfc through a gateway implementation towards the proprietary Alba object storage technology developed by GIG.tech NV.