Amazon Lambda (Beta) List Function activity

Introduction

An Amazon Lambda (Beta) List Function activity, using its Amazon Lambda (Beta) connection, lists functions from AWS Lambda and is intended to be used as a source to provide data in an operation.

Prerequisites

To successfully use this activity, you must have the following AWS IAM account permissions:

• lambda:ListFunctions

Create an Amazon Lambda (Beta) List Function activity

An instance of an Amazon Lambda (Beta) List Function activity is created from an Amazon Lambda (Beta) connection using its List Function activity type.

To create an instance of an activity, drag the activity type to the design canvas or copy the activity type and paste it on the design canvas. For details, see Creating an activity instance in Component reuse.

An existing Amazon Lambda (Beta) List Function activity can be edited from these locations:

• The design canvas (see Component actions menu in Design canvas).
• The project pane's Components tab (see Component actions menu in Project pane Components tab).

Configure an Amazon Lambda (Beta) List Function activity

Follow these steps to configure an Amazon Lambda (Beta) List Function activity:

• Step 1: Enter a name and optional settings
  Provide a name for the activity and specify the optional settings.

• Step 2: Review the data schemas
  Any request or response schemas are displayed.

Step 1: Enter a name and optional settings

In this step, provide a name for the activity and specify the optional settings. Each user interface element of this step is described below.

• Name: Enter a name to identify the activity. The name must be unique for each Amazon Lambda (Beta) List Function activity and must not contain forward slashes / or colons :.

• Function version: Select the function version to return, one of All or Latest.

• Max items: Enter the maximum number of functions to return, up to 50.

• Save & Exit: If enabled, click to save the configuration for this step and close the activity configuration.

• Next: Click to temporarily store the configuration for this step and continue to the next step. The configuration will not be saved until you click the Finished button on the last step.

• Discard Changes: After making changes, click to close the configuration without saving changes made to any step. A message asks you to confirm that you want to discard changes.

Step 2: Review the data schemas

Any request or response schemas are displayed. Each user interface element of this step is described below.

• Data schema: These data schemas are inherited by adjacent transformations and are displayed again during transformation mapping.

  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.

• Refresh: Click the refresh icon or the word Refresh to regenerate schemas from the Amazon Lambda (Beta) endpoint. This action also regenerates a schema in other locations throughout the project where the same schema is referenced, such as in an adjacent transformation.

• Back: Click to temporarily store the configuration for this step and return to the previous step.

• Finished: Click to save the configuration for all steps and close the activity configuration.

• Discard Changes: After making changes, click to close the configuration without saving changes made to any step. A message asks you to confirm that you want to discard changes.

Next steps

After configuring an Amazon Lambda (Beta) List Function activity, complete the configuration of the operation by adding and configuring other activities, transformations, or scripts as operation steps. You can also configure the operation settings, which include the ability to chain operations together that are in the same or different workflows.

Menu actions for an activity are accessible from the project pane and the design canvas. For details, see Activity actions menu in Connector basics.

Amazon Lambda (Beta) List Function activities can be used as a source with these operation patterns:

• Transformation pattern
• Two-target archive pattern (as the first source only)
• Two-target HTTP archive pattern (as the first source only)
• Two-transformation pattern (as the first or second source)

To use the activity with scripting functions, write the data to a temporary location and then use that temporary location in the scripting function.

When ready, deploy and run the operation and validate behavior by checking the operation logs.