BackendBench
Coffee

Home › Convert › Apache Airflow to AWS EventBridge

Apache Airflow → AWS EventBridge

Convert Apache Airflow cron to AWS EventBridge

Apache Airflow 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 Apache Airflow to AWS EventBridge

    Worked examples

    ScheduleApache AirflowAWS 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

    Apache Airflow

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

    Airflow defaults to UTC. On a time-zone-aware DAG a cron schedule follows wall-clock time, so a daily 00:00 US/Eastern run moves between 04:00 and 05:00 UTC across daylight saving changes.

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

    Frequently asked questions

    How do I convert a Apache Airflow cron expression to AWS EventBridge?

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

    Is every Apache Airflow expression convertible to AWS EventBridge?

    Yes for the common schedules we tested (30 of 30), though unusual expressions with special characters might need manual review.

    Does AWS EventBridge run in the same time zone as Apache Airflow?

    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