Menu

Direct Image Upload to Object Storage Using JS in Browser (5 MiB Tenant Boundaries)
📰

Direct Image Upload to Object Storage Using JS in Browser (5 MiB Tenant Boundaries)

DEV Community: javascript·BarnabyVance6852·11 days ago
#2rdfCMpa
#devtojavascript#devto#dev#intent#account
Reading 0:00
15s threshold

Short answer: Use a short-lived signed request from an authenticated control plane, send the image directly from browser JavaScript to object storage, and verify ownership before publishing the avatar.

Fintech avatar ingestion with a browser-issued signed request is a boundary problem before it is a JavaScript problem. The browser sends bytes to storage; a Node.js control-plane endpoint authenticates the account, fixes the key prefix and content limits, and records a pending intent. That split avoids routing image bytes through the application, but it does not create tenant isolation by itself. Isolation comes from authorization, an unguessable key, and a post-upload check before the avatar becomes visible.

My rule is simple: the signer owns policy, storage owns bytes, and the browser owns neither tenant identity nor object naming.…

Continue reading — create a free account

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