We are trying to implement Uppy S3 Mulitpart upload. We currently have a working demo and greatly thank the team for the awesome work.
We have currently deployed a standalone companion on a AWS EC2 linux machine and have managed to start the standalone server as a daemon service and is working as expected.
Our project consist of large zipped files (GB) to be uploaded via Uppy to AWS S3.
We recently realized that Uppy Companion can be deployed as a serverless AWS Lambda. However, since AWS Lambda has a 500 MB disk restriction would AWS Lambda be a incompatible solution to run Uppy Companion on AWS Lambda for large file upload since Companion writes to a temporary file (etc. /tmp).
What would your recommendation be to run a Companion server?
Thanks in Advance
and
proudlyDisplayPoweredByUppy: true
Unfortunately no. However, we decided to launch a seperate vm for companion and i worked fine. However, depending on you system I also remember companion having a docker image would be a decent solution if you are using docker/kubernetes.
Hi there. I see this only now (years later) searching for the answer to another question. But we do run companion on AWS lambda for years already. Let me know if this is still relevant.