Wasabi

From the Wasabi API documentation... https://wasabi.com/wp-content/themes/wasabi/docs/API_Guide/index.html#t=topics%2Fapidiff-intro.htm

Wasabi is a cloud-based object storage service for a broad range of applications and use cases. Wasabi is designed for individuals and organizations that require a high-performance, reliable, and secure data stor­age infrastructure at minimal cost.

Wasabi’s object storage service is built to be 100% bit-compatible with Amazon Web Services’ Simple Stor­age Service (AWS S3) and Identity and Access Management (AWS IAM) APIs. This means that any existing AWS S3-compatible application or gateway device will work seamlessly with Wasabi.

In certain cases, Wasabi provides additional functionality relative to AWS S3 (or implements functionality in a different manner than AWS S3). The primary purpose of this guide is to describe these variations in func­tionality as they pertain to using the Wasabi API relative to the AWS S3 and IAM APIs.

Given that Wasabi is built to be 100% bit-compatible with AWS S3, the AWS documentation for S3 and IAM is a complementary resource to the information provided in this guide. The following AWS documents apply to the Wasabi API design:

AWS S3 capabilities referenced in this Guide are based on API version 2006-03-01, described in the Amazon Simple Storage Service API Reference:
http://docs.aws.amazon.com/AmazonS3/latest/API/s3-api.pdf

AWS IAM capabilities referenced in this Guide are based on API version 2010-05-08, described in the AWS Identity and Access Management API Reference:
http://docs.aws.amazon.com/IAM/latest/APIReference/iam-api.pdf

Throughout this guide, for the sake of brevity, the Wasabi API functionality is designated as “Wasabi” and the AWS S3 API functionality is designed as “AWS S3.”

In addition, examples indicate access to buckets created in the East Coast region. Note, however, that you must use URLs based on the region to access buckets. If the bucket was created in the East Coast region, use one of the following:

s3.wasabisys.com
s3.us-east-1.wasabisys.com
s3.us-east-2.wasabisys.com

If the bucket was created in the West Coast region, use:

s3.us-west-1.wasabisys.com

If the bucket was created in Europe region, use:

s3.eu-central-1.wasabisys.com

Using the incorrect URL will enable you to do a GET, but not a PUT or DELETE function.

Refer to the Wasabi Knowledge Base for service URLs for different regions.

Steve, Thanks for the info, but since Wasabi is not a straight drop in replacement for S3, I don't believe PHPR will work with it now.
It's quite a bit less expensive than S3, though S3 is not real expensive, so I would like to be able to eventually use Wasabi with PHPR.

Alan

We are always looking for ways to add more cloud providers but they need to be well known and established like ones we have added already. If Wasabi becomes hugely popular we will definitely add it.