Wasabi S3 offers enterprise cloud blob storage at an affordable price. Only 5 years ago talking about cloud was something everybody was aiming for but also a nice to have. In particular with the businesses, it has become even more critical considering the nature of their data. The fact that valuable information is sitting into someone else’s infrastructure was making certain admins a bit skeptical. A few years forward it is not a matter of “if”. It is just a matter of “when”. Due to the digital transformation and other new waves embracing different industries it has become a must to leverage cloud resources. Be it for extending “local resources”, or for competitive advantage or even capability of the business more and more Apps now benefit from cloud resources. Cloud Compute in its various forms (native workloads, apps and containers) and Cloud Storage.
Wasabi S3 offers an interesting option for all those customer who wants to benefit from cloud resources and in particular for object or blob storage. It is offered for a fraction of the price when compared to other solutions in the market. The ideal companion not just for long term storage (for example backups) but also for modern Apps who leverage the cloud storage. It features no in/egress charges and provides data redundancy, durability (up to 11x9s) together with the immutable storage option.
In this quick article series the focus is to setup a trial account that will be used in conjunction with Veeam Backup & Replication to store long term backup. the idea is to capture all the main steps from start to finish. In this case how to create a Wasabi S3 free account for a trial. Later on also the ability to explore content directly from the cloud for granular restores.
How to setup Wasabi S3 account
First things first: creating a trial account is a straight forward process and requires no credit card. Trial provides access for 30 days for a maximum of 1 TB. Once the account is created the next step is to create a bucket. Wasabi S3 follows the same principles of S3 protocol available with AWS as well.
Everything is wizard driven from the web browser and very handy. Of course it is also possible to use command line as covered in a dedicated article. Step 1 is to provide a name for the bucket and the region. Currently US (Virginia and Oregon) and Central Europe (Amsterdam) are supported.
At the time of the creation of the account it is also possible to see the name of the regions. In this instance “eu-central-1” is used.
In the properties the option to enable the versioning and logging. These can also be changed at later stage.
A final step to review and amend changes. Interestingly also the option to enable Logging and Versioning. Whereas the first one is very useful troubleshooting scenarios the latter allows an extra level of protection when accidental deletions or changes occur.
At this point the first bucket is created As a next step is to create the wasabi S3 folders where the application will store and read the data.
In this example several folders will be created to store weekly, monthly and yearly backups.
As a next step the option to create a user or better a service account which will have access to the specific bucket.
For each user created there is also the option to specify the access type. By default is “console” and “API based” can be enabled as well.
When multiple users need to access the same bucket it is possible to add these to groups and grant specific permissions to the group directly.
Permissions are defined by policies. The wizard already shows the default ones and it is also possible to create custom ones based on requirements.
And a final step to review and commit the options.
At this point everything is ready for this user and eventually create a new one with different level of access and settings.
For the created users it is also possible to define the security criteria for the passwords.
As a last step it is now time to create the Access Key. The status and the creation of the keys can be controlled by the wasabi S3 console.
The wizard will create an Access and Secret Key. These would be the information to provide when configuring client apps to access the pertinent bucket. In addition it is necessary to also provide the correct name of the region where the bucket is located. More on this in the next article when configuring the blob storage repository in Veeam Backup & Replication.
Add Comment