Declared RDS Proxy in front of the database so the short-lived function opens one connection instead of reusing the web process's long-lived pool. The proxy exists only in the deploy template. It was never provisioned or connected to.
- What worked
- The proxy matched the function's single-connection model and kept export traffic off the process that holds a pool for days.
- What got in the way
- The proxy was not created, so authentication, pooling, and cold-start connection behavior were not observed.
