Answer: AWS Lambda

## Explanation **AWS Lambda** is the correct choice because: - **Serverless Architecture**: AWS Lambda is a serverless compute service that automatically manages the underlying infrastructure, eliminating operational overhead for provisioning, scaling, and maintaining servers - **Event-Driven Execution**: Lambda functions run only when triggered by events, making it ideal for applications that run infrequently for short periods - **Automatic Scaling**: Lambda automatically scales to handle the number of requests without any manual intervention - **High Availability**: AWS Lambda is inherently highly available as it runs across multiple Availability Zones within a region - **Pay-per-Use Pricing**: You only pay for the compute time you consume, which is cost-effective for infrequent workloads **Why not the others:** - **Amazon EC2**: Requires manual management of servers, scaling, and maintenance - **AWS Fargate**: While serverless, still requires container management and is better for longer-running applications - **Amazon Aurora**: This is a database service, not a compute service for hosting applications AWS Lambda provides the least operational overhead while meeting the requirements for high availability and infrequent, short-duration execution.

Author: Ritesh Yadav