Send Files from Amazon S3 Cloud Storage

Use MASV to send files straight from your Amazon S3 cloud storage.

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

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

You need to do this setup only once to send files from an S3 bucket.

💡You can also save files to the same Amazon S3 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 S3 bucket, one for saving and the other for sending. To learn more, see Save Files to Amazon S3 Cloud 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 S3. 
  • The files in a package can be either only from your local storage or only from S3. You cannot combine local and cloud files in a single package.
  • S3 files in a package must come from the same Cloud Integration. You cannot combine files from different S3 buckets.

Setting up Your S3 Bucket

Before you add a Cloud Integration for your S3 bucket, make sure you have an AWS 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 Amazon Management Console.

Here’s an example of an AWS 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, to simply provide 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 Amazon S3

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

To add a Cloud Integration to send from S3:

  1. Log-in or sign-up
  2. Select Cloud integrations in the left sidebar. 
  3. Select Add Integration then choose Amazon S3.
  4. In Connection Name, give the integration a distinctive name.
  5. Fill in Bucket, Access Key ID, and Secret Access Key for your S3 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 is optional. But if your AWS policy limits access to specific folders in the bucket, then you must specify at least one of these folders.
  8. Select Connect.
  9. To start sending files from this S3 bucket, see How to Send Files Using MASV.