> For the complete documentation index, see [llms.txt](https://rudderlabs.gitbook.io/rudderlabs-1/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://rudderlabs.gitbook.io/rudderlabs-1/docs/destinations/streaming-platforms/amazon-eventbridge.md).

# Amazon EventBridge

[Amazon EventBridge](https://aws.amazon.com/eventbridge/) is a serverless event bus that allows you to connect applications using data from your own apps, integrated SaaS applications, or AWS services. You can collect streams of real time data from a variety of event sources such as Zendesk, Pagerduty, and more, and route them to your preferred endpoints such as AWS Lambda. EventBridge also allows you to set up routing rules that determine where and how to send your data to your application, and how it reacts to the data sources in real-time.

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 our** [**GitHub repo**](https://github.com/rudderlabs/rudder-transformer/tree/master/v0/destinations/eventbridge)**.**

## **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 Mode** | **Web**       | **Mobile**    | **Server**    |
| ------------------- | ------------- | ------------- | ------------- |
| **Device mode**     | -             | -             | -             |
| **Cloud mode**      | **Supported** | **Supported** | **Supported** |

To know more about the difference between Cloud mode and Device mode in RudderStack, read the [RudderStack connection modes](https://rudderstack.com/docs/rudderstack-cloud/rudderstack-connection-modes/) guide.

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

* Choose a source to which you would like to add Amazon EventBridge as a destination.

Please follow our [Adding a Source](https://www.rudderstack.com/docs/rudderstack-cloud/sources/#adding-a-source) guide to know how to add a source in RudderStack.

* Select the destination as **Amazon EventBridge** to your source. Give your destination a name and then click on **Next**.
* 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:

![](/files/znNMdqaSc0L4V68o9Sxq)EventBridge Destination Settings on the RudderStack Dashboard

* **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. Please refer to the [Using Identity-Based Policies (IAM Policies) for EventBridge](https://docs.aws.amazon.com/eventbridge/latest/userguide/iam-identity-based-access-control-eventbridge.html) guide to know the applicable policies.

Please 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:

```javascript
{
  "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:

| 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.

## FAQs

### Why are the events not visible on my EventBridge target?

Verify that you are sending the events in the **Live Events** tab of your source.

![](/files/4zn2OfaxN833sa3mk1lS)Live Events in Source Details Page

You can also check for any delivery failures in the **Live Events** tab of your destination.

![](/files/euIVQ96hFYojeFURvyiJ)Live Events in the Destination Details Page

## Contact Us

If you come across any issues while configuring AWS EventBridge as a destination with RudderStack, please feel free to [contact us](mailto:%20docs@rudderstack.com). You can also start a conversation in our [Slack](https://rudderstack.com/join-rudderstack-slack-community) community; we will be happy to talk to you!


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://rudderlabs.gitbook.io/rudderlabs-1/docs/destinations/streaming-platforms/amazon-eventbridge.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.