---
keyword: [Extend, Third Party Technology, AWS]
nav: wcp_docs
parent_url: /wcp_docs/
title: AWS Lambda
layout: subsection
---

You can create new AWS Lambda functions in the AWS CLI.

Sign in to the [AWS Command Line Interface](https://aws.amazon.com/cli/). For more information, refer to [Authenticate to Workday-Provided AWS Account](/wcp_docs/GUID-aef194e4-cf8a-4d71-8550-a77573a3e512-enHYPHENus.html).

## <a id="section_1"></a>AWS Lambda Component Orchestration

This orchestration enables you to invoke a Lambda function.

AWS Lambda functions can be invoked synchronously only. Synchronous invocation means that the Lambda function is invoked inline from the Orchestration and the Orchestration waits for a response from the function before proceeding with its work. If the Lambda function takes longer to complete, the Orchestration will also be delayed. Synchronous invocation is useful in situations where the use case requires a response from the Lambda function before continuing.

In the request, you must specify:

<table><thead></thead><tbody><tr><td>Reference Name</td><td>The name you use in the Expression Builder to refer to this component from other components.</td></tr><tr><td>Function Name</td><td>The name or ARN of the AWS Lambda function to invoke. This can be the full ARN or a partial ARN that includes the function name and any necessary qualifiers. Examples: <code>my-function</code> or <code>arn:aws:lambda:us-west-2:123456789012:function:my-function:1.0</code>. <p>You can also use a string expression to dynamically generate the function name at runtime.</p></td></tr><tr><td>Payload</td><td>The input data to be passed to the AWS Lambda function. This can be an expression that evaluates to a JSON object or array of JSON objects. The payload can be a maximum of 6 MB.</td></tr><tr><td>Return Tail of Log</td><td>Enabling the Tail log type option in AWS Lambda means that the response from the function invocation will include a LogResult field that contains up to 4 KB of base64-encoded CloudWatch logs from the invocation. This allows the Orchestration to access logging information from the function invocation in addition to the result of the function’s execution. <p>The Tail log type can be useful for debugging and monitoring the function’s behavior. However, note that including the logs in the response can increase the size of the response and therefore increase the latency of the function invocation. Including the CloudWatch logs in the Application logs for the Orchestrate requires a downstream log component.</p></td></tr></tbody></table><br/>

If the request is successful, the component will output:

<table><thead></thead><tbody><tr><td>HTTP response code</td><td>The HTTP status code returned by the AWS Lambda function invocation.</td></tr><tr><td>HTTP response body</td><td>The response data returned by the AWS Lambda function invocation. This output can be used to capture any data returned by the function, such as a confirmation message. <p>The <code>content-type</code> of the response will be <code>application/json</code>.</p></td></tr><tr><td>Function Error</td><td>The error message returned by the AWS Lambda function invocation, if an error occurred. This output is useful for handling errors that may occur during the invocation.</td></tr><tr><td>Executed Version</td><td>The version of the AWS Lambda function that was executed. This output can be useful for tracking which version of the function was invoked.</td></tr><tr><td>Log Result</td><td>The base64-encoded log output from the AWS Lambda function invocation. This output can be useful for troubleshooting issues that may have occurred during the invocation.</td></tr></tbody></table><br/>

<b>Note:</b> The component has a 20 second response timeout, a 10 second server connection timeout, and a 5 minute overall timeout (inclusive of request, connect, and response). The component does not retry for failed requests.

## <a id="section_2"></a>Lambda Functions with Additional Dependencies

To deploy Lambda functions with language specific dependencies, (such as NodeJS NPM or Python PIP), follow the corresponding link for the language of your function. Each language has a menu item titled <b>Deploy .zip file archives</b> that describes how to package your dependencies with your function for deployment.

-   [Building Lambda Functions with Java](https://docs.aws.amazon.com/lambda/latest/dg/lambda-java.html)
-   [Building Lambda Functions with Node.js](https://docs.aws.amazon.com/lambda/latest/dg/lambda-nodejs.html)
-   [Building Lambda Functions with Python](https://docs.aws.amazon.com/lambda/latest/dg/lambda-python.html)


### Related Information

[Example: Create an AWS Lambda Function Using SAM CLI](/wcp_docs/GUID-807619f6-1b04-4a31-8f29-661aa92058d4-enHYPHENus.html)
Reference Name	The name you use in the Expression Builder to refer to this component from other components.
Function Name	The name or ARN of the AWS Lambda function to invoke. This can be the full ARN or a partial ARN that includes the function name and any necessary qualifiers. Examples: `my-function` or `arn:aws:lambda:us-west-2:123456789012:function:my-function:1.0`. You can also use a string expression to dynamically generate the function name at runtime.
Payload	The input data to be passed to the AWS Lambda function. This can be an expression that evaluates to a JSON object or array of JSON objects. The payload can be a maximum of 6 MB.
Return Tail of Log	Enabling the Tail log type option in AWS Lambda means that the response from the function invocation will include a LogResult field that contains up to 4 KB of base64-encoded CloudWatch logs from the invocation. This allows the Orchestration to access logging information from the function invocation in addition to the result of the function’s execution. The Tail log type can be useful for debugging and monitoring the function’s behavior. However, note that including the logs in the response can increase the size of the response and therefore increase the latency of the function invocation. Including the CloudWatch logs in the Application logs for the Orchestrate requires a downstream log component.
HTTP response code	The HTTP status code returned by the AWS Lambda function invocation.
HTTP response body	The response data returned by the AWS Lambda function invocation. This output can be used to capture any data returned by the function, such as a confirmation message. The `content-type` of the response will be `application/json`.
Function Error	The error message returned by the AWS Lambda function invocation, if an error occurred. This output is useful for handling errors that may occur during the invocation.
Executed Version	The version of the AWS Lambda function that was executed. This output can be useful for tracking which version of the function was invoked.
Log Result	The base64-encoded log output from the AWS Lambda function invocation. This output can be useful for troubleshooting issues that may have occurred during the invocation.