maybe rclone.org is usefull to backup/sync S3 objects. and in combination with restic it should be easy to get a scripted backup of the database and the S3 objects.
that line should be replaced with an rclone command.
but still I would try this in a save environment before release it to production. because I have no idea how to recover a single file. and if recover a hole site works at all.
I even have a playbook for this. but not yet released. because this would be a tricky setup. (that is to say, if something breaks I would have no idea how to recover.)
imho there are too many layer between you and the files on the physical storage device. and you have to rely on a lot of people fixing bugs.
same with “normal” filesystems (hdd, esb, nfs, you-name-it). or?
yeah. sorry. I had only the Armageddon scenario in mind that one aws region goes down. user deleting files or getting attacked from malware or aws taking down its S3 service is of course not covered. (and except armageddon I have seen this all. you are right.)
so “Why should I use this over a file system?”: I wouldn’t use S3 as primary storage. to many layers and unclear how to recover. but as a backup target (restic/rclone) it should be ideal. (replicate/backup everything to aws, digitalocean and scaleway and you should be more than save.)
p.s.: i’m not speaking on behalves of nextcloud prof service. If you bought a subscription and nextcloud is happy to support your setup. ignore my comments.