A company exposes a REST API through Amazon API Gateway that invokes a single Lambda function. The function is invoked infrequently by multiple concurrent clients. The code is optimized, but the company wants to reduce the function’s startup (cold-start) time. What should a developer do?

Configuring provisioned concurrency for the Lambda function is the most effective solution to reduce cold starts for infrequently invoked functions. Provisioned concurrency keeps a specified number of execution environments pre-initialized, ensuring that invocations are processed with minimal latency. Enabling API Gateway caching would reduce calls to the Lambda function for repeated requests with the same parameters but wouldn't address cold starts for unique or uncached requests. Using Lambda proxy integration simplifies the integration but doesn't inherently reduce cold start times. AWS Global Accelerator improves performance by routing traffic through the AWS global network but doesn't directly impact Lambda function startup times.