GitHub Actions & AWS EventBridge Cron Guide: Avoiding UTC & DST Drift
Eliminate missed midnight jobs and unexpected 1-hour Daylight Saving Time shifts in cloud schedulers.
5-Field POSIX Cron vs. 6-Field AWS EventBridge Syntax
Linux crontab, GitHub Actions, and Kubernetes CronJobs all parse the standard 5-field expression: Minute, Hour, Day-of-Month, Month, and Day-of-Week. By contrast, AWS EventBridge requires 6 fields (adding a Year field at the end) and strictly forbids putting * in both Day-of-Month and Day-of-Week simultaneously—one of them must be ?.
Handling US Eastern & Pacific Daylight Saving Time Shifts
Because GitHub Actions workflows and default AWS EventBridge rules evaluate schedules in UTC, a report configured for 0 14 * * 1-5 runs at 9:00 AM EST during winter—but shifts to 10:00 AM EDT between March and November:
- On Kubernetes v1.27+, explicitly declare spec.timeZone: "America/New_York" on CronJob manifests when schedules track US business hours.
- On AWS EventBridge Scheduler, set ScheduleExpressionTimezone to "America/New_York" rather than adjusting UTC offsets twice a year.
- For critical billing or ETL scripts, combine concurrency guards or distributed locks so delayed cloud runners never execute duplicate runs concurrently.
Preview Exact US Eastern, Pacific & UTC Next Runs
Validate any 5-field cron expression visually and check its next 10 execution timestamps before deploying.