Wasabi Permission Requirements for Remote Storage
Written by Mira Beltre
Updated at November 7th, 2024
Table of Contents
Scope
Intended Audience: All Users
This article will show you how to configure the Wasabi permissions requirements necessary
for Remote Storage.
Requirements
- Manager Portal Access
- Wasabi Access
Setting Up Wasabi
- Create a SUB-User in Wasabi.
- Go to Policies>Create Policy via the main dashboard. This is NOT a policy inside the
bucket properties. Make note of the policy name because you will need it later.
- Below is the coding that will give you LIST access to the entire account, give you full
access to the bucket you specify, and prevent access to anything else outside that
bucket
{
"Version": "2012-10-17",
"Statement": [
{
"Sid": "ListMy",
"Effect": "Allow",
"Action": "s3:ListAllMyBuckets",
"Resource": "arn:aws:s3:::*"
},
{
"Sid": "AllowAll-S3ActionsToOwnBucket",
"Effect": "Allow",
"Action": "s3:*",
"Resource": [
"arn:aws:s3:::bucketname",
"arn:aws:s3:::bucketname/*"
]
}
]
}
- After that, click on Users>username>Policies. Find the policy that you just created and
add it the user's account. - Here is an example of the policy directly inside the bucket properties:
{
"Id": "Policy1730147711484",
"Version": "2012-10-17",
"Statement": [
{
"Sid": "Stmt1730147699754",
"Effect": "Allow",
"Principal": {
"AWS": "arn:aws:iam::100000999999:user/useraccountname"
},
"Action": "s3:*",
"Resource": "arn:aws:s3:::bucketname/*"
}
]
}
- To continue setting up Remote Storage for Call Recordings, please visit this doc