Start an aggregation at 02:00 Japan time.
Make the time zone and daylight-saving behavior explicit instead of applying manual UTC corrections.
Which automation approach is most appropriate?
Use EventBridge Scheduler with an explicit time zone and review execution-window and duplicate-run behavior.
Detailed explanation
The schedule can be evaluated in the selected regional time zone instead of relying on manual conversion.
The schedule can be evaluated in the selected regional time zone instead of relying on manual conversion.
Lifecycle rules manage objects, not ETL scheduling.
Lifecycle rules manage objects, not ETL scheduling.
A fixed conversion can run at the wrong local time when rules change.
A fixed conversion can run at the wrong local time when rules change.
Continuous polling adds runtime cost and complexity.
Continuous polling adds runtime cost and complexity.
Check official documentation
Compare the following points with the official documentation.
Amazon EventBridge Scheduler time zones、cron、flexible time windowの公式説明を確認する。
What to confirm
UTC固定のcronとタイムゾーン指定スケジューラの違いを説明できる。
Key points
- EventBridge Scheduler
- Time zone
- UTC
- Daylight saving time
Notes
- Environment: AWS公式DEA-C01試験ガイドと各サービスの公式ドキュメントの確認
- Confirm current AWS service behavior in the official DEA-C01 documentation.
Foundation review
Dual timestamps
Record both UTC and business-local time when reconciling data windows.
Execution window
A flexible window can spread load but must remain within the business deadline.