Connect MinIO or other S3-compatible storage

quickS3 runs in the cloud, so it has to reach your MinIO server over the internet. Before you start, check that:

• the server has a public address, like https://minio.example.com,
• it uses HTTPS with a valid certificate (not a self-signed one),
• it isn’t only reachable over a VPN or office network.

1. Create an access key

In the MinIO Console, create a user or access key just for quickS3, with a policy covering only the buckets your team needs. It needs to list buckets and read objects. Add write and delete for uploads, and permission to get and set bucket CORS if you want quickS3 to set up browser uploads for you.

2. Add the connection

1. In quickS3, open Connections, select New connection, and pick MinIO.
2. Enter a Name.
3. In Endpoint, enter your server’s full address, like https://minio.example.com.
4. In Region, enter your server’s region. MinIO uses us-east-1 unless you’ve changed it.
5. Paste the Access key ID and Secret access key. Leave Session token empty.
6. If the key can’t list all buckets, type the bucket names into Bucket scopes.
7. Keep CORS updates on and select Connect provider.

Then select Test connection, and after that try an upload, a download, and a delete in a test bucket.

If uploads are blocked by CORS

If the test warns about CORS, allow origin https://quicks3.com on the server with methods GET, HEAD, and PUT, all headers allowed, and ETag exposed. How you do that depends on your MinIO version, so check its documentation for CORS settings. Never make a bucket public to get uploads working.

Other S3-compatible storage

The MinIO option works with most other services that speak the S3 API. quickS3 needs them to support listing, reading, uploading, and deleting objects, multipart uploads for large files, and bucket CORS. Not every “S3-compatible” service supports all of these, so test your own setup with a real upload before your team relies on it.