Hi, I tried running supertokens (the binary) in aws lambda and it doesn't seem to work. What I did was I downloaded the supertokens-postgresql binary, dockerize it by copying the binary over to the docker image and installing it there. I tried to "docker ps" into it and ran "supertokens start" and it worked. However, when I deploy the image to AWS lambda it fails to run everytime. Hence, I set the erro flag in config.yaml to "null" so that the error would show in std-in, and what I found was always a java exception, something related to read-only file system. I suspect this is because aws lambda has the entire file system as read-only, except for /tmp. But Supertokens is trying to write to /usr/lib/supertoken/webserver-temp. Any idea about this? I essentially tried to run "supertokens start" when the lambda function is triggered but failed to do so.

hey @chunkygoo.

Thanks rp, I don't think it's a good idea either since supertokens has to start up every time. Do you know of any good resources about the share volume you mentioned?

What do you mean by "services that can help you run docker images on their own"?

@rp_st where will we be notified once Lmabda support for supertokens_python is released?

Hey @chunkygoo. you can watch this issue: https://github.com/supertokens/docs/issues/464