A ReactJS frontend calls REST APIs through Amazon API Gateway. A data engineer needs to provide a Python script that can be invoked occasionally via API Gateway and must return responses to API Gateway. Which option gives the required behavior with the LEAST operational overhead?

Creating an AWS Lambda Python function with provisioned concurrency is the most suitable option. Lambda is a serverless compute service, meaning AWS manages the underlying infrastructure, significantly reducing operational overhead. Provisioned concurrency keeps the function warm, eliminating cold starts and ensuring low-latency responses, which is crucial for API Gateway integrations. Deploying on Amazon ECS or EKS involves managing servers, clusters, and scaling, leading to higher operational overhead compared to Lambda. While creating an AWS Lambda function and using an EventBridge rule to keep it warm can work, provisioned concurrency is a more direct and managed solution for maintaining warm functions, specifically designed to address cold starts for performance-critical applications like API Gateway backends.