You built a web application that uses an API Gateway Regional endpoint and an AWS Lambda function. Consumers are near the Region. The Lambda function queries an Amazon Aurora MySQL database that has three read replicas. Under high load, the application opens many database connections and fails to meet performance targets. Which actions should you take to improve performance? (Choose two.)

Amazon RDS Proxy provides connection pooling, reducing the overhead of establishing new database connections for each Lambda invocation. By pointing it at the Aurora reader endpoint, the Lambda function can efficiently utilize the read replicas. Enabling Lambda Provisioned Concurrency keeps a specified number of execution environments pre-initialized, reducing cold start times and ensuring the function is ready to process requests immediately, which is crucial under high load. Using the Aurora cluster endpoint directs traffic to the writer instance, which is not ideal for read-heavy operations and doesn't address connection management. Moving database connection code outside the handler is a good practice for connection reuse but doesn't solve the fundamental issue of too many connections under high load, which RDS Proxy addresses more robustly. Changing API Gateway to an edge-optimized endpoint would improve latency for geographically dispersed users, but the problem states consumers are near the Region, and the issue is database performance, not API Gateway latency.