Menu

3 Presigned Browser Storage Upload Modes for Large Reports (Tenant Isolation First)
📰

3 Presigned Browser Storage Upload Modes for Large Reports (Tenant Isolation First)

DEV Community: backend·ValdemarBlack3817·about 10 hours ago
#Ik6MFe9M
#devtobackend#devto#dev#report#tenant
Reading 0:00
15s threshold

Short answer: use a presigned single PUT for ordinary generated reports, switch to multipart when retrying the whole file would violate the upload failure budget, and reserve presigned POST for browser forms that need policy-style field constraints. In every case, let the application choose the object key and bind it to the authenticated tenant.

A marketplace report is private output, not anonymous media. The upload method matters, but the tenant boundary matters more: a successful transfer to another customer's key is still a security failure. I treat signing as a narrowly scoped authorization decision, then treat completion as a separate state transition. That distinction comes from the same lesson as OTP delivery: accepting a request doesn't prove that the intended recipient can safely use the result.

Keep it boring.

Govern write authority as tenant-scoped data access

Begin with the maximum report size the product accepts and a connection profile drawn from supported clients.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.