Amazon EventBridge is a serverless event bus that allows you to connect applications using data from your own apps, integrated SaaS applications, or AWS services.
RudderStack supports Amazon EventBridge as a destination where you can seamlessly send your event data.
Getting started
RudderStack supports sending event data to EventBridge via the following connection modes:
| Connection Mode | Web | Mobile | Server | 
|---|---|---|---|
| Device mode | - | - | - | 
| Cloud mode | Supported | Supported | Supported | 
Once you have confirmed that the source platform supports sending events to EventBridge, follow these steps:
- From your RudderStack dashboard, add the source. Then, from the list of destinations, select AWS EventBridge.
 - Assign a name to your destination and click Continue.
 
Connection settings
To successfully set up EventBridge as a destination, you need to configure the following settings:
- AWS Region: Enter the AWS region in which you have created the EventBridge bus. This is a required field.
 - Role-based Authentication: Enable this setting to use the RudderStack IAM role for authentication. For more information on creating an AWS IAM role for RudderStack, refer to this guide.
- IAM Role ARN: Enter the ARN of the IAM role.
 
 
- If Role-based Authentication is disabled, you need to enter the AWS Access Key ID and AWS Secret Access Key to authorize RudderStack in order to write to the configured event bus.
 
- Event Bus Name: Specify the name of the event bus where you want to send the events. RudderStack sends the event to the default bus if no event bus name is specified.
 - Detail Type: Specify the event's detail type to send to EventBridge. This is a required field.
 - Amazon Resource Name: This field contains an ARN (Amazon Resource Name) that identifies a resource involved in your EventBridge setup. To add multiple ARNs (for multiple targets involved in your setup), click + ADD MORE.
 
Policy permissions
To authorize RudderStack, you need to create an IAM policy that provides the required permission to write to your event bus. Refer to the Using Identity-Based Policies (IAM Policies) for EventBridge guide to know the applicable policies.
A sample permissions policy that allows a user to put event data into EventBridge is shown below:
{  "Version": "2012-10-17",  "Statement": [    {      "Sid": "CloudWatchEventsInvocationAccess",      "Effect": "Allow",      "Action": ["events:PutEvents"],      "Resource": "*"    }  ]}Sending events to EventBridge
You can map a RudderStack event to an EventBridge event in the following manner:
| RudderStack | EventBridge | 
|---|---|
| Event payload | Detail | 
| Amazon Resource Name | Resources | 
| Detail Type | DetailType | 
| Event Bus Name | EventBusName | 
"rudderstack" | Source | 
- Event Payload: This is the generated event payload
 - Amazon Resource Name, Detail Type, Event Bus Name: These are the values you configured while setting up the destination with RudderStack.
 
Contact us
For more information on the topics covered on this page, email us or start a conversation in our Slack community.