Skip to Content

Amazon Lambda (Beta) connector for Jitterbit Integration Studio

Summary

The Amazon Lambda (Beta) connector establishes access to AWS Lambda.

The Amazon Lambda (Beta) connector provides an interface for creating an Amazon Lambda (Beta) connection, the foundation used for generating instances of Amazon Lambda (Beta) activities. These activities, once configured, interact with AWS Lambda through the connection.

The Amazon Lambda (Beta) connector is accessed from the design component palette's Project endpoints and connectors tab (see Design component palette).

Note

To provide feedback on this beta feature, contact the Jitterbit Product Team.

Connector overview

This connector is used to first configure an Amazon Lambda (Beta) connection. Activity types associated with that connection are then used to create instances of activities that are intended to be used as sources (to provide data in an operation) or targets (to consume data in an operation).

Together, a specific Amazon Lambda (Beta) connection and its activities are referred to as an Amazon Lambda (Beta) endpoint:

Amazon Lambda activity types

  • Get Async Response: Retrieves an asynchronous AWS Lambda response from an Amazon SQS queue and is intended to be used as a source to provide data in an operation.

  • Get Function: Retrieves a function from AWS Lambda and is intended to be used as a source in an operation.

  • Invoke Function: Invokes a function in AWS Lambda and is intended to be used as a target in an operation.

  • List Function: Lists functions from AWS Lambda and is intended to be used as a source in an operation.

Note

This connector is a Connector SDK-based connector, which may be referred to by Jitterbit when communicating changes made to connectors built with the Connector SDK.

Prerequisites and supported API versions

The Amazon Lambda (Beta) connector requires the use of an agent version 10.1 or later. These agent versions automatically download the latest version of the connector when required.

The Amazon Lambda (Beta) connector uses the AWS SDK for Java 2.x. Refer to the SDK documentation as well as the general AWS Lambda API reference documentation for information on the schema nodes and fields.

For additional information about AWS Lambda, refer to the AWS Lambda developer guide.

To use the Amazon Lambda (Beta) connector's activities, the AWS IAM account associated with AWS Lambda must have certain AWS Lambda and Amazon SQS permissions set. All of the connector's activities require the lambda:ListFunctions permission. In addition, individual activities require additional specific permissions. The following table summarizes the necessary permissions:

Permission needed Functionality
lambda:ListFunctions Retrieving activity metadata during activity configuration and List Function execution
sqs:GetQueueUrl, sqs:ListQueues, and sqs:ReceiveMessage Get Async Response execution
lambda:GetFunction, lambda:ListTags Get Function execution
lambda:GetFunction, lambda:ListTags, and lambda:InvokeFunction Invoke Function execution

Prior to using the Get Async Response activity, additional prerequisites must be met.

Troubleshooting

If you experience issues with the Amazon Lambda (Beta) connector, these troubleshooting steps are recommended:

  1. Click the Test button in the connection configuration to ensure the connection is successful and to ensure the latest version of the connector is downloaded to the agent (unless using the Disable Auto Connector Update organization policy).

  2. Check the operation logs for any information written during execution of the operation.

  3. Enable operation debug logging (for cloud agents or for private agents) to generate additional log files and data.

  4. If using private agents, you can enable connector verbose logging for this connector by adding this logger configuration entry to your private agent's logback.xml file:

    <logger name="org.jitterbit.connector.lambda" level="DEBUG"/>

    For more information on connector verbose logging, see Verbose logging for connectors using Jitterbit private agents.

  5. If using private agents, you can check the agent logs for more information.

  6. For additional troubleshooting considerations, see Operation troubleshooting.