Daily Backups Improved - MikroCloud Roadmap

Backups have been completely revamped for version 4. We now utilize an AWS Transfer Family SFTP cluster for the delivery of backups. This implementation boasts the following features and improvements:

Credentials for uploading backups to the SFTP server are used only once.
Users (MikroTiks) are placed in a chroot jail with permissions that only allow the upload of the backup file; operations such as read, list, delete, etc., are prohibited.
Transfer Family channels backups through Kinesis, enabling enrichment and analysis before storage.
Backups are immutable and have a lifecycle of 12 months.
Backups can be requested by other microservices simply by sending a message to the corresponding SNS topic.

This means it is now significantly easier to request backups and associate metadata with them. For instance, if significant changes to the configuration are detected as reported by the MikroTik's logging, we can trigger a backup and associate those changes with the currently logged-in users.

The pipeline processing also allows us to apply the best practice analyzer on the fly.