RDS Proxy + ORM for lambda

Greetings,

Thank you for contact AWS Team.

Your understanding is correct on the update of endpoint. That would be the only change required which makes the integration of RDS Proxy useful.

Now, with regards to using sequalize, it not recommended to be used as it is in Lambda as its containers based architecture. It is mentioned in their documentation as well and please go through them to get more details. [+] https://sequelize.org/docs/v6/other-topics/aws-lambda/#sequelize-connection-pooling-in-aws-lambda

On the other hand, RDS Proxy provides the required options of maintaining the connections across the containers. The best practice would be to close the connections at the end of the running code in lambda.

To summarise on adding ORM with RDS Proxy, we cannot assure on it being useful to help on performance. It would be better to first being with only RDS Proxy and test for your applications, optimize the proxy on its settings and avoid pinning and only then look at added integrations if required.

Hope this answers your query.

Thanks