At the time of writing, Transmit for S3 has been tested with AWS and MinIO. However, there are many other S3 compatible object storage providers, such as Digital Ocean Spaces and Cloudflare R2. Transmit for S3 should in theory work with most of them, although we can’t guarantee support for any specific service. There might be some subtle differences in terms of how they name specific credentials, but they should have relevant equivalents for each of them.
- You’ll need to create a `bucket` for your uploaded files and enter its name here. Since we use a custom proxy to serve them, you don’t need to enable public access. You can usually leave whatever the default settings are, although you’ll need to check to make sure they are suitable.
- They should all have a mechanism for creating an access `key` and `secret` pair, usually you want permissions for this to be restricted to the specific bucket for maximum security.
- You’ll also need to know the `region` code your bucket is in, and its `endpoint` url. Please refer to your provider’s documentation or support for more information on those.
If you would like to request a guide for a specific S3 compatible provider, please contact our support team.