Skip to content

Commit 1e5c4a2

Browse files
authored
Apply suggestions from code review
1 parent 11f63d6 commit 1e5c4a2

File tree

1 file changed

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

1 file changed

+2
-2
lines changed

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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -21,7 +21,7 @@ The Event Source will be denoted by your Segment Source ID, which you can find i
2121
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.
2222

2323
> info "Create a separate Segment source for testing"
24-
> We recommend 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, because you cannot change the test Account ID to a production Account ID at a later date.
2525
2626
## Page
2727
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:
@@ -53,4 +53,4 @@ analytics.track("User Registered", {
5353
### Can I change my AWS Account ID?
5454
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.
5555

56-
As an alternative, you can use a [Repeater destination](https://segment-docs.netlify.app/docs/connections/destinations/catalog/repeater/) to your existing source, which will repeat 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+
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.

0 commit comments

Comments
 (0)