Developer Tools

AWS cron expression generator

Build and validate six-field AWS cron expressions, then inspect upcoming scheduled times. This simulator does not create an AWS resource or invoke a target.

On your device

Files and text are processed in your browser.

AWS service

Previewed values are scheduled times with minute precision, not a promise of target delivery.

AWS cron expression

Six AWS fields: minute, hour, day of month, month, day of week, year. Use ? in exactly one day field. Maximum 256 characters.

Edit the six fieldsMinute0–59Hour0–23Day of month1–31Month1–12Day of week1–7 · 1 or SUN: Sunday; 7 or SAT: SaturdayYear1970–2199

IANA time zoneSearch after this instant

ISO 8601: 2026-01-01T00:00:00Z. Results are strictly after this instant.

Upcoming scheduled times

Choose an AWS schedule and calculate to see up to ten matching times.

02 / How to use it

About this tool

How to use this tool

Choose AWS semantics
Start with a preset or enter six fields. The year is last, and exactly one day field must be ?.
Set service, zone, and start
Choose Scheduler for an IANA zone or legacy rules for UTC. Enter an ISO instant with Z or an explicit offset.
Check the scheduled times
Calculate up to ten matches, inspect local and UTC values, then copy cron(...). Confirm deployment settings in AWS.

Worked example

The last Friday at 10:15 UTC

The start is exclusive. 6L selects the last Friday of each month under AWS weekday numbering.

Input

cron(15 10 ? * 6L 2026-2027)

Result

2026-09-25T10:15:00.000Z
2026-10-30T10:15:00.000Z
2026-11-27T10:15:00.000Z

Options: EventBridge Scheduler · UTC · 2026-09-18T00:00:00Z

Formats and limits

Syntax: Supported AWS subset: six fields, names, lists, ranges, steps, ?, L, nW, nL and n#k. LW, L offsets and special-operator lists are rejected.
Limits: Up to 256 characters, 10 dates, and a 5-year search. Years range from 1970 to 2199.
Service clock: Legacy scheduled rules are evaluated in UTC. Choose Scheduler for an IANA time zone.

Common issues

Both day fields contain a rule

AWS requires exactly one of day of month and day of week to be ?. The other field defines the calendar rule.

No dates appear

Fewer than ten matches were found in the five-year horizon. A valid expression with a distant year may return no results.

Build an AWS calendar expression

AWS cron has six required fields, with year after day of week. Named months and weekdays make reviews easier, while ?, L, W, and # express AWS day rules.

Scheduler zones and legacy UTC

EventBridge Scheduler evaluates a cron expression in a chosen IANA time zone. Legacy scheduled rules use UTC. The selector keeps that service decision visible while reviewing dates.

A bounded local preview

The browser searches for ten matches within five years and accepts up to 256 input characters. It never contacts AWS, creates a schedule, or guarantees delivery.

Frequently Asked Questions

How is AWS cron different from Unix cron?

AWS uses six fields including year, supports names and special day operators, and requires ? in exactly one of the two day fields.

Which service should I select?

Choose EventBridge Scheduler for current AWS scheduling and IANA time zones. Choose scheduled rules only when reviewing that legacy UTC-only feature.

What happens at daylight-saving changes?

Scheduler skips a nonexistent spring local time and invokes once for a repeated autumn local time. UTC rules have no daylight-saving transition.

Does the preview deploy or test a schedule in AWS?

No. It performs a local calendar calculation without credentials. Configure the target, retries, permissions, and delivery behavior in AWS.

Why can a valid expression show no dates?

The preview stops after five years. A valid year outside that window can produce no results even though the expression is valid.