I found this reply from Amazon helpful. TL;DR don't use a connection pool in Lambda > Now I see that you mentioned in one of the github posts: "The Lambda doe

I found this reply from Amazon helpful. TL;DR don't use a connection pool in Lambda > Now I see that you mentioned in one of the github posts: "The Lambda does seem to use the pool, but if I make maybe 3 / 4 quick requests to the lambda, new connections are opened up despite there being all of those connections already." > 3/4 quick requests would mean concurrent invocations, and concurrent invocations will execute in new containers. Containers are not aware of each other and cannot share state information so if an execution occurs in new container, it will open a new connection if there are none in this new container, despite there being existing connections from different containers. This can also cause your RDS instance to have too many open connections, because another container may have all the connections saturated, and if a new container is required to handle the load it may not be able to create the new RDS connection it needs to do it's work. - https://github.com/sequelize/sequelize/issues/4938#issuecomment-245211042 https://github.com/sequelize/sequelize/issues/4938#issuecomm...