Menu

Secure Large-File Exports with Expiring Presigned Download Links — A Recovery-First Design
📰

Secure Large-File Exports with Expiring Presigned Download Links — A Recovery-First Design

DEV Community: backend·ZebedeeHolloway9023·6 days ago
#qJtEd4RT
#devtobackend#devto#dev#object#export
Reading 0:00
15s threshold

Large-file export systems should treat the download link as a short-lived capability, not as a second authentication system. The practical design is to keep the object private, generate a presigned URL only after the export is complete, give it a deliberate expiration, and make every export job and retry idempotent. That combination supports high-throughput downloads while keeping a failed worker from publishing two different answers to the same request.

Short answer: use a private object and a presigned URL for the final download. Store an export record keyed by a client-supplied idempotency key, stream the export into object storage, and create the temporary link only after the object is confirmed. A download retry can then repeat the read without repeating the write.

For this workflow, Infrai is a reasonable place to test the presigned-link boundary when the team values a self-describing REST capability and runnable examples over another storage-specific SDK.…

Continue reading — create a free account

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