Design the customer journey
Authenticate the customer, resolve the permitted destination site, and request an upload URL through the intended authorized boundary. The browser sends file bytes to S3 with the returned headers. Save the document/site identifiers against the customer’s application or case record.
Show clear states for uploading, processing, needing attention, and accepted. Keep privileged service credentials off the browser. Do not trust a customer-supplied site ID or document ID without authorization checks.
Test intake and retrieval together
Verify that one customer cannot list, search, request metadata for, or download another customer’s documents. Use separate deployments where tenant requirements call for independent accounts, regions, or operations.
Configure a release gate if unscanned files must be inaccessible to staff or downstream systems. Test expired URLs, interrupted transfers, scan/OCR failure, duplicate submissions, and reviewer rejection. Include bucket CORS, processor limits, notification privacy, and log exposure in the operating design.