Skip to content
Current

Wasabi: cloud storage and its growth per partner

Paste your Wasabi Account Control API key into Current and bring each partner's Wasabi cloud storage onto the company record: how much each sub-account stores, how it grew over 30 and 90 days, its objects, data out and largest buckets. The sync only reads Wasabi, every 6 hours, and reaches back 90 days.

Updated 6 min read
On this page · 6 sections
  1. Get the API key from Wasabi
  2. Connect it in Current
  3. Map sub-accounts to your companies
  4. How growth is worked out
  5. Where the data shows up
  6. When something looks wrong

Wasabi is cloud object storage that MSPs resell to their partners, each partner as a sub-account under the MSP's own Control Account. Backup tools often write into it. This connector reads that estate into Current every 6 hours and hangs each sub-account off the matching company: how much it stores now, how that grew over the last 30 and 90 days, its objects, the data it sent out on the newest day, its storage quota and its largest buckets. It is a reporting feed: the sync reads Wasabi and changes nothing in it.

Note
What Current keeps, and what it never does
Current stores each sub-account's name, its trial and inactive flags and its quota, one row per sub-account per day for the last 90 days (storage, objects, data in and out, API calls), and the newest day for each bucket. It never reads an invoice, a price or a cost, so no money from Wasabi is ever shown. It never creates, changes or deletes a sub-account, an access key or a bucket: the sync only reaches five read addresses on Wasabi's own API. Partner viewers never see any of it; that is enforced at the database rather than hidden in the interface.

Get the API key from Wasabi

  1. 1
    1 · Ask Wasabi to turn on API access
    The Account Control API is for paid Control Accounts. Ask your Wasabi account manager or Wasabi support to enable it for your Control Account.
  2. 2
    2 · Keep the key Wasabi gives you
    Wasabi issues an API key for the Control Account. It reads every sub-account under it, so one key covers all of your partners. It is not an S3 access key, and an S3 key will not work here.

Connect it in Current

  1. 1
    Open the Wasabi card
    In Current, open Settings › Integrations (Tenant Admins only) and find Wasabi under Backup.
  2. 2
    Paste the key and press Test connection
    Current reads your sub-account list once to prove the key works, and only then stores it, server-side. It only ever sends the key to Wasabi's own API address and never follows a redirect anywhere else.
  3. 3
    Wait for the first sync
    The first sync takes a few minutes. It reads every sub-account, the newest days, and then each sub-account's 90 days of history, up to 25 sub-accounts a run, so a large estate fills in over the next few syncs.

Map sub-accounts to your companies

Current links each sub-account to a company by normalized name when exactly one company matches. Many Wasabi sub-accounts are named by an email address; when the name does not match, Current tries that email's domain against your companies' websites, and only when exactly one company has that website. Free mailbox domains such as gmail.com never match. Anything still unmatched waits on the mapping panel for you to decide, and a mapping you set by hand is never overwritten by a later sync.

How growth is worked out

  • Storage is Wasabi's active storage on the newest day it has computed, summed across the company's sub-accounts. Figures are in decimal TB and GB, the way Wasabi shows them.
  • Growth compares the newest day with the nearest day 30 or 90 days earlier. When the history does not reach back that far yet, the card shows a dash rather than a guess.
  • A sub-account whose newest day is more than four days old reads Not updating, with the date it stopped.
  • If the company also backs up with MSP360, MSP360 reports its own storage figure. The two are never added together, because a backup tool writing into Wasabi would be counted twice.

Where the data shows up

  • The company record's Wasabi card: storage now, the 30 and 90 day growth with a trend line, objects, data out on the newest day, quota used, each sub-account's largest buckets, and any sub-account that stopped updating. It has no action buttons.
  • The service desk ticket, for a ticket whose company maps to a Wasabi sub-account: one short line per sub-account under the company health panel with its storage, buckets, quota and when it last updated.
  • The backup chapter of a Strategic Business Review, as storage and growth figures, never a bucket name.

When something looks wrong

What you seeWhat it means
Wasabi rejected the API keyThe key is wrong, or it is an S3 access key rather than the Account Control API key. Ask Wasabi for the Control Account key, paste it and press Test connection.
A company shows no Wasabi dataIts sub-account is not mapped yet. Check the Unmapped tab on the card.
Growth shows a dashCurrent does not have enough history for that window yet. It reads 90 days on the first sync, so a dash usually means the sub-account itself is newer than the window.
A sub-account reads Not updatingWasabi has not reported a new day for it in more than four days. Check the sub-account in the Wasabi console.
Note
Who can do this, and disconnecting
Connecting, testing, Sync now, mapping and disconnecting are Tenant Admin actions. On the company record, anyone who can open that company sees the Wasabi card. Disconnect stops the sync; the figures already read stay and stop updating, and reconnecting resumes with your mappings intact. Disconnecting doesn't revoke the key at Wasabi; ask Wasabi to retire it. Partner (read-only) viewers never see any of this data; it is blocked at the database, not just hidden.
Was this helpful?
← Previous
SimpleMDM: Apple devices, encryption and check-ins per partner
Next →
NinjaOne SaaS Backup (Dropsuite): Microsoft 365 and Google Workspace backups per partner

Related articles