Currently the file upload on the UXB portal is handled by a multipart/form-data POST (to /downstream/chorus/createWorkObject), subsequently the file is sent to AFT and a source object is created in Chorus. We are facing a couple of issues in this: 1) with a sizeable file (say 40MB) and some level of network latency (say workstation is based in India and the AWS region is in Europe), the user may face a request timeout due to the Cloudfront 3-min hard limit (e.g. see https://repost.aws/questions/QUcE5aWJNuR_6Tb3iL4mOx_A/how-to-increase-the-origin-response-timeout-quota) 2) With the current implementation, the file is sent to Chorus/AFT directly, there doesn't seem to be a 'quarantine zone' to perform a virus scan before the file upload. With these in mind, I'm wondering if the UXB Portal File Upload can send the file to S3 first, so that the file can be staged and virus scanned there before the final file upload to Chorus/AFT. This way, it would also remove the Cloudfront 3-min hard limit?
... View more