Optimal Methods to Manage Wasabi Accounts With Wasabi Account Control Manager

Updated on 10 Jun 2024
2 Minutes to read

Article summary

Did you find this summary helpful?

Thank you for your feedback

What are the optimal methods for an MSP/CSP partner to manage Wasabi accounts?

For Wasabi partners who want to resell Wasabi Hot Cloud Storage as part of a solution offer, it is important to understand the optimal methods for provisioning and usage monitoring of Wasabi accounts associated with the end user customers served by Wasabi partners. The recommended method for this is to use the Wasabi Account Control Manager (WACM) or the Wasabi Account Control API (WACA). Other non-recommended methods are discussed in this article.

Method	Pros	Cons	Notes
#1: Using WACM to provision separate Wasabi sub-accounts for each customer	Provides a hosted platform and graphic user interface for setting up and managing accounts Provides usage information via an invoice for each end customer Allows a single payment method to be used for all sub-accounts	None	Each Wasabi sub-account has a TB monthly minimum Reach out to Wasabi Sales for pricing information
#2: Using WACA to provision separate Wasabi sub-accounts for each customer	Provides a programmatic method (via API) of setting up and monitoring accounts Provides usage information via an invoice for each end customer Allows a single payment method to be used for all sub-accounts	Requires that the partner develop provisioning and usage monitoring code to interface with WACA (not all partners may want to do this work)	Using WACA capability assumes the partner is capable of developing the appropriate application logic to use the API (if a partner is not capable of developing the appropriate application logic, the use of WACM is recommended) Each Wasabi sub-account has a TB monthly minimum Reach out to Wasabi Sales for pricing information

Method #1: Using WACM

This method involves the use of a Wasabi-hosted platform for setting up and managing Wasabi sub-accounts.

Method #2: Using Separate Wasabi Accounts for Each Customer (Provisioning via WACA)

This method involves the partner building application logic in their customer portal that allows them to provision and monitor the usage of Wasabi accounts via Wasabi’s REST-based Account Control API (WACA). As part of using the WACA, the partner establishes a control account with Wasabi. The partner then uses this control account to provision Wasabi sub-accounts that are associated with end users. If needed, Wasabi can provide a partner test sandbox for use by the partner in developing the application logic on the partner’s portal. Once the partner successfully integrates with the partner sandbox, a control account on the production Wasabi service is provided.

The creation of the control account and general support of WACA integration efforts is done in coordination with Wasabi Partner Engineering Support.

Other Methods Not Recommended by Wasabi

Using a Single Folder for Each Customer

While it is technically possible to use a single folder for each customer, this method is not recommended because:

Wasabi does not provide per-folder utilization information and
Complex access control policies are required to ensure that customer 1 can only access their folder data and not the folder data of customer 2, for example.

Using a Single Bucket for Each Customer

While it is technically possible to use a single bucket for each customer, this method is not recommended because:

Wasabi does not provide easy-to-use bucket utilization information and
Complex access control policies are required to ensure that customer 1 can only access their bucket data and not the bucket data of customer 2, for example.

What's Next

5—Accessing and Exporting Consumption Data With Wasabi Account Control Manager

Table of contents

Method #1: Using WACM
Method #2: Using Separate Wasabi Accounts for Each Customer (Provisioning via WACA)
Other Methods Not Recommended by Wasabi