Home › Convert › node-cron to AWS EventBridge
Convert node-cron cron to AWS EventBridge
node-cron expressions look similar to AWS EventBridge, but the differences matter. Paste yours below; the result is checked against the original run times.
What changes from node-cron to AWS EventBridge
- AWS EventBridge has no seconds field, so a schedule that fires on specific seconds cannot be converted exactly. The seconds value is dropped and flagged.
- node-cron numbers Sunday as 0, but AWS EventBridge uses 1-7 starting on Sunday. Every weekday number is increased by one (Monday-Friday becomes 2-6).
- AWS EventBridge requires a
?in exactly one of the two day fields. The converter puts it in the day field you did not use. - AWS EventBridge has a year field. The converter appends
*so the schedule repeats every year.
Worked examples
| Schedule | node-cron | AWS EventBridge |
|---|---|---|
| every minute | * * * * * | * * * * ? * |
| every 5 minutes | */5 * * * * | */5 * * * ? * |
| every 10 minutes | */10 * * * * | */10 * * * ? * |
| every 15 minutes | */15 * * * * | */15 * * * ? * |
| every 30 minutes | */30 * * * * | */30 * * * ? * |
| every hour | 0 * * * * | 0 * * * ? * |
| every 2 hours | 0 */2 * * * | 0 */2 * * ? * |
| every 3 hours | 0 */3 * * * | 0 */3 * * ? * |
Conversions that come with a warning
- on the first Monday of every month at 9:00 AM:
0 9 1-7 * 1→0 9 1-7 * ? *. Both day-of-month and day-of-week were set. AWS EventBridge cannot express "either"; day-of-week was dropped. Check the result. - every 10 seconds:
*/10 * * * * *→* * * * ? *. AWS EventBridge has no seconds field; the seconds value "*/10" was dropped. - every 30 seconds:
*/30 * * * * *→* * * * ? *. AWS EventBridge has no seconds field; the seconds value "*/30" was dropped.
Field layout and time zones
second (0-59), minute (0-59), hour (0-23), day-of-month (1-31), month (1-12), day-of-week (0-7, 0 and 7 = Sunday).
node-cron uses the server time zone unless you pass { timezone: "Asia/Kolkata" }. Its documentation advises timezone: "UTC" for jobs that must not skip or repeat when clocks change.
minute (0-59), hour (0-23), day-of-month (1-31), month (1-12), day-of-week (1-7, 1 = Sunday), year (1970-2199, required).
EventBridge rules always run in UTC. If you want a local time zone with DST support, use EventBridge Scheduler instead.
Go the other way
Convert AWS EventBridge to node-cron, or open the node-cron builder or the AWS EventBridge builder.
Frequently asked questions
How do I convert a node-cron cron expression to AWS EventBridge?
Paste it into the converter above with node-cron as the source and AWS EventBridge as the target. For example, * * * * * becomes * * * * ? *.
Is every node-cron expression convertible to AWS EventBridge?
Yes for the common schedules we tested (32 of 32), though unusual expressions with special characters might need manual review.
Does AWS EventBridge run in the same time zone as node-cron?
Not necessarily. Conversion changes the syntax, not the time zone. Check where each system evaluates the schedule before you rely on the same clock times.