Skip to main content
IAM Policy Map

AmazonEventBridgeFullAccess

AdminAWS managedActiveReviewedShow on mapCompare

Summary

Provides full access to Amazon EventBridge. The Amazon EventBridge User Guide says it grants permissions to use all EventBridge actions, including EventBridge Pipes, Schemas and Scheduler.

Permissions imported from the AWS Managed Policy Reference Guide; other sections reviewed against the listed AWS sources.

Identity

ARN
arn:aws:iam::aws:policy/AmazonEventBridgeFullAccess
Default version
v7
Created
Last edited
Services
events, iam, pipes, scheduler, schemas, secretsmanager

Control-plane actions (132)

By access level: 24 List, 4 Permissions management, 27 Read, 8 Tagging, 69 Write.

Control-plane actions by service
ServiceGrantedAccess levels and limitsGranted by
EventBridgeAll 71 actions (see the EventBridge page)15 List, 4 Permissions management, 12 Read, 2 Tagging, 38 Write; 0 restricted, 0 conditionalevents:*
IAM2 of 1902 Write; 2 restricted, 2 conditionaliam:CreateServiceLinkedRole, iam:PassRole
EventBridge PipesAll 10 actions (see the EventBridge Pipes page)1 List, 2 Read, 2 Tagging, 5 Write; 0 restricted, 0 conditionalpipes:*
EventBridge SchedulerAll 13 actions (see the EventBridge Scheduler page)3 List, 3 Read, 2 Tagging, 5 Write; 0 restricted, 0 conditionalscheduler:*
EventBridge SchemasAll 31 actions (see the EventBridge Schemas page)5 List, 9 Read, 2 Tagging, 15 Write; 0 restricted, 0 conditionalschemas:*
Secrets Manager5 of 271 Read, 4 Write; 5 restricted, 0 conditionalsecretsmanager:CreateSecret, secretsmanager:DeleteSecret, secretsmanager:GetSecretValue, secretsmanager:PutSecretValue, secretsmanager:UpdateSecret
IAM: 2 actions
  • iam:CreateServiceLinkedRole (Write)
  • iam:PassRole (Write)
Secrets Manager: 5 actions
  • secretsmanager:CreateSecret (Write)
  • secretsmanager:DeleteSecret (Write)
  • secretsmanager:GetSecretValue (Read)
  • secretsmanager:PutSecretValue (Write)
  • secretsmanager:UpdateSecret (Write)

Data-plane actions (3)

By access level: 3 Write.

Data-plane actions by service
ServiceGrantedAccess levels and limitsGranted by
EventBridgeAll 3 actions (see the EventBridge page)3 Write; 0 restricted, 0 conditionalevents:*

Excluded and conditional actions

No patterns are excluded by NotAction or Deny statements.

Resource scope and attachment

Resource scope across granted actions: mixed.

Can be attached: Yes, to users, groups and roles.

Why this tier

  • Grants at least 80% of the write and permissions-management actions of: events (45 of 45), pipes (5 of 5), scheduler (5 of 5), schemas (15 of 15).
  • Grants iam:PassRole, but only for scoped roles or under conditions (for example iam:PassedToService).

Guidance

Practical scope

The EventBridgeActions statement allows events:*, schemas:*, scheduler:* and pipes:* on Resource "*". Two statements allow iam:CreateServiceLinkedRole for the API destinations and Schemas service-linked roles. SecretsManagerAccessForApiDestinations allows secretsmanager:CreateSecret, UpdateSecret, DeleteSecret, GetSecretValue and PutSecretValue on secrets named events!*. Three statements allow iam:PassRole on arn:aws:iam::*:role/* when iam:PassedToService is events.amazonaws.com, scheduler.amazonaws.com or pipes.amazonaws.com.

Use cases

  • Give users, groups or roles full access to Amazon EventBridge, including EventBridge Pipes, EventBridge Schemas and EventBridge Scheduler.

Best practices

  • AWS managed policies don't grant least privilege permissions. The IAM User Guide suggests using IAM Access Analyzer to see which permissions principals actually use, then writing a custom policy or generating one with only the required permissions.

Security considerations

  • events:*, schemas:*, scheduler:* and pipes:* allow every action in those services on all resources.
  • iam:PassRole is allowed on any role (arn:aws:iam::*:role/*) when it is passed to EventBridge, Scheduler or Pipes. The IAM User Guide warns that a user should not be able to pass a role that has more permissions than you want the user to have.
  • The policy allows secretsmanager:GetSecretValue on secrets named events!*. The Amazon EventBridge User Guide says EventBridge requires the Secrets Manager permissions to manage secrets when you provide credentials through a connection for API destinations.
  • You cannot change the permissions in an AWS managed policy. If AWS updates the policy, the update affects every user, group and role it is attached to.

Assignment guidance

You can attach this policy to your users, groups and roles. The reference page also links to guidance on creating a permission set using AWS managed policies in IAM Identity Center. It fits where full access to Amazon EventBridge is intended.

Related policies

Same service

Same domain

Frequently asked questions

When should I attach AmazonEventBridgeFullAccess?
The Amazon EventBridge User Guide says it grants permissions to use all EventBridge actions, and the reference page says you can attach it to your users, groups and roles. Attach it where that scope is intended.
What does AmazonEventBridgeFullAccess grant?
It allows events:*, schemas:*, scheduler:* and pipes:* on all resources, service-linked role creation for API destinations and Schemas, Secrets Manager actions on secrets named events!*, and iam:PassRole to EventBridge, Scheduler and Pipes.
What are the security risks of AmazonEventBridgeFullAccess?
It allows every action in four services on all resources and iam:PassRole on any role to EventBridge, Scheduler and Pipes. The IAM User Guide warns against letting a user pass a role that has more permissions than you want the user to have. AWS managed policies don't grant least privilege permissions, and you must consider the security risk of granting principals more permissions than they need. AWS updates to the policy affect every identity it is attached to.

Policy JSON

Download policy.json

{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Sid": "EventBridgeActions",
      "Effect": "Allow",
      "Action": [
        "events:*",
        "schemas:*",
        "scheduler:*",
        "pipes:*"
      ],
      "Resource": "*"
    },
    {
      "Sid": "IAMCreateServiceLinkedRoleForApiDestinations",
      "Effect": "Allow",
      "Action": "iam:CreateServiceLinkedRole",
      "Resource": "arn:aws:iam::*:role/aws-service-role/apidestinations.events.amazonaws.com/AWSServiceRoleForAmazonEventBridgeApiDestinations",
      "Condition": {
        "StringEquals": {
          "iam:AWSServiceName": "apidestinations.events.amazonaws.com"
        }
      }
    },
    {
      "Sid": "IAMCreateServiceLinkedRoleForAmazonEventBridgeSchemas",
      "Effect": "Allow",
      "Action": "iam:CreateServiceLinkedRole",
      "Resource": "arn:aws:iam::*:role/aws-service-role/schemas.amazonaws.com/AWSServiceRoleForSchemas",
      "Condition": {
        "StringEquals": {
          "iam:AWSServiceName": "schemas.amazonaws.com"
        }
      }
    },
    {
      "Sid": "SecretsManagerAccessForApiDestinations",
      "Effect": "Allow",
      "Action": [
        "secretsmanager:CreateSecret",
        "secretsmanager:UpdateSecret",
        "secretsmanager:DeleteSecret",
        "secretsmanager:GetSecretValue",
        "secretsmanager:PutSecretValue"
      ],
      "Resource": "arn:aws:secretsmanager:*:*:secret:events!*"
    },
    {
      "Sid": "IAMPassRoleAccessForEventBridge",
      "Effect": "Allow",
      "Action": "iam:PassRole",
      "Resource": "arn:aws:iam::*:role/*",
      "Condition": {
        "StringLike": {
          "iam:PassedToService": "events.amazonaws.com"
        }
      }
    },
    {
      "Sid": "IAMPassRoleAccessForScheduler",
      "Effect": "Allow",
      "Action": "iam:PassRole",
      "Resource": "arn:aws:iam::*:role/*",
      "Condition": {
        "StringLike": {
          "iam:PassedToService": "scheduler.amazonaws.com"
        }
      }
    },
    {
      "Sid": "IAMPassRoleAccessForPipes",
      "Effect": "Allow",
      "Action": "iam:PassRole",
      "Resource": "arn:aws:iam::*:role/*",
      "Condition": {
        "StringLike": {
          "iam:PassedToService": "pipes.amazonaws.com"
        }
      }
    }
  ]
}

Version history

Current version v7, edited by AWS on 2026-02-12. Version history is recorded from 2026-11-11. Earlier versions are in the IAM console under Policy versions.

Attach snippets

AWS CLI

aws iam attach-role-policy --role-name ROLE_NAME --policy-arn arn:aws:iam::aws:policy/AmazonEventBridgeFullAccess
aws iam attach-user-policy --user-name USER_NAME --policy-arn arn:aws:iam::aws:policy/AmazonEventBridgeFullAccess
aws iam attach-group-policy --group-name GROUP_NAME --policy-arn arn:aws:iam::aws:policy/AmazonEventBridgeFullAccess

CloudFormation

Resources:
  ExampleRole:
    Type: AWS::IAM::Role
    Properties:
      AssumeRolePolicyDocument: {}  # replace with your trust policy
      ManagedPolicyArns:
        - arn:aws:iam::aws:policy/AmazonEventBridgeFullAccess

Terraform

resource "aws_iam_role_policy_attachment" "amazoneventbridgefullaccess" {
  role       = aws_iam_role.example.name
  policy_arn = "arn:aws:iam::aws:policy/AmazonEventBridgeFullAccess"
}

CDK (TypeScript)

role.addManagedPolicy(
  iam.ManagedPolicy.fromAwsManagedPolicyName("AmazonEventBridgeFullAccess"),
);

Sources