Search Documentation
-
Deployment
-
Administrative Guide
-
- AWS S3 Storage Configuration using Access and Secret keys
- AWS S3 Storage Configuration using IAM role
- Google Storage Configuration using JSON Authentication Key
- Azure Blob/File Storage Configuration using Access Keys
- Backblaze B2 Storage Configuration using Access and Secret Keys
- DigitalOcean Storage Configuration using Access and Secret Keys
- Oracle Storage Configuration using Access and Secret Keys
- Wasabi Storage Configuration
-
-
Tutorials
- Quick Start
- AWS S3 File Sharing With Password Protection
- Google Cloud Storage Integration
- SSO for Admin Console using IAM Identity Center
- SSL and Load balancer for NirvaShare on AWS
- SSO for AdminConsole using Azure ActiveDirectory
- SSL Using Nginx Proxy Manager
- How to Share and Manage File Access from AWS S3, Azure Blob with Salesforce Users
- Configure SSO for Admin Console using Google Workspace as Identity Provider
- Share Azure Blob Files with ActiveDirectory Users using SSO
- S3 File Sharing with Okta Users
-
Troubleshoot
Table of Contents
< All Topics
Wasabi Storage Configuration
Wasabi Object Storage configuration with NirvaShare can be configured using access and secret keys obtained from Wasabi cloud console. In this document, we will look into how to create the access and secret keys and configure the storage with NirvaShare.
Access and Secret keys
In order to configure NirvaShare with Wasabi Storage, Access Keys are required from your Wasabi account. To create Access Keys, follow the steps below.
- Login to Wasabi cloud console as administrator.
- From the left menu list, click on Access Keys
- Click on the button CREATE NEW ACCESS KEY located at the top right corner.
- Select the radio button Root User or Sub-User.
Note: It is advisable to have a separate user for API access and in such case select Sub-User. For this, you may have to create a new user in Wasabi full permissions. - Click on CREATE button.

- Download the Access credentials, store it in safe place.
- The Access Key and Secret Key obtained from this will be needed during the configuration of NirvaShare