Ah bummer. Ok well I guess Provisioned Concurrency isn’t really viable at this point in time. Let me know if I can help in some way to get this into Jets 5!
Not sure if this is new or not, but AWS gives you a little estimate of how much the provisioned concurrency is going to add to your bill when setting it up in AWS Console:
I think there are probably a lot of variables that affect the cost, but probably the most impactful is the memory size allocation for the function. It looks like the default memory size is still 1536 MB per function. I recall posting a question about this years ago. On our production application, I have it set to 256MB and on our internal bot application we’re using 512MB (probably should lower that to 256 as well). Makes a huge difference on the AWS bill!
Regarding one_lambda_for_all_controllers, oh yes! This could really help with the cold-start problem and simplify some things.
Keep up the good work!