Amazon EventBridge rules - Amazon EventBridge
Services or capabilities described in Amazon Web Services documentation might vary by Region. To see the differences applicable to the China Regions, see Getting Started with Amazon Web Services in China (PDF).

Amazon EventBridge rules

You specify what EventBridge does with the events delivered to each event bus. To do this, you create rules. A rule specifies which events to send to which targets for processing. A single rule can send an event to multiple targets, which then run in parallel.

You can create two types of rules:

  • Rules that match on event data

    You can create rules that match against incoming events based on event data criteria (called an event pattern). An event pattern defines the event structure and the fields that a rule matches. If an event matches the criteria defined in the event pattern, EventBridge sends it to the target(s) you specify.

    For more information, see Creating Amazon EventBridge rules that react to events.

  • Rules that run on a schedule

    You can also create rules that sends events to the specified targets at specified intervals. For example, to periodically run an Lambda function, you can create a rule to run on a schedule.


    EventBridge offers Amazon EventBridge Scheduler, a serverless scheduler that allows you to create, run, and manage tasks from one central, managed service. EventBridge Scheduler is highly customizable, and offers improved scalability over EventBridge scheduled rules, with a wider set of target API operations and Amazon services.

    We recommend that you use EventBridge Scheduler to invoke targets on a schedule. For more information, see Using Amazon EventBridge Scheduler with Amazon EventBridge.

The following video goes over the basics of rules:

Amazon EventBridge managed rules

In addition to the rules you create, Amazon services can create and manage EventBridge rules in your Amazon account that are needed for certain functions in those services. These are called managed rules.

When a service creates a managed rule, it can also create an IAM policy that grants permission to that service to create the rule. IAM policies created this way are scoped narrowly with resource-level permissions to allow the creation of only the necessary rules.

You can delete managed rules by using the Force delete option, but you should only delete them if you're sure that the other service no longer needs the rule. Otherwise, deleting a managed rule causes the features that rely on it to stop working.