When a large CSV or PDF export times out in a browser, treat the file and its download URL as two different operational objects. Generate the export asynchronously, upload it completely, validate its size and content type, and only then issue a presigned URL with enough lifetime for the slowest expected connection. If the user retries an old link, mint a fresh URL; do not regenerate an object that is already complete.
Short answer: object storage is a good delivery boundary for large exports, but the timeout investigation belongs in the retry policy, URL expiry window, and object validation path.
Find the boundary before changing the client
A browser's “download failed” message does not identify which stage timed out. Record three state transitions: export generation finished, upload finished, and the link was issued. Keep the expected byte count and content type with the export job.…