Merge pull request #7966 from segmentio/eventbridge-actions

[EventBridge Actions] - new Destination

Author: sade-wusi

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

@@ -0,0 +1,28 @@
+---
+title: Amazon EventBridge (Actions) Destination
+id: 67be4b2aef865ee6e0484fe5
+beta: true
+hidden: false
+---
+
+{% include content/plan-grid.md name="actions" %}
+
+[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.
+
+Segment maintains this destination. For any issues with the destination, [contact the Segment Support team](mailto:friends@segment.com){:target="_blank”}.
+
+## Getting started
+
+1. From your workspace's [Destination catalog page](https://app.segment.com/goto-my-workspace/destinations/catalog){:target="_blank”} search for "Amazon EventBridge (Actions)".
+2. Select "Amazon EventBridge (Actions)" and click **Add destination**.
+3. Choose the source you want to connect to Amazon EventBridge (Actions) and create the destination.
+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 the destination settings in Segment.
+5. Select the appropriate **AWS Region** for your EventBridge destination and save the changes.
+6. Go to the Mappings tab, click **+ New Mapping**, then choose the **Send** mapping type. Configure your event trigger and field mappings as needed.
+7. (**Required**:) Before saving your mapping, create a Partner Source. This creates a new EventBridge Partner Event Source in your AWS account if it does not already exist. The source name is
+`aws.partner/segment.com/SEGMENT_SOURCE_ID`. If you don't complete this step, data won't flow to EventBridge.
+8. (Optional:) Once the EventBridge Partner Event Source is created in your AWS account, you can associate the source with the [EventBridge Event Bus](https://docs.aws.amazon.com/eventbridge/latest/userguide/eb-event-bus.html){:target="_blank”}.
+9. Save and enable your mappings. 
+10. Enable the destination in settings to send data to Amazon EventBridge.
+
+{% include components/actions-fields.html %}

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

@@ -8,29 +8,29 @@ id: 5d1994fb320116000112aa12
 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”}.
 
 
-## Getting Started
+## Getting started
 
+To set up:
 
-
-  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.
-  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.
+  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.
+  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.
   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.
 
-The Event Source will be denoted by your Segment Source ID, which you can find in your Source Settings page under API Keys.
+The Event Source will be denoted by your Segment Source ID, which you can find in Source Settings under API Keys.
 
-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.
+All messages in the source (pending any Destination Filters you've enabled) are fowarded to the Segment Partner Event Source, created in EventBridge.
 
 > info "Create a separate Segment source for testing"
-> 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. 
+> 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. 
 
 ## Page
-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:
+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:
 ```javascript
   analytics.page();
 ```
 
 ## Identify
-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:
+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:
 ```javascript
 analytics.identify('97980cfea0085', {
   email: 'gibbons@example.com',
@@ -39,7 +39,7 @@ analytics.identify('97980cfea0085', {
 ```
 
 ## Track
-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:
+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:
 
 ```javascript
 analytics.track("User Registered", {
@@ -50,7 +50,7 @@ analytics.track("User Registered", {
 
 ## FAQs
 
-### Can I change my AWS Account ID?
-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.
+#### Can I change my AWS Account ID?
+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.
 
-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. 
+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.