- Newest
- Most votes
- Most comments
Hi there, yes I already added trusted entities like this, but still got the error when creating the scheduler.
An execution role is an IAM role that EventBridge Scheduler assumes in order to interact with other AWS services on your behalf. You attach permission policies to this role to grant EventBridge Scheduler access to invoke targets.
Please see a reference example for the same : https://docs.aws.amazon.com/scheduler/latest/UserGuide/setting-up.html
Yes, followed the doc for both "Create new role" or "Use existing role" but still stuck with the error "The execution role you provide must allow AWS EventBridge Scheduler to assume the role."
This can occur when there is no "sts:AssumeRole" in "scheduler.amazonaws.com" in the trusted entity of the execution role that was set when creating the EventBridge Scheduler.
Check to see if the following entities are set up.
{
"Version": "2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Principal": {
"Service": "scheduler.amazonaws.com"
},
"Action": "sts:AssumeRole"
}
]
}
I gave up and switched to Google Cloud Scheduler https://firebase.google.com/docs/functions/schedule-functions, everything working fine now. Thanks all!
I created an rule with this condition below, after that I created an scheduled to reboot EC2 instances.
{ "Version": "2012-10-17", "Statement": [ { "Effect": "Allow", "Action": [ "sts:AssumeRole", "scheduler:*" ], "Resource": [ "*" ] } ] }
Relevant content
- Accepted Answerasked 6 months ago
- asked 6 months ago
- asked a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago
Can I set it up by changing aws:SourceArn as follows?
Hi there, tried update aws:SourceAccount as your suggested, but still got the error "The execution role you provide must allow AWS EventBridge Scheduler to assume the role."
Is the "condition" part absolutely necessary? If it is not needed, it can be deleted.