imho. there should be no reason to use s3 in your case. it’s just another protocol to access the same physical layer of storage. except your storage cluster has some special feature only available to s3 objects like remote site replication, encryption or versioning.
in the cloud because of the price. on aws s3 is 3-4 times cheaper than ebs.
i don’t know about the smaller providers but s3 on aws can be configured to replicate your data automatically to another region. and “normal” s3 is always replicated to three AZs. aws s3 is designed to give you 99.999999999% durability of objects.
encryption and versioning is already build into nextcloud. and I don’t know if nextcloud versioning is using s3 versioning or you have everything versioned twice and pay for it double.
since s3 is a network storage you can put your server in the us and your data the eu. (if that’s senseful depends on your use case.)
38tb medical data in the cloud imho s3 is the only way to go. My experience deploying a HIPAA Compliant Nextcloud
yes. and what i don’t know wether the database is the single point of failure here. if you loose the database in a normal setting you might be able to restore it from backup and rescan the file folders. in a worst case scenario you still have the files in folder named after the users. (app data, links and so forth are lost)
but i don’t know how to backup and restore an s3 based nextcloud. ok. s3 needs no backup. pgdump is one of the tools to backup your database. but i have no clue how that fits together. e.g. your database backup is 3h old. how to recover the changes to files in the mean time? are there any addintional metadata in the s3 bucket.
since up to now i didn’t have the need to setup a s3 nextcloud i didn’t dive into that matter. if you want to know you may contact the author the hipaa article or just test it in a save environment. i would be interested if my playbook runs with your s3 backend. feedback would be welcome. support would be limited.