BackendBench
Coffee

Home › Convert › Kubernetes to AWS EventBridge

Kubernetes → AWS EventBridge

Convert Kubernetes cron to AWS EventBridge

Kubernetes expressions look similar to AWS EventBridge, but the differences matter. Paste yours below; the result is checked against the original run times.

Result

    What changes from Kubernetes to AWS EventBridge

    Worked examples

    ScheduleKubernetesAWS EventBridge
    every minute* * * * ** * * * ? *
    every 5 minutes*/5 * * * **/5 * * * ? *
    every 10 minutes*/10 * * * **/10 * * * ? *
    every 15 minutes*/15 * * * **/15 * * * ? *
    every 30 minutes*/30 * * * **/30 * * * ? *
    every hour0 * * * *0 * * * ? *
    every 2 hours0 */2 * * *0 */2 * * ? *
    every 3 hours0 */3 * * *0 */3 * * ? *

    Field layout and time zones

    Kubernetes

    minute (0-59), hour (0-23), day-of-month (1-31), month (1-12), day-of-week (0-7, 0 and 7 = Sunday).

    Set spec.timeZone (Kubernetes 1.27+) to a name like Asia/Kolkata. Without it the schedule follows the controller's time zone, usually UTC.

    AWS EventBridge

    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 Kubernetes, or open the Kubernetes builder or the AWS EventBridge builder.

    Frequently asked questions

    How do I convert a Kubernetes cron expression to AWS EventBridge?

    Paste it into the converter above with Kubernetes as the source and AWS EventBridge as the target. For example, * * * * * becomes * * * * ? *.

    Is every Kubernetes 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 Kubernetes?

    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.

    More tools you might need