you can replace all the call from amazon to wasabi and still only have the data written to the bucket but not read. There  are other calls in the php script to amazon cloudfront I am not sure how to handle. Wasabi sees this issue strictly as the app developers responsibility.  Looking at their exponential growth I do not for-see any reason for them in the near future take on any developers responsibility. I requested information on the ease and procedures for transferring data from amazon to wasahi buckets incase una decides to have a scrlipt written for wasabi storage option.

Wasabi support informed me that there are 3rd party services that can transfer s3.bucket data from amazon to wasabi but it looks like you still have to use a service like cloudfront to deliver the file as a url from the bucket. From what I can understand they are primarly a cloud storage service (s3.bucket)

This is the problem that I was facing. "you can replace all the call from amazon to wasabi and still only have the data written to the bucket but not read." Everything stores in Wasabi, but it shows a broken link in UNA. Also, for this, the github issue is still set to "future".