AWS SAM Parameter ScheduleExpression is not valid when adding day of week - amazon-web-services

I am making a CloudWatch event and I need it to run every Friday at 11pm UTC. I attempted to turn this on by doing cron(0 23 * * FRI *) which according to all documentation I could find, is perfectly correct syntax. However it was failing every time I tried to deploy it.

I found the issue was that if you set a day of the week specifically, then you can not set the third parameter to * it needs to be set to ?. This makes logic sense because the third parameter is Day of Month and so you can't have it run every day of the month AND every Friday. Updating to
cron(0 23 ? * FRI *) solved the problem for me.
An important and I suppose obvious note when setting cron values: Think about how each value affects the other values you've set. Does each one make logical sense in conjunction with the others?

Related

Google Cloud Scheduler trigger last day of month

I want to create a trigger in Google Cloud Scheduler that runs at 9am on the 25th and the last day of each month (depending of the month that would be 28, 30, or 31th).
I assumed somethink like this might work, but GCP does not understand the L-syntax:
0 9 25,L * *
Any (elegant) ideas how to do it without having multiple triggers?
One trigger, with minimized overhead calls:
0 0 25,28-31 * *
Then, inside the function:
IF is25() OR islastDayOfMonthHelper()
work
ELSE
return
I just want to mention two alternative options I see for the end of month part of the question.
Simply run the function just past midnight to the 1st of each month. Depending on your use case this may be good enough.
Reschedule the function each month to the specific date which will be the last day of the next month.

AWS cron jobs to run every minute across a span of time across two hours?

I have a Lambda function on AWS scheduled using the following cron expression:
* 19-20 ? * SAT *
So it runs every minute from 19:00 - 20:59 on Saturdays. In reality, though, it really just needs to run from 19:50 - 20:30 on Saturdays, and my current setup is costing me money for no good reason. Is there any way to specify that with a cron expression (or is there another AWS scheduling mechanism I could use to accomplish this)?
I think you have to split it to two expressions:
From 19:50-19:59:
50/1 19 ? * SAT *
From 20:00-20:30:
0-30/1 20 ? * SAT *

Cloud scheduler trigger on the first monday of each month

I'm trying to schedule a job to trigger on the first Monday of each month:
This is the cron expression I got: 0 5 1-7 * 1
(which ,as far as I can read unix cron expressions, triggers at 5:00 am on Monday if it happens to be in the first 7 days of the month)
However the job is triggered on what seems to be random days at 5:00 am. the job was triggered today on the 16 of Aug!
Am I reading the expression awfully wrong? BTW, I'm setting the timezone to be on AEST, if that makes difference.
You can use the legacy cron syntax to describe the schedule.
For your case, specify something like below:
"first monday of month 05:00"
Do explore the "Custom interval" tab in the provided link, to get better understanding on this.

AWS Cloudwatch event rule: Start and stop time

Is it possible to set start and stop time of cloudwatch event rules?
Use Case - I want to create a rule which triggers a lambda, but I want it to run at a specific date (every 2 minutes) and disable it at another date (these date interval can span across months).
As far as I know, when we create a rule (rate (2 minutes)), it starts running immediately. I can use this approach and in the lambda I can check if the current date is same as target date and proceed with lambda execution, and disable the rule when current date is greater than end date. Although, it might work but it does not seem the right approach since lambda would be unnecessarily executing until the target date.
Is there any way I can achieve the same thing without the hack?
Yes, you can set it to specific date only. For instance the following rule 0/2 0 28 9 ? 2020 would execute every 2 minutes on 28 Sep 2020 only:
Update
To span across months, I think you need separate rules. For example you could define two rules to span date range 28 Sep to finish 5 Oct: 0/2 0 28-31 9 ? 2020 and 0/2 0 1-5 10 ? 2020.

Run Amazon CloudWatch Event every Sunday at 10:00 am UTC

I have already read Amazon CloudWatch Events - Schedule Expressions for Rules.
Now I want to trigger an event every Sunday at 10:00 am and I am confused if this is correct?
Currently I have cron(0 10 * * SUN *) & cron(0 10 ? * SUN *)
I don't know the difference between ? & * in Cronjob. So which one is correct is confusing?
Side Note
What is the difference between rate and schedule because rate is simpler to use so I can do like rate(7 days) but I don't know when it will run?
Will it run every 7 days from the moment of deployment?
That page says:
You can't specify the Day-of-month and Day-of-week fields in the same cron expression. If you specify a value (or a *) in one of the fields, you must use a ? (question mark) in the other.
It also says:
A rate expression starts when you create the scheduled event rule, and then runs on its defined schedule.
To run every Sunday at 10:00 AM UTC,
cron(0 10 ? * SUN *) or cron(0 10 ? * 1 *)
Use ? for Day-of-month part when Day-of-week has a value(here, SUN or 1) because when you want to run only on a specific day of the week, you can't use *, you can't say run everyday. Instead, we should say run one or another day of the month, using ?, which will be every Sunday of the month because we have set Day-of-week.
Refer Schedule Expressions for all details