BackendBench
Coffee

Home › Convert › GitHub Actions to AWS EventBridge

GitHub Actions → AWS EventBridge

Convert GitHub Actions cron to AWS EventBridge

GitHub Actions 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 GitHub Actions to AWS EventBridge

    Worked examples

    ScheduleGitHub ActionsAWS EventBridge
    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 * * ? *
    every 6 hours0 */6 * * *0 */6 * * ? *

    Field layout and time zones

    GitHub Actions

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

    GitHub Actions schedules are always UTC. Convert your local time to UTC before writing the expression.

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

    Frequently asked questions

    How do I convert a GitHub Actions cron expression to AWS EventBridge?

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

    Is every GitHub Actions expression convertible to AWS EventBridge?

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

    Does AWS EventBridge run in the same time zone as GitHub Actions?

    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