A legacy application being migrated to AWS relies on hundreds of cron jobs that run for 1–20 minutes on various recurring schedules. The company wants to schedule and run these cron jobs on AWS with minimal refactoring and also support running jobs in response to a future event. Which solution meets these requirements?

The correct solution uses Amazon EventBridge Scheduler for recurring schedules and AWS Fargate to run the containerized cron jobs. EventBridge Scheduler is designed for creating, running, and managing scheduled tasks at scale, directly addressing the need for hundreds of recurring cron jobs. Fargate provides a serverless compute engine for containers, eliminating the need to manage servers and allowing jobs to run for up to 14 hours, accommodating the 1-20 minute job durations. This combination requires minimal refactoring as existing cron jobs can be containerized. Running cron jobs as AWS Lambda functions is not ideal because Lambda has a maximum execution duration of 15 minutes, which might be insufficient for jobs running up to 20 minutes, and it's less cost-effective for containerized workloads. AWS Batch is suitable for large-scale batch processing but might be overkill for simple recurring cron jobs and introduces more management overhead than Fargate for this specific use case. AWS Step Functions with a Wait state is not the primary service for recurring schedules; EventBridge Scheduler is purpose-built for this.