Buckets and Access Keys

Buckets are the top-level containers for objects in Sliplane Object Storage. Access keys are credentials that allow applications and S3 clients to access one bucket.

Buckets

Buckets belong to your team. Any team member with access to Object Storage can manage the team’s buckets in the Sliplane dashboard.

A bucket has a globally unique name, a region, an endpoint, and a status.

You can store any number of objects in a bucket, as long as your team stays within the documented limits.

Versioning

Versioning keeps previous versions of objects when they are overwritten or deleted.

Enable versioning when you want protection against accidental overwrites or deletes. Keep in mind that stored versions count toward your total Object Storage usage.

Object locking

Object locking prevents objects from being deleted or overwritten for a retention period.

Object locking also enables versioning. Use it for workloads that need stronger protection against accidental or unwanted changes.

Access keys

Each access key is scoped to exactly one bucket.

An access key can:

read and write objects in its bucket
list objects in its bucket
list buckets and see whether other buckets exist in the same team

An access key cannot read, write, or delete objects in any other bucket.

Deleting access keys

Delete an access key when it is no longer used or if you think it may have been exposed.

Deleting an access key immediately prevents clients from using that key to access the bucket.

Deleting buckets

When you delete a bucket, Sliplane schedules it for deletion with a 24-hour grace period.

After the grace period, the bucket and its access keys are removed.

API

The Sliplane API supports listing, creating, and deleting buckets, as well as listing, creating, and deleting bucket access keys.

Open the API documentation for the full request and response schema.