Home › Convert › Azure Functions to AWS EventBridge
Convert Azure Functions cron to AWS EventBridge
Azure Functions expressions look similar to AWS EventBridge, but the differences matter. Paste yours below; the result is checked against the original run times.
What changes from Azure Functions to AWS EventBridge
- AWS EventBridge has no seconds field, so a schedule that fires on specific seconds cannot be converted exactly. The seconds value is dropped and flagged.
- Azure Functions numbers Sunday as 0, but AWS EventBridge uses 1-7 starting on Sunday. Every weekday number is increased by one (Monday-Friday becomes 2-6).
- AWS EventBridge requires a
?in exactly one of the two day fields. The converter puts it in the day field you did not use. - AWS EventBridge has a year field. The converter appends
*so the schedule repeats every year.
Worked examples
| Schedule | Azure Functions | AWS EventBridge |
|---|---|---|
| every minute | 0 * * * * * | * * * * ? * |
| every 5 minutes | 0 */5 * * * * | */5 * * * ? * |
| every 10 minutes | 0 */10 * * * * | */10 * * * ? * |
| every 15 minutes | 0 */15 * * * * | */15 * * * ? * |
| every 30 minutes | 0 */30 * * * * | */30 * * * ? * |
| every hour | 0 0 * * * * | 0 * * * ? * |
| every 2 hours | 0 0 */2 * * * | 0 */2 * * ? * |
| every 3 hours | 0 0 */3 * * * | 0 */3 * * ? * |
Conversions that come with a warning
- every 10 seconds:
*/10 * * * * *→* * * * ? *. AWS EventBridge has no seconds field; the seconds value "*/10" was dropped. - every 30 seconds:
*/30 * * * * *→* * * * ? *. AWS EventBridge has no seconds field; the seconds value "*/30" was dropped.
Field layout and time zones
second (0-59), minute (0-59), hour (0-23), day-of-month (1-31), month (1-12), day-of-week (0-6, 0 = Sunday).
Azure Functions evaluates NCRONTAB in UTC unless the WEBSITE_TIME_ZONE app setting is set; with it, the schedule adjusts for daylight saving. The setting is not supported on Linux Consumption or Flex Consumption plans.
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 Azure Functions, or open the Azure Functions builder or the AWS EventBridge builder.
Frequently asked questions
How do I convert a Azure Functions cron expression to AWS EventBridge?
Paste it into the converter above with Azure Functions as the source and AWS EventBridge as the target. For example, 0 * * * * * becomes * * * * ? *.
Is every Azure Functions expression convertible to AWS EventBridge?
Yes for the common schedules we tested (29 of 29), though unusual expressions with special characters might need manual review.
Does AWS EventBridge run in the same time zone as Azure Functions?
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.