Db connections are not removed when established from aws lambda
Hi team, we are running in aws lambdas and setting up a connection like this:
This db is reused between invocations in lambda. Current executions never get above 25 in aws, and there's concurrency limits set on that, however in neon dashboard it's seen the db connection count approaches 100. how is that possible? Is there a way to counteract this?
This db is reused between invocations in lambda. Current executions never get above 25 in aws, and there's concurrency limits set on that, however in neon dashboard it's seen the db connection count approaches 100. how is that possible? Is there a way to counteract this?
