MongoDB and Atlas users are experiencing poor performance when using MongoDB from AWS Lambda Functions. This is likely due to a current inability to persist connection pools between execution of Lambda functions, thus a connection pool must be created for each execution.

I imagine Lambda provides some type of execution context which users can persist mongoclient instances to be referenced for subsequent operations. The drivers may need to be modified to make use of this persistent context.