Skip to content

Commit 9482c27

Browse files
authored
page cleanup + edits
1 parent 191c16c commit 9482c27

File tree

1 file changed

+14
-12
lines changed
  • src/connections/destinations/catalog/amazon-eventbridge

1 file changed

+14
-12
lines changed

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

Lines changed: 14 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -8,27 +8,29 @@ id: 5d1994fb320116000112aa12
88
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”}.
99

1010

11-
## Getting Started
11+
## Getting started
1212

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

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

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

2123
> 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.
2325
2426
## 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:
2628
```javascript
2729
analytics.page();
2830
```
2931

3032
## 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:
3234
```javascript
3335
analytics.identify('97980cfea0085', {
3436
@@ -37,7 +39,7 @@ analytics.identify('97980cfea0085', {
3739
```
3840

3941
## Track
40-
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:
4143

4244
```javascript
4345
analytics.track("User Registered", {
@@ -48,7 +50,7 @@ analytics.track("User Registered", {
4850

4951
## FAQs
5052

51-
### Can I change my AWS Account ID?
52-
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.
5355

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

Comments
 (0)