Amazon Lambda (Tech Preview) operation

The Amazon Lambda operation lets you invoke functions in AWS Lambda from a Boomi process. You can execute serverless functions using structured JSON payloads, supporting synchronous and asynchronous invocation modes.

---

Select the operation type

When creating a new connector operation, choose the following option:

Invoke – Invoke a Lambda function to execute serverless code with a custom payload.

tip

• Choose RequestResponse when you need the function response returned to the process.
• Choose Event for asynchronous execution when no immediate response is required.
• Choose DryRun to validate parameter values and verify that the user or role has permission to invoke the function.

---

Operation: Invoke

The Invoke operation executes Lambda functions with support for:

• Multiple invocation types (RequestResponse, Event and DryRun)
• Function versions and aliases (qualifiers)
• Client context

The connector automatically manages authentication, request signing (AWS Signature Version 4), and API invocation handling.

---

Prerequisites

Before configuring the operation:

• Ensure IAM permissions allow invoking Lambda functions:
  • lambda:InvokeFunction
  • lambda:ListFunctions
• The Lambda function must exist in the configured AWS region.
• Configure AWS credentials in the connection component.

---

Configuration

1. Click Import Operation.
2. Select the configured Connection.
3. Choose Invoke as the Operation Type.
4. Click Next to browse and select a Lambda function.

The connector handles the following automatically:

• Retrieves available Lambda functions using the ListFunctions API.
• Signs requests using AWS Signature Version 4.
• Sends payloads to the Lambda Invoke API endpoint.

---

Tracking Direction

Supports document tracking:

• Input Documents – Track request payload
• Output Documents – Track Lambda response

---

Browse/Import

During the browse/import step, the connector displays:

• A list of Lambda functions available in the selected AWS account and region.
• Functions displayed in the format: Function: {function-name}

Function discovery is performed through live API calls to AWS Lambda.

---

Invocation Type

The Invocation Type determines execution behavior and response handling.

Invocation Type	HTTP Status	Description
RequestResponse	200	Synchronous execution. Returns function response payload.
Event	202	Asynchronous execution. Returns immediately after queuing the request.
DryRun	204	Validates permissions only. Function is not executed.

---

Operation Fields

Field	Type	Required	Description
Invocation Type	String	Yes	RequestResponse, Event, or DryRun
Client Context	String	No	JSON metadata passed to Lambda (Base64-encoded automatically)
Qualifier	String	No	Version or alias (e.g., $LATEST, PROD, 1)

---

Field Limits

Function Name

• Minimum: 1 character
• Maximum: 170 characters

Qualifier

• Minimum: 1 character
• Maximum: 128 characters

Client Context

• Maximum: 3,583 bytes (before Base64 encoding)
• Must be valid JSON

Logging

Invocation metadata is logged at INFO level:

[Lambda Connector] Invocation - Function: my-function, InvocationType: RequestResponse, Region: us-east-1, StatusCode: 200.
Errors include function error details if present.

Archiving tab

See the topic Connector operation’s Archiving tab for more information.

Tracking tab

See the topic Connector operation’s Tracking tab for more information.

Caching tab

See the topic Connector operation’s Caching tab for more information.