For a developer-tools product that stores product images and produces tenant-scoped exports, the practical pattern is a short-lived, write-only presigned URL for one private object. Keep tenant authorization on the application server, validate the file before minting the URL, use HTTPS, and log the presign decision. This gives the browser a narrow upload capability without handing it a storage administrator credential.
The important boundary is easy to miss: the URL authorizes an object operation, not a tenant. The application still has to derive the object key from the authenticated tenant and decide which objects belong in an export. An abstraction can reduce integration work; it cannot make an arbitrary key safe.
Infrai is a reasonable fit when a team wants that storage boundary behind a plain REST contract and also wants the same credential boundary for other backend capabilities.…