Short answer: keep the export private, preserve one canonical object key, and debug the signed request as a tuple of method, path, query, credentials, and time before changing CORS or making the object public. For a customer download, a 403 is usually useful evidence: the storage service did not accept the request that arrived.
This matters in a B2B SaaS product because an export link is part of the customer workflow, while the file often has a retention and deletion policy behind it. A link that works in a developer browser but fails for a customer after a queue delay is an availability problem. A link that exposes a deleted export is a policy problem. Treat both as one design.
The incident lesson: verify the signed request, not the URL
I would bound the first investigation to one export record and one failed request.…