AWS cron expression builder and validator
Build and check an expression
Everything runs in your browser, offline too: nothing you type is sent anywhere. Share a schedule by copying the page address; the expression is kept after the #.
An AWS cron expression has six fields, minutes, hours, day-of-month, month, day-of-week and year, wrapped in cron(): cron(0 9 ? * MON-FRI *) runs at 09:00 every weekday. One of the two day fields must be ?, day-of-week counts 1 = Sunday to 7 = Saturday, and EventBridge rules run in UTC while EventBridge Scheduler can use any time zone.
AWS cron syntax: the six fields
EventBridge scheduled rules and EventBridge Scheduler use the same cron format: cron(minutes hours day-of-month month day-of-week year). All six fields are required and are separated by spaces.
| Field | Values | Wildcards |
|---|---|---|
| Minutes | 0–59 | , - * / |
| Hours | 0–23 | , - * / |
| Day-of-month | 1–31 | , - * ? / L W |
| Month | 1–12 or JAN–DEC | , - * / |
| Day-of-week | 1–7 or SUN–SAT (1 = Sunday) | , - * ? L # |
| Year | 1970–2199 | , - * / |
Wildcards
,adds values:JAN,FEB,MARin month means January, February and March.-is a range:1-15in day-of-month is days 1 to 15. AWS’s own examples include a range that wraps past midnight,20-2in hours.*means every value. You can’t use it in both day-of-month and day-of-week./is an increment:1/10in minutes runs at minutes 1, 11, 21 and so on;0/15every 15 minutes from the top of the hour. Day-of-week doesn’t accept it.?means any, and goes in whichever day field you aren’t using:7in day-of-month with?in day-of-week runs on the 7th whatever the weekday.Lis the last day: of the month in day-of-month, of the week in day-of-week.6Lin day-of-week is the last Friday of the month.Wis the nearest weekday:3Wis the weekday closest to the 3rd of the month.#is the nth weekday of the month:3#2is the second Tuesday (3 is Tuesday, the third day of the week). A day-of-week field with#can hold only that one expression, so3#1,6#3is invalid.
Two limits apply to every expression: you can’t set both day fields (one must be ?), and cron expressions that would run more often than once a minute aren’t supported.
Examples
| Expression | Runs |
|---|---|
cron(0 10 * * ? *) | 10:00 UTC every day |
cron(15 12 * * ? *) | 12:15 UTC every day |
cron(0 18 ? * MON-FRI *) | 18:00 UTC, Monday to Friday |
cron(0 8 1 * ? *) | 08:00 UTC on the 1st of every month |
cron(0/15 * * * ? *) | Every 15 minutes |
cron(0/10 * ? * MON-FRI *) | Every 10 minutes, Monday to Friday |
cron(0/5 8-17 ? * MON-FRI *) | Every 5 minutes from 08:00 to 17:55 UTC, Monday to Friday |
cron(15 10 ? * 6L 2019-2022) | 10:15 UTC on the last Friday of each month, 2019 to 2022 |
cron(0 12 ? * 3#2 *) | 12:00 on the second Tuesday of each month |
cron(0 9 15W * ? *) | 09:00 on the weekday nearest the 15th |
The first eight are from the AWS documentation. For EventBridge rules the times are UTC; in EventBridge Scheduler they are in the schedule’s time zone.
How AWS cron differs from Unix cron
A crontab line won’t work as it is. Paste one into the builder and it suggests the AWS version.
| Difference | Unix cron | AWS cron |
|---|---|---|
| Fields | 5: minute, hour, day of month, month, day of week | 6: the same five plus year, wrapped in cron( ) |
| Day-of-month and day-of-week | Both can be set; when both are restricted the job runs when either matches | One of them must be ?; you can’t restrict both |
| Sunday | 0 (and 7 in most versions); days are 0–6 | 1; days are 1–7, SUN to SAT |
| Every 5 minutes | */5 * * * * | cron(0/5 * * * ? *) or rate(5 minutes) |
| Steps in day-of-week | Allowed in most versions | Not allowed: list the days instead |
| L, W and # | Not in standard cron | Last day (L, 6L), nearest weekday (15W), nth weekday (3#2) |
| Time zone | The server’s time zone | UTC for EventBridge rules; any IANA time zone per schedule in EventBridge Scheduler |
Neither has a seconds field. Quartz and Spring expressions do; drop their first field to get the AWS form.
rate() expressions
For a fixed interval, rate(value unit) is simpler: rate(5 minutes), rate(1 hour), rate(12 hours), rate(1 day). The value is a positive whole number and the unit is minutes, hours or days; there are no seconds, weeks or months.
- EventBridge rules need the singular unit for a value of 1 and the plural above 1:
rate(1 hour)andrate(5 hours)are valid,rate(1 hours)andrate(5 hour)aren’t. - EventBridge Scheduler’s guide lists the units as
minutes | hours | daysand writesrate(1 days)itself.
A rate schedule counts from when it starts, not from the clock: from when you create the rule, or from a Scheduler schedule’s StartDate (without one, it starts invoking straight away). Use cron when it has to run at particular minutes.
Time zones and daylight saving time
EventBridge rules evaluate cron in UTC, and AWS’s examples are all given in UTC+0. To run at 09:00 in New York you have to work out the UTC hour yourself and change it when the clocks change.
EventBridge Scheduler evaluates cron and one-time schedules in the time zone you give the schedule (--schedule-expression-timezone, or ScheduleExpressionTimezone in CloudFormation), from the IANA time zone database, and adjusts for daylight saving time:
- When the clocks go forward, a run that falls in the missing hour is skipped that day.
- When the clocks go back, a time that happens twice runs only once, at the second occurrence.
rate(1 days)means 24 hours, so on a 23- or 25-hour day it drifts by an hour against the clock.
The builder follows these rules and flags skipped or repeated times. Scheduler invokes targets with 60-second precision: a run due at 1:00 happens between 1:00:00 and 1:00:59, unless you set a flexible time window.
One-time schedules: at()
EventBridge Scheduler also runs a target once at a given time: at(2026-12-31T23:30:00), in the schedule’s time zone. EventBridge rules don’t support it. A one-time schedule still counts against your schedule quota after it has run, so AWS recommends deleting it once it has.
Sources
Questions
Why does AWS say “Parameter ScheduleExpression is not valid”?
EventBridge checks the whole expression and rejects it with that ValidationException if any part breaks a rule. The usual causes are five fields instead of six, * in both day-of-month and day-of-week (one of them must be ?), 0 for Sunday (AWS counts 1–7 from Sunday), a / increment in day-of-week, or rate(1 minutes) instead of rate(1 minute). Paste the expression into the builder above to see which field is wrong.
Is AWS cron in UTC?
For EventBridge scheduled rules, yes: the expression is always evaluated in UTC. EventBridge Scheduler lets you set a time zone per schedule (ScheduleExpressionTimezone, any IANA name such as Europe/London) and adjusts for daylight saving time; without one it uses UTC.
How do I run a Lambda function every 5 minutes?
Use rate(5 minutes) or cron(0/5 * * * ? *). With EventBridge Scheduler, create a schedule with the function as the target and a role Scheduler can assume. With an EventBridge rule, add the function as a target and give EventBridge permission to invoke it with aws lambda add-permission.
What does ? mean in an AWS cron expression?
“Any”. AWS cron has separate day-of-month and day-of-week fields and doesn’t let you restrict both, so the one you aren’t using must be ?. For example cron(0 9 ? * MON *) runs on Mondays, and cron(0 9 1 * ? *) on the 1st.
Can an EventBridge schedule run more often than once a minute?
No. Cron expressions that lead to rates faster than one minute aren’t supported, and rate() takes minutes, hours or days. EventBridge Scheduler also invokes targets with 60-second precision: a schedule for 1:00 runs between 1:00:00 and 1:00:59.
Does the builder send my expressions anywhere?
No. Parsing and the run-time calculation happen in your browser, including the time-zone conversion, which uses your browser’s built-in time zone data. Nothing you type is sent anywhere, and the page sets no cookies.
EventBridge, Lambda and CloudWatch alarms and logs have their own screens in CloudConsole, so you can see which alarm fired and read the logs of the run from your phone, on iPhone and Android.
About the app →