AWS Lambda Triggering Output and Integration

Overview

The output type sends notifications and alerts to the specified AWS Lambda FaaS endpoint.

Review Sample Configuration

The following sample configuration displays an output without the name of the organization-level integration:

    - name: aws-lambda-integration
      type: awslambda
      endpoint: "https://XXXXXXXXXX.execute-api.XXXXXXXXX.amazonaws.com/XXXX/XXXXXX"
      notify_content:
        advanced_content: |
          {
            "foo": "bar",
          }

Review Parameters

Review the following parameters that you can configure in the Edge Delta App.

name

Required

Enter a descriptive name for the output or integration.

For outputs, this name will be used to map this destination to a workflow.

Review the following example: 

name: aws-lambda-output

integration_name

Optional

This parameter refers to the organization-level integration created in the Integrations page. 

If you need to add multiple instances of the same integration into the config, then you can add a custom name to each instance via the name parameter. In this situation, the name should be used to refer to the specific instance of the destination in the workflows.

Review the following example: 

integration_name: ed-alert-awslamda

type

Required

Enter awslambda.

Review the following example: 

type: awslambda

endpoint

Required

Enter the AWS Lambda FaaS endpoint.

Review the following example: 

endpoint: "https://XX.execute-api.XX.amazonaws.com/XX/XX"

custom_headers and custom_fields

Optional

This parameter is used to customize the notification content.

If you do not want to use default fields in a notification, then you can create custom headers and fields.

To learn more, see Review Notify Content Parameters.

notify_content: advanced_content

Optional

A payload is JSON object that is used to define metadata about the message.

You are responsible for ensuring the validity of the JSON object. 

Additionally, configurations you make with this parameter will override all other configurations, including custom_fields, title, and disable_default_fields.

To learn more, see Review Template Values for Trigger Payloads.

Review the following example: 

notify_content: 
  advanced_content: | 
    { 
      "foo": "bar", 
    }