A serverless city permit API uses many concurrent AWS Lambda functions that open short-lived connections to Amazon RDS. During renewal season the database hits max_connections and new Lambdas fail. What should the solutions architect introduce to stabilize connection churn?
Select an answer to reveal the explanation.
Short Explanation
Lambdas are like hundreds of clerks opening a new phone line to the same records clerk every few seconds—the switchboard melts. RDS Proxy is the shared switchboard that keeps a polite pool of open lines for everyone.
Full Explanation
AWS Lambda concurrency can create connection storms against RDS because each invoke may open its own client connection. Amazon RDS Proxy sits between the application and the database, pooling and multiplexing connections so the engine’s max_connections limit is protected. Dedicated per-Lambda databases and disabling concurrency are not scalable designs; static hosting does not meet a transactional permit API requirement.