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 allows you to configure Amazon EventBridge as a destination to which you can send your event data seamlessly.

Find the open source transformer code for this destination in the GitHub repository.

Getting started

In order to enable dumping data to Amazon EventBridge, you will first need to add it as a destination to the source from which you are sending event data. Once the destination is enabled, events from RudderStack will start to flow to Amazon EventBridge. Before configuring your source and destination on the RudderStack app, please check whether the platform you are working on is supported by Amazon EventBridge. Refer to the table below:

Connection ModeWebMobileServer
Device mode---
Cloud modeSupportedSupportedSupported
To know more about the difference between cloud mode and device mode in RudderStack, refer to the RudderStack Connection Modes guide.

Once you have confirmed that the platform supports sending events to EventBridge, perform the steps below:

  • Set up a source in the RudderStack dashboard.
  • Select the destination as Amazon EventBridge. Give your destination a name and then click on Continue.
  • Next, in the Settings section, fill all the fields with the relevant information and click Next.

A brief description of each of these fields is mentioned below:

image  70
  • AWS Credentials
    • AWS Region: Enter the AWS region in which you have created the EventBridge bus.This is a required field.
    • The AWS Access Key ID and AWS Secret Access Key are required to authorize RudderStack in order to write to the configured event bus.
To authorize RudderStack, you will 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.
Note that if the AWS credentials are already configured on your machine where the RudderStack server is set up, you will not need the security credentials.

The following snippet shows an example of a permissions policy that allows a user to put event data into Kinesis:

{
"Version": "2012-10-17",
"Statement": [
{
"Sid": "CloudWatchEventsInvocationAccess",
"Effect": "Allow",
"Action": ["kinesis:PutRecord"],
"Resource": "*"
}
]
}
  • EventBridge Settings
    • Event Bus Name: Specify the name of the event bus you want to send the events to. If no event bus name is specified, the event will be sent to the default bus.
    • Detail Type: Specify the value for detail-type , which you would like to send to EventBridge.This is a required field.
  • Amazon Resources
    • Amazon Resource Name: This field contains an ARN (Amazon Resource Name) that identifies a resource that is involved in your EventBridge setup. To add multiple ARNs (for targets which might be involved in your setup), you can click on + ADD MORE.

Sending events to Amazon EventBridge

We map a RudderStack event to an EventBridge event in the following manner:

RudderStackEventBridge
Event payloadDetail
Amazon Resource NameResources
Detail TypeDetailType
Event Bus NameEventBusName
"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.

Contents