We want to move towards storing all the scheduled event parameters inside a database as opposed to within the provided JSON of the given CloudWatch Rule. Couple sweet benefits:
We can develop a nice UI for creating new rules and retroactively altering them.
We remove the risk of mismatching query intervals with rule schedules. (see #56)
We can key in a logging table and get custom per-job usage history
We want to move towards storing all the scheduled event parameters inside a database as opposed to within the provided JSON of the given CloudWatch Rule. Couple sweet benefits: