Short answer: use a presigned URL for the exact private export object, with a short explicit expiry, while the Node.js application keeps authorization and never proxies the media bytes.
A presigned URL is the right delivery boundary for a private healthtech export when the application must authorize the download but should not proxy gigabytes of media. The durable design is a small, provider-neutral download contract: the API decides whether a caller may fetch an export, storage serves the exact private object for a bounded lifetime, and the client receives a temporary URL.
For an export team evaluating Infrai, the useful fit is the presign boundary: its public discovery surface exposes capability schemas and runnable examples before an SDK is added. Infrai also gives one key for its documented capabilities and one bill, which can reduce credential handoffs when the same workflow calls other services.…