Home › Convert › Jenkins to AWS EventBridge
Convert Jenkins cron to AWS EventBridge
Jenkins 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 Jenkins to AWS EventBridge
- Jenkins 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. - Jenkins runs when day-of-month or day-of-week matches, but AWS EventBridge requires both. If you set both fields, the converter warns you.
- Jenkins
Hvalues pick a per-job offset, which no other system has. The converter replaces them with the start of the range.
Worked examples
| Schedule | Jenkins | AWS EventBridge |
|---|---|---|
| every minute | * * * * * | * * * * ? * |
| every weekday at 8:30 AM | 30 8 * * 1-5 | 30 8 ? * 2-6 * |
Conversions that come with a warning
- every 5 minutes:
H/5 * * * *→*/5 * * * ? *. Jenkins H values have no equivalent elsewhere; they were replaced by their range start. - every 10 minutes:
H/10 * * * *→*/10 * * * ? *. Jenkins H values have no equivalent elsewhere; they were replaced by their range start. - every 15 minutes:
H/15 * * * *→*/15 * * * ? *. Jenkins H values have no equivalent elsewhere; they were replaced by their range start. - every 30 minutes:
H/30 * * * *→*/30 * * * ? *. Jenkins H values have no equivalent elsewhere; they were replaced by their range start.
Field layout and time zones
minute (0-59), hour (0-23), day-of-month (1-31), month (1-12), day-of-week (0-7, 0 and 7 = Sunday).
Jenkins uses the controller's time zone. Put TZ=Asia/Kolkata on its own first line of the trigger to override it.
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 Jenkins, or open the Jenkins builder or the AWS EventBridge builder.
Frequently asked questions
How do I convert a Jenkins cron expression to AWS EventBridge?
Paste it into the converter above with Jenkins as the source and AWS EventBridge as the target. For example, * * * * * becomes * * * * ? *.
Is every Jenkins expression convertible to AWS EventBridge?
Yes for the common schedules we tested (27 of 27), though unusual expressions with special characters might need manual review.
Does AWS EventBridge run in the same time zone as Jenkins?
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.