Menu

2026 Node.js Private Object Storage Exports: Presigned Links That Expire
📰

2026 Node.js Private Object Storage Exports: Presigned Links That Expire

DEV Community: node·JaggerBlack5781·9 days ago
#v4mRfmvS
#devtonodejs#devto#dev#bucket#storage
Reading 0:00
15s threshold

An export link is a retention policy with a URL attached. For a one-person e-commerce SaaS, I use private object storage, a short-lived presigned GET link, and a bucket lifecycle rule that deletes old files. Permanent public URLs look convenient, but they turn every leaked order export into a long-lived incident.

Short answer: generate the CSV, PDF, or ZIP privately, upload it under a unique key, then presign a GET URL for the customer. Keep the object private and let lifecycle deletion enforce retention.

Why private exports change the design

The useful boundary is the object key, not the download page. A job writes exports/{accountId}/{jobId}.zip ; the API stores that key and an expiry timestamp; the browser receives a URL that grants GET access for a limited window. The export worker never has to make the bucket public.

This is a good fit for invoice PDFs, CSV reports, and ZIP bundles. It is not a fit for static hosting, a forever-public image link, or a public CDN origin.…

Continue reading — create a free account

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