You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/connections/destinations/catalog/amazon-eventbridge/index.md
+14-12Lines changed: 14 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,27 +8,29 @@ id: 5d1994fb320116000112aa12
8
8
In addition to already supported destinations like Kinesis, S3, and Redshift, you can use EventBridge to selectively route streaming data into Amazon SQS, SNS, and any service supported by [AWS CloudWatch Events](https://docs.aws.amazon.com/AmazonCloudWatch/latest/events/WhatIsCloudWatchEvents.html){:target="_blank”}.
9
9
10
10
11
-
## Getting Started
11
+
## Getting started
12
12
13
-
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.
14
-
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.
13
+
To set up:
14
+
15
+
1. In Segment, provide your AWS Account ID and the region you'd like to configure the Segment Partner Event Source in. Ensure the same region is selected in both Segment and AWS.
16
+
2. Once you send an event through with the destination enabled, Segment creates a Partner Event Source in Amazon EventBridge. You can then activate this source in the AWS Console.
15
17
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.
16
18
17
-
The Event Source will be denoted by your Segment Source ID, which you can find in your Source Settings page under API Keys.
19
+
The Event Source will be denoted by your Segment Source ID, which you can find in Source Settings under API Keys.
18
20
19
-
We'll forward all the messages in the source (pending any Destination Filters you've enabled) to the Segment Partner Event Source we create for you in EventBridge.
21
+
All messages in the source (pending any Destination Filters you've enabled) are fowarded to the Segment Partner Event Source, created in EventBridge.
20
22
21
23
> info "Create a separate Segment source for testing"
22
-
> Segment recommends that you create a separate Segment source for testing if you use a test Account ID, because you cannot change the test Account ID to a production Account ID at a later date.
24
+
> Segment recommends that you create a separate Segment source for testing if you use a test Account ID. You **cannot change** the test Account ID to a production Account ID later.
23
25
24
26
## Page
25
-
If you're not familiar with the Segment Specs, take a look to understand what the [Page method](/docs/connections/spec/page/)does. An example call would look like:
27
+
If you're not familiar with the Segment Specs, review the [Page method](/docs/connections/spec/page/)docs for more detail. An example Page call is as follows:
26
28
```javascript
27
29
analytics.page();
28
30
```
29
31
30
32
## Identify
31
-
If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](/docs/connections/spec/identify/)does. An example identify call is shown below:
33
+
If you're not familiar with the Segment Specs, review the [Identify method](/docs/connections/spec/identify/)docs for more detail. An example Identify call is as follows:
If you're not familiar with the Segment Specs, take a look to understand what the [Track method](/docs/connections/spec/track/)does. An example identify call is shown below:
42
+
If you're not familiar with the Segment Specs, review the [Track method](/docs/connections/spec/track/)docs for more detail. An example Track call is as follows:
You are only able to configure one AWS Account ID per source. Once you've configured your Amazon EventBridge destination with an AWS Account ID, it is not possible to modify it. If you do need to change the AWS Account ID for any reason, you will need to create a new Segment source and configure a new destination.
53
+
####Can I change my AWS Account ID?
54
+
You can only configure one AWS Account ID per source. Once you've configured your Amazon EventBridge destination with an AWS Account ID, you cannot modify it. If you need to change the AWS Account ID, you need to create a new Segment source and configure a new destination.
53
55
54
-
As an alternative, you can use a [Repeater destination](/docs/connections/destinations/catalog/repeater/) to your existing source, which repeats the events through the new source you create. This new source can then be connected to a new EventBridge destination which can be configured with a new Account ID in the settings.
56
+
Alternatively, you can sync a [Repeater destination](/docs/connections/destinations/catalog/repeater/) to your existing source. It repeats the events through the new source you've created. This new source can then be connected to a new EventBridge destination which can be configured with a new Account ID in the settings.
0 commit comments