
Several standard implementations of the S3 API have significant differences between them in compliance with the S3 standard. To be fair, most vendors have done a decent job implementing the core components of the S3 API, but it's imperative to know if they cover what you need that isn’t core.

And generally, you will always have to rewrite some stuff to make things work, no matter how “100%” compatible the vendor’s S3 API is.įor example, looking at one specific aspect of the S3 API, Amazon S3 has plenty of settings on the S3 Multi-part Upload configuration that we find are rarely consistent with anyone else’s implementation of the S3 API. Want pre-signed URLs for your customers to upload straight to your storage safely? Unfortunately, you’re not in luck with Wasabi, or Backblaze B2. In some cases, saving on the total cost of storage makes it worth it. To use a non-native storage service, you’ll have to pay for the additional egress and engineering time it takes to integrate. Integration with other services is the most significant advantage of the big cloud storage providers like AWS, Azure, or Google Cloud Platform.Īre you doing anything other than storing and serving files? Are you analyzing your unstructured data with Amazon Athena or Google BigQuery? Low-cost providers might end up being more expensive. Gotchas of Every Single Low-Cost Object Storage Provider



Vendors are Promising 80%+ Savings on Object Storage Compared To Amazon S3.
