Maybe this all looks like networking issue. In fact, Stripe or Algolia clients would, at the end, just call an URL too.
I had problem with upload too, but it might have been related to input timeout, which was 30s and was raised to 60s as per this thread: Realm functions 30s input timeout
Now back to us, I also tested a Ream App deployed Global vs a Local, just in case. And no difference. The Algolia saveObject just reaches “execution time limit exceeded” in both apps.
Ahh you’re not uploading from a browser, sorry my bad. your uploading from node. I wouldn’t do that in a serverless function, as wouldn’t you be paying for a long running task this way? why not upload from the client directly.
no no… if you need to upload from the browser uses temp keys that are generated for that user only. i think aws has something called a STS KEY, you first define which path and what the keys can do dynamically, then pass the keys to the browser, and allow the browser to upload… the keys live for a short time say 60 mins.
I acknowledge the frustration with the issues with dependencies in Realm functions.
The Engineering team is working on these issues and please expect significant improvements in the upcoming weeks. For your questions and comments on specific packages, we would request to open a new topic to avoid confusion.
For updates on AWS S3, please follow this thread:
I will update here for the release updates on Stripe.
The engineering team have made performance improvements and Stripe, Algolia and Axios run much faster than before.