Skip to content

Commit 5448df4

Browse files
[EventBridge Actions] - new Destination
1 parent cb09fc2 commit 5448df4

File tree

2 files changed

+26
-2
lines changed
  • src/connections/destinations/catalog

2 files changed

+26
-2
lines changed
Lines changed: 26 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,26 @@
1+
# 💥 Segment Partner Actions Destination Documentation Template
2+
---
3+
title: Amazon EventBridge (Actions) Destination
4+
---
5+
6+
{% include content/plan-grid.md name="actions" %}
7+
8+
> (delete after reading) Include a 1-2 sentence introduction to your company and the value it provides to customers - updating the name and hyperlink. Please leave the utm string unchanged.
9+
10+
[Amazon EventBridge (Actions)](https://yourintegration.com/?utm_source=segmentio&utm_medium=docs&utm_campaign=partners){:target="_blank”} is a serverless event bus that routes real-time data between applications, AWS services, and SaaS tools — making it easy to build scalable, event-driven systems without custom integration code.
11+
12+
This destination is maintained by Segment. For any issues with the destination, [contact the Segment Support team](mailto:[email protected]).
13+
14+
## Getting started
15+
16+
1. From your workspace's [Destination catalog page](https://app.segment.com/goto-my-workspace/destinations/catalog){:target="_blank”} search for "Amazon EventBridge (Actions)".
17+
2. Select Amazon EventBridge (Actions) and click **Add Destination**.
18+
3. Choose the Source you want to connect to Amazon EventBridge (Actions).
19+
4. In your AWS account, find the EventBridge event bus. Copy your AWS Account ID, then paste it into the AWS Account ID field in Segment.
20+
5. In Segment, select the appropriate **AWS Region** for your EventBridge destination.
21+
6. Go to the Mappings tab, click New Mapping, then choose the **Send** mapping type. Configure your trigger and field mappings as needed.
22+
7. Before saving your mapping, click the **Create Partner Source** button. This step is required. Without it, data will not flow to EventBridge.
23+
8. Save and enable your Mapping.
24+
9. Enable the Destination
25+
26+
{% include components/actions-fields.html %}

src/connections/destinations/catalog/amazon-eventbridge/index.md

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -10,8 +10,6 @@ In addition to already supported destinations like Kinesis, S3, and Redshift, yo
1010

1111
## Getting Started
1212

13-
14-
1513
1. Provide Segment your AWS Account ID and the region you'd like us to configure the Segment Partner Event Source in. Ensure you've provided the same region in Segment where you'd like to configure your Event Bus.
1614
2. Once you send an event through with the destination enabled, we'll create a Partner Event Source in Amazon EventBridge, which you can activate in the AWS Console.
1715
3. Use the [AWS Console](http://console.aws.amazon.com/events/){:target="_blank”} to configure rules and destinations for the events in your Segment Partner Event Source.

0 commit comments

Comments
 (0)