Files

Keep uploaded files in your own S3 bucket

Store the files people upload to your published app in your own S3-compatible bucket instead of Ahamo's storage.

On this page

A published app can keep the files people upload in your own S3-compatible bucket, such as Amazon S3, Cloudflare R2, Hetzner Object Storage or MinIO, instead of Ahamo's storage. The app's code does not change. It applies to the published app only; the preview keeps its own storage.

When to use it

  • Your organisation requires files to stay in an account you control.
  • You want to manage retention, replication or costs of uploads yourself.

How to use it

  1. Create a bucket and an access key that may read, write and delete objects in that bucket only.

  2. Open Secrets & variables and choose Production.

  3. Add these settings:

    NameTypeValue
    FILES_S3_BUCKETVariableThe bucket name
    FILES_S3_REGIONVariableFor example eu-central-1
    FILES_S3_ENDPOINTVariableNeeded outside AWS, for example https://fsn1.your-objectstorage.com
    FILES_S3_ACCESS_KEY_IDSecretThe access key ID
    FILES_S3_SECRET_ACCESS_KEYSecretThe secret access key
  4. Publish the app. Production values reach the published app the next time you publish.

New uploads then go to your bucket. Files uploaded before stay readable from Ahamo's storage; they are not copied over. Deleting a file removes it from both places.

You can also ask the build AI, which asks for the two keys in a secure input instead of the chat.

Store this app's uploaded files in our own S3 bucket in eu-central-1.

Plans and limits

The same on every plan. The app's file limits stay the same with your own bucket.

LimitValue
Largest file25 MB, or less where the app sets it
Total storage1 GB
Number of files10,000
Uploads30 a minute per person

Changing production settings needs permission to publish the app.

Troubleshooting

Publishing says the files bucket needs a production secret. One of the five settings is missing or invalid. Add it in Secrets & variables › Production, then publish again.

Uploads fail with a redirect or "files storage answered 301". The region or endpoint doesn't match the bucket. Correct FILES_S3_REGION or FILES_S3_ENDPOINT and publish again.

Saving a key is refused as a variable. Save the access key ID and secret key as Secret, not Variable.

On this page