Disclaimer

Your use of this download is governed by Stonebranch’s Terms of Use.

Overview

AWS Lambda is a serverless compute service that runs your code in response to events and automatically manages the underlying compute resources for you. You can use AWS Lambda to extend other AWS services with custom logic, or create your own back-end services that operate at AWS scale, performance, and security.

This Universal Extension provides the capability to execute a AWS Lambda function and return the result of that execution.

Key Features

• Trigger Lambda function Synchronously or Asynchronously.
• Support authorization via IAM Role-Based Access Control (RBAC) strategy.
• Support Proxy communication via HTTP/HTTPS protocol.

Version Information

Refer to Changelog for version history information.

Requirements

This integration requires a Universal Agent and a Python runtime to execute the Universal Task.

Task Examples

Trigger Lambda Synchronously with Log

Triggering a Lambda function Synchronously with Log Type set to "Tail".

Synchronicity is set by Invocation Type = "Request_Response".

Trigger Lambda Asynchronously with Role Based Access and HTTPS Proxy

Triggering Lambda function Asynchronously with:

• Role Based Access
• HTTPS Proxy connection
• Payload Source
• Client Context Source

Trigger Lambda Synchronously with HTTPS with Credentials Proxy

Triggering a Lambda function Synchronously with "HTTPS with Credentials" Proxy connection.

Trigger Lambda Synchronously with Log

Triggering a Lambda function Synchronously with "Region" provided as Environment Variables and without AWS Credentials. See AWS Credentials input field for more information.

Input Fields

The input fields for this Universal Extension are described below.

Task Output

Exit Codes

The exit codes for AWS Lambda Extension are described in the following table.

Extension Output

In the context of a workflow, subsequent tasks can rely on the information provided by this integration as Extension Output.

Attribute changed is populated as follows.

• true in case the job is triggered successfully
• false otherwise

result section includes the following attributes.

An example of the Extension Output for a successful triggering job is presented below.

{
    "exit_code": 0,
    "status_description": "SUCCESS: AWS Lambda function invoked successfully",
    "changed": true,
    "invocation": {
        "extension": "ue-aws-lambda",
        "version": "1.3.0",
        "fields": {
            "action": "Trigger Lambda Function",
            "credentials_user": "****",
            "credentials_password": "****",
            "region": "us-east-1",
            "role_based_access": false,
            "role_arn": null,
            "function_name": "test-function",
            "invocation_type": "Event",
            "payload_source": null,
            "payload_script": null,
            "client_context_source": null,
            "client_context_script": null,
            "log_type": "None",
            "qualifier": null,
            "use_proxy": false,
            "proxy_type": null,
            "proxy": null,
            "proxy_credentials_user": null,
            "proxy_credentials_password": null,
            "proxy_ca_bundle_file": null,
            "wait_for_completion_timeout": 60,
            "endpoint_url": null
        }
    },
    "result": {
        "status_code": 202,
        "log_result": null,
        "payload": null,
        "executed_version": null,
        "function_error": null
    }
}

STDOUT and STDERR

STDOUT and STDERR provide additional information to the User. The populated content can be changed in future versions of this extension without notice. Backward compatibility is not guaranteed.

1. This Universal Task requires the Resolvable Credentials feature. Check that the Resolvable Credentials Permitted system property has been set to true.
2. Import the Universal Template into your Controller:

   1. Extract the zip file, you downloaded from the Integration Hub.

   2. In the Controller UI, select Services > Import Integration Template option.

   3. Browse to the “export” folder under the extracted files for the ZIP file (Name of the file will be unv_tmplt_*.zip) and click Import.

   4. When the file is imported successfully, refresh the Universal Templates list; the Universal Template will appear on the list.

Modifications of this integration, applied by users or customers, before or after import, might affect the supportability of this integration. For more information refer to Integration Modifications paragraph.

Known Issues

Document References

This document references the following documents.

Changelog

ue-aws-lambda-1.3.0 (2025-08-14)

Enhancements

• Changed: Updated the bundled Boto3 library which makes the integration compatible with more AWS environment variables like AWS_ENDPOINT_URL_STS (#45471)

Fixes

• Fixed: "Proxy Type" field incorrectly used. It is not required to be filled anymore by users on task definition and from this version onwards it is hidden and not used (#47840)

ue-aws-lambda-1.2.0 (2024-01-04)

Enhancements

• Added: Provide the capability to specify a custom endpoint URL to call instead of the default one. (#33020)

ue-aws-lambda-1.1.2 (2023-09-01)

Fixes

• Fixed: Provide a fix on the decoding of AWS Log Message. (#34100)

ue-aws-lambda-1.1.1 (2023-02-24)

Fixes

• Fixed: Provide the capability to define the completion timeout of the lambda function and avoid lambda function re-execution if the completion timeout is exceeded. (#31671)

ue-aws-lambda-1.1.0 (2022-06-30)

Enhancements

• Added: Provide the capability to rely on AWS credentials set-up on the environment where the extension is running and therefore it is not mandatory to be passed on the task definition as input fields. The same applies to AWS Region. (#29115)

ue-aws-lambda-1.0.1 (2022-03-14)

Fixes

• Fixed: Change of template SysId. (#27744)