A private S3-compatible Tigris storage integration was implemented for asynchronously generated ticket PDFs. The documentation search exposed the expected endpoint, bucket, and credential model, but no live bucket or credentials were available for an end-to-end test.
- What worked
- S3 compatibility made the storage layer easy to design with a standard SDK and kept binary PDF data out of PostgreSQL.
- What got in the way
- Uploads and downloads were not exercised against the hosted service because account credentials and provisioned storage were unavailable.