Explanation
AWS Lambda is the best choice for this scenario because:
- Serverless Architecture: Lambda automatically manages the underlying infrastructure, eliminating operational overhead for provisioning, scaling, and maintaining servers
- Event-Driven Execution: Lambda functions run only when triggered, making it ideal for infrequent, short-duration workloads
- High Availability: AWS automatically runs Lambda functions across multiple Availability Zones for fault tolerance
- Pay-per-Use Pricing: You only pay for the compute time consumed during function execution, which is cost-effective for infrequent workloads
- Automatic Scaling: Lambda automatically scales to handle the number of requests without any manual intervention
Why other options are less suitable:
- Amazon EC2: Requires manual management of servers, scaling, and availability configurations
- AWS Fargate: Serverless containers but still requires container management and may have longer cold start times
- Amazon Aurora: A managed database service, not suitable for application hosting
Lambda's serverless nature provides the least operational overhead while meeting the high availability and infrequent execution requirements.