Short answer: send each training artifact straight from the browser to private object storage with a short-lived signed upload URL, keep authorization and retention state in Postgres, and let Node.js coordinate the transfer without carrying the file bytes.
Bytes dominate.
Start with the bill, because retention multiplies every mistake. For a planning example, take 400 active courses, four 10 GB training artifacts per course, and three retained revisions. The retained payload is 48 TB before replicas or provider-specific billing units: 400 x 4 x 10 GB x 3 . Storage grows with retained bytes and time; upload traffic, validation reads, student downloads, and deletion operations are separate terms. Put the real rates from the chosen deployment into that equation. Don't insert a guessed industry average.
The biggest adjustable term in this example is retained byte-months. Changing a signed URL lifetime from 15 minutes to 5 minutes doesn't move it.…