01 — Overview
Most operational work comes with files: delivery photos, signed contracts, invoices, CSV exports. Connect a bucket and describe how files fit into the tool, and the Bench adds upload fields, previews and download links to the screens that need them. A delivery app gets photo upload on the driver’s screen, and a contracts tool gets a searchable file list with previews.
Files never pass through Chamfer’s storage. Uploads go straight to your bucket with a presigned URL, and downloads use signed links that expire in minutes. Chamfer assumes an IAM role you define, so you control exactly which buckets and prefixes it can touch. The same connection works with S3-compatible stores such as MinIO and Cloudflare R2, including storage inside your own network for teams running Chamfer Onsite. Every upload, download and delete is in the Logbook with the person and the object key.
02 — What you can do
Direct uploads
Files go from the browser to your bucket with presigned URLs, never through Chamfer.
Expiring links
Downloads use signed links that expire in minutes, so shared files don't stay open.
Scoped by prefix
Limit each app to specific buckets or prefixes through the IAM role Chamfer assumes.
03 — FAQ
Before you connect Amazon S3
Do files pass through Chamfer's servers?
How should we grant Chamfer access?
Can we use S3-compatible storage?
Can uploads be limited by file type or size?
04 — Pairs well with
Teams often connect these next
05 — Used in
Give support, finance and ops a safe way to look up and change production records, without console access.
Turn the shared sheet everyone is afraid to touch into an app with validation, roles and a named owner.
Mobile checklists, inspections and dock boards for people who work on their feet, with offline saving and photos.
