Backup system - better integration with Cloudflare R2 object storage
Currently, we are able to configure various options for our backup storage. One of these options is S3-compatible, which largely adheres to S3 standards.
Some time ago, Cloudflare introduced R2, an object storage solution that is S3-compatible to a certain extent. I have tested it, and it works well with ISPManager, but only if we configure full access to our buckets within R2 (granting admin access rights).
When configuring API tokens for buckets, we have these four options on the R2 side (Permissions specify the R2 Storage permission type for this token):
ISPManager, with its current implementation of the S3-compatible option, only works if we use the Admin Read & Write permissions. However, this gives ISPManager access to all the buckets and allows it to manage them. From a security perspective, this is not acceptable, as we do not want to give access to any other bucket than the one dedicated to our backups.
If we use the Object Read & Write permissions for our token and select which bucket should be accessible, ISPManager will not work with such permissions. It still requires creating a new bucket even if we set the bucket name in the URL path, but a token with Object Read & Write permission does not allow this.
It would be great to either:
I believe having a proper implementation for R2 within ISPManager would be beneficial, as Cloudflare's offerings are often much more cost-effective than others and may become more popular soon.
08.12.2023 10:47
Hello,
Thanks for your feedback! This year is planned to improve the backup system. While doing this we will also solve the issue. We'll most likely go the way - update the current S3-compatible implementation.
09.01.2024 05:48