A data engineering team runs 40 independent Glue ETL jobs that must each start at specific times throughout the day. They currently manage schedules using cron expressions in individual Glue triggers, but they want a single, centralized service to manage all schedules, support one-time and recurring runs, apply flexible time windows, and automatically retry failed invocations with a dead-letter queue for troubleshooting. Which approach best meets these requirements with the least operational overhead?