Project storage
Compute isn’t the only thing you can attribute to a project — storage is too. A project can have its own dedicated Wasabi bucket, and that bucket’s warm-storage cost rolls up into the project’s totals alongside its compute.
Buckets across your organization
Section titled “Buckets across your organization”An organization is no longer limited to a single shared bucket. You can now run several, each clearly labelled:
| Bucket type | Scope | Labelled with | Who can delete |
|---|---|---|---|
| Base org storage | Org-wide | — (the org’s default, unlabelled bucket) | Nobody — it’s permanent |
| Project bucket | Org-wide | The project it belongs to | Org admins |
| Personal storage | Just you | — (your private scratch bucket) | You |
Each project gets at most one bucket — a clean one-to-one mapping, so “the glaxo-oncology bucket” is never ambiguous. Your organization’s base bucket stays available for anything that isn’t tied to a project.
You can see all of them — your personal bucket, the org base bucket, and every project bucket — as a card grid on the Connect to Storage page.
Creating a project bucket
Section titled “Creating a project bucket”Org admins provision a project bucket from Connect to Storage:
- Click the + New project bucket card.
- Pick a project from the dropdown. Only projects that don’t already have a bucket appear — each project is limited to one.
- Click Create.
Carolina Cloud provisions a dedicated Wasabi bucket, a scoped IAM user, and access credentials — exactly like a personal bucket, but owned by the org and nicknamed after the project.
Bucket limits
Section titled “Bucket limits”An organization can have up to 5 buckets by default, counting the base org bucket. So out of the box that’s the base bucket plus up to four project buckets. Deleting a project bucket frees the slot immediately. Email hello@carolinacloud.io to raise the limit.
Reading a bucket card
Section titled “Reading a bucket card”Each bucket on the Connect to Storage page is a card showing:
- A scope badge — Personal or Org.
- A project chip (📁) naming the project, for project buckets.
- The display name — “My Storage”, “{Org} Storage”, or the project name.
- Stored size in GB and the monthly cost for that bucket.
- An Access button that opens connection instructions (endpoint, keys, and how to mount it), and a Delete button where applicable.
Connecting to and using a project bucket works the same as any Carolina Cloud bucket — see Carolina Cloud Storage for mounting at ~/ccloud-s3/, the file browser, the aws CLI, and pre-filling instances.
Deleting a project bucket
Section titled “Deleting a project bucket”An admin can delete a project bucket from its card. This permanently removes all objects, the bucket, and its IAM user and keys — it cannot be undone — and frees the project’s one-bucket slot so you could provision a fresh one later.
The base org bucket can’t be deleted (it’s your org’s permanent default), and personal scratch buckets are deleted by their owner, not by admins.
How storage cost is attributed
Section titled “How storage cost is attributed”A project bucket’s warm-storage cost — billed per the standard storage pricing and deletion policy — is attributed to its project at the moment it’s metered, and that attribution is snapshotted into the billing record. So even if you later archive the project or delete the bucket, the spend that already happened stays correctly attributed in the project’s history.
See it all add up on the Projects page.