Send Files from Wasabi Object Storage

Use MASV to send files straight from your Wasabi object storage.

You can set up MASV to send files from Wasabi object storage that you’re already using:

  • First, set up your Wasabi bucket
  • Then add a Cloud Integration in the MASV Web app.  

You need to do this setup only once to send files from a Wasabi bucket.

💡 You can also save files to the same Wasabi storage. For example, to save footage that you receive from users then send the same footage to other users, you need to add two separate integrations for the same Wasabi bucket, one for saving and the other for sending. To learn more, see Save Files to Wasabi Object Storage.

Keep in Mind

  • Only a MASV team owner or administrator may add Cloud Integrations. 
  • Only a MASV team owner or administrator may send files from Wasabi. 
  • The files in a package can be either only from your local storage or only from Wasabi. You cannot combine local and Wasabi files in a single package.
  • Wasabi files in a package must come from the same Cloud Integration. You cannot combine files from different Wasabi buckets.

Setting up Your Wasabi Bucket

Before you add a Cloud Integration for your Wasabi bucket, make sure you have an access key with a policy that gives MASV the permission to use the s3:GetObject and s3:ListBucket actions. You can do this in the Wasabi Management Console.

Here’s an example of a policy that gives MASV permission to send any file or folder in a bucket named second-unit:

{
   "Version": "2012-10-17",
   "Statement": [
       {
           "Effect": "Allow",
           "Action": [
               "s3:GetObject",
               "s3:ListBucket"
           ],
           "Resource": [
               "arn:aws:s3:::second-unit",
               "arn:aws:s3:::second-unit/*"
           ]
       }
   ]
}

You can restrict access in your policy for convenience so that it simply provides only relevant folders. Or you can do this for security, to limit access to specific folders. Here’s an example that limits access to the location-a and location-b folders in the second-unit bucket. Notice that the folder names in s3:prefix use the trailing wildcard character (“*”), not the path separator (“/”):

{
   "Version": "2012-10-17",
   "Statement": [
       {
           "Effect": "Allow",
           "Action": [
               "s3:GetObject"
           ],
           "Resource": [
               "arn:aws:s3:::second-unit/location-a/",
               "arn:aws:s3:::second-unit/location-a/*",
               "arn:aws:s3:::second-unit/location-b/",
               "arn:aws:s3:::second-unit/location-b/*"
           ]
       },
       {
           "Effect": "Allow",
           "Action": [
               "s3:ListBucket"
           ],
           "Resource": [
               "arn:aws:s3:::second-unit"
           ],
           "Condition": {
               "StringLike": {
                   "s3:prefix": [
                       "location-a*", "location-b*"
                   ]
               }
           }
       }
   ]
}

Adding a Cloud Integration for Wasabi Object Storage

With your Wasabi bucket ready, you can add a Cloud Integration in the MASV Web app.

To add a Cloud Integration to send from Wasabi:

  1. Log-in or sign-up.
  2. Select Cloud integrations in the left sidebar. 
  3. Select Add Integration then choose Wasabi.
  4. In Connection Name, give the integration a distinctive name.
  5. Fill in Bucket, Access Key ID, and Secret Access Key for your Wasabi bucket. 
  6. Enable Send from Cloud.
  7. Fill in Source Directories with the folders in the bucket that you want to send from. Press Enter to separate each folder.
    This step is optional. But if your policy limits access to specific folders in the bucket, then you must specify at least one of these folders.
  8. Select Connect.
    To start sending files from this Wasabi bucket, see How to Send Files.