RDS connections in Lambda
In server setup, the connections to RDS DB (Aurora) instances has pool where the connections are bit long lived and cached. This will give us faster connectivity. I would like to understand the guidance on this scenario for serverless/lambda. With lambda there is no sessions and no connections are cached. I think it will create connections every time, it might impact the performance. Are there any workaround or solves/guidance for Lambda ? Is it okay to open the connection every time with the DB instances ? Any leads on this will be super helpful ?
Lambda functions execute in micro VMs. Lambda reuses the micro VM between invocations. For this reason we recommend you create the connection to the database outside the handler (in the init code) and leave it open. As the micro VMs are completely isolated, you can't use a connection pool as you do in servers. For this reason we created RDS Proxy. RDS proxy maintains a connection pool to the database. Your Lambda functions connects to the proxy instead of the directly to the database.
Using DocumentDB with Lambda: connection poolingAccepted Answerasked a year ago
RDS Proxy Metricsasked 4 months ago
Changes to connection handling with Aurora Postgres?Accepted Answerasked 3 years ago
AWS RDS proxy connection closeAccepted Answerasked 3 months ago
Using RDS Proxy doubles or triples average response timesasked 6 months ago
Aurora Serverless MySQL - Downtime during scaling eventasked 4 months ago
AWS Client VPN timeoutAccepted Answerasked 2 years ago
DB Connections Upper Limitasked 2 years ago
RDS connections in LambdaAccepted Answerasked 25 days ago
Use RDS Postgres Replicas as a clusterAccepted Answerasked 4 months ago