Integrations
/
S3 Compatible

Store files with S3-compatible storage

Databases
Store and access data with S3-compatible storage
Overview

The S3 Compatible integration connects Jet Admin to any storage provider that speaks the S3 API — including MinIO, Wasabi, Backblaze B2, and self-hosted object stores — not just Amazon S3 itself. Point Jet Admin at your endpoint and bucket, and files uploaded through a Jet form or table are stored exactly where your infrastructure already expects them.

Because the connection is provider-agnostic, you can join stored files to records in your own database, scope access by role, and require an approval step before a file is exposed to end users — the same controls you'd apply to any other data source in Jet Admin. If you ever change providers, you can repoint the endpoint without reworking your forms or apps.

What you can do
List objects
Pull the contents of a bucket into a Jet table with search and pagination, filtered by prefix or file type.
Upload file
Upload a file from a Jet form straight into your S3-compatible bucket, whichever provider hosts it.
Download file
Pull a file into your app for preview, or pass it along in a workflow such as an approval or an export.
Delete object
Remove a file when a record is deleted or a document is replaced. Put it behind an approval step so it cannot happen on a single click.
Generate presigned URL
Create a temporary, secured link to a private file, so a customer or partner can download it without a login.
Use Cases
Scenario
What it looks like
Bring your own S3-compatible bucket
Connect any S3-compatible provider, from MinIO to Wasabi to Backblaze B2, to Jet Admin without vendor lock-in.
Media library for a Jet app
Store and serve images, videos and documents from your existing bucket inside a Jet Admin interface.
Switch storage providers without rework
Swap the underlying S3-compatible provider without changing how your Jet app reads or writes files.

Key benefits

  • Works with any S3-compatible provider. Connect MinIO, Wasabi, Backblaze B2, or a self-hosted object store using the same integration.
  • No vendor lock-in. Swap providers later by updating the endpoint, without rebuilding your Jet Admin app.
  • Files tied to your data. Link stored objects to records in your own database instead of managing a bucket separately.
  • Full access control. Use roles and an approval step to decide who can upload or view files.

How to connect Jet Admin with S3 Compatible storage

  1. In Jet Admin, go to Data Sources and select S3 Compatible.
  2. Enter your provider's endpoint URL, access key, and secret key.
  3. Specify the bucket (and region, if your provider requires one) you want Jet Admin to use.
  4. Test the connection to confirm Jet Admin can read and write to the bucket.
  5. Add a File field to a Jet form or table and select the S3 Compatible source to start uploading and managing files.