Short answer: keep receipt originals in private object storage, let FastAPI issue narrow signed upload and download grants, and move bytes directly between the browser and the correct US or EU storage region.
The deciding constraint is large-file throughput. FastAPI should authorize a transfer, record its state, and verify its completion; it shouldn't relay a 600 MB scan through an application worker. The file is evidence, so an HTTP success from storage is only one event in a longer chain: upload, verification, malware screening, receipt processing, retention, and deletion all need distinct states.
This is an architecture decision record for a media application that processes receipts while retaining each original for audit. It is deliberately narrower than a generic object-storage roundup. The hard part isn't generating a URL.…