Short answer: keep the bucket private, let Node.js authorize the document operation, and give the client a short-lived signed download URL only after checking the document's tenant and user ownership in your application database. Store PDF and DOCX bytes in object storage; store identity, state, and policy in the database. Treat bucket metadata as an operational copy, never as the authorization system.
That decision rule matters because document systems have two very different traffic shapes. A small request issues permission. A large request moves bytes. Sending both through the application fleet makes capacity planning and incident response harder than they need to be.…