Cloud Scheduler Cron Standards & Quirks (2026)
Syntax rules, field counts, and timezone execution semantics across AWS, GCP, and Kubernetes.
| Cloud Platform | Field Count | Day-of-Week Index | Default Timezone | Special Characters | Official Docs |
|---|---|---|---|---|---|
| Kubernetes CronJob | 5 fields | 0-6 (0 = Sunday) | Kube-controller UTC | *, /, -, , | K8s Docs ↗ |
| AWS EventBridge | 6 fields | 1-7 (1 = Sunday) | Always UTC | ?, L, W, # | AWS Docs ↗ |
| Google Cloud Scheduler | 5 fields | 0-6 (0 = Sunday) | User-specified IANA | *, /, -, , | Google Cloud Docs ↗ |
Cron Syntax Standards in Cloud Architectures
Cron expressions are ubiquitous in modern cloud engineering—powering AWS EventBridge rules, Google Cloud Scheduler, Kubernetes CronJobs, and GitHub Actions workflows. However, subtle syntax variations between 5-field POSIX cron and 6-field quartz cron frequently cause misconfigured schedules.
Frequently Asked Questions
What are the 5 fields of a standard cron expression?
The five standard fields in order are: Minute (0-59), Hour (0-23), Day of the month (1-31), Month of the year (1-12 or JAN-DEC), and Day of the week (0-6 or SUN-SAT).
What does the asterisk (*) symbol mean in cron?
An asterisk is a wildcard that matches every possible value within that field. For example, an asterisk in the minute field means 'every minute'.
What does the slash (/) character represent?
A slash designates step values. For instance, '*/15' in the minute field specifies execution every 15 minutes starting at minute 0.