- 最新
- 最多得票
- 最多評論
Thank you both, appreciate the effort. Its a shame as I'm sure peeps would find it useful. I might go with trying the separate lambda first and see which ones least messy, but yes thanks for the logic on the Tuesdays timing, that could work. I'm doing this 3rd Tuesday of month etc, so I will have a play and see who wins :0) Anyone from AWS who wants a project ahem.. 'AWS maintenance scheduler' 'TM' Thanks G
Yes, endtime must be after begintime. With the way one-sided periods currently work they are not really appropriate for designating a "not-running" period. You can get the behavior you want by thinking of the inverse of your "not-running" period. The running periods (which are what instance scheduler expects) are all days of the week except Tuesday, from 00:00 to 18:00 on Tuesday, and from 19:00 to 23:59 on Tuesday. With this approach Instance Scheduler will also start your instance at midnight.
相關內容
AWS 官方已更新 2 年前- AWS 官方已更新 2 年前
If your use-case is narrow (just the one schedule/maintenance period), I would recommend investigating, in order of increasing complexity: EventBridge scheduled Rules, EventBridge Scheduler, or Resource Scheduler (SSM Quick Setup), before implementing something custom. Instance Scheduler is more appropriate if you need centrally managed schedules operating across accounts, regions, and services.