How to Schedule ECS Tasks: Choosing Between EventBridge Scheduler, EventBridge Rules, and Step Functions
This guide examines three approaches for implementing scheduled ECS task execution, comparing their features, costs, and ideal use cases. As of 2025, EventBridge Scheduler is recommended for most new implementations due to its timezone support, flexible retry configuration, and generous free tier.
Introduction
As cloud-native development continues to evolve, so do the approaches for implementing scheduled tasks. The shift from traditional crontab on EC2 instances to serverless execution platforms using ECS and Lambda is accelerating, with an increasing number of use cases running containerized workloads such as batch processing and data aggregation on a scheduled basis.
However, when it comes to implementing scheduled execution on ECS, questions often arise: "Which method should I use?" or "What's the optimal choice for my use case?" AWS offers multiple implementation approaches, each with its own characteristics and ideal scenarios.
This article organizes the primary implementation methods for scheduling ECS tasks and explains how to choose between them based on your use case. It serves as a practical guide for those already familiar with ECS basics who are ready to implement scheduled task execution as their next step.
Three Implementation Methods for Scheduling ECS Tasks
There are three primary implementation methods for scheduling ECS tasks:
- EventBridge Scheduler
- EventBridge Rules
- Step Functions IntegrationEventBridge Scheduler
This chapter organizes the overview and positioning of these three methods and provides guidance on when to use each approach.
Positioning of Each Implementation Method
EventBridge Scheduler (Recommended)
The newest implementation method with the most comprehensive feature set, including timezone support, flexible retry configurations, and DLQ support.
Released in November 2022, EventBridge Scheduler is the most recommended method for simple scheduled execution as of 2025.
EventBridge Rules (Legacy Approach)
A previously established method with UTC-fixed scheduling.
While there are fewer reasons to adopt this for new implementations, it remains a viable option for maintaining existing systems or when specific requirements exist.
Step Functions Integration
The choice when complex workflows are required, such as sequential execution of multiple ECS tasks, preventing concurrent execution, or branching logic based on execution results.
This approach incurs additional costs and is excessive for simple use cases.
Basic Selection Guidelines
EventBridge Scheduler
Overview and Features
EventBridge Scheduler is an AWS serverless scheduler service released in November 2022.
It enables flexible scheduling for over 270 AWS services, including ECS tasks, Lambda, and Step Functions.
Key Features
- Timezone support: Specify timezones like Japan Standard Time (Asia/Tokyo)
- Flexible retry configuration: Configure up to 185 retries with a maximum retention period of 24 hours
- Dead Letter Queue support: Send failed events to SQS or SNS
- One-time schedules: Execute tasks once at a specific date and time
- Scalability: Manage tens of millions of schedules: Specify timezones like Japan Standard Time (Asia/Tokyo)
The greatest advantages compared to traditional EventBridge Rules are the increased flexibility in configuration and improved operational ease.
Advantages and Disadvantages
Advantages
- Easy execution in JST with timezone support
- Simplified failure handling with retry and DLQ configurations
- Centralized schedule management
- Free tier up to 14 million invocations per monthEasy execution in JST with timezone support
Disadvantages
- Slightly higher cost than the legacy approach beyond the free tier
- Not directly creatable from the ECS console
Pricing
EventBridge Scheduler pricing is $1.00 per 1 million invocations (Tokyo region).
Cost Examples
- Daily execution (30 times per month): $0.0000375
- Hourly execution (720 times per month): $0.0009
With a free tier of 14 million invocations per month, typical use cases can operate essentially free of charge.
EventBridge Rules
Overview and Features
EventBridge Rules (formerly CloudWatch Events) is the established scheduling method that has been available for some time.
It allows you to start ECS tasks periodically using cron or rate expressions.
Key Features
- UTC-fixed: No timezone specification available; always executes in UTC
- Simple configuration: Supports basic cron or rate expressions only
- Free: No charge as an AWS managed event
Comparison with EventBridge Scheduler
Feature | EventBridge Scheduler | EventBridge Rules |
|---|---|---|
Timezone | Configurable (JST, etc.) | UTC-fixed |
Retry Configuration | Up to 185 retries, granular settings | No native support |
DLQ | Native support | Manual configuration |
Pricing | $1.00/M invocations | Free |
Advantages and Disadvantages
Advantages
- Completely free to use
- Simple and easy to understand
- Proven track record with existing systems
Disadvantages
- UTC-fixed, requiring timezone calculations for JST execution
- Complex retry and DLQ configuration
Pricing
Cron/rate-based schedules with EventBridge Rules are completely free as AWS managed events.
There are no charges regardless of the number of executions.
Step Functions Integration
Overview and Features
Combining Step Functions with EventBridge (Scheduler or Rules) enables scheduled task execution with complex workflows.
Step Functions handles workflow orchestration, while EventBridge periodically triggers the workflow.
Key Features
- Sequential task execution: Control like "execute Task B after Task A completes"
- Mutual exclusion: Prevent concurrent execution using locking mechanisms with DynamoDB
- Conditional branching: Change subsequent actions based on task execution results
- Error handling: Flexible error processing with Catch/Retry
- Timeout control: Set maximum execution time per task
While this is overkill for simple scheduled execution, it becomes a powerful option when complex requirements exist.
Advantages and Disadvantages
Advantages
- Visual design and management of complex workflows
- Flexible error handling and retry control
- Detailed execution history recording
- Easy data passing between tasks
Disadvantages
- Additional Step Functions costs incurred
- Complex configuration with higher learning curve
- Excessive for simple use cases
Pricing
Step Functions offers two types with different pricing structures: Standard Workflows and Express Workflows.
Standard Workflows
Standard Workflows pricing is $0.025 per 1,000 state transitions (Tokyo region).
Express Workflows
Express Workflows are charged based on the number of requests and duration:
- $1.00 per 1 million requests
- $0.00001667 per GB-second
For scheduled ECS execution, Standard Workflows, which retain execution history, are typically used.
Note that EventBridge Scheduler or Rules costs are incurred separately.
Comparison of the Three Implementation Methods
Detailed Comparison
Feature | EventBridge Scheduler | EventBridge Rules | Step Functions Integration |
|---|---|---|---|
Pricing | $1.00/M invocations | Free | Standard: $0.025/1K transitions |
Timezone | Configurable (JST, etc.) | UTC-fixed | Depends on Scheduler |
Retry | Up to 185 retries | No support | Flexible with Catch/Retry |
DLQ | Native support | Manual configuration | Native support |
Complex Workflows | Not possible | Not possible | Possible |
Configuration Complexity | Low | Low | High |
Recommendation | ◎ | △ | Specific cases only |
Cost Comparison
When comparing actual operational costs, there's minimal difference for typical scheduled task use cases.
Monthly Execution
- EventBridge Scheduler: $0 (within free tier)
- EventBridge Rules: $0
- Step Functions (3 steps: ECS RunTask → Wait → Notification): Less than $0.0001
Hourly Execution (720 times per month)
- EventBridge Scheduler: $0 (within free tier)
- EventBridge Rules: $0
- Step Functions (3 steps: ECS RunTask → Wait → Notification): $0.05
The EventBridge Scheduler free tier (14 million invocations per month) is very generous. Even executing every minute results in only 43,200 invocations per month, well within the free tier.
There's little reason to choose Rules purely for cost considerations.
Operational Comparison
Operational Benefits of EventBridge Scheduler
- Timezone configuration eliminates the need for daylight saving time adjustments
- Easy retry configuration provides resilience against transient failures
- DLQ configuration simplifies tracking of failed events
Cases for Continuing with EventBridge Rules
- System already running stably with minimal migration benefits
- UTC-fixed operation is acceptable and avoiding configuration change risks is preferred
Cases Requiring Step Functions Integration
- Using the output of a previous task as input for the next task
- Task execution time is variable, requiring waiting for completion before proceeding
- Parallel execution of multiple tasks followed by subsequent processing after all complete
When to Consider Migration
Migration from existing EventBridge Rules is worth considering in the following cases:
- Timezone support becomes necessary (global expansion, daylight saving time handling)
- Need to strengthen failure handling mechanisms with retry and DLQ
- Require automatic tracking to new task definition revisions
If your current Rules implementation is working without issues, there's no need to force a migration.
Summary
This article compared three implementation methods for scheduling ECS tasks and explained how to choose between them based on use case:
- EventBridge Scheduler: Recommended method with comprehensive features including timezone support and retry configuration
- EventBridge Rules: Legacy approach that's UTC-fixed but completely free
- Step Functions Integration: Option when complex workflows are required
As of 2025, EventBridge Scheduler is optimal for new ECS scheduled task implementations.
It makes JST execution simple and includes practical features like retry and DLQ support. The generous free tier also makes it essentially free for typical use cases.
For systems already running stably with EventBridge Rules, forced migration is unnecessary.
Consider Step Functions integration only when you need sequential execution of multiple tasks or mutual exclusion control.
Reference
Enjoyed reading this content? Let the author know!
Your likes, comments, shares, and saves help creators reach more builders.
Loading recommendations
Loading article