Just to throw it out there, I use wasabi for s3 storage and the pricing is good. But! be careful too, as previous I had a WHM server that was backing up about 350GB a day to wasabi. Not an issue. Total cost of storage also wasn't an issue. Even ingress was free and not the issue.
Creating and deleting files stored for less then 90 days (I think it was 90) came with a delete tax, at 14TB/month transfer, that deleting tax (per my retention policy) was causing a bill of $170 a month.
So just look out for this aspect of object storage. As Adam has said their s3 implementation will be sending full server backups as tar files, and nothing incremental. (as I was doing in my scenario above) Therefore it would be pretty easy to fall into this same pitfall.
I would love to see an option from enhance team that could maybe handle an s3 backup of the server itself, not site/email data, nothing else, just a pure server recovery feature. I.e. I rebuild the hardware, then when going to do the script to add the server to the estate. Have another option for recovery. i.e. it's same name, so lookup it's id, and use that, install and then allow an s3/or enhance backup server feature to pull any locally needed files to complete that setup of that server. Backups of sites/email can then be restored to it in a normal fashion.
Features, Requirements, Roles, Scaling, Security. It's like making a cake, there's plenty of recipe's even for a single type of cake.
+1 for keeping some features high priority. However, remember a team of engineers and programmers come at varying levels, so whilst your seniors, leads and architects are working out X or Y backup/security feature, some of the others on the team, building their skills ect... can be working on the more "supplemental" pieces. So there will always be a balance of features within a given update and there's only so much the core programmers can output in a given month.
Hat tip to enhance team as we can see from the release notes, there's not many patches added after any given release, which speaks to the quality of an update. Likewise there comes a point where edge cases will materialise in the wild that couldn't be accounted for inhouse and the programmers will get pulled sideways to address these which might take a hit on the next release of updates.
I am just very grateful we can have this discourse between ourselves and with the input of the enhance team.
