AWS EventBridge Cloudwatch Configuration

Introduction

Once Genesys Cloud has been configured to send events to AWS EventBridge, you must configure EventBridge to send the Genesys events to Nectar DXP. These steps are intended for those who are using their existing AWS EventBridge configuration and are able to use CloudFormation templates to automate the process. If you are unable to use CloudFormation, you can manually configure EventBridge by following these steps.

If you choose to use Nectar’s EventBridge infrastructure for an additional fee, these steps are not required.

The CloudFormation template automates the entire process of connecting the Genesys partner event source to Nectar DXP. It creates and configures the following objects:

• Connects the Genesys Partner Event Source to a new event bus

• Creates an API Destination and connection that points to the Nectar DXP infrastructure

• Creates event rules in the event bus to route events to the API Destination

Prerequisites

• You must have an available AWS role to assign to the API destination. This role must have the permission events:InvokeApiDestination.

• If you use S3 buckets to store templates, the account creating the CloudFormation template must have the ability to write data to the S3 bucket where the CloudFormation template will be stored.

Configuration

Partner Event Source

1. First, login to your AWS console and navigate to Amazon EventBridge. Make sure you are in the same region that was configured when setting up the Genesys EventBridge Integration.

2. On the left-side menu under Integration, click on Partner event sources

3. You should see a list of partner event sources. The Genesys integration should have created a new partner event source that ends with the Event Source Suffix defined when setting up the Genesys EventBridge integration. The Status should say Pending. Copy the entire name of the partner event source and save it for later.
   

CloudFormation

1. Navigate to CloudFormation and click on Create Stack
   
   

2. Select Build from Infrastructure Composer and click the button Create in Infrastructure Composer
   
   

3. The Infrastructure Composer will open. At the top of the canvas, select Template to switch to the text editor.

4. Paste the contents of the following CloudFormation template into the editor:

   Genesys-DXP-CloudFormation

   3.93 KB

5. Validate the template to make sure there are no errors and click Create Template.
   
   

6. The template should offer to put the template in an existing bucket. Accept the bucket or use a different bucket, then click Confirm and continue to CloudFormation.

7. You should now be back at the Create Stack screen with the URL of the newly created template under Amazon S3 URL. Click Next.
   
   

8. Under Specify stack details, enter the information as requested. Contact your Nectar Professional Services rep for the values to enter in  AWSResourceSuffix, ApiKeyValue and DXPDatagateURL.

   • Stack name: Genesys-Nectar-DXP-Integration

   • AWSResourceSuffix: Your Nectar DXP tenant name (obtain from Nectar PS)

   • ApiDestinationRole: The name of the role to assign to the API destination (name only, not full ARN)

   • ApiKeyValue: The API key secret (obtain from Nectar PS)

   • DXPDatagateURL: The URL to send events to (obtain from Nectar PS). Will be something like https://datagate-cloudagent.us.nectar.services/genesys/events

   • PartnerEventSourceName: the name of the partner event source that you copied from the first steps.
     
     

9. Click Next.

10. Leave all options at defaults unless instructed by your AWS administrators and click Next.

11. Review all settings and click Submit.

Your stack should now deploy. If any portion fails, review the events for information on how to resolve the errors (likely permissions).