Wasabi Customer Managed Storage
Configure Wasabi as a cost-effective, high-performance storage solution for your GitHub repository backups in Cloudback, with S3-compatible API and no egress fees.
Last updated
Was this helpful?
Configure Wasabi as a cost-effective, high-performance storage solution for your GitHub repository backups in Cloudback, with S3-compatible API and no egress fees.
Last updated
Was this helpful?
Wasabi is a public cloud object storage service that is 1/5th the price of Amazon S3 and faster than the competition with no fees for egress or API requests. Wasabi provides 11 x 9s of data durability, high system availability, and support for immutable storage buckets. Wasabi is fully compatible with the Amazon S3 API with support for hundreds of S3-compatible storage applications and has been certified for compliance with enterprise security and privacy standards.
To set up Wasabi Bucket as a storage for your backups, follow the steps below.
Type a storage name in the Storage name field. Use a name that will help you identify this storage in the future.
Select Wasabi S3 from a Storage Provider dropdown:
Choose the settings for the storage:
Deduplication type - enable or disable data deduplication. For more details, please refer to the Deduplication documentation
Archive type - enable or disable archive password protection. For more details, please refer to the Password-Protected Backups documentation
Archive name pattern - configure the archive name pattern, which is used to generate the name of the backup archive. For more details, please refer to the Archive Name Pattern documentation
To upload backups to Wasabi, you need to have a bucket. You can find more information on how to create a bucket in the Wasabi documentation. You can use existing bucket if you already have one.
In the Step 1, provide the Bucket Region and Bucket ARN. Buckets from different regions have different service URLs, so it is important to select the correct region so that Cloudback can upload backups to your bucket.
In the Step 2, provide the Access Key ID and Access Key Secret. These credentials are used to authenticate Cloudback with Wasabi. You can find more information on how to create Access Key in the Wasabi documentation.
In the Step 3 field you can provide additional HTTP headers to be used when uploading backups to the bucket. The headers can be used to set the S3 Object Lock or S3 Object Tagging headers.
Open the Cloudback Dashboard
Navigate to the Storages page by clicking on the Storages link in the left-side navigation pane
Click on the + New storage button:
Click on Save button to save the new storage. You can also use a Test button to check if the storage is configured correctly. After saving the storage, you can use it for storing backups of your repositories.
All storage settings can be changed later in the Storages page. To edit the storage settings, click on the Edit button next to the storage you want to edit.
You can change the storage for a particular repository in the Repository Details page. Also, you can assign it to multiple repositories through the Bulk Operations.
