A company hosts an on-premises Git repository and uses webhooks to trigger logic running in AWS. The webhook code currently runs on EC2 instances in an Auto Scaling group behind an Application Load Balancer (ALB); the Git server calls the ALB. The company wants to convert this to a serverless architecture with the least operational overhead. Which solution should you recommend?

The correct solution leverages Amazon API Gateway HTTP API and AWS Lambda functions. API Gateway HTTP APIs are designed for low-latency, cost-effective, and scalable integration with Lambda functions, making them ideal for serverless webhooks. Each webhook handler can be a separate Lambda function, providing granular control and easy management. This approach significantly reduces operational overhead compared to managing EC2 instances or containers. Individual Lambda function URLs are less suitable because managing multiple distinct URLs for various webhooks can become cumbersome and lacks a centralized management point that API Gateway provides. AWS App Runner is a good serverless container service but introduces more operational overhead than a pure Lambda-based solution for simple webhook logic. Amazon ECS with Fargate is a container orchestration service that, while serverless in terms of infrastructure management, still involves container image management and can have higher operational overhead than a direct API Gateway to Lambda integration for this use case.