Schedule format reference

Syntax

[time-range] [day-spec] [timezone?]

The time range must precede the day specification. Both are required unless using a named preset. The timezone suffix is optional — see Timezone resolution.

Time range

Hour precision

H-H

Single or double-digit hours in 24-hour format.

Example	Start	End
`9-17`	9:00 AM	5:00 PM
`0-23`	Midnight	11:00 PM
`8-18`	8:00 AM	6:00 PM

Minute precision

HHMM-HHMM

Zero-padded 4-digit times.

Example	Start	End
`0800-1730`	8:00 AM	5:30 PM
`0900-1700`	9:00 AM	5:00 PM
`0630-2200`	6:30 AM	10:00 PM

Day specification

Value	Days
`mon`	Monday only
`tue`	Tuesday only
`wed`	Wednesday only
`thu`	Thursday only
`fri`	Friday only
`sat`	Saturday only
`sun`	Sunday only
`mon-fri`	Monday through Friday
`weekdays`	Monday through Friday (alias)
`sat-sun`	Saturday and Sunday
`weekends`	Saturday and Sunday (alias)
`mon-sun`	All days
`daily`	All days (alias)

Day ranges use the order Monday → Sunday. wed-fri is valid; fri-wed is not.

Named presets

Value	Equivalent	Description
`weekdays-business-hours`	`9-17 mon-fri`	Mon–Fri, 9 AM–5 PM
`always-on`	—	No schedule, always running
`always-off`	—	No schedule, always stopped

Timezone resolution

Times are interpreted using the first timezone that resolves in this order:

Priority	Source	Example
1	Explicit suffix on the tag	`9-17 mon-fri CET`
2	Resource’s AWS region	`eu-west-3` → `Europe/Paris`
3	Stack `Timezone` CloudFormation parameter	`Europe/London`
4	UTC	fallback

Timezone suffix

Append a timezone abbreviation (case-insensitive) after the day specification:

9-17 mon-fri CET
0830-1730 mon-fri BST
8-18 weekdays EST

Supported abbreviations: UTC, GMT, BST, CET, CEST, EET, EEST, EST, EDT, CST, CDT, MST, MDT, PST, PDT, IST, JST, AEST, AEDT, ACST, ACDT, AWST.

Region defaults

If no suffix is given, the resource’s own AWS region determines the timezone. Resources in different regions each get the correct local time automatically, even within the same account.

AWS Region	Default timezone
`us-east-1`	America/New_York
`us-east-2`	America/New_York
`us-west-1`	America/Los_Angeles
`us-west-2`	America/Los_Angeles
`eu-west-1`	Europe/Dublin
`eu-west-2`	Europe/London
`eu-west-3`	Europe/Paris
`eu-central-1`	Europe/Berlin
`eu-north-1`	Europe/Stockholm
`ap-southeast-1`	Asia/Singapore
`ap-southeast-2`	Australia/Sydney
`ap-northeast-1`	Asia/Tokyo
`ap-south-1`	Asia/Kolkata

Examples

9-17 mon-fri              Monday–Friday, 9 AM–5 PM (resource region timezone)
8-18 weekdays             Monday–Friday, 8 AM–6 PM (resource region timezone)
0800-1730 mon-fri         Monday–Friday, 8:00 AM–5:30 PM (resource region timezone)
9-17 mon-fri CET          Monday–Friday, 9 AM–5 PM Central European Time
0830-1730 mon-fri BST     Monday–Friday, 8:30 AM–5:30 PM British Summer Time
8-18 weekdays EST         Monday–Friday, 8 AM–6 PM Eastern Standard Time
10-16 weekends            Saturday–Sunday, 10 AM–4 PM (resource region timezone)
weekdays-business-hours   Monday–Friday, 9 AM–5 PM (resource region timezone)

Validation rules

Time must come before days (9-17 mon-fri ✓, mon-fri 9-17 ✗)
Hours must be 0–23
Minutes must be 0–59
End time must be after start time
Day ranges must follow Monday → Sunday order

If the schedule tag value is invalid, the resource will still appear in the dashboard with a parse error notice. No EventBridge rules will be created until the value is corrected.