The Jet Admin Amazon S3 integration lets your app list, upload, download and delete files in your S3 buckets, driven by the same tables, forms and record actions you already build in Jet. Whether a customer uploads a document, a team member needs to preview a file, or an old object needs archiving, the whole workflow runs inside Jet, and every action is scoped by role and written to the audit log.

That covers what teams build on S3 first: document management consoles that attach files to a record, media libraries for content and marketing teams, and secure file-sharing screens that generate links without handing out AWS credentials. Because Jet reads your own database alongside S3, every screen shows the file next to the customer, project or order it belongs to, and nobody needs console access to work with it.

Key benefits

• File management without AWS access. Let your team upload, preview and delete files from your app, without an AWS console login.
• Files joined to your own data. S3 sits next to the Postgres, MySQL or Mongo you already use, so a file appears beside the record it belongs to.
• Secure sharing. Generate presigned links so customers or partners download private files without an S3 login or a shared account.
• Actions with limits and a record. Deletes and moves run inside your app, scoped by role, held for approval where you need it, and written to the audit log.
• Complete workflows. Tie an upload to everything that follows it: tag the file, update the record, notify the team.
• Organized storage. Create folders, copy and move objects from your app, keeping buckets organized as records change.

How to connect Jet Admin with Amazon S3

1. In AWS, open IAM and create an access key with permissions scoped to the buckets you want to use.
2. In Jet Admin, open your project and add a new resource, or pick Amazon S3 while creating a project.
3. Choose Amazon S3 and enter your access key, secret key and region.
4. Jet loads your buckets and their objects.
5. Add the data sources you want to join with them, for example the records your files belong to.
6. Generate the screens you need, then set role permissions on which buckets and folders each team can access.
7. Add actions and workflows on top: uploads from a form, presigned links for sharing, and automatic tagging on upload.