This article explains how to set up a Wasabi bucket as storage in GitProtect.
Open the Storages section and click Add storage button.
The Add storage sidebar will appear—use it to enter the name of your new storage in the Add storage name field (step 1), then click the arrow next to the Storage type section (step 2) to expand the list of available storage types.
Scroll down the list and select the Wasabi option.
Copy the access key ID and secret access key from Wasabi, paste the access key ID to the corresponding field, and click Select or add secret access key to open the Password Manager menu and add your copied secret key to your bucket.
Click the Add new button to add your Wasabi secret access key to GitProtect Password Manager. Enter a password name, then enter the secret access key in the New password and Confirm password fields. Click Save to finish.
Next, select the region where your bucket is created and enter the bucket name (the bucket name is the unique identifier of the container where your objects are stored) in the appropriate field.
Ensure that the browsing machine—a device with an active license and the GitProtect worker installed—can access your Wasabi bucket. To use a different device, click Change next to the Browsing machine at the bottom.
Review your settings and click the Save button to add the storage to GitProtect. Refresh the page to see the newly added storage on your storages list.
You can verify your bucket region on the Wasabi platform through the Buckets tab.
This article lists the minimal permissions required for a Wasabi bucket to be used as backup storage in GitProtect. The policies below allow you to add your Wasabi storage to the GitProtect platform, store backup data, and restore it when needed.
Access keys are generated for each Wasabi user account. You can view the list of access keys by logging in to your Wasabi account and navigating to the Access Keys tab.
To create a new user account or edit an existing one, go to the Users tab. In the Policies section, select WasabiReadOnlyAccess and WasabiWriteOnlyAccess, according to your needs.
Remember that immutable storage configuration is available only when creating a new bucket — there is no option to enable it for an existing bucket.
Enabling retention and/or versioning for the bucket may result in additional data being stored. It is recommended that the retention period in GitProtect be longer than the one set for the storage. Otherwise, this may lead to storage overload.
If you want to use immutable storage, the following permissions are required:
It must be added to the Action section, and after the changes, the section should look as shown below:
arn:aws:iam::100000176259:user/xone-storage— Wasabi user
arn:aws:s3:::xopero-test— Wasabi bucket
s3:GetBucketObjectLockConfigurationconfiguration.s3:GetBucketVersioning"Action": [
"s3:ListBucket",
"s3:GetObject",
"s3:PutObject",
"s3:DeleteObject",
"s3:GetBucketVersioning",
            "s3:GetBucketObjectLockConfiguration"
],{
"Version": "2012-10-17",
"Statement": [
{
"Sid": "AllowPublicRead",
"Effect": "Allow",
"Principal": {
"AWS": "arn:aws:iam::100000176259:user/xone-storage"
},
"Action": [
"s3:ListBucket",
"s3:GetObject",
"s3:PutObject",
"s3:DeleteObject",
"s3:GetBucketVersioning",
"s3:GetBucketObjectLockConfiguration"
],
"Resource": [
"arn:aws:s3:::xopero-test/*",
"arn:aws:s3:::xopero-test"
]
}
]
}
