Amazon Lambda (Beta) Invoke Function activity

Introduction

An Amazon Lambda (Beta) Invoke Function activity, using its Amazon Lambda (Beta) connection, invokes a function in AWS Lambda and is intended to be used as a target in an operation.

Prerequisites

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

• lambda:GetFunction
• lambda:InvokeFunction
• lambda:ListFunctions
• lambda:ListTags

Create an Amazon Lambda (Beta) Invoke Function activity

An instance of an Amazon Lambda (Beta) Invoke Function activity is created from an Amazon Lambda (Beta) connection using its Invoke 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) Invoke 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) Invoke Function activity

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

• Step 1: Enter a name and specify settings
  Provide a name for the activity and select or enter a function, invocation type, and optional settings.

• Step 2: Provide the request schema
  Provide a custom request schema (optional). If you do not provide a custom response schema, the connector's default response schema will be used.

• Step 3: Provide the response schema
  Provide a custom response schema (optional). If you do not provide a custom response schema, the connector's default response schema will be used.

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

Step 1: Enter a name and specify settings

In this step, provide a name for the activity and select or enter a function, invocation type, and 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) Invoke Function activity and must not contain forward slashes / or colons :.

• List all functions: Select this option to choose from a list of functions retrieved from AWS Lambda:

  • Select an object: This section displays functions available in AWS Lambda.

    • Selected object: After a function is selected, it is listed here.

    • Search: Enter any column's value into the search box to filter the list of functions. The search is not case-sensitive. If functions are already displayed within the table, the table results are filtered in real time with each keystroke. To reload functions from the endpoint when searching, enter search criteria and then refresh, as described below.

    • Refresh: Click the refresh icon or the word Refresh to reload functions from the Amazon Lambda (Beta) endpoint. This may be useful if functions have been added to Amazon Lambda. This action refreshes all metadata used to build the table of functions displayed in the configuration.

    • Selecting an object: Within the table, click anywhere on a row to select a function. Only one function can be selected. The information available for each function is fetched from the Amazon Lambda (Beta) endpoint:

      • Name: The name of the function.

      • Type: The runtime of the function.

      • Description: The description of the function.

    Tip

    If the table does not populate with available functions, the Amazon Lambda (Beta) connection may not be successful. Ensure you are connected by reopening the connection and retesting the credentials.

• Enter function name: Select this option to manually enter the name of a function in AWS Lambda:

  

  • Function name: Enter the function name.

• Invocation type: Select the invocation type to be used when invoking the function, either Dry Run or Synchronous. In this context, Synchronous is also known as RequestResponse. Refer to Amazon's documentation for additional information on each option.

  Important

  Asynchronous (Event) invocations are not currently supported.

• Optional settings: Click to expand additional optional settings:

  • Log Type: Select either None or Tail. If Tail is selected and the Invocation Type is set to Synchronous, an execution log will be included in the function response.
  • Alias: Specify an alias to invoke a published version of the function. This is also known as a function's qualifier.
  • Client Context: Enter valid JSON pertaining to the invoking client context.

• 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: Provide the request schema

In this step, you can provide a custom request schema. If you do not provide a custom request schema, the connector's default request schema will be used.

• Provide request schema: The request schema defines the structure of request data that is used by the Amazon Lambda (Beta) Invoke Function activity. For instructions on completing this section of activity configuration, refer to Schemas defined in an activity.

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

• 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 3: Provide the response schema

In this step, you can provide a custom response schema. If you do not provide a custom response schema, the connector's default response schema will be used.

• Provide response schema: The response schema defines the structure of response data that is used by the Amazon Lambda (Beta) Invoke Function activity. For instructions on completing this section of activity configuration, refer to Schemas defined in an activity.

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

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

  Note

  Data supplied in a transformation takes precedence over the activity configuration.

  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) Invoke 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) Invoke Function activities can be used as a target with these operation patterns:

• Transformation pattern
• Two-transformation pattern (as the first or second target)

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.