File storage

What you get

• File storage for each app, through the S3 API
• Uploads that go straight from the browser to storage
• Size and file type enforced by the store
• Private files, read through short-lived links
• Every upload scanned for viruses
• Usage shown against the plan's allowance

How it works

Add storage: true to the app's whisk.yaml and the app receives its storage address and keys. Any S3 client works, because Whisk uses the S3 API, the common standard for file storage. Each business has its own bucket, and each app writes under its own folder in it.

For uploads from a browser, the app asks Whisk for an upload form. The browser sends the file directly to storage, so large files never pass through the app. A file over the size the app allowed, or of another type, is refused by the store itself.

Files are private, and to show one the app asks Whisk for a link that works for a few minutes. Every upload is checked by virus scanning, and video and audio can be played through video hosting. On the Business plan, files can live in a bucket your business owns.

Example

An engineering firm keeps drawings, site photos and signed reports against each project in its job app. Field staff upload photos from their phones straight to storage, and the office opens them from the project page.

For your coding agent

storage: true

Use any S3 client with path-style addressing and write under WHISK_STORAGE_PREFIX. Browser uploads and every storage setting are described in the environment reference.