The S3 API is a widely accepted set of commands for interacting with cloud storage, first made popular by Amazon. By building our software to use this specific set of commands, it can communicate fluently with not just Amazon, but any other storage company that has also adopted them like IBM, Wasabi, and Cloudflare. More examples at the end of this document.
How it works
Go to ADD INTEGRATIONS
Select the OBJECT STORAGE (S3 COMPATIBLE)
Fill out the form and hit SUBMIT
📕 Note: We do not support virtually hosted URLs and have provided both a tooltip and some extra warnings when a user inputs a URL we think may be a virtually hosted URL.
Examples of S3-compatible providers
Our platform can now seamlessly distribute video content to a growing list of providers, including:
Cloudflare R2: Offers zero egress fees, making it ideal for large-scale public distribution.
Backblaze B2 Cloud Storage: A well-regarded, cost-effective storage solution.
Wasabi Hot Cloud Storage: Known for its straightforward, low-cost pricing model with no egress fees.
DigitalOcean Spaces: A simple object storage solution popular with developers.
IBM Cloud Object Storage: An enterprise-grade solution offering advanced features for resilience and security.
Note: Base Media Cloud uses IBM Cloud storage
MinIO: A leading open-source object storage server, perfect for self-hosting on-premise or in a private cloud for ultimate control.
Virtually hosted URLS
While we show warnings, we do not block users from adding virtually hosted URLs outright.
📕 Note: If a user does add a virtually hosted URL, they will still be able to share, but they will experience the unexpected behaviour where the file is added to a new folder within their bucket with the name of their hosted URL.
Example
A path-style URL looks like this:
A path-style URL looks like this:
https://storage-provider.com/<bucket>/<key>
A virtually hosted URL would look like this:
A virtually hosted URL would look like this:
https://<bucket>.storage-provider.com/<key>
In this example, the user would expect clips to be added to:
In this example, the user would expect clips to be added to:
https://<bucket>.storage-provider.com/<key>/{file}
However, the file will be added to:
However, the file will be added to:
https://<bucket>.storage-provider.com/<bucket>/<key>/{file}
(Where the name at the beginning of the virtually hosted URL has been used to create a new bucket).