4 ms·
This isn’t using S3 as a scheduler. Cloudwatch already supports cron and rate expressions, as the post alluded to. This is a hack to schedule something once. A
by jimmytucson 8y ago
This isn’t using S3 as a scheduler. Cloudwatch already supports cron and rate expressions, as the post alluded to. This is a hack to schedule something once.
All Cloudwatch would have to do is implement a recurrence = 1 feature but I’m guessing it's not a common enough use case.
- scarface74 8y agoIt supports the year it should be scheduled. You could specify the exact time for it to be scheduled.
- nivertech 8y agoI think there is a limit on a number of scheduled events per account per region. So when doing one-time events (by specifying a year) - the triggered lambda need to delete it. Or have a hourly scheduled lambda to delete already fired one-time events. Or maybe CloudWatch is so smart it can delete them by itself?
- scarface74 8y agoYou would have to delete the rule. In theory, it’s just like deleting an item from a queue once it has been processed. Another advantage is that you could look in the console to see which overdue rules haven’t been deleted. And if you really need more than 50 rules, it’s just a soft limit. You send a request to support and they will raise it.