Latest Blog Posts with 'Release notes' Tag
Cloudback announces the latest addition to its robust suite of features: support for Amazon S3 Object Lock. This enhancement will enable developers to further strengthen the security and protection of their GitHub repository backups stored on Amazon S3.
Amazon S3 Object Lock is a feature that provides an additional layer of security by enabling users to enforce retention policies and prevent the accidental or malicious deletion of their critical data. By integrating this functionality, Cloudback users can now benefit from the highest level of data protection available for their repository backups.
The Cloudback Team is excited to announce the addition of regional storage options for our clients. If you’re utilizing Cloudback Storage for your repositories, you can now select from a variety of storage regions to best suit your needs. See the list of supported storage locations below:
Storage name Region Cloudback US USA East, N. Virginia Cloudback EU EU Central, Amsterdam Cloudback UK EU West, London Cloudback Sidney Asia, Australia, Sidney Cloudback Singapore Asia, Singapore By default, all backups are stored in the Cloudback US storage.
Cloudback provides an easy way to store GitHub repository backups in various storages. And today, we are delighted to announce the support of a new storage - Wasabi Cloud Storage.
Wasabi provides simple, predictable and affordable hot cloud storage for businesses all over the world. It enables organizations to store and instantly access an infinite amount of data at 1/5th the price of the competition with no complex tiers or unpredictable egress fees.
The Cloudback team is happy to announce that an alternative view for Cloudback Dashboard is released. It is a Table View. Using table view it is much easier to navigate through a large number of repositories and trigger on-demand backups. We put the Table View Toggle in the header, so it is always easy to switch to the Table View and back to the Card View. It was a feature request of our client and we are glad to deliver it.
Four months ago, in February 2022, we received a new feature request from our user in our issue tracker. In the request, the user asked us to implement real-time notification support via messengers. As soon as a backup fails or succeeds, he should receive a notification. We found the request extremely useful and prioritized it in the backlog of our project. Despite the delay in delivery, we are happy to say that the work is done and the feature is now available.