Skip to content
Portal

Objectspace Buckets & Access Management

Objectspace buckets are containers for storing objects (files, backups, disk images) in S3-compatible storage. This page covers bucket creation, deletion, and access control.

For general Objectspace creation and management, see Objectspaces & S3.

Creating a Bucket

  1. Navigate to the Objectspaces section.
  2. Click the Objectspace that will host the bucket.
  3. Select the Buckets tab.
  4. Click ADD BUCKET at the top of the page.
  5. Fill in the Name (must be unique within the objectspace).
  6. (Optional) Set the Limit (IOPS) for the bucket to control throughput (default 2000), and check Enable locking to turn on object locking for this bucket.
  7. Click CREATE BUCKET.

The bucket is created in the selected Objectspace and is immediately available for storing objects.

Bucket Lifecycle

Deleting a Bucket

  1. Navigate to the Buckets tab of the Objectspace.
  2. Select the bucket.
  3. Click DELETE.
  4. Confirm the deletion. The dialog has no reason field, and the bucket is soft-deleted: it moves to the Recycle Bin.

Note: A bucket with object locking enabled must be emptied before it can be deleted.

Access Management

There is no customer-wide "S3 credentials" section — access credentials are scoped to an Objectspace or to an individual bucket within it.

  • Objectspace-level: a single access key and secret, shown on the Objectspace details page. Click RESET CREDENTIALS there to rotate them.
  • Bucket-level: each bucket can additionally have its own set of named credentials, each with a coarse access type — read, write, or read + write — created from the bucket's Bucket Access Credentials table via ADD ACCESS KEY. There's no finer-grained, prefix-scoped policy mechanism (e.g. restricting a credential to one folder within a bucket).

Using Credentials to Access a Bucket

Once you have credentials (from either level above), use any S3-compatible client:

AWS CLI: 

export AWS_ACCESS_KEY_ID=your-access-key-id
export AWS_SECRET_ACCESS_KEY=your-secret-key
export AWS_ENDPOINT_URL=https://your-objectspace-endpoint

# List buckets
aws s3 ls --endpoint-url $AWS_ENDPOINT_URL

# List objects in a bucket
aws s3 ls s3://my-bucket/ --endpoint-url $AWS_ENDPOINT_URL

# Upload a file
aws s3 cp myfile.txt s3://my-bucket/myfile.txt --endpoint-url $AWS_ENDPOINT_URL

Python (boto3): 

import boto3

s3 = boto3.client(
    's3',
    endpoint_url='https://your-objectspace-endpoint',
    aws_access_key_id='your-access-key-id',
    aws_secret_access_key='your-secret-key',
)

# List objects
response = s3.list_objects_v2(Bucket='my-bucket')

# Upload a file
s3.upload_file('myfile.txt', 'my-bucket', 'myfile.txt')

Making a Bucket Publicly Reachable

There's no per-bucket public/private toggle. Public access works the same way as for the rest of an Objectspace: expose it through a reverse proxy on a connected cloudspace (see Objectspaces & S3), or check Make publicly available when creating the Objectspace for the DNS-driven express path (see Cloudspace DNS). This applies at the Objectspace level, not to individual buckets.

Bucket Resource Information

The bucket list shows Name and Limit (IOPS). Once a bucket is deleted, it moves to the Recycle Bin, whose list additionally shows the parent Objectspace, Location, and Deletion Time — see Recycle Bin.

Note

Lifecycle rules (for example, auto-expiring objects after a set time) exist as a backend API but have no portal interface yet — there's no way to configure them from the UI today.

Next Steps