QuestionQ65

VerifiedAccelerate Workload Migration and Modernization

A company hosts a Git repository in an on-premises data center and uses webhooks to invoke functionality running in the AWS Cloud. The company runs the webhook logic on a set of Amazon EC2 instances in an Auto Scaling group configured as a target for an Application Load Balancer (ALB). The Git server calls the ALB for configured webhooks. The company wants to move this solution to a serverless architecture.

Which solution meets these requirements with the LEAST operational overhead?

Explanation

An API Gateway HTTP API gives all the webhooks a single stable endpoint, with routing, throttling, authorization and logging handled by the service, while each webhook's logic stays in its own Lambda function. The Git server is pointed at one URL and the EC2 instances, Auto Scaling group and load balancer all disappear.

Lambda function URLs would also remove the servers, but each webhook then has its own separate endpoint that the Git server must be configured with and that must be secured and monitored individually — more to operate, not less. App Runner and Fargate keep a container platform in the picture, which is more operational overhead than either serverless option.

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!