Enviar eventos de activadores a AWS EventBridge

Create a New Error Handler

En la sección Configure Error Function, seleccione + New Function.

You can also select an existing Function, if one is already defined, from the dropdown.

Name the New Function

Escribe un nombre único e identificador para la función en el campo Name. Este nombre debe ser diferente al de todas las demás funciones de la aplicación.

Write the Function Code

In the Function section, write the JavaScript code directly in the function editor. The function editor contains a default function that you can edit as needed. For more information on creating functions, refer to the Functions documentation.

Probar la función

In the Testing Console tab beneath the function editor, you can test the function by passing in example values to the error and changeEvent parameters, as shown in the comments of the testing console.

Para obtener más información sobre estos parámetros, consulte la sección Parámetros del controlador de errores en esta página.

Click Run to run the test.

Save the Function

Once you are satisfied with the custom error handler, click Save.

Write the Error Handler

Follow the steps in Define a Function to write your error handler source code and configuration file.

For the error handler source code, see the following template error handler:

exports = async function(error, changeEvent) {
   // This sample function will log additional details if the error is not
   // a DOCUMENT_TOO_LARGE error
   if (error.code === 'DOCUMENT_TOO_LARGE') {
      console.log('Document too large error');
      // Comment out the line below in order to skip this event and not suspend the Trigger
      throw new Error(`Encountered error: ${error.code}`);
   }
   console.log('Error sending event to EventBridge');
   console.log(`DB: ${changeEvent.ns.db}`);
   console.log(`Collection: ${changeEvent.ns.coll}`);
   console.log(`Operation type: ${changeEvent.operationType}`);
   // Throw an error in your function to suspend the trigger and stop processing additional events
   throw new Error(`Encountered error: ${error.message}`);
};

Add an Error Handler to Your Trigger Configuration

Add an error_handler attribute to your trigger configuration file in the Triggers folder. The trigger configuration file should resemble the following:

      {
         "name": "...",
         "type": "DATABASE",
         "event_processors": {
            "AWS_EVENTBRIDGE": {
               "config": {
                  "account_id": "<AWS Account ID>",
                  "region": "<AWS Region>",
                  "extended_json_enabled": <boolean>
               }
            }
         },
         "error_handler": {
            "config": {
               "enabled": <boolean>,
               "function_name": "<Error Handler Function Name>"
            }
         }
      }

For more information on trigger configuration files, see Trigger Configuration Files.

Autenticar a un usuario de MongoDB Atlas

Call the admin user authentication endpoint with your MongoDB Atlas API key pair:

curl -X POST \
  https://services.cloud.mongodb.com/api/admin/v3.0/auth/providers/mongodb-cloud/login \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json' \
  -d '{
    "username": "<Public API Key>",
    "apiKey": "<Private API Key>"
  }'

If authentication succeeds, the response body contains a JSON object with an access_token value:

{
  "access_token": "<access_token>",
  "refresh_token": "<refresh_token>",
  "user_id": "<user_id>",
  "device_id": "<device_id>"
}

El access_token concede acceso a la API de Administración de App Services. Debe incluirlo como un token Bearer en el encabezado Authorization para todas las solicitudes a la API de administración.

Create a Deployment Draft (Optional)

A draft represents a group of application changes that you can deploy or discard as a single unit. If you don't create a draft, updates automatically deploy individually.

To create a draft, send a POST request with no body to the Create a Deployment Draft endpoint:

curl -X POST 'https://services.cloud.mongodb.com/api/admin/v3.0/groups/{groupId}/apps/{appId}/drafts' \
-H 'Content-Type: application/json' \
-H 'Authorization: Bearer <access_token>'

Crear la función de gestión de errores

Create the function to handle errors for a failed AWS EventBridge trigger via a POST request to the Create a new Function endpoint.

curl -X POST \
   https://services.cloud.mongodb.com/api/admin/v3.0/groups/{groupId}/apps/{appId}/functions \
   -H 'Authorization: Bearer <access_token>' \
   -d '{
      "name": "string",
      "private": true,
      "source": "string",
      "run_as_system": true
      }'

Create the AWS EventBridge Trigger

Create the AWS EventBridge Trigger with error handling enabled via a POST request to the Create a Trigger endpoint.

curl -X POST \
   https://services.cloud.mongodb.com/api/admin/v3.0/groups/{groupId}/apps/{appId}/triggers \
   -H 'Authorization: Bearer <access_token>' \
   -d '{
         "name": "string",
         "type": "DATABASE",
         "config": {
            "service_id": "string",
            "database": "string",
            "collection": "string",
            "operation_types": {
               "string"
            },
            "match": ,
            "full_document": false,
            "full_document_before_change": false,
            "unordered": true
         },
         "event_processors": {
            "AWS_EVENTBRIDGE": {
               "account_id": "string",
               "region": "string",
               "extended_json_enabled": false
            },
         },
         "error_handler": {
            "enabled": true,
            "function_id": "string"
         }
      }'

Implementa el borrador

If you created a draft, you can deploy all changes in the draft by sending a POST request with no body to the Deploy a deployment draft endpoint. If you did not create a draft as a first step, the individual function and trigger requests deployed automatically.

curl -X POST \
'https://services.cloud.mongodb.com/api/admin/v3.0/groups/{groupId}/apps/{appId}/drafts/{draftId}/deployment' \
--header 'Content-Type: application/json' \
--header 'Authorization: Bearer <access_token>' \