AmazonEventBridgeSchedulerFullAccess

Last Modified

Mar 12, 2026

March 12, 2026 at 09:27 PM UTC

Version

Total Versions

Created

Feb 12, 2026

Actions

Subscribe to updates

Risk

Medium

The same capabilities in a scoped form, resource policy writes, reads across all data, or full access to a whole service. Read from this policy document alone: trust policies, boundaries and SCPs in your account still decide what actually succeeds. How this is assessed

Medium
Can launch resources that run as a more privileged role
Grants the actions of 1 documented escalation path, but only on named resources or under a condition. Review that scope before trusting it.
- scheduler-001iam:PassRole + scheduler:CreateSchedulescoped
  - iam:PassRole: condition iam:PassedToService, on arn:aws:iam::*:role/*
Use with caution: Check which roles, users or policies fall inside the scope shown above. Within it the escalation works as documented, so keep privileged principals out of it.
Medium
Full scheduler access on every resource
Uses scheduler:* with Resource "*" and no condition, so every action AWS adds to that service later is granted too.
scheduler:*
Use with caution: The grant grows every time the service does. For long-lived access, prefer a policy that lists the actions you actually need.

Policy Document

View on GitHub

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27{
  "PolicyVersion": {
    "Document": {
      "Version": "2012-10-17",
      "Statement": [
        {
          "Effect": "Allow",
          "Action": "scheduler:*",
          "Resource": "*"
        },
        {
          "Effect": "Allow",
          "Action": "iam:PassRole",
          "Resource": "arn:aws:iam::*:role/*",
          "Condition": {
            "StringLike": {
              "iam:PassedToService": "scheduler.amazonaws.com"
            }
          }
        }
      ]
    },
    "VersionId": "v4",
    "IsDefaultVersion": true,
    "CreateDate": "2026-02-12T18:03:15+00:00"
  }
}