AWS teams struggle to keep scheduled jobs aligned with local time
In the cited requests, developers using Terraform or CDK to manage CloudWatch event rules wanted jobs to run at a consistent local time through daylight-saving changes. Their reported workarounds included seasonal edits to infrastructure definitions or manual console changes, which add operational effort and risk. The clock-synchronization and desktop-clock requests are adjacent time-related needs, but point to different products.
For AWS infrastructure developers using Terraform or CDK. Mentioned from Oct 2020 to Dec 2025 on GitHub and Hacker News.
5 different people described this problem in 4 separate discussions.
- Indie fit
- 5.0/10
- Pain
- 5.6/10
- Frequency
- 6.5/10
- Willingness to pay
- 0.0/10
- Momentum
- 5.0/10
- Who pays
- Businesses
- Competition
- Medium
- Build difficulty
- Low
What people said
Quoted word for word. Follow a link to read the whole discussion.
The only workaround I've thought of is to edit the terraform definitions every spring & fall to shift things by one hour, which is clearly pretty inconvenient and error-prone
For timezones such as Europe/London, currently if I want the schedule to be consistent all year around I need to manually update this field in the console after creating the Rule via CDK
Build brief
See what to build and who will buy it
- 1 product idea with the smallest useful version and pricing
- 3 places to find your first customers
- 3 more quotes from people who have this problem
- Current workarounds, existing solutions and risks