Configure EventBridge

Perform the following steps:

1. Go to EventBridge > Integration > API destinations to manage external HTTP targets that EventBridge can send events to.

2. Click Create API destination to initiate the creation of a new destination endpoint.

3. Enter the API destination name and the endpoint URL shared by Acqueon to identify and route events correctly.

4. Select POST as the HTTP method to ensure event data is sent in the request body to the destination endpoint.

5. Under Connection type, click Create a new connection to configure authentication details for the API destination.

6. Enter the connection name provided by Acqueon to uniquely identify this OAuth connection.

7. Select OAuth ClientCredentials as the authorization type to enable secure token-based authentication.

8. Enter the authorization endpoint URL provided by Acqueon to define the location for retrieving access tokens.

9. Select POST as the HTTP method for the OAuth token request to ensure proper credential transmission.

10. Enter the client ID and client secret shared by Acqueon to authenticate against the OAuth server.

11. Add an OAuth HTTP parameter with Parameter type: Query String, Key: grant_type, and Value: client_credentials to define the grant type for token requests.
    

12. Click Create to finalize the connection and link it with the API destination configuration.

13. If an EventBridge rule already exists for Acqueon, open the existing rule, remove the current API destination, and attach the newly created API destination to update the endpoint.

14. If no EventBridge rule exists, go to Rules in the left menu pane to start rule creation.

15. Enter a rule name and description to help identify its purpose, then click Next to continue.

16. Select AWS events or EventBridge partner events depending on your source, and skip the sample event section to manually define triggers.

17. On the Event Pattern screen, select Custom patterns (JSON editor) to input a tailored JSON pattern.

18. Enter the following event pattern to filter events from Amazon Connect:

    {
      "source": ["aws.connect", "custom.connect"],
      "detail-type": ["Amazon Connect Contact Event"],
      "resources": ["arn:aws:connect:us-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"],
      "detail": {
        "initiationMethod": ["API", "OUTBOUND"],
        "channel": ["VOICE"],
        "eventType": ["INITIATED", "CONNECTED_TO_SYSTEM", "AMD_DISABLED", "QUEUED", "CONNECTED_TO_AGENT", "DISCONNECTED"]
      }
    }

19. Click Next to proceed to the target configuration step.

20. Select EventBridge API destination as the rule target to forward events to an external system.

21. Choose Use an existing API destination, then select the API destination created earlier from the dropdown list.

22. Click Next to advance to the tagging section.

23. Skip the Configure tags page and click Next to configure secondary targets.

24. Click Add a second target to enable parallel event delivery.

25. In Target types, select AWS service to choose another AWS destination for logging.

26. In the Select a target dropdown, choose CloudWatch log group to capture event logs.

27. Enter a name for the CloudWatch log group to help organize and access logs related to these events.

28. Click Next to review all settings.

29. On the Review and Create screen, confirm all entries and click Create rule to activate the configuration.

30. Update the EventBridge IAM role to include invoke permissions for the created API destination so EventBridge can call the endpoint successfully.