Answer-first summary for fast verification
Answer: 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.
Answer B is the most suitable solution for moving the company's webhook functionality to a serverless architecture with the least operational overhead. Here's why: 1. **Serverless Nature**: Amazon API Gateway is a fully managed service that allows you to create, publish, maintain, and secure APIs at any scale without managing the infrastructure. This aligns with the serverless approach, where the infrastructure management is handled by AWS. 2. **Scalability**: API Gateway can automatically scale to handle a large number of requests without requiring manual intervention. This is beneficial for webhooks, which may experience variable traffic. 3. **Integration with AWS Lambda**: API Gateway can be easily integrated with AWS Lambda, allowing each webhook to trigger a separate Lambda function. This decouples the webhook logic from the API layer, adhering to the microservices architecture pattern. 4. **Operational Overhead**: Since API Gateway and Lambda are both managed services, the operational overhead is significantly reduced compared to managing EC2 instances, an Auto Scaling group, or even containerized services like ECS and Fargate. 5. **Cost-Effectiveness**: With a serverless architecture, the company only pays for the resources consumed by the API Gateway and Lambda functions, which can be more cost-effective than maintaining a fleet of EC2 instances or a container service. 6. **Security and Maintenance**: API Gateway provides built-in security features such as rate limiting, authorization, and access control, which can help protect the webhook endpoints. Additionally, AWS takes care of the underlying infrastructure maintenance, updates, and patching. 7. **Simplicity**: Updating the Git servers to call the API Gateway endpoint is a straightforward process, and it centralizes the webhook invocation point, simplifying management and monitoring. In summary, option B offers a serverless, scalable, and cost-effective solution with reduced operational overhead, making it the best choice for the company's requirements.
Author: LeetQuiz Editorial Team
Ultimate access to all questions.
No comments yet.
A company hosts a Git repository in an on-premises data center. The company uses webhooks to invoke functionality that runs in the AWS Cloud. The company hosts the webhook logic on a set of Amazon EC2 instances in an Auto Scaling group that the company set as a target for an Application Load Balancer (ALB). The Git server calls the ALB for the configured webhooks. The company wants to move the solution to a serverless architecture. Which solution will meet these requirements with the LEAST operational overhead?
A
For each webhook, create and configure an AWS Lambda function URL. Update the Git servers to call the individual Lambda function URLs.
B
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.
C
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.
D
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.