Skip to Content

Amazon Lambda (Beta) connection

Introduction

An Amazon Lambda (Beta) connection, created using the Amazon Lambda (Beta) connector, establishes access to AWS Lambda. Once a connection is configured, you can create instances of Amazon Lambda (Beta) activities associated with that connection to be used either as sources (to provide data in an operation) or as targets (to consume data in an operation).

Note

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

Important

Configure your AWS IAM account with the required permissions before configuring a connection.

Create or edit an Amazon Lambda (Beta) connection

A new Amazon Lambda (Beta) connection is created using the Amazon Lambda (Beta) connector from one of these locations:

An existing Amazon Lambda (Beta) connection can be edited from these locations:

Configure an Amazon Lambda (Beta) connection

Each user interface element of the Amazon Lambda (Beta) connection configuration screen is described below.

Amazon Lambda configuration

Tip

Fields with a variable icon support using global variables, project variables, and Jitterbit variables. Begin either by typing an open square bracket [ into the field or by clicking the variable icon to display a list of the existing variables to choose from.

  • Connection name: Enter a name to use to identify the connection. The name must be unique for each Amazon Lambda (Beta) connection and must not contain forward slashes / or colons :. This name is also used to identify the Amazon Lambda (Beta) endpoint, which refers to both a specific connection and its activities.

  • Access key ID: Enter the AWS IAM access key ID configured for AWS Lambda. For more information, see Amazon's documentation on IAM for AWS Lambda and identity-based IAM policies for AWS Lambda.

  • Secret access key: Enter the AWS IAM secret access key configured for AWS Lambda. For more information, see Amazon's documentation on IAM for AWS Lambda and identity-based IAM policies for AWS Lambda.

  • AWS region: Select the AWS region to be used.

  • Optional settings: Click to expand additional optional settings:

    • Idle Connection Timeout (in milliseconds): Enter the connection max idle timeout in milliseconds. For example, 60000.

    • Connection Time To Live (in milliseconds): Enter the connection time-to-live (TTL) in milliseconds. If required, the recommended range is 300000 to 600000.

    • Socket Timeout (in milliseconds): Enter the socket timeout in milliseconds. If required, the recommended range is 10000 to 30000.

    • Keep-Alive: Select to enable the Keep-Alive setting for the connection.

    • Use Proxy Settings (Private Agent Only): When using a private agent, this setting can be selected to use private agent proxy settings.

  • Test: Click to verify the connection using the specified configuration. When the connection is tested, the latest version of the connector is downloaded by the agent(s) in the agent group associated with the current environment. This connector supports suspending the download of the latest connector version by using the Disable Auto Connector Update organization policy.

  • Save Changes: Click to save and close the connection configuration.

  • Discard Changes: After making changes to a new or existing configuration, click to close the configuration without saving. A message asks you to confirm that you want to discard changes.

  • Delete: After opening an existing connection configuration, click to permanently delete the connection from the project and close the configuration (see Component dependencies, deletion, and removal). A message asks you to confirm that you want to delete the connection.

Next steps

After an Amazon Lambda (Beta) connection has been created, you place an activity type on the design canvas to create activity instances to be used either as sources (to provide data in an operation) or as targets (to consume data in an operation).

Menu actions for a connection and its activity types are accessible from the project pane and design component palette. For details, see Actions menus in Connector Basics.

These activity types are available:

  • 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.