Which solution will meet these requirements with the LEAST operational overhead?
For each webhook, create and configure an AWS Lambda function URL. Update the Git servers to call the individual Lambda function URLs.
Create an Amazon API Gateway HTTP API. Implement each webhook logic in a separate AWS Lambda function. Update the Git servers to call the API Gateway endpoint.
Deploy the webhook logic to AWS App Runner. Create an ALB, and set App Runner as the target. Update the Git servers to call the ALB endpoint.
Containerize the webhook logic. Create an Amazon Elastic Container Service (Amazon ECS) cluster, and run the webhook logic in AWS Fargate. Create an Amazon API Gateway REST API, and set Fargate as the target. Update the Git servers to call the API Gateway endpoint.
Explanations:
Lambda function URLs do not support built-in request management, security, or scaling for multiple webhooks, potentially requiring more configuration and maintenance for each webhook individually.
API Gateway HTTP API with Lambda functions provides a fully serverless, highly scalable, and low-maintenance solution, allowing easy management of multiple webhooks with minimal overhead.
App Runner is managed, but using it with an ALB adds unnecessary complexity and operational overhead, as it requires additional setup, monitoring, and scaling of App Runner resources.
ECS with Fargate and API Gateway REST API adds complexity due to container management and API integration, which is not as serverless or low-maintenance as an API Gateway with Lambda functions.
I infer that the answer is:
Create an Amazon API Gateway HTTP API. Implement each webhook logic in a separate AWS Lambda function. Update the Git servers to call the API Gateway endpoint.