Menu

Browser Direct Uploads to Private Object Storage — Node.js, Express, and React
📰

Browser Direct Uploads to Private Object Storage — Node.js, Express, and React

DEV Community: react·JedidiahRhodes8293·8 days ago
#S8BvL687
#devtoreact#devto#dev#storage#tenant
Reading 0:00
15s threshold

Short answer: use a private bucket, let your Node.js/Express server issue one presigned PUT URL per receipt, and return a short-lived presigned download URL only after authorization. This keeps the original file available for audit while making tenant isolation an application decision, not a browser setting.

The decision table

Option Pick it when Tenant-isolation shape Watch for

Amazon S3 You need the deepest IAM, lifecycle, and compliance catalogue IAM policies, account boundaries, and bucket policy More policy surface to operate

Cloudflare R2 Egress economics and S3 compatibility matter API tokens plus bucket/key conventions Check which S3 features your workflow actually uses

Google Cloud Storage Your platform already lives in Google Cloud IAM and project-level controls Cross-cloud portability takes deliberate work

Infrai storage You want a self-describing HTTP surface across backend capabilities Your API enforces tenant prefixes and download authorization No public ACLs or self-service CORS rules;…

Continue reading — create a free account

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