Navigation

Send Trigger Events to AWS EventBridge

Overview

MongoDB offers an AWS Eventbridge partner event source that lets you send Realm Trigger events to an event bus instead of calling a Realm Function. You can configure any Realm Trigger to send events to EventBridge.

All you need to send Trigger events to EventBridge is an AWS account ID. This guide walks through finding your account ID, configuring the Trigger, and associating the Trigger event source with an event bus.

Official AWS Partner Event Source Guide

This guide is based on Amazon’s Receiving Events from a SaaS Partner documentation.

Procedure

1

Begin Setup of the MongoDB Partner Event Source

To send trigger events to AWS EventBridge, you need the AWS account ID of the account that should receive the events. Open the Amazon EventBridge console and click Partner event sources in the navigation menu. Search for the MongoDB partner event source and then click Set up.

The MongoDB partner event source in EventBridge

On the MongoDB partner event source page, click Copy to copy your AWS account ID to the clipboard.

The prompt to copy your AWS account ID in EventBridge
2

Configure the Trigger

Once you have the AWS account ID, you can configure a trigger to send events to EventBridge.

In the Realm UI, create and configure a new database trigger, authentication trigger, or scheduled trigger and select the EventBridge event type.

Paste in the AWS Account ID that you copied from EventBridge and select an AWS Region to send the trigger events to.

The EventBridge input boxes in the trigger configuration.

Create a trigger configuration file in the /triggers directory. Omit the function_name field and define an AWS_EVENTBRIDGE event processor.

Set the account_id field to the AWS Account ID that you copied from EventBridge and set the region field to an AWS Region.

The trigger configuration file should resemble the following:

{
  "type": "...",
  "name": "...",
  "event_processors": {
    "AWS_EVENTBRIDGE": {
      "type": "AWS_EVENTBRIDGE",
      "account_id": "<AWS Account ID>",
      "region": "<AWS Region>"
    }
  }
}

Supported AWS Regions

For a full list of supported AWS regions, refer to Amazon’s Receiving Events from a SaaS Partner guide.

3

Associate the Trigger Event Source with an Event Bus

Go back to the EventBridge console and choose Partner event sources in the navigation pane. In the Partner event sources table, find and select the Pending trigger source and then click Associate with event bus.

The MongoDB partner event sources table in EventBridge

On the Associate with event bus screen, define any required access permissions for other accounts and organizations and then click Associate.

The screen to associate the MongoDB event source with an event bus in EventBridge

Once confirmed, the status of the trigger event source changes from Pending to Active, and the name of the event bus updates to match the event source name. You can now start creating rules that trigger on events from that partner event source. For more information, see Creating a Rule That Triggers on a SaaS Partner Event.

The MongoDB partner event sources table in EventBridge showing the active trigger event source