A generated gaming report may be hundreds of megabytes, so routing every authenticated download through the application turns authorization into a throughput bottleneck. Short answer: keep each report private in object storage, save its exact object key in the application database, verify that object, and issue a short-lived presigned GET URL; treat a 403 as a signing-input problem before touching public access settings.
This split keeps the control plane in the application and puts large-file transfer on storage. It also gives the audit trail a useful shape: customer, report ID, immutable object key, authorization decision, issuance time, expiry, and request ID belong in the ledger; the signed URL itself does not need to become a durable credential.…