For a healthtech service, a large CSV or PDF export download can time out even after object storage reports a completed upload: a slow browser may outlive its presigned URL, while the signed clinical document still has to remain tenant-isolated and disappear on its retention deadline.
Short answer: generate each large CSV or PDF asynchronously into a tenant-scoped private object, validate its headers, and only then issue a presigned URL with enough lifetime for the slowest expected download; on retry, mint a fresh URL and let the client resume where its storage provider supports range requests.
This is an operating-cost decision, not a unit-price contest. The bill includes export compute, object storage, support contacts, retry traffic, and the engineering time required to integrate and observe the path.…