Question

A company runs a serverless application on AWS Lambda that connects to an Amazon Aurora MySQL cluster. During traffic spikes, the number of concurrent Lambda executions surges into the thousands, and the database begins rejecting connections and consuming excessive memory managing them. The team must improve scalability and reliability without rearchitecting the application's SQL-based data access, while keeping operational overhead low. Which approach BEST addresses the connection scaling problem?

Accepted Answer

Enable Amazon RDS Proxy in front of the Aurora cluster and have Lambda functions connect through the proxy endpoint.

Answer

Migrate the workload to Amazon DynamoDB and use the AWS SDK's built-in connection reuse to eliminate connection limits.

Answer

Increase the Aurora instance class to the largest available memory-optimized size to support more simultaneous connections.

Answer

Configure Lambda reserved concurrency to a low value so fewer functions can open database connections at once.