Home › Convert › AWS EventBridge to node-cron
Convert AWS EventBridge cron to node-cron
AWS EventBridge expressions look similar to node-cron, but the differences matter. Paste yours below; the result is checked against the original run times.
What changes from AWS EventBridge to node-cron
- node-cron has a leading seconds field. The converter adds
0in front so the job fires at the start of the minute. - AWS EventBridge numbers weekdays 1-7 starting on Sunday. node-cron starts on Sunday = 0, so every weekday number is reduced by one.
- node-cron does not use
?, so it is replaced with*. - node-cron has no year field. A specific year would be dropped, so the schedule would repeat every year; the converter warns you.
Worked examples
| Schedule | AWS EventBridge | node-cron |
|---|---|---|
| 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 * * * |
Field layout and time zones
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.
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.
Go the other way
Convert node-cron to AWS EventBridge, or open the AWS EventBridge builder or the node-cron builder.
Frequently asked questions
How do I convert a AWS EventBridge cron expression to node-cron?
Paste it into the converter above with AWS EventBridge as the source and node-cron as the target. For example, * * * * ? * becomes * * * * *.
Is every AWS EventBridge expression convertible to node-cron?
Yes for the common schedules we tested (30 of 30), though unusual expressions with special characters might need manual review.
Does node-cron run in the same time zone as AWS EventBridge?
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.