# mulesoft Amazon Lambda Connector - Full Documentation

<!-- document id=d2bf92004ca031e227cb2af442ddb2d50dcc170216d4a9461fa1a6e49161e95b url=/mulesoft/current/en-us/amazon-lambda-connector/1.0/index.md -->

---
product: Amazon Lambda Connector
version: 1.0
---

# Amazon Lambda Connector 1.0

> For the full documentation index, see: https://docs.mulesoft.com/llms.txt

Anypoint Connector for Amazon Lambda (Amazon Lambda Connector) enables you to execute AWS Lambda
operations within your Mule flows. You can then use the response of the Lambda operation to process
another Mule flow as needed.

For compatibility information and fixed issues, see the Amazon Lambda Release Notes.

## Before You Begin

To use this connector, you must be familiar with:

- The AWS Lambda API

- Anypoint Connectors

- Mule runtime engine (Mule)

- Elements and global elements in a Mule flow

- Creating a Mule app using Anypoint Studio or Anypoint Code Builder

Before creating an app, you must have:

- AWS Identity and Access Management (IAM) access key credentials

- Access to the AWS Lambda target resource

- Anypoint Studio version 7.3 or later

## Common Use Case for the Connector

When your app manages large amounts of streaming data from various sources, Amazon Lambda Connector
enables you to send the data stream to an AWS Lambda application that is specifically designed to
quickly pull and process the required information. This enables you to manage necessary realtime
tasks without slowing down your main application.

## Authentication Types

AWS Lambda Connector supports AWS Lambda authentication.

## See Also

- [Introduction to Anypoint Connectors](https://docs.mulesoft.com/connectors/introduction/introduction-to-anypoint-connectors)

- [Use Exchange to Discover Connectors, Templates, and Examples](https://docs.mulesoft.com/connectors/introduction/intro-use-exchange)

- [Salesforce Help](https://help.salesforce.com)

<!-- document id=aa6b220f032d1a2c3df38b2d0432154cc49557bee29578a83db263e041f00534 url=/mulesoft/current/en-us/amazon-lambda-connector/1.0/amazon-lambda-connector-xml-maven.md -->

---
product: Amazon Lambda Connector
version: 1.0
---

# Amazon Lambda Connector 1.0 - XML and Maven Support

> For the full documentation index, see: https://docs.mulesoft.com/llms.txt

Although you can manually code a Mule app in XML, it is more efficient to use Anypoint Studio:

- If you manually code a Mule runtime engine (Mule) app in XML either from the Anypoint Studio XML
  editor or from a text editor, you can access the connector from your app by adding reference
  statements to both your XML Mule flow and the Apache Maven `pom.xml` file.

- If you add the connector in Studio, Studio automatically populates the XML code with the
  connector’s namespace and schema location and it also adds a dependency to the `pom.xml` file.

## Add a Namespace for the Connector

Paste the following code inside the `mule` tag of the header of your configuration XML:

```xml
http://www.mulesoft.org/schema/mule/amazon-lambda
http://www.mulesoft.org/schema/mule/amazon-lambda/current/mule-amazon-lambda.xsd
```

This example shows how the namespace statements are placed in the XML:

```xml
<mule xmlns:amazon-lambda="http://www.mulesoft.org/schema/mule/amazon-lambda"
	xmlns="http://www.mulesoft.org/schema/mule/core"
	xmlns:doc="http://www.mulesoft.org/schema/mule/documentation"
	xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
	xsi:schemaLocation="http://www.mulesoft.org/schema/mule/core
	http://www.mulesoft.org/schema/mule/core/current/mule.xsd
	http://www.mulesoft.org/schema/mule/amazon-lambda
	http://www.mulesoft.org/schema/mule/amazon-lambda/current/mule-amazon-lambda.xsd">
```

## Add a POM File Dependency

The Apache Maven `pom.xml` file generated by Anypoint Studio contains dependencies for a Mule app.
When you code a Mule app manually, include this XML snippet in your `pom.xml` file to enable access
to this connector:

```xml
<dependency>
  <groupId>com.mulesoft.connectors</groupId>
  <artifactId>mule4-amazon-lambda-connector</artifactId>
  <version>1.0.0</version>
  <classifier>mule-plugin</classifier>
</dependency>
```

Replace the value for `<version>` with the version that corresponds to the connector you are using.

To obtain the most up-to-date `pom.xml` file information:

1.  Go to [Anypoint Exchange](https://www.mulesoft.com/exchange/).

2.  In Exchange, click **Login** and supply your Anypoint Platform username and password.

3.  In Exchange, search for `amazon lambda`.

4.  Select the connector.

5.  Click **Dependency Snippets** near the upper right of the screen.

## See Also

- [Introduction to Anypoint Connectors](https://docs.mulesoft.com/connectors/introduction/introduction-to-anypoint-connectors)

- [Salesforce Help](https://help.salesforce.com)

<!-- document id=4eadb68ad2098c1c6e407014355ba6fdb2b14d2d921d350597fdd0f5749cef95 url=/mulesoft/current/en-us/amazon-lambda-connector/1.0/amazon-lambda-connector-examples.md -->

---
product: Amazon Lambda Connector
version: 1.0
---

# Amazon Lambda Connector 1.0 Examples

> For the full documentation index, see: https://docs.mulesoft.com/llms.txt

This example shows how to use the Anypoint Connector for Amazon Lambda (Amazon Lambda Connector) to
invoke a synchronous call and get results from AWS Lambda.

## Before You Begin

Verify that Amazon Lambda Connector is added to your Mule project in Anypoint Studio. If it’s not,
follow the instructions in
[Add the Connector to Your Mule Project](https://docs.mulesoft.com/amazon-lambda-connector/1.0/amazon-lambda-connector-studio#add-connector-to-project).

## Synchronous Invocation Flow

This example shows a simple AWS Lambda function call that is invoked using an HTTP listener. When
the `http://localhost:8081/invoke` URL is called, the Lambda **Invoke** operation is performed, and
the result is returned directly to you.

### Create the Configuration File

1.  In Studio, go to the **Package Explorer** view and right-click the `/src/main/resources` folder
    in your project.

2.  Select **New > File**.

3.  Name the file `environment.properties`.

4.  Edit the file to define the properties and values you need.

### Configure HTTP Listener

Configure an HTTP Listener source to initiate the Amazon Lambda Connector **Invoke** operation flow
each time it receives a request on the configured host (`localhost`) and port (`8081`):

1.  In **Mule Palette**, select **HTTP > Listener**.

2.  Drag **Listener** to the Studio canvas.

3.  Click **+** next to **Connector configuration** to configure a global element that can be used
    by all instances of the HTTP Listener source in the app.

4.  In the **General** tab, specify connection information for the connector.

5.  Click **Test Connection** to confirm that Mule can connect with the specified server.

6.  Click **OK**.

### Configure the Invoke Operation

1.  In **Mule Palette**, select **Amazon Lambda Connector > Invoke**.

2.  Drag **Invoke** to the Studio canvas to the right of the **Listener** source:

    ![Simple invoke example flow in Studio](/mulesoft/current/en-us/amazon-lambda-connector/1.0/_images/amazon-lambda-simple-invoke-example.png)

3.  Configure the **Invoke** operation:

    ![Simple invoke operation General properties configuration](/mulesoft/current/en-us/amazon-lambda-connector/1.0/_images/amazon-lambda-simple-invoke-example-properties.png)

    In this example, the function name is supplied in the `environment.properties` file as
    `$config.functionName`.

    The payload from the HTTP Listener is passed directly into the body of the **Invoke** operation,
    which is specified as `REQUEST_RESPONSE`. This tells AWS Lambda that it does not need to store
    any logs for this operation and effectively makes this a synchronous call, which waits until the
    AWS Lambda function is finished processing before it returns its results.

    Alternatively, you can set **Invocation Type** to `EVENT`, which acts like an asynchronous call
    and returns an empty response immediately while AWS Lambda performs its action in the
    background.

### Create an AWS Lambda Function

Depending on your Lambda function, when you run this flow, you might need to send in a request body.
For example, you can create a Python 3.8 Lambda function like this:

```python
def lambda_handler(event, context):
    message = 'Hello {} {}!'.format(event['first_name'], event['last_name'])

	return {'message' : message}
```

Consult the official AWS documentation if you don’t know how to create a new AWS Lambda function.

This function takes the fields `first_name` and `last_name` from the input in JSON format and sends
a greeting using the specified first and last names.

Call the `http://localhost:8081/invoke` endpoint with a JSON body like this:

```json
{
  "first_name": "<first_name>",
  "last_name": "<last_name>"
}
```

The Mule flow responds with a Code 200 message:

{ "message": "Hello <first\_name> <last\_name>!" }

## XML for the Invoke Example

Paste this code into the Studio XML editor to quickly load the flow for this example into your Mule
app:

```xml
<?xml version="1.0" encoding="UTF-8"?>

<mule xmlns:amazon-lambda="http://www.mulesoft.org/schema/mule/amazon-lambda" xmlns:http="http://www.mulesoft.org/schema/mule/http"
	xmlns="http://www.mulesoft.org/schema/mule/core"
	xmlns:doc="http://www.mulesoft.org/schema/mule/documentation" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.mulesoft.org/schema/mule/core http://www.mulesoft.org/schema/mule/core/current/mule.xsd
http://www.mulesoft.org/schema/mule/http http://www.mulesoft.org/schema/mule/http/current/mule-http.xsd
http://www.mulesoft.org/schema/mule/amazon-lambda http://www.mulesoft.org/schema/mule/amazon-lambda/current/mule-amazon-lambda.xsd">
	<flow name="amazon-lambda-invoke-example">
		<http:listener doc:name="Listener" config-ref="HTTP_Listener_config" path="/invoke"/>
		<amazon-lambda:create20150331-functions-invocations-by-function-name doc:name="Invoke" config-ref="Test_Aws_Config" functionName="${config.functionName}" xAmzInvocationType="REQUEST_RESPONSE">
		</amazon-lambda:create20150331-functions-invocations-by-function-name>
	</flow>
</mule>
```

### See Also

- [Introduction to Anypoint Connectors](https://docs.mulesoft.com/connectors/introduction/introduction-to-anypoint-connectors)

- [Anypoint Connector Configuration](https://docs.mulesoft.com/connectors/introduction/intro-connector-configuration-overview).

- [Amazon Lambda Connector Reference](https://docs.mulesoft.com/amazon-lambda-connector/1.0/amazon-lambda-connector-reference).

- [Salesforce Help](https://help.salesforce.com)

<!-- document id=c10611f08add25c87d677ac32d880c5cdd9387f22f45b4ee55501e452ab4893d url=/mulesoft/current/en-us/amazon-lambda-connector/1.0/amazon-lambda-connector-reference.md -->

---
product: Amazon Lambda Connector
version: 1.0
---

# Amazon Lambda Connector 1.0 Reference

> For the full documentation index, see: https://docs.mulesoft.com/llms.txt

> [!NOTE] Where possible, we changed noninclusive terms to align with our company value of Equality.
> We maintained certain terms to avoid any effect on customer implementations.

Anypoint Connector for Amazon Lambda (Amazon Lambda Connector) provides access to standard Amazon
Lambda operations using Anypoint Platform.

## Configurations

<table><colgroup><col> <col> <col> <col> <col></colgroup><thead><tr><th>Name</th><th>Type</th><th>Description</th><th>Default Value</th><th>Required</th></tr></thead><tbody><tr><td><p>Name</p></td><td><p>String</p></td><td><p>The name for this configuration. Connectors reference the configuration with this name.</p></td><td></td><td><p>x</p></td></tr><tr><td><p>Connection</p></td><td><div><div><p><a href="#Config_Connection">Amazon Lambda Connection</a></p></div></div></td><td><p>The connection types to provide to this configuration.</p></td><td></td><td><p>x</p></td></tr><tr><td><p>Response Timeout</p></td><td><div><div><p>Number</p></div></div></td><td><p>Timeout for requests to the remote service. This value is qualified by the <strong>Response Timeout Unit</strong> field.</p></td><td><p>1</p></td><td></td></tr><tr><td><p>Response Timeout Unit</p></td><td><div><div><p>Enumeration, one of:</p></div><div><ul><li><p>NANOSECONDS</p></li><li><p>MICROSECONDS</p></li><li><p>MILLISECONDS</p></li><li><p>SECONDS</p></li><li><p>MINUTES</p></li><li><p>HOURS</p></li><li><p>DAYS</p></li></ul></div></div></td><td><p>Time unit for the <strong>Response Timeout</strong> field.</p></td><td><p>MINUTES</p></td><td></td></tr><tr><td><p>Name</p></td><td><div><div><p>String</p></div></div></td><td><p>Identifier of this element, which is used to reference it in other components.</p></td><td></td><td><p>x</p></td></tr><tr><td><p>Expiration Policy</p></td><td><div><div><p><a href="#ExpirationPolicy">Expiration Policy</a></p></div></div></td><td><p>Minimum amount of time that a dynamic configuration instance can remain idle before Mule considers it eligible for expiration.</p></td><td></td><td></td></tr></tbody></table>

## Connection Types

### Amazon Lambda Connection

<table><colgroup><col> <col> <col> <col> <col></colgroup><thead><tr><th>Name</th><th>Type</th><th>Description</th><th>Default Value</th><th>Required</th></tr></thead><tbody><tr><td><p>Default Headers</p></td><td><div><div><p>Array of <a href="#DefaultHeader">Default Header</a></p></div></div></td><td></td><td></td><td></td></tr><tr><td><p>Query Parameters</p></td><td><div><div><p>Array of <a href="#DefaultQueryParam">Default Query Param</a></p></div></div></td><td></td><td></td><td></td></tr><tr><td><p>Connection Timeout</p></td><td><div><div><p>Number</p></div></div></td><td><p>Timeout for establishing connections to the remote service.</p></td><td><p>30</p></td><td></td></tr><tr><td><p>Connection Timeout Unit</p></td><td><div><div><p>Enumeration, one of:</p></div><div><ul><li><p>NANOSECONDS</p></li><li><p>MICROSECONDS</p></li><li><p>MILLISECONDS</p></li><li><p>SECONDS</p></li><li><p>MINUTES</p></li><li><p>HOURS</p></li><li><p>DAYS</p></li></ul></div></div></td><td><p>Time unit for the <strong>Connection Timeout</strong> field.</p></td><td><p>SECONDS</p></td><td></td></tr><tr><td><p>Use Persistent Connections</p></td><td><div><div><p>Boolean</p></div></div></td><td><p>If false, each connection is closed after the first request is completed.</p></td><td><p>true</p></td><td></td></tr><tr><td><p>Max Connections</p></td><td><div><div><p>Number</p></div></div></td><td><p>Maximum number of outbound connections to keep open at the same time.</p></td><td><p>-1</p></td><td></td></tr><tr><td><p>Connection Idle Timeout</p></td><td><div><div><p>Number</p></div></div></td><td><p>Timeout for how long a connection can remain idle before it is closed.</p></td><td><p>30</p></td><td></td></tr><tr><td><p>Connection Idle Timeout Unit</p></td><td><div><div><p>Enumeration, one of:</p></div><div><ul><li><p>NANOSECONDS</p></li><li><p>MICROSECONDS</p></li><li><p>MILLISECONDS</p></li><li><p>SECONDS</p></li><li><p>MINUTES</p></li><li><p>HOURS</p></li><li><p>DAYS</p></li></ul></div></div></td><td><p>Time unit for the <strong>Connection Idle Timeout</strong> field.</p></td><td><p>SECONDS</p></td><td></td></tr><tr><td><p>Proxy Config</p></td><td><div><div><p><a href="#Proxy">Proxy</a></p></div></div></td><td><p>Reusable configuration element for outbound connections through a proxy.</p></td><td></td><td></td></tr><tr><td><p>Stream Response</p></td><td><div><div><p>Boolean</p></div></div></td><td><p>Whether or not to stream received responses.</p></td><td><p>false</p></td><td></td></tr><tr><td><p>Response Buffer Size</p></td><td><div><div><p>Number</p></div></div></td><td><p>Space in bytes for the buffer where the HTTP response will be stored.</p></td><td><p>-1</p></td><td></td></tr><tr><td><p>Access Key</p></td><td><div><div><p>String</p></div></div></td><td><p>The access key provided by Amazon.</p></td><td></td><td><p>x</p></td></tr><tr><td><p>Secret Key</p></td><td><div><div><p>String</p></div></div></td><td><p>The secret key provided by Amazon.</p></td><td></td><td><p>x</p></td></tr><tr><td><p>Role ARN</p></td><td><div><div><p>String</p></div></div></td><td><p>The ARN of the role to use.</p></td><td></td><td></td></tr><tr><td><p>Region</p></td><td><div><div><p>String</p></div></div></td><td><p>The region of the Amazon instance.</p></td><td><p>us-east-1</p></td><td></td></tr><tr><td><p>Protocol</p></td><td><div><div><p>Enumeration, one of:</p></div><div><ul><li><p>HTTP</p></li><li><p>HTTPS</p></li></ul></div></div></td><td><p>Protocol to use for communication. Valid values are HTTP and HTTPS.</p></td><td><p>HTTP</p></td><td></td></tr><tr><td><p>TLS Configuration</p></td><td><div><div><p><a href="#Tls">TLS</a></p></div></div></td><td></td><td></td><td></td></tr><tr><td><p>Reconnection</p></td><td><div><div><p><a href="#Reconnection">Reconnection</a></p></div></div></td><td><p>When the application is deployed, a connectivity test is performed on all connectors. If set to true, deployment fails if the test doesn’t pass after exhausting the associated reconnection strategy.</p></td><td></td><td></td></tr></tbody></table>

## Operations

- [Invoke Async](#Create20141113FunctionsInvokeAsyncByFunctionName)

- [Invoke](#Create20150331FunctionsInvocationsByFunctionName)

- [List Functions](#Get20150331Functions)

- [Get Function](#Get20150331FunctionsByFunctionName)

## Invoke Async

`<amazon-lambda:create20141113-functions-invoke-async-by-function-name>`

For asynchronous function invocation, use Invoke. Invokes a function asynchronously. This operation
makes an HTTP POST request to the `/2014-11-13/functions/{FunctionName}/invoke-async/` endpoint.

### Parameters

<table><colgroup><col> <col> <col> <col> <col></colgroup><thead><tr><th>Name</th><th>Type</th><th>Description</th><th>Default Value</th><th>Required</th></tr></thead><tbody><tr><td><p>Configuration</p></td><td><p>String</p></td><td><p>The name of the configuration to use.</p></td><td></td><td><p>x</p></td></tr><tr><td><p>Function Name</p></td><td><div><div><p>String</p></div></div></td><td><div><div><p>Name of the Lambda function. Name formats:</p></div><div><ul><li><p>Function name: my-function.</p></li><li><p>Function ARN: arn:aws:lambda:us-west-2:123456789012:function:my-function.</p></li><li><p>Partial ARN: 123456789012:function:my-function.</p></li></ul></div><div><p>The length constraint applies only to the full ARN. If you specify only the function name, it is limited to 64 characters in length.</p></div></div></td><td></td><td><p>x</p></td></tr><tr><td><p>Body</p></td><td><div><div><p>Any</p></div></div></td><td><p>the content to use</p></td><td><p>#[payload]</p></td><td></td></tr><tr><td><p>Config Ref</p></td><td><div><div><p>ConfigurationProvider</p></div></div></td><td><p>The name of the configuration to use to execute this component.</p></td><td></td><td><p>x</p></td></tr><tr><td><p>Streaming Strategy</p></td><td><div><div><ul><li><p><a href="#RepeatableInMemoryStream">Repeatable In Memory Stream</a></p></li><li><p><a href="#RepeatableFileStoreStream">Repeatable File Store Stream</a></p></li><li><p>non-repeatable-stream</p></li></ul></div></div></td><td><p>Configures how Mule processes streams. The default is to use repeatable streams.</p></td><td></td><td></td></tr><tr><td><p>Custom Query Parameters</p></td><td><div><div><p>Object</p></div></div></td><td><p>Custom query parameters to include in the request. The specified query parameters are merged with the default query parameters that are specified in the configuration.</p></td><td></td><td></td></tr><tr><td><p>Custom Headers</p></td><td><div><div><p>Object</p></div></div></td><td><p>Custom headers to include in the request. The specified custom headers are merged with the default headers that are specified in the configuration.</p></td><td></td><td></td></tr><tr><td><p>Response Timeout</p></td><td><div><div><p>Number</p></div></div></td><td><p>Timeout for requests to the remote service. This value is qualified by the <strong>Response Timeout Unit</strong>.</p></td><td></td><td></td></tr><tr><td><p>Response Timeout Unit</p></td><td><div><div><p>Enumeration, one of:</p></div><div><ul><li><p>NANOSECONDS</p></li><li><p>MICROSECONDS</p></li><li><p>MILLISECONDS</p></li><li><p>SECONDS</p></li><li><p>MINUTES</p></li><li><p>HOURS</p></li><li><p>DAYS</p></li></ul></div></div></td><td><p>Time unit for the <strong>Response Timeout</strong> field.</p></td><td></td><td></td></tr><tr><td><p>Target Variable</p></td><td><div><div><p>String</p></div></div></td><td><p>Name of the variable that stores the operation’s output.</p></td><td></td><td></td></tr><tr><td><p>Target Value</p></td><td><div><div><p>String</p></div></div></td><td><p>Expression that evaluates the operation’s output. The outcome of the expression is stored in the <strong>Target Variable</strong>.</p></td><td><p>#[payload]</p></td><td></td></tr><tr><td><p>Reconnection Strategy</p></td><td><div><div><ul><li><p><a href="#Reconnect">Reconnect</a></p></li><li><p><a href="#ReconnectForever">Reconnect Forever</a></p></li></ul></div></div></td><td><p>A retry strategy in case of connectivity errors.</p></td><td></td><td></td></tr></tbody></table>

### Output

<table><colgroup><col> <col></colgroup><tbody><tr><td><p>Type</p></td><td><p>Any</p></td></tr><tr><td><p>Attributes Type</p></td><td><div><div><p><a href="#HttpResponseAttributes">HTTP Response Attributes</a></p></div></div></td></tr></tbody></table>

### For Configurations

- [Configurations](#configurations)

### Throws

- AMAZON-LAMBDA:BAD\_REQUEST

- AMAZON-LAMBDA:CLIENT\_ERROR

- AMAZON-LAMBDA:CONNECTIVITY

- AMAZON-LAMBDA:INTERNAL\_SERVER\_ERROR

- AMAZON-LAMBDA:NOT\_ACCEPTABLE

- AMAZON-LAMBDA:NOT\_FOUND

- AMAZON-LAMBDA:RETRY\_EXHAUSTED

- AMAZON-LAMBDA:SERVER\_ERROR

- AMAZON-LAMBDA:SERVICE\_UNAVAILABLE

- AMAZON-LAMBDA:TIMEOUT

- AMAZON-LAMBDA:TOO\_MANY\_REQUESTS

- AMAZON-LAMBDA:UNAUTHORIZED

- AMAZON-LAMBDA:UNSUPPORTED\_MEDIA\_TYPE

## Invoke

`<amazon-lambda:create20150331-functions-invocations-by-function-name>`

Invokes a Lambda function. You can invoke a function synchronously (and wait for the response), or
asynchronously.

To invoke a function asynchronously, set `InvocationType` to `Event`.

For synchronous invocation, details about the function response, including errors, are included in
the response body and headers. For either invocation type, you can find more information in the
execution log and trace.

When an error occurs, your function may be invoked multiple times. Retry behavior varies by error
type, client, event source, and invocation type. For example, if you invoke a function
asynchronously and it returns an error, Lambda executes the function up to two more times. For more
information, see Retry Behavior.

For asynchronous invocation, Lambda adds events to a queue before sending them to your function. If
your function does not have enough capacity to keep up with the queue, events may be lost.
Occasionally, your function might receive the same event multiple times, even if no error occurs.

To retain events that were not processed, configure your function with a dead-letter queue. The
status code in the API response doesn’t reflect function errors. Error codes are reserved for errors
that prevent your function from executing, such as permissions errors, limit errors, or issues with
your function’s code and configuration. For example, Lambda returns `TooManyRequestsException` if
executing the function causes you to exceed a concurrency limit at either the account level
(`ConcurrentInvocationLimitExceeded`) or function level
(`ReservedFunctionConcurrentInvocationLimitExceeded`).

For functions with a long timeout, your client might be disconnected during synchronous invocation
while it waits for a response. Configure your HTTP client, SDK, firewall, proxy, or operating system
to allow for long connections with timeout or keep-alive settings.

This operation requires permission for the lambda:InvokeFunction action.

This operation makes an HTTP POST request to the `/2015-03-31/functions/{FunctionName}/invocations`
endpoint.

### Parameters

<table><colgroup><col> <col> <col> <col> <col></colgroup><thead><tr><th>Name</th><th>Type</th><th>Description</th><th>Default Value</th><th>Required</th></tr></thead><tbody><tr><td><p>Configuration</p></td><td><p>String</p></td><td><p>Name of the configuration to use.</p></td><td></td><td><p>x</p></td></tr><tr><td><p>Function Name</p></td><td><div><div><p>String</p></div></div></td><td><div><div><p>Name of the Lambda function, version, or alias. Name formats:</p></div><div><ul><li><p>Function name: my-function (name-only), my-function:v1 (with alias).</p></li><li><p>Function ARN: arn:aws:lambda:us-west-2:123456789012:function:my-function.</p></li><li><p>Partial ARN: 123456789012:function:my-function.</p></li></ul></div><div><p>You can append a version number or alias to any of the formats. The length constraint applies only to the full ARN. If you specify only the function name, it is limited to 64 characters in length.</p></div></div></td><td></td><td><p>x</p></td></tr><tr><td><p>Qualifier</p></td><td><div><div><p>String</p></div></div></td><td><p>Specify a version or alias to invoke a published version of the function.</p></td><td></td><td></td></tr><tr><td><p>X Amz Invocation Type</p></td><td><div><div><p>Enumeration, one of:</p></div><div><ul><li><p>EVENT</p></li><li><p>REQUEST_RESPONSE</p></li><li><p>DRY_RUN</p></li></ul></div></div></td><td><div><div><p>Choose from the following options:</p></div><div><ul><li><p>RequestResponse (default): Invoke the function synchronously. Keep the connection open until the function returns a response or times out. The API response includes the function response and additional data.</p></li><li><p>Event: Invoke the function asynchronously. Send events that fail multiple times to the function’s dead-letter queue (if it’s configured). The API response only includes a status code.</p></li><li><p>DryRun: Validate parameter values and verify that the user or role has permission to invoke the function.</p></li></ul></div></div></td><td></td><td></td></tr><tr><td><p>X Amz Log Type</p></td><td><div><div><p>Enumeration, one of:</p></div><div><ul><li><p>NONE</p></li><li><p>TAIL</p></li></ul></div></div></td><td><p>Set to <code>TAIL</code> to include the execution log in the response.</p></td><td></td><td></td></tr><tr><td><p>X Amz Client Context</p></td><td><div><div><p>String</p></div></div></td><td><p>Up to 3583 bytes of Base64-encoded data about the invoking client to pass to the function in the context object.</p></td><td></td><td></td></tr><tr><td><p>Body</p></td><td><div><div><p>Any</p></div></div></td><td><p>Content to use.</p></td><td><p>#[payload]</p></td><td></td></tr><tr><td><p>Config Ref</p></td><td><div><div><p>ConfigurationProvider</p></div></div></td><td><p>Name of the configuration to use to execute this component.</p></td><td></td><td><p>x</p></td></tr><tr><td><p>Streaming Strategy</p></td><td><div><div><ul><li><p><a href="#RepeatableInMemoryStream">Repeatable In Memory Stream</a></p></li><li><p><a href="#RepeatableFileStoreStream">Repeatable File Store Stream</a></p></li><li><p>non-repeatable-stream</p></li></ul></div></div></td><td><p>Configures how Mule processes streams. The default is to use repeatable streams.</p></td><td></td><td></td></tr><tr><td><p>Custom Query Parameters</p></td><td><div><div><p>Object</p></div></div></td><td><p>Custom query parameters to include in the request. The specified query parameters are merged with the default query parameters that are specified in the configuration.</p></td><td></td><td></td></tr><tr><td><p>Custom Headers</p></td><td><div><div><p>Object</p></div></div></td><td><p>Custom headers to include in the request. The specified custom headers are merged with the default headers that are specified in the configuration.</p></td><td></td><td></td></tr><tr><td><p>Response Timeout</p></td><td><div><div><p>Number</p></div></div></td><td><p>Timeout for requests to the remote service. This value is qualified by the <strong>Response Timeout Unit</strong>.</p></td><td></td><td></td></tr><tr><td><p>Response Timeout Unit</p></td><td><div><div><p>Enumeration, one of:</p></div><div><ul><li><p>NANOSECONDS</p></li><li><p>MICROSECONDS</p></li><li><p>MILLISECONDS</p></li><li><p>SECONDS</p></li><li><p>MINUTES</p></li><li><p>HOURS</p></li><li><p>DAYS</p></li></ul></div></div></td><td><p>Time unit for the <strong>Response Timeout</strong> field.</p></td><td></td><td></td></tr><tr><td><p>Target Variable</p></td><td><div><div><p>String</p></div></div></td><td><p>Name of the variable that stores the operation’s output.</p></td><td></td><td></td></tr><tr><td><p>Target Value</p></td><td><div><div><p>String</p></div></div></td><td><p>Expression that evaluates the operation’s output. The outcome of the expression is stored in the <strong>Target Variable</strong>.</p></td><td><p>#[payload]</p></td><td></td></tr><tr><td><p>Reconnection Strategy</p></td><td><div><div><ul><li><p><a href="#Reconnect">Reconnect</a></p></li><li><p><a href="#ReconnectForever">Reconnect Forever</a></p></li></ul></div></div></td><td><p>A retry strategy in case of connectivity errors.</p></td><td></td><td></td></tr></tbody></table>

### Output

<table><colgroup><col> <col></colgroup><tbody><tr><td><p>Type</p></td><td><p>Any</p></td></tr><tr><td><p>Attributes Type</p></td><td><div><div><p><a href="#HttpResponseAttributes">HTTP Response Attributes</a></p></div></div></td></tr></tbody></table>

### For Configurations

- [Configurations](#configurations)

### Throws

- AMAZON-LAMBDA:BAD\_REQUEST

- AMAZON-LAMBDA:CLIENT\_ERROR

- AMAZON-LAMBDA:CONNECTIVITY

- AMAZON-LAMBDA:INTERNAL\_SERVER\_ERROR

- AMAZON-LAMBDA:NOT\_ACCEPTABLE

- AMAZON-LAMBDA:NOT\_FOUND

- AMAZON-LAMBDA:RETRY\_EXHAUSTED

- AMAZON-LAMBDA:SERVER\_ERROR

- AMAZON-LAMBDA:SERVICE\_UNAVAILABLE

- AMAZON-LAMBDA:TIMEOUT

- AMAZON-LAMBDA:TOO\_MANY\_REQUESTS

- AMAZON-LAMBDA:UNAUTHORIZED

- AMAZON-LAMBDA:UNSUPPORTED\_MEDIA\_TYPE

## List Functions

`<amazon-lambda:get20150331-functions>`

Returns a list of Lambda functions, with the version-specific configuration of each function. Lambda
returns up to 50 functions per call. Set `FunctionVersion` to `ALL` to include all published
versions of each function in addition to the unpublished version. The ListFunctions action returns a
subset of the FunctionConfiguration fields.

To get the additional fields (State, StateReasonCode, StateReason, LastUpdateStatus,
LastUpdateStatusReason, LastUpdateStatusReasonCode) for a function or version, use GetFunction.

This operation makes an HTTP GET request to the `/2015-03-31/functions` endpoint.

### Parameters

<table><colgroup><col> <col> <col> <col> <col></colgroup><thead><tr><th>Name</th><th>Type</th><th>Description</th><th>Default Value</th><th>Required</th></tr></thead><tbody><tr><td><p>Configuration</p></td><td><p>String</p></td><td><p>Name of the configuration to use.</p></td><td></td><td><p>x</p></td></tr><tr><td><p>Master Region</p></td><td><div><div><p>String</p></div></div></td><td><p>For Lambda@Edge functions, the AWS Region of the master function. For example, us-east-1 filters the list of functions to include only Lambda@Edge functions replicated from a master function in US East (N. Virginia). If specified, you must set FunctionVersion to ALL.</p></td><td></td><td></td></tr><tr><td><p>Function Version</p></td><td><div><div><p>Enumeration, one of:</p></div><div><ul><li><p>ALL</p></li></ul></div></div></td><td><p>Set to ALL to include entries for all published versions of each function.</p></td><td></td><td></td></tr><tr><td><p>Marker</p></td><td><div><div><p>String</p></div></div></td><td><p>Specify the pagination token that’s returned by a previous request to retrieve the next page of results.</p></td><td></td><td></td></tr><tr><td><p>Max Items</p></td><td><div><div><p>Number</p></div></div></td><td><p>The maximum number of functions to return in the response. Note that ListFunctions returns a maximum of 50 items in each response, even if you set the number higher.</p></td><td></td><td></td></tr><tr><td><p>Config Ref</p></td><td><div><div><p>ConfigurationProvider</p></div></div></td><td><p>Name of the configuration to use to execute this component.</p></td><td></td><td><p>x</p></td></tr><tr><td><p>Streaming Strategy</p></td><td><div><div><ul><li><p><a href="#RepeatableInMemoryStream">Repeatable In Memory Stream</a></p></li><li><p><a href="#RepeatableFileStoreStream">Repeatable File Store Stream</a></p></li><li><p>non-repeatable-stream</p></li></ul></div></div></td><td><p>Configures how Mule processes streams. The default is to use repeatable streams.</p></td><td></td><td></td></tr><tr><td><p>Custom Query Parameters</p></td><td><div><div><p>Object</p></div></div></td><td><p>Custom query parameters to include in the request. The specified query parameters are merged with the default query parameters that are specified in the configuration.</p></td><td><p>#[null]</p></td><td></td></tr><tr><td><p>Custom Headers</p></td><td><div><div><p>Object</p></div></div></td><td><p>Custom headers to include in the request. The specified custom headers are merged with the default headers that are specified in the configuration.</p></td><td></td><td></td></tr><tr><td><p>Response Timeout</p></td><td><div><div><p>Number</p></div></div></td><td><p>Timeout for requests to the remote service. This value is qualified by the <strong>Response Timeout Unit</strong>.</p></td><td></td><td></td></tr><tr><td><p>Response Timeout Unit</p></td><td><div><div><p>Enumeration, one of:</p></div><div><ul><li><p>NANOSECONDS</p></li><li><p>MICROSECONDS</p></li><li><p>MILLISECONDS</p></li><li><p>SECONDS</p></li><li><p>MINUTES</p></li><li><p>HOURS</p></li><li><p>DAYS</p></li></ul></div></div></td><td><p>Time unit for the <strong>Response Timeout</strong> field.</p></td><td></td><td></td></tr><tr><td><p>Target Variable</p></td><td><div><div><p>String</p></div></div></td><td><p>Name of the variable that stores the operation’s output.</p></td><td></td><td></td></tr><tr><td><p>Target Value</p></td><td><div><div><p>String</p></div></div></td><td><p>Expression that evaluates the operation’s output. The outcome of the expression is stored in the <strong>Target Variable</strong>.</p></td><td><p>#[payload]</p></td><td></td></tr><tr><td><p>Reconnection Strategy</p></td><td><div><div><ul><li><p><a href="#Reconnect">Reconnect</a></p></li><li><p><a href="#ReconnectForever">Reconnect Forever</a></p></li></ul></div></div></td><td><p>A retry strategy in case of connectivity errors.</p></td><td></td><td></td></tr></tbody></table>

### Output

<table><colgroup><col> <col></colgroup><tbody><tr><td><p>Type</p></td><td><p>Any</p></td></tr><tr><td><p>Attributes Type</p></td><td><div><div><p><a href="#HttpResponseAttributes">HTTP Response Attributes</a></p></div></div></td></tr></tbody></table>

### For Configurations

- [Configurations](#configurations)

### Throws

- AMAZON-LAMBDA:BAD\_REQUEST

- AMAZON-LAMBDA:CLIENT\_ERROR

- AMAZON-LAMBDA:CONNECTIVITY

- AMAZON-LAMBDA:INTERNAL\_SERVER\_ERROR

- AMAZON-LAMBDA:NOT\_ACCEPTABLE

- AMAZON-LAMBDA:NOT\_FOUND

- AMAZON-LAMBDA:RETRY\_EXHAUSTED

- AMAZON-LAMBDA:SERVER\_ERROR

- AMAZON-LAMBDA:SERVICE\_UNAVAILABLE

- AMAZON-LAMBDA:TIMEOUT

- AMAZON-LAMBDA:TOO\_MANY\_REQUESTS

- AMAZON-LAMBDA:UNAUTHORIZED

- AMAZON-LAMBDA:UNSUPPORTED\_MEDIA\_TYPE

## Get Function

`<amazon-lambda:get20150331-functions-by-function-name>`

Returns information about the function or function version, with a link to download the deployment
package that’s valid for 10 minutes. If you specify a function version, only details that are
specific to that version are returned.

This operation makes an HTTP GET request to the `/2015-03-31/functions/{FunctionName}` endpoint.

### Parameters

<table><colgroup><col> <col> <col> <col> <col></colgroup><thead><tr><th>Name</th><th>Type</th><th>Description</th><th>Default Value</th><th>Required</th></tr></thead><tbody><tr><td><p>Configuration</p></td><td><p>String</p></td><td><p>Name of the configuration to use.</p></td><td></td><td><p>x</p></td></tr><tr><td><p>Function Name</p></td><td><div><div><p>String</p></div></div></td><td><div><div><p>The name of the Lambda function, version, or alias. Name formats:</p></div><div><ul><li><p>Function name: my-function (name-only), my-function:v1 (with alias).</p></li><li><p>Function ARN: arn:aws:lambda:us-west-2:123456789012:function:my-function.</p></li><li><p>Partial ARN: 123456789012:function:my-function.</p></li></ul></div><div><p>You can append a version number or alias to any of the formats. The length constraint applies only to the full ARN. If you specify only the function name, it is limited to 64 characters in length.</p></div></div></td><td></td><td><p>x</p></td></tr><tr><td><p>Qualifier</p></td><td><div><div><p>String</p></div></div></td><td><p>Specify a version or alias to get details about a published version of the function.</p></td><td></td><td></td></tr><tr><td><p>Config Ref</p></td><td><div><div><p>ConfigurationProvider</p></div></div></td><td><p>Name of the configuration to use to execute this component</p></td><td></td><td><p>x</p></td></tr><tr><td><p>Streaming Strategy</p></td><td><div><div><ul><li><p><a href="#RepeatableInMemoryStream">Repeatable In Memory Stream</a></p></li><li><p><a href="#RepeatableFileStoreStream">Repeatable File Store Stream</a></p></li><li><p>non-repeatable-stream</p></li></ul></div></div></td><td><p>Configures how Mule processes streams. The default is to use repeatable streams.</p></td><td></td><td></td></tr><tr><td><p>Custom Query Parameters</p></td><td><div><div><p>Object</p></div></div></td><td><p>Custom query parameters to include in the request. The specified query parameters are merged with the default query parameters that are specified in the configuration.</p></td><td><p>#[null]</p></td><td></td></tr><tr><td><p>Custom Headers</p></td><td><div><div><p>Object</p></div></div></td><td><p>Custom headers to include in the request. The specified custom headers are merged with the default headers that are specified in the configuration.</p></td><td></td><td></td></tr><tr><td><p>Response Timeout</p></td><td><div><div><p>Number</p></div></div></td><td><p>Timeout for requests to the remote service. This value is qualified by the <strong>Response Timeout Unit</strong>.</p></td><td></td><td></td></tr><tr><td><p>Response Timeout Unit</p></td><td><div><div><p>Enumeration, one of:</p></div><div><ul><li><p>NANOSECONDS</p></li><li><p>MICROSECONDS</p></li><li><p>MILLISECONDS</p></li><li><p>SECONDS</p></li><li><p>MINUTES</p></li><li><p>HOURS</p></li><li><p>DAYS</p></li></ul></div></div></td><td><p>Time unit for the <strong>Response Timeout</strong> field.</p></td><td></td><td></td></tr><tr><td><p>Target Variable</p></td><td><div><div><p>String</p></div></div></td><td><p>Name of the variable that stores the operation’s output.</p></td><td></td><td></td></tr><tr><td><p>Target Value</p></td><td><div><div><p>String</p></div></div></td><td><p>Expression that evaluates the operation’s output. The outcome of the expression is stored in the <strong>Target Variable</strong>.</p></td><td><p>#[payload]</p></td><td></td></tr><tr><td><p>Reconnection Strategy</p></td><td><div><div><ul><li><p><a href="#Reconnect">Reconnect</a></p></li><li><p><a href="#ReconnectForever">Reconnect Forever</a></p></li></ul></div></div></td><td><p>A retry strategy in case of connectivity errors.</p></td><td></td><td></td></tr></tbody></table>

### Output

<table><colgroup><col> <col></colgroup><tbody><tr><td><p>Type</p></td><td><p>Any</p></td></tr><tr><td><p>Attributes Type</p></td><td><div><div><p><a href="#HttpResponseAttributes">HTTP Response Attributes</a></p></div></div></td></tr></tbody></table>

### For Configurations

- [Configurations](#configurations)

### Throws

- AMAZON-LAMBDA:BAD\_REQUEST

- AMAZON-LAMBDA:CLIENT\_ERROR

- AMAZON-LAMBDA:CONNECTIVITY

- AMAZON-LAMBDA:INTERNAL\_SERVER\_ERROR

- AMAZON-LAMBDA:NOT\_ACCEPTABLE

- AMAZON-LAMBDA:NOT\_FOUND

- AMAZON-LAMBDA:RETRY\_EXHAUSTED

- AMAZON-LAMBDA:SERVER\_ERROR

- AMAZON-LAMBDA:SERVICE\_UNAVAILABLE

- AMAZON-LAMBDA:TIMEOUT

- AMAZON-LAMBDA:TOO\_MANY\_REQUESTS

- AMAZON-LAMBDA:UNAUTHORIZED

- AMAZON-LAMBDA:UNSUPPORTED\_MEDIA\_TYPE

## Types

### Default Header

<table><colgroup><col> <col> <col> <col> <col></colgroup><thead><tr><th>Field</th><th>Type</th><th>Description</th><th>Default Value</th><th>Required</th></tr></thead><tbody><tr><td><p><strong>Key</strong></p></td><td><div><div><p>String</p></div></div></td><td><div></div></td><td><div></div></td><td><div><div><p>x</p></div></div></td></tr><tr><td><p><strong>Value</strong></p></td><td><div><div><p>String</p></div></div></td><td><div></div></td><td><div></div></td><td><div><div><p>x</p></div></div></td></tr></tbody></table>

### Default Query Param

<table><colgroup><col> <col> <col> <col> <col></colgroup><thead><tr><th>Field</th><th>Type</th><th>Description</th><th>Default Value</th><th>Required</th></tr></thead><tbody><tr><td><p><strong>Key</strong></p></td><td><div><div><p>String</p></div></div></td><td><div></div></td><td><div></div></td><td><div><div><p>x</p></div></div></td></tr><tr><td><p><strong>Value</strong></p></td><td><div><div><p>String</p></div></div></td><td><div></div></td><td><div></div></td><td><div><div><p>x</p></div></div></td></tr></tbody></table>

### Proxy

<table><colgroup><col> <col> <col> <col> <col></colgroup><thead><tr><th>Field</th><th>Type</th><th>Description</th><th>Default Value</th><th>Required</th></tr></thead><tbody><tr><td><p><strong>Host</strong></p></td><td><div><div><p>String</p></div></div></td><td><div></div></td><td><div></div></td><td><div><div><p>x</p></div></div></td></tr><tr><td><p><strong>Port</strong></p></td><td><div><div><p>Number</p></div></div></td><td><div></div></td><td><div></div></td><td><div><div><p>x</p></div></div></td></tr><tr><td><p><strong>Username</strong></p></td><td><div><div><p>String</p></div></div></td><td><div></div></td><td><div></div></td><td><div></div></td></tr><tr><td><p><strong>Password</strong></p></td><td><div><div><p>String</p></div></div></td><td><div></div></td><td><div></div></td><td><div></div></td></tr><tr><td><p><strong>Non Proxy Hosts</strong></p></td><td><div><div><p>String</p></div></div></td><td><div></div></td><td><div></div></td><td><div></div></td></tr></tbody></table>

### TLS

Configures TLS to provide secure communications for your Mule app.

<table><colgroup><col> <col> <col> <col> <col></colgroup><thead><tr><th>Field</th><th>Type</th><th>Description</th><th>Default Value</th><th>Required</th></tr></thead><tbody><tr><td><p><strong>Enabled Protocols</strong></p></td><td><div><div><p>String</p></div></div></td><td><div><div><p>A comma-separated list of protocols enabled for this context.</p></div></div></td><td><div></div></td><td><div></div></td></tr><tr><td><p><strong>Enabled Cipher Suites</strong></p></td><td><div><div><p>String</p></div></div></td><td><div><div><p>A comma-separated list of cipher suites enabled for this context.</p></div></div></td><td><div></div></td><td><div></div></td></tr><tr><td><p><strong>Trust Store</strong></p></td><td><div><div><p><a href="#TrustStore">Truststore</a></p></div></div></td><td><div></div></td><td><div></div></td><td><div></div></td></tr><tr><td><p><strong>Key Store</strong></p></td><td><div><div><p><a href="#KeyStore">Keystore</a></p></div></div></td><td><div></div></td><td><div></div></td><td><div></div></td></tr><tr><td><p><strong>Revocation Check</strong></p></td><td><div><div><ul><li><p><a href="#StandardRevocationCheck">Standard Revocation Check</a></p></li><li><p><a href="#CustomOcspResponder">Custom OCSP Responder</a></p></li><li><p><a href="#CrlFile">CRL File</a></p></li></ul></div></div></td><td><div></div></td><td><div></div></td><td><div></div></td></tr></tbody></table>

### Truststore

<table><colgroup><col> <col> <col> <col> <col></colgroup><thead><tr><th>Field</th><th>Type</th><th>Description</th><th>Default Value</th><th>Required</th></tr></thead><tbody><tr><td><p><strong>Path</strong></p></td><td><div><div><p>String</p></div></div></td><td><div><div><p>Path to the truststore. Mule resolves the path relative to the current classpath and file system, if possible.</p></div></div></td><td><div></div></td><td><div></div></td></tr><tr><td><p><strong>Password</strong></p></td><td><div><div><p>String</p></div></div></td><td><div><div><p>The password used to protect the truststore.</p></div></div></td><td><div></div></td><td><div></div></td></tr><tr><td><p><strong>Type</strong></p></td><td><div><div><p>String</p></div></div></td><td><div><div><p>The type of truststore used.</p></div></div></td><td><div></div></td><td><div></div></td></tr><tr><td><p><strong>Algorithm</strong></p></td><td><div><div><p>String</p></div></div></td><td><div><div><p>The algorithm used by the truststore.</p></div></div></td><td><div></div></td><td><div></div></td></tr><tr><td><p><strong>Insecure</strong></p></td><td><div><div><p>Boolean</p></div></div></td><td><div><div><p>If <code>true</code>, Mule stops performing certificate validations. This can make connections vulnerable to attacks.</p></div></div></td><td><div></div></td><td><div></div></td></tr></tbody></table>

### Keystore

<table><colgroup><col> <col> <col> <col> <col></colgroup><thead><tr><th>Field</th><th>Type</th><th>Description</th><th>Default Value</th><th>Required</th></tr></thead><tbody><tr><td><p><strong>Path</strong></p></td><td><div><div><p>String</p></div></div></td><td><div><div><p>Path to the keystore. Mule resolves the path relative to the current classpath and file system, if possible.</p></div></div></td><td><div></div></td><td><div></div></td></tr><tr><td><p><strong>Type</strong></p></td><td><div><div><p>String</p></div></div></td><td><div><div><p>Type of keystore used.</p></div></div></td><td><div></div></td><td><div></div></td></tr><tr><td><p><strong>Alias</strong></p></td><td><div><div><p>String</p></div></div></td><td><div><div><p>When the keystore contains many private keys, this attribute indicates the alias of the key to use. If not defined, the first key in the file is used by default.</p></div></div></td><td><div></div></td><td><div></div></td></tr><tr><td><p><strong>Key Password</strong></p></td><td><div><div><p>String</p></div></div></td><td><div><div><p>Password used to protect the private key.</p></div></div></td><td><div></div></td><td><div></div></td></tr><tr><td><p><strong>Password</strong></p></td><td><div><div><p>String</p></div></div></td><td><div><div><p>Password used to protect the keystore.</p></div></div></td><td><div></div></td><td><div></div></td></tr><tr><td><p><strong>Algorithm</strong></p></td><td><div><div><p>String</p></div></div></td><td><div><div><p>Algorithm used by the keystore.</p></div></div></td><td><div></div></td><td><div></div></td></tr></tbody></table>

### Standard Revocation Check

<table><colgroup><col> <col> <col> <col> <col></colgroup><thead><tr><th>Field</th><th>Type</th><th>Description</th><th>Default Value</th><th>Required</th></tr></thead><tbody><tr><td><p><strong>Only End Entities</strong></p></td><td><div><div><p>Boolean</p></div></div></td><td><div><div><p>Only verify the last element of the certificate chain.</p></div></div></td><td><div></div></td><td><div></div></td></tr><tr><td><p><strong>Prefer Crls</strong></p></td><td><div><div><p>Boolean</p></div></div></td><td><div><div><p>Try CRL instead of OCSP first.</p></div></div></td><td><div></div></td><td><div></div></td></tr><tr><td><p><strong>No Fallback</strong></p></td><td><div><div><p>Boolean</p></div></div></td><td><div><div><p>Do not use the secondary checking method (the one not selected before).</p></div></div></td><td><div></div></td><td><div></div></td></tr><tr><td><p><strong>Soft Fail</strong></p></td><td><div><div><p>Boolean</p></div></div></td><td><div><div><p>Avoid verification failure when the revocation server can not be reached or is busy.</p></div></div></td><td><div></div></td><td><div></div></td></tr></tbody></table>

### Custom OCSP Responder

<table><colgroup><col> <col> <col> <col> <col></colgroup><thead><tr><th>Field</th><th>Type</th><th>Description</th><th>Default Value</th><th>Required</th></tr></thead><tbody><tr><td><p><strong>Url</strong></p></td><td><div><div><p>String</p></div></div></td><td><div><div><p>The URL of the OCSP responder.</p></div></div></td><td><div></div></td><td><div></div></td></tr><tr><td><p><strong>Cert Alias</strong></p></td><td><div><div><p>String</p></div></div></td><td><div><div><p>Alias of the signing certificate for the OCSP response (must be in the trust store), if present.</p></div></div></td><td><div></div></td><td><div></div></td></tr></tbody></table>

### CRL File

<table><colgroup><col> <col> <col> <col> <col></colgroup><thead><tr><th>Field</th><th>Type</th><th>Description</th><th>Default Value</th><th>Required</th></tr></thead><tbody><tr><td><p><strong>Path</strong></p></td><td><div><div><p>String</p></div></div></td><td><div><div><p>The path to the CRL file.</p></div></div></td><td><div></div></td><td><div></div></td></tr></tbody></table>

### Reconnection

<table><colgroup><col> <col> <col> <col> <col></colgroup><thead><tr><th>Field</th><th>Type</th><th>Description</th><th>Default Value</th><th>Required</th></tr></thead><tbody><tr><td><p><strong>Fails Deployment</strong></p></td><td><div><div><p>Boolean</p></div></div></td><td><div><div><p>When the application is deployed, a connectivity test is performed on all connectors. If set to true, deployment fails if the test doesn’t pass after exhausting the associated reconnection strategy.</p></div></div></td><td><div></div></td><td><div></div></td></tr><tr><td><p><strong>Reconnection Strategy</strong></p></td><td><div><div><ul><li><p><a href="#Reconnect">Reconnect</a></p></li><li><p><a href="#ReconnectForever">Reconnect Forever</a></p></li></ul></div></div></td><td><div><div><p>The reconnection strategy to use.</p></div></div></td><td><div></div></td><td><div></div></td></tr></tbody></table>

### Reconnect

<table><colgroup><col> <col> <col> <col> <col></colgroup><thead><tr><th>Field</th><th>Type</th><th>Description</th><th>Default Value</th><th>Required</th></tr></thead><tbody><tr><td><p><strong>Frequency</strong></p></td><td><div><div><p>Number</p></div></div></td><td><div><div><p>How often in milliseconds to reconnect.</p></div></div></td><td><div></div></td><td><div></div></td></tr><tr><td><p><strong>Blocking</strong></p></td><td><div><div><p>Boolean</p></div></div></td><td><div><div><p>If false, the reconnection strategy will run in a separate, non-blocking thread.</p></div></div></td><td><div></div></td><td><div></div></td></tr><tr><td><p><strong>Count</strong></p></td><td><div><div><p>Number</p></div></div></td><td><div><div><p>How many reconnection attempts to make.</p></div></div></td><td><div></div></td><td><div></div></td></tr></tbody></table>

### Reconnect Forever

<table><colgroup><col> <col> <col> <col> <col></colgroup><thead><tr><th>Field</th><th>Type</th><th>Description</th><th>Default Value</th><th>Required</th></tr></thead><tbody><tr><td><p><strong>Frequency</strong></p></td><td><div><div><p>Number</p></div></div></td><td><div><div><p>How often in milliseconds to reconnect.</p></div></div></td><td><div></div></td><td><div></div></td></tr><tr><td><p><strong>Blocking</strong></p></td><td><div><div><p>Boolean</p></div></div></td><td><div><div><p>If false, the reconnection strategy will run in a separate, non-blocking thread.</p></div></div></td><td><div></div></td><td><div></div></td></tr></tbody></table>

### Expiration Policy

<table><colgroup><col> <col> <col> <col> <col></colgroup><thead><tr><th>Field</th><th>Type</th><th>Description</th><th>Default Value</th><th>Required</th></tr></thead><tbody><tr><td><p><strong>Max Idle Time</strong></p></td><td><div><div><p>Number</p></div></div></td><td><div><div><p>A scalar time value for the maximum amount of time a dynamic configuration instance should be allowed to be idle before it’s considered eligible for expiration.</p></div></div></td><td><div></div></td><td><div></div></td></tr><tr><td><p><strong>Time Unit</strong></p></td><td><div><div><p>Enumeration, one of:</p></div><div><ul><li><p>NANOSECONDS</p></li><li><p>MICROSECONDS</p></li><li><p>MILLISECONDS</p></li><li><p>SECONDS</p></li><li><p>MINUTES</p></li><li><p>HOURS</p></li><li><p>DAYS</p></li></ul></div></div></td><td><div><div><p>Time unit that qualifies the <strong>Max Idle Time</strong> attribute.</p></div></div></td><td><div></div></td><td><div></div></td></tr></tbody></table>

### HTTP Response Attributes

<table><colgroup><col> <col> <col> <col> <col></colgroup><thead><tr><th>Field</th><th>Type</th><th>Description</th><th>Default Value</th><th>Required</th></tr></thead><tbody><tr><td><p><strong>Status Code</strong></p></td><td><div><div><p>Number</p></div></div></td><td><div></div></td><td><div></div></td><td><div><div><p>x</p></div></div></td></tr><tr><td><p><strong>Headers</strong></p></td><td><div><div><p>Object</p></div></div></td><td><div></div></td><td><div></div></td><td><div><div><p>x</p></div></div></td></tr><tr><td><p><strong>Reason Phrase</strong></p></td><td><div><div><p>String</p></div></div></td><td><div></div></td><td><div></div></td><td><div><div><p>x</p></div></div></td></tr></tbody></table>

### Repeatable In Memory Stream

<table><colgroup><col> <col> <col> <col> <col></colgroup><thead><tr><th>Field</th><th>Type</th><th>Description</th><th>Default Value</th><th>Required</th></tr></thead><tbody><tr><td><p><strong>Initial Buffer Size</strong></p></td><td><div><div><p>Number</p></div></div></td><td><div><div><p>Initial amount of memory to allocate to the memory stream. If the stream data exceeds this value, the buffer expands by <strong>Buffer Size Increment</strong>, with an upper limit <strong>Max In Memory Size value</strong>.</p></div></div></td><td><div></div></td><td><div></div></td></tr><tr><td><p><strong>Buffer Size Increment</strong></p></td><td><div><div><p>Number</p></div></div></td><td><div><div><p>Amount by which the buffer size expands if it exceeds its initial size. Setting a value of <code>0</code> or lower specifies that the buffer can’t expand. Mule raises a <code>STREAM_MAXIMUM_SIZE_EXCEEDED</code> error when the buffer gets full.</p></div></div></td><td><div></div></td><td><div></div></td></tr><tr><td><p><strong>Max Buffer Size</strong></p></td><td><div><div><p>Number</p></div></div></td><td><div><div><p>Maximum size of the buffer. A value less than or equal to <code>0</code> means no limit.</p></div></div></td><td><div></div></td><td><div></div></td></tr><tr><td><p><strong>Buffer Unit</strong></p></td><td><div><div><p>Enumeration, one of:</p></div><div><ul><li><p>BYTE</p></li><li><p>KB</p></li><li><p>MB</p></li><li><p>GB</p></li></ul></div></div></td><td><div><div><p>The unit in which all these attributes are expressed</p></div></div></td><td><div></div></td><td><div></div></td></tr></tbody></table>

### Repeatable File Store Stream

<table><colgroup><col> <col> <col> <col> <col></colgroup><thead><tr><th>Field</th><th>Type</th><th>Description</th><th>Default Value</th><th>Required</th></tr></thead><tbody><tr><td><p><strong>In Memory Size</strong></p></td><td><div><div><p>Number</p></div></div></td><td><div><div><p>Defines the maximum memory that the stream should use to keep data in memory. If more than that is consumed content on the disk is buffered.</p></div></div></td><td><div></div></td><td><div></div></td></tr><tr><td><p><strong>Buffer Unit</strong></p></td><td><div><div><p>Enumeration, one of:</p></div><div><ul><li><p>BYTE</p></li><li><p>KB</p></li><li><p>MB</p></li><li><p>GB</p></li></ul></div></div></td><td><div><div><p>The unit in which maxInMemorySize is expressed</p></div></div></td><td><div></div></td><td><div></div></td></tr></tbody></table>

## See Also

- [Amazon Lambda Connector Overview](https://docs.mulesoft.com/amazon-lambda-connector/1.0/)

- [Salesforce Help](https://help.salesforce.com)

<!-- document id=75bcab528c2b8dc1400b7bbb296bcfa230bd47eb79679003119decf01b5ff35a url=/mulesoft/current/en-us/amazon-lambda-connector/1.1/index.md -->

---
product: Amazon Lambda Connector
version: 1.1
---

# Amazon Lambda Connector 1.1

> For the full documentation index, see: https://docs.mulesoft.com/llms.txt

Anypoint Connector for Amazon Lambda (Amazon Lambda Connector) enables you to execute AWS Lambda
operations within your Mule flows. You can then use the response of the Lambda operation to process
another Mule flow as needed.

For compatibility information and fixed issues, see the Amazon Lambda Release Notes.

## Before You Begin

To use this connector, you must be familiar with:

- The AWS Lambda API

- Anypoint Connectors

- Mule runtime engine (Mule)

- Elements and global elements in a Mule flow

- Creating a Mule app using Anypoint Studio or Anypoint Code Builder

Before creating an app, you must have:

- AWS Identity and Access Management (IAM) access key credentials

- Access to the AWS Lambda target resource

- Anypoint Studio version 7.3 or later

## Common Use Case for the Connector

When your app manages large amounts of streaming data from various sources, Amazon Lambda Connector
enables you to send the data stream to an AWS Lambda application that is specifically designed to
quickly pull and process the required information. This enables you to manage necessary realtime
tasks without slowing down your main application.

## Authentication Types

AWS Lambda Connector supports AWS Lambda authentication.

## See Also

- [Introduction to Anypoint Connectors](https://docs.mulesoft.com/connectors/introduction/introduction-to-anypoint-connectors)

- [Use Exchange to Discover Connectors, Templates, and Examples](https://docs.mulesoft.com/connectors/introduction/intro-use-exchange)

- [Salesforce Help](https://help.salesforce.com)

<!-- document id=2fac1325735221a465af9aeadce4c92047a18ff964ee3353f97217926be1766c url=/mulesoft/current/en-us/amazon-lambda-connector/1.1/amazon-lambda-connector-xml-maven.md -->

---
product: Amazon Lambda Connector
version: 1.1
---

# Amazon Lambda Connector 1.1 - XML and Maven Support

> For the full documentation index, see: https://docs.mulesoft.com/llms.txt

Although you can manually code a Mule app in XML, it is more efficient to use Anypoint Studio:

- If you manually code a Mule runtime engine (Mule) app in XML either from the Anypoint Studio XML
  editor or from a text editor, you can access the connector from your app by adding reference
  statements to both your XML Mule flow and the Apache Maven `pom.xml` file.

- If you add the connector in Studio, Studio automatically populates the XML code with the
  connector’s namespace and schema location and it also adds a dependency to the `pom.xml` file.

## Add a Namespace for the Connector

Paste the following code inside the `mule` tag of the header of your configuration XML:

```xml
http://www.mulesoft.org/schema/mule/amazon-lambda
http://www.mulesoft.org/schema/mule/amazon-lambda/current/mule-amazon-lambda.xsd
```

This example shows how the namespace statements are placed in the XML:

```xml
<mule xmlns:amazon-lambda="http://www.mulesoft.org/schema/mule/amazon-lambda"
	xmlns="http://www.mulesoft.org/schema/mule/core"
	xmlns:doc="http://www.mulesoft.org/schema/mule/documentation"
	xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
	xsi:schemaLocation="http://www.mulesoft.org/schema/mule/core
	http://www.mulesoft.org/schema/mule/core/current/mule.xsd
	http://www.mulesoft.org/schema/mule/amazon-lambda
	http://www.mulesoft.org/schema/mule/amazon-lambda/current/mule-amazon-lambda.xsd">
```

## Add a POM File Dependency

The Apache Maven `pom.xml` file generated by Anypoint Studio contains dependencies for a Mule app.
When you code a Mule app manually, include this XML snippet in your `pom.xml` file to enable access
to this connector:

```xml
<dependency>
  <groupId>com.mulesoft.connectors</groupId>
  <artifactId>mule4-amazon-lambda-connector</artifactId>
  <version>1.1.0</version>
  <classifier>mule-plugin</classifier>
</dependency>
```

Replace the value for `<version>` with the version that corresponds to the connector you are using.

To obtain the most up-to-date `pom.xml` file information:

1.  Go to [Anypoint Exchange](https://www.mulesoft.com/exchange/).

2.  In Exchange, click **Login** and supply your Anypoint Platform username and password.

3.  In Exchange, search for `amazon lambda`.

4.  Select the connector.

5.  Click **Dependency Snippets** near the upper right of the screen.

## See Also

- [Introduction to Anypoint Connectors](https://docs.mulesoft.com/connectors/introduction/introduction-to-anypoint-connectors)

- [Salesforce Help](https://help.salesforce.com)

<!-- document id=2cd7cc508bf0e6d91c43cc38d8e46da251dfdf1a7e247dbdee77c39332344af4 url=/mulesoft/current/en-us/amazon-lambda-connector/1.1/amazon-lambda-connector-examples.md -->

---
product: Amazon Lambda Connector
version: 1.1
---

# Amazon Lambda Connector 1.1 Examples

> For the full documentation index, see: https://docs.mulesoft.com/llms.txt

This example shows how to use the Anypoint Connector for Amazon Lambda (Amazon Lambda Connector) to
invoke a synchronous call and get results from AWS Lambda.

## Before You Begin

Verify that Amazon Lambda Connector is added to your Mule project in Anypoint Studio. If it’s not,
follow the instructions in
[Add the Connector to Your Mule Project](https://docs.mulesoft.com/amazon-lambda-connector/1.1/amazon-lambda-connector-studio#add-connector-to-project).

## Synchronous Invocation Flow

This example shows a simple AWS Lambda function call that is invoked using an HTTP listener. When
the `http://localhost:8081/invoke` URL is called, the Lambda **Invoke** operation is performed, and
the result is returned directly to you.

### Create the Configuration File

1.  In Studio, go to the **Package Explorer** view and right-click the `/src/main/resources` folder
    in your project.

2.  Select **New > File**.

3.  Name the file `environment.properties`.

4.  Edit the file to define the properties and values you need.

### Configure HTTP Listener

Configure an HTTP Listener source to initiate the Amazon Lambda Connector **Invoke** operation flow
each time it receives a request on the configured host (`localhost`) and port (`8081`):

1.  In **Mule Palette**, select **HTTP > Listener**.

2.  Drag **Listener** to the Studio canvas.

3.  Click **+** next to **Connector configuration** to configure a global element that can be used
    by all instances of the HTTP Listener source in the app.

4.  In the **General** tab, specify connection information for the connector.

5.  Click **Test Connection** to confirm that Mule can connect with the specified server.

6.  Click **OK**.

### Configure the Invoke Operation

1.  In **Mule Palette**, select **Amazon Lambda Connector > Invoke**.

2.  Drag **Invoke** to the Studio canvas to the right of the **Listener** source:

    ![Simple invoke example flow in Studio](/mulesoft/current/en-us/amazon-lambda-connector/1.1/_images/amazon-lambda-simple-invoke-example.png)

3.  Configure the **Invoke** operation:

    ![Simple invoke operation General properties configuration](/mulesoft/current/en-us/amazon-lambda-connector/1.1/_images/amazon-lambda-simple-invoke-example-properties.png)

    In this example, the function name is supplied in the `environment.properties` file as
    `$config.functionName`.

    The payload from the HTTP Listener is passed directly into the body of the **Invoke** operation,
    which is specified as `REQUEST_RESPONSE`. This tells AWS Lambda that it does not need to store
    any logs for this operation and effectively makes this a synchronous call, which waits until the
    AWS Lambda function is finished processing before it returns its results.

    Alternatively, you can set **Invocation Type** to `EVENT`, which acts like an asynchronous call
    and returns an empty response immediately while AWS Lambda performs its action in the
    background.

### Create an AWS Lambda Function

Depending on your Lambda function, when you run this flow, you might need to send in a request body.
For example, you can create a Python 3.8 Lambda function like this:

```python
def lambda_handler(event, context):
    message = 'Hello {} {}!'.format(event['first_name'], event['last_name'])

	return {'message' : message}
```

Consult the official AWS documentation if you don’t know how to create a new AWS Lambda function.

This function takes the fields `first_name` and `last_name` from the input in JSON format and sends
a greeting using the specified first and last names.

Call the `http://localhost:8081/invoke` endpoint with a JSON body like this:

```json
{
  "first_name": "<first_name>",
  "last_name": "<last_name>"
}
```

The Mule flow responds with a Code 200 message:

{ "message": "Hello <first\_name> <last\_name>!" }

## XML for the Invoke Example

Paste this code into the Studio XML editor to quickly load the flow for this example into your Mule
app:

```xml
<?xml version="1.0" encoding="UTF-8"?>

<mule xmlns:amazon-lambda="http://www.mulesoft.org/schema/mule/amazon-lambda" xmlns:http="http://www.mulesoft.org/schema/mule/http"
	xmlns="http://www.mulesoft.org/schema/mule/core"
	xmlns:doc="http://www.mulesoft.org/schema/mule/documentation" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.mulesoft.org/schema/mule/core http://www.mulesoft.org/schema/mule/core/current/mule.xsd
http://www.mulesoft.org/schema/mule/http http://www.mulesoft.org/schema/mule/http/current/mule-http.xsd
http://www.mulesoft.org/schema/mule/amazon-lambda http://www.mulesoft.org/schema/mule/amazon-lambda/current/mule-amazon-lambda.xsd">
	<flow name="amazon-lambda-invoke-example">
		<http:listener doc:name="Listener" config-ref="HTTP_Listener_config" path="/invoke"/>
		<amazon-lambda:create20150331-functions-invocations-by-function-name doc:name="Invoke" config-ref="Test_Aws_Config" functionName="${config.functionName}" xAmzInvocationType="REQUEST_RESPONSE">
		</amazon-lambda:create20150331-functions-invocations-by-function-name>
	</flow>
</mule>
```

### See Also

- [Introduction to Anypoint Connectors](https://docs.mulesoft.com/connectors/introduction/introduction-to-anypoint-connectors)

- [Anypoint Connector Configuration](https://docs.mulesoft.com/connectors/introduction/intro-connector-configuration-overview).

- [Amazon Lambda Connector Reference](https://docs.mulesoft.com/amazon-lambda-connector/1.1/amazon-lambda-connector-reference).

- [Salesforce Help](https://help.salesforce.com)

<!-- document id=b99a0bd569c2848b95ec232cb87be9eef450eb25bf59fc0f440669121a79beb4 url=/mulesoft/current/en-us/amazon-lambda-connector/1.1/amazon-lambda-connector-reference.md -->

---
product: Amazon Lambda Connector
version: 1.1
---

# Amazon Lambda Connector 1.1 Reference

> For the full documentation index, see: https://docs.mulesoft.com/llms.txt

Anypoint Connector for Amazon Lambda (Amazon Lambda Connector) provides access to standard Amazon
Lambda operations using Anypoint Platform.

## Configurations

<table><colgroup><col> <col> <col> <col> <col></colgroup><thead><tr><th>Name</th><th>Type</th><th>Description</th><th>Default Value</th><th>Required</th></tr></thead><tbody><tr><td><p>Name</p></td><td><p>String</p></td><td><p>The name for this configuration. Connectors reference the configuration with this name.</p></td><td></td><td><p>x</p></td></tr><tr><td><p>Connection</p></td><td><div><div><p><a href="#Config_Connection">Amazon Lambda Connection</a></p></div></div></td><td><p>The connection types to provide to this configuration.</p></td><td></td><td><p>x</p></td></tr><tr><td><p>Response Timeout</p></td><td><div><div><p>Number</p></div></div></td><td><p>Timeout for requests to the remote service. This value is qualified by the <strong>Response Timeout Unit</strong> field.</p></td><td><p>1</p></td><td></td></tr><tr><td><p>Response Timeout Unit</p></td><td><div><div><p>Enumeration, one of:</p></div><div><ul><li><p>NANOSECONDS</p></li><li><p>MICROSECONDS</p></li><li><p>MILLISECONDS</p></li><li><p>SECONDS</p></li><li><p>MINUTES</p></li><li><p>HOURS</p></li><li><p>DAYS</p></li></ul></div></div></td><td><p>Time unit for the <strong>Response Timeout</strong> field.</p></td><td><p>MINUTES</p></td><td></td></tr><tr><td><p>Name</p></td><td><div><div><p>String</p></div></div></td><td><p>Identifier of this element, which is used to reference it in other components.</p></td><td></td><td><p>x</p></td></tr><tr><td><p>Expiration Policy</p></td><td><div><div><p><a href="#ExpirationPolicy">Expiration Policy</a></p></div></div></td><td><p>Minimum amount of time that a dynamic configuration instance can remain idle before Mule considers it eligible for expiration.</p></td><td></td><td></td></tr></tbody></table>

## Connection Types

### Amazon Lambda Connection

<table><colgroup><col> <col> <col> <col> <col></colgroup><thead><tr><th>Name</th><th>Type</th><th>Description</th><th>Default Value</th><th>Required</th></tr></thead><tbody><tr><td><p>Default Headers</p></td><td><div><div><p>Array of <a href="#DefaultHeader">Default Header</a></p></div></div></td><td></td><td></td><td></td></tr><tr><td><p>Query Parameters</p></td><td><div><div><p>Array of <a href="#DefaultQueryParam">Default Query Param</a></p></div></div></td><td></td><td></td><td></td></tr><tr><td><p>Connection Timeout</p></td><td><div><div><p>Number</p></div></div></td><td><p>Timeout for establishing connections to the remote service.</p></td><td><p>30</p></td><td></td></tr><tr><td><p>Connection Timeout Unit</p></td><td><div><div><p>Enumeration, one of:</p></div><div><ul><li><p>NANOSECONDS</p></li><li><p>MICROSECONDS</p></li><li><p>MILLISECONDS</p></li><li><p>SECONDS</p></li><li><p>MINUTES</p></li><li><p>HOURS</p></li><li><p>DAYS</p></li></ul></div></div></td><td><p>Time unit for the <strong>Connection Timeout</strong> field.</p></td><td><p>SECONDS</p></td><td></td></tr><tr><td><p>Use Persistent Connections</p></td><td><div><div><p>Boolean</p></div></div></td><td><p>If false, each connection is closed after the first request is completed.</p></td><td><p>true</p></td><td></td></tr><tr><td><p>Max Connections</p></td><td><div><div><p>Number</p></div></div></td><td><p>Maximum number of outbound connections to keep open at the same time.</p></td><td><p>-1</p></td><td></td></tr><tr><td><p>Connection Idle Timeout</p></td><td><div><div><p>Number</p></div></div></td><td><p>Timeout for how long a connection can remain idle before it is closed.</p></td><td><p>30</p></td><td></td></tr><tr><td><p>Connection Idle Timeout Unit</p></td><td><div><div><p>Enumeration, one of:</p></div><div><ul><li><p>NANOSECONDS</p></li><li><p>MICROSECONDS</p></li><li><p>MILLISECONDS</p></li><li><p>SECONDS</p></li><li><p>MINUTES</p></li><li><p>HOURS</p></li><li><p>DAYS</p></li></ul></div></div></td><td><p>Time unit for the <strong>Connection Idle Timeout</strong> field.</p></td><td><p>SECONDS</p></td><td></td></tr><tr><td><p>Proxy Config</p></td><td><div><div><p><a href="#Proxy">Proxy</a></p></div></div></td><td><p>Reusable configuration element for outbound connections through a proxy.</p></td><td></td><td></td></tr><tr><td><p>Stream Response</p></td><td><div><div><p>Boolean</p></div></div></td><td><p>Whether or not to stream received responses.</p></td><td><p>false</p></td><td></td></tr><tr><td><p>Response Buffer Size</p></td><td><div><div><p>Number</p></div></div></td><td><p>Space in bytes for the buffer where the HTTP response will be stored.</p></td><td><p>-1</p></td><td></td></tr><tr><td><p>Access Key</p></td><td><div><div><p>String</p></div></div></td><td><p>The access key provided by Amazon.</p></td><td></td><td><p>x</p></td></tr><tr><td><p>Secret Key</p></td><td><div><div><p>String</p></div></div></td><td><p>The secret key provided by Amazon.</p></td><td></td><td><p>x</p></td></tr><tr><td><p>Role ARN</p></td><td><div><div><p>String</p></div></div></td><td><p>The ARN of the role to use.</p></td><td></td><td></td></tr><tr><td><p>Region</p></td><td><div><div><p>String</p></div></div></td><td><p>The region of the Amazon instance.</p></td><td><p>us-east-1</p></td><td></td></tr><tr><td><p>Custom Service Endpoint</p></td><td><div><div><p>String</p></div></div></td><td><p>Sets a custom service endpoint. Useful when a non-standard service endpoint is required, such as a VPC endpoint.</p></td><td></td><td></td></tr><tr><td><p>Custom STS Endpoint</p></td><td><div><div><p>String</p></div></div></td><td><p>Sets a custom STS endpoint. Useful when a non-standard service endpoint is required, such as a VPC endpoint. The custom STS endpoint might not work if <code>DefaultAWSCredentialsProviderChain</code> is used. Instead, use AWS environment variables such as <code>AWS_STS_REGIONAL_ENDPOINTS</code>, <code>AWS_REGION</code>, and <code>AWS_ENDPOINT_URL</code>.</p></td><td></td><td></td></tr><tr><td><p>Protocol</p></td><td><div><div><p>Enumeration, one of:</p></div><div><ul><li><p>HTTP</p></li><li><p>HTTPS</p></li></ul></div></div></td><td><p>Protocol to use for communication. Valid values are HTTP and HTTPS.</p></td><td><p>HTTP</p></td><td></td></tr><tr><td><p>TLS Configuration</p></td><td><div><div><p><a href="#Tls">TLS</a></p></div></div></td><td></td><td></td><td></td></tr><tr><td><p>Reconnection</p></td><td><div><div><p><a href="#Reconnection">Reconnection</a></p></div></div></td><td><p>When the application is deployed, a connectivity test is performed on all connectors. If set to true, deployment fails if the test doesn’t pass after exhausting the associated reconnection strategy.</p></td><td></td><td></td></tr></tbody></table>

## Operations

- [Invoke Async](#Create20141113FunctionsInvokeAsyncByFunctionName)

- [Invoke](#Create20150331FunctionsInvocationsByFunctionName)

- [List Functions](#Get20150331Functions)

- [Get Function](#Get20150331FunctionsByFunctionName)

## Invoke Async

`<amazon-lambda:create20141113-functions-invoke-async-by-function-name>`

For asynchronous function invocation, use Invoke. Invokes a function asynchronously. This operation
makes an HTTP POST request to the `/2014-11-13/functions/{FunctionName}/invoke-async/` endpoint.

### Parameters

<table><colgroup><col> <col> <col> <col> <col></colgroup><thead><tr><th>Name</th><th>Type</th><th>Description</th><th>Default Value</th><th>Required</th></tr></thead><tbody><tr><td><p>Configuration</p></td><td><p>String</p></td><td><p>The name of the configuration to use.</p></td><td></td><td><p>x</p></td></tr><tr><td><p>Function Name</p></td><td><div><div><p>String</p></div></div></td><td><div><div><p>Name of the Lambda function. Name formats:</p></div><div><ul><li><p>Function name: my-function.</p></li><li><p>Function ARN: arn:aws:lambda:us-west-2:123456789012:function:my-function.</p></li><li><p>Partial ARN: 123456789012:function:my-function.</p></li></ul></div><div><p>The length constraint applies only to the full ARN. If you specify only the function name, it is limited to 64 characters in length.</p></div></div></td><td></td><td><p>x</p></td></tr><tr><td><p>Body</p></td><td><div><div><p>Any</p></div></div></td><td><p>the content to use</p></td><td><p>#[payload]</p></td><td></td></tr><tr><td><p>Config Ref</p></td><td><div><div><p>ConfigurationProvider</p></div></div></td><td><p>The name of the configuration to use to execute this component.</p></td><td></td><td><p>x</p></td></tr><tr><td><p>Streaming Strategy</p></td><td><div><div><ul><li><p><a href="#RepeatableInMemoryStream">Repeatable In Memory Stream</a></p></li><li><p><a href="#RepeatableFileStoreStream">Repeatable File Store Stream</a></p></li><li><p>non-repeatable-stream</p></li></ul></div></div></td><td><p>Configures how Mule processes streams. The default is to use repeatable streams.</p></td><td></td><td></td></tr><tr><td><p>Custom Query Parameters</p></td><td><div><div><p>Object</p></div></div></td><td><p>Custom query parameters to include in the request. The specified query parameters are merged with the default query parameters that are specified in the configuration.</p></td><td></td><td></td></tr><tr><td><p>Custom Headers</p></td><td><div><div><p>Object</p></div></div></td><td><p>Custom headers to include in the request. The specified custom headers are merged with the default headers that are specified in the configuration.</p></td><td></td><td></td></tr><tr><td><p>Response Timeout</p></td><td><div><div><p>Number</p></div></div></td><td><p>Timeout for requests to the remote service. This value is qualified by the <strong>Response Timeout Unit</strong>.</p></td><td></td><td></td></tr><tr><td><p>Response Timeout Unit</p></td><td><div><div><p>Enumeration, one of:</p></div><div><ul><li><p>NANOSECONDS</p></li><li><p>MICROSECONDS</p></li><li><p>MILLISECONDS</p></li><li><p>SECONDS</p></li><li><p>MINUTES</p></li><li><p>HOURS</p></li><li><p>DAYS</p></li></ul></div></div></td><td><p>Time unit for the <strong>Response Timeout</strong> field.</p></td><td></td><td></td></tr><tr><td><p>Target Variable</p></td><td><div><div><p>String</p></div></div></td><td><p>Name of the variable that stores the operation’s output.</p></td><td></td><td></td></tr><tr><td><p>Target Value</p></td><td><div><div><p>String</p></div></div></td><td><p>Expression that evaluates the operation’s output. The outcome of the expression is stored in the <strong>Target Variable</strong>.</p></td><td><p>#[payload]</p></td><td></td></tr><tr><td><p>Reconnection Strategy</p></td><td><div><div><ul><li><p><a href="#Reconnect">Reconnect</a></p></li><li><p><a href="#ReconnectForever">Reconnect Forever</a></p></li></ul></div></div></td><td><p>A retry strategy in case of connectivity errors.</p></td><td></td><td></td></tr></tbody></table>

### Output

<table><colgroup><col> <col></colgroup><tbody><tr><td><p>Type</p></td><td><p>Any</p></td></tr><tr><td><p>Attributes Type</p></td><td><div><div><p><a href="#HttpResponseAttributes">HTTP Response Attributes</a></p></div></div></td></tr></tbody></table>

### For Configurations

- [Configurations](#configurations)

### Throws

- AMAZON-LAMBDA:BAD\_REQUEST

- AMAZON-LAMBDA:CLIENT\_ERROR

- AMAZON-LAMBDA:CONNECTIVITY

- AMAZON-LAMBDA:INTERNAL\_SERVER\_ERROR

- AMAZON-LAMBDA:NOT\_ACCEPTABLE

- AMAZON-LAMBDA:NOT\_FOUND

- AMAZON-LAMBDA:RETRY\_EXHAUSTED

- AMAZON-LAMBDA:SERVER\_ERROR

- AMAZON-LAMBDA:SERVICE\_UNAVAILABLE

- AMAZON-LAMBDA:TIMEOUT

- AMAZON-LAMBDA:TOO\_MANY\_REQUESTS

- AMAZON-LAMBDA:UNAUTHORIZED

- AMAZON-LAMBDA:UNSUPPORTED\_MEDIA\_TYPE

## Invoke

`<amazon-lambda:create20150331-functions-invocations-by-function-name>`

Invokes a Lambda function. You can invoke a function synchronously (and wait for the response), or
asynchronously.

To invoke a function asynchronously, set `InvocationType` to `Event`.

For synchronous invocation, details about the function response, including errors, are included in
the response body and headers. For either invocation type, you can find more information in the
execution log and trace.

When an error occurs, your function may be invoked multiple times. Retry behavior varies by error
type, client, event source, and invocation type. For example, if you invoke a function
asynchronously and it returns an error, Lambda executes the function up to two more times. For more
information, see Retry Behavior.

For asynchronous invocation, Lambda adds events to a queue before sending them to your function. If
your function does not have enough capacity to keep up with the queue, events may be lost.
Occasionally, your function might receive the same event multiple times, even if no error occurs.

To retain events that were not processed, configure your function with a dead-letter queue. The
status code in the API response doesn’t reflect function errors. Error codes are reserved for errors
that prevent your function from executing, such as permissions errors, limit errors, or issues with
your function’s code and configuration. For example, Lambda returns `TooManyRequestsException` if
executing the function causes you to exceed a concurrency limit at either the account level
(`ConcurrentInvocationLimitExceeded`) or function level
(`ReservedFunctionConcurrentInvocationLimitExceeded`).

For functions with a long timeout, your client might be disconnected during synchronous invocation
while it waits for a response. Configure your HTTP client, SDK, firewall, proxy, or operating system
to allow for long connections with timeout or keep-alive settings.

This operation requires permission for the lambda:InvokeFunction action.

This operation makes an HTTP POST request to the `/2015-03-31/functions/{FunctionName}/invocations`
endpoint.

### Parameters

<table><colgroup><col> <col> <col> <col> <col></colgroup><thead><tr><th>Name</th><th>Type</th><th>Description</th><th>Default Value</th><th>Required</th></tr></thead><tbody><tr><td><p>Configuration</p></td><td><p>String</p></td><td><p>Name of the configuration to use.</p></td><td></td><td><p>x</p></td></tr><tr><td><p>Function Name</p></td><td><div><div><p>String</p></div></div></td><td><div><div><p>Name of the Lambda function, version, or alias. Name formats:</p></div><div><ul><li><p>Function name: my-function (name-only), my-function:v1 (with alias).</p></li><li><p>Function ARN: arn:aws:lambda:us-west-2:123456789012:function:my-function.</p></li><li><p>Partial ARN: 123456789012:function:my-function.</p></li></ul></div><div><p>You can append a version number or alias to any of the formats. The length constraint applies only to the full ARN. If you specify only the function name, it is limited to 64 characters in length.</p></div></div></td><td></td><td><p>x</p></td></tr><tr><td><p>Qualifier</p></td><td><div><div><p>String</p></div></div></td><td><p>Specify a version or alias to invoke a published version of the function.</p></td><td></td><td></td></tr><tr><td><p>X Amz Invocation Type</p></td><td><div><div><p>Enumeration, one of:</p></div><div><ul><li><p>EVENT</p></li><li><p>REQUEST_RESPONSE</p></li><li><p>DRY_RUN</p></li></ul></div></div></td><td><div><div><p>Choose from the following options:</p></div><div><ul><li><p>RequestResponse (default): Invoke the function synchronously. Keep the connection open until the function returns a response or times out. The API response includes the function response and additional data.</p></li><li><p>Event: Invoke the function asynchronously. Send events that fail multiple times to the function’s dead-letter queue (if it’s configured). The API response only includes a status code.</p></li><li><p>DryRun: Validate parameter values and verify that the user or role has permission to invoke the function.</p></li></ul></div></div></td><td></td><td></td></tr><tr><td><p>X Amz Log Type</p></td><td><div><div><p>Enumeration, one of:</p></div><div><ul><li><p>NONE</p></li><li><p>TAIL</p></li></ul></div></div></td><td><p>Set to <code>TAIL</code> to include the execution log in the response.</p></td><td></td><td></td></tr><tr><td><p>X Amz Client Context</p></td><td><div><div><p>String</p></div></div></td><td><p>Up to 3583 bytes of Base64-encoded data about the invoking client to pass to the function in the context object.</p></td><td></td><td></td></tr><tr><td><p>Body</p></td><td><div><div><p>Any</p></div></div></td><td><p>Content to use.</p></td><td><p>#[payload]</p></td><td></td></tr><tr><td><p>Config Ref</p></td><td><div><div><p>ConfigurationProvider</p></div></div></td><td><p>Name of the configuration to use to execute this component.</p></td><td></td><td><p>x</p></td></tr><tr><td><p>Streaming Strategy</p></td><td><div><div><ul><li><p><a href="#RepeatableInMemoryStream">Repeatable In Memory Stream</a></p></li><li><p><a href="#RepeatableFileStoreStream">Repeatable File Store Stream</a></p></li><li><p>non-repeatable-stream</p></li></ul></div></div></td><td><p>Configures how Mule processes streams. The default is to use repeatable streams.</p></td><td></td><td></td></tr><tr><td><p>Custom Query Parameters</p></td><td><div><div><p>Object</p></div></div></td><td><p>Custom query parameters to include in the request. The specified query parameters are merged with the default query parameters that are specified in the configuration.</p></td><td></td><td></td></tr><tr><td><p>Custom Headers</p></td><td><div><div><p>Object</p></div></div></td><td><p>Custom headers to include in the request. The specified custom headers are merged with the default headers that are specified in the configuration.</p></td><td></td><td></td></tr><tr><td><p>Response Timeout</p></td><td><div><div><p>Number</p></div></div></td><td><p>Timeout for requests to the remote service. This value is qualified by the <strong>Response Timeout Unit</strong>.</p></td><td></td><td></td></tr><tr><td><p>Response Timeout Unit</p></td><td><div><div><p>Enumeration, one of:</p></div><div><ul><li><p>NANOSECONDS</p></li><li><p>MICROSECONDS</p></li><li><p>MILLISECONDS</p></li><li><p>SECONDS</p></li><li><p>MINUTES</p></li><li><p>HOURS</p></li><li><p>DAYS</p></li></ul></div></div></td><td><p>Time unit for the <strong>Response Timeout</strong> field.</p></td><td></td><td></td></tr><tr><td><p>Target Variable</p></td><td><div><div><p>String</p></div></div></td><td><p>Name of the variable that stores the operation’s output.</p></td><td></td><td></td></tr><tr><td><p>Target Value</p></td><td><div><div><p>String</p></div></div></td><td><p>Expression that evaluates the operation’s output. The outcome of the expression is stored in the <strong>Target Variable</strong>.</p></td><td><p>#[payload]</p></td><td></td></tr><tr><td><p>Reconnection Strategy</p></td><td><div><div><ul><li><p><a href="#Reconnect">Reconnect</a></p></li><li><p><a href="#ReconnectForever">Reconnect Forever</a></p></li></ul></div></div></td><td><p>A retry strategy in case of connectivity errors.</p></td><td></td><td></td></tr></tbody></table>

### Output

<table><colgroup><col> <col></colgroup><tbody><tr><td><p>Type</p></td><td><p>Any</p></td></tr><tr><td><p>Attributes Type</p></td><td><div><div><p><a href="#HttpResponseAttributes">HTTP Response Attributes</a></p></div></div></td></tr></tbody></table>

### For Configurations

- [Configurations](#configurations)

### Throws

- AMAZON-LAMBDA:BAD\_REQUEST

- AMAZON-LAMBDA:CLIENT\_ERROR

- AMAZON-LAMBDA:CONNECTIVITY

- AMAZON-LAMBDA:INTERNAL\_SERVER\_ERROR

- AMAZON-LAMBDA:NOT\_ACCEPTABLE

- AMAZON-LAMBDA:NOT\_FOUND

- AMAZON-LAMBDA:RETRY\_EXHAUSTED

- AMAZON-LAMBDA:SERVER\_ERROR

- AMAZON-LAMBDA:SERVICE\_UNAVAILABLE

- AMAZON-LAMBDA:TIMEOUT

- AMAZON-LAMBDA:TOO\_MANY\_REQUESTS

- AMAZON-LAMBDA:UNAUTHORIZED

- AMAZON-LAMBDA:UNSUPPORTED\_MEDIA\_TYPE

## List Functions

`<amazon-lambda:get20150331-functions>`

Returns a list of Lambda functions, with the version-specific configuration of each function. Lambda
returns up to 50 functions per call. Set `FunctionVersion` to `ALL` to include all published
versions of each function in addition to the unpublished version. The ListFunctions action returns a
subset of the FunctionConfiguration fields.

To get the additional fields (State, StateReasonCode, StateReason, LastUpdateStatus,
LastUpdateStatusReason, LastUpdateStatusReasonCode) for a function or version, use GetFunction.

This operation makes an HTTP GET request to the `/2015-03-31/functions` endpoint.

### Parameters

<table><colgroup><col> <col> <col> <col> <col></colgroup><thead><tr><th>Name</th><th>Type</th><th>Description</th><th>Default Value</th><th>Required</th></tr></thead><tbody><tr><td><p>Configuration</p></td><td><p>String</p></td><td><p>Name of the configuration to use.</p></td><td></td><td><p>x</p></td></tr><tr><td><p>Master Region</p></td><td><div><div><p>String</p></div></div></td><td><p>For Lambda@Edge functions, the AWS Region of the master function. For example, us-east-1 filters the list of functions to include only Lambda@Edge functions replicated from a master function in US East (N. Virginia). If specified, you must set FunctionVersion to ALL.</p></td><td></td><td></td></tr><tr><td><p>Function Version</p></td><td><div><div><p>Enumeration, one of:</p></div><div><ul><li><p>ALL</p></li></ul></div></div></td><td><p>Set to ALL to include entries for all published versions of each function.</p></td><td></td><td></td></tr><tr><td><p>Marker</p></td><td><div><div><p>String</p></div></div></td><td><p>Specify the pagination token that’s returned by a previous request to retrieve the next page of results.</p></td><td></td><td></td></tr><tr><td><p>Max Items</p></td><td><div><div><p>Number</p></div></div></td><td><p>The maximum number of functions to return in the response. Note that ListFunctions returns a maximum of 50 items in each response, even if you set the number higher.</p></td><td></td><td></td></tr><tr><td><p>Config Ref</p></td><td><div><div><p>ConfigurationProvider</p></div></div></td><td><p>Name of the configuration to use to execute this component.</p></td><td></td><td><p>x</p></td></tr><tr><td><p>Streaming Strategy</p></td><td><div><div><ul><li><p><a href="#RepeatableInMemoryStream">Repeatable In Memory Stream</a></p></li><li><p><a href="#RepeatableFileStoreStream">Repeatable File Store Stream</a></p></li><li><p>non-repeatable-stream</p></li></ul></div></div></td><td><p>Configures how Mule processes streams. The default is to use repeatable streams.</p></td><td></td><td></td></tr><tr><td><p>Custom Query Parameters</p></td><td><div><div><p>Object</p></div></div></td><td><p>Custom query parameters to include in the request. The specified query parameters are merged with the default query parameters that are specified in the configuration.</p></td><td><p>#[null]</p></td><td></td></tr><tr><td><p>Custom Headers</p></td><td><div><div><p>Object</p></div></div></td><td><p>Custom headers to include in the request. The specified custom headers are merged with the default headers that are specified in the configuration.</p></td><td></td><td></td></tr><tr><td><p>Response Timeout</p></td><td><div><div><p>Number</p></div></div></td><td><p>Timeout for requests to the remote service. This value is qualified by the <strong>Response Timeout Unit</strong>.</p></td><td></td><td></td></tr><tr><td><p>Response Timeout Unit</p></td><td><div><div><p>Enumeration, one of:</p></div><div><ul><li><p>NANOSECONDS</p></li><li><p>MICROSECONDS</p></li><li><p>MILLISECONDS</p></li><li><p>SECONDS</p></li><li><p>MINUTES</p></li><li><p>HOURS</p></li><li><p>DAYS</p></li></ul></div></div></td><td><p>Time unit for the <strong>Response Timeout</strong> field.</p></td><td></td><td></td></tr><tr><td><p>Target Variable</p></td><td><div><div><p>String</p></div></div></td><td><p>Name of the variable that stores the operation’s output.</p></td><td></td><td></td></tr><tr><td><p>Target Value</p></td><td><div><div><p>String</p></div></div></td><td><p>Expression that evaluates the operation’s output. The outcome of the expression is stored in the <strong>Target Variable</strong>.</p></td><td><p>#[payload]</p></td><td></td></tr><tr><td><p>Reconnection Strategy</p></td><td><div><div><ul><li><p><a href="#Reconnect">Reconnect</a></p></li><li><p><a href="#ReconnectForever">Reconnect Forever</a></p></li></ul></div></div></td><td><p>A retry strategy in case of connectivity errors.</p></td><td></td><td></td></tr></tbody></table>

### Output

<table><colgroup><col> <col></colgroup><tbody><tr><td><p>Type</p></td><td><p>Any</p></td></tr><tr><td><p>Attributes Type</p></td><td><div><div><p><a href="#HttpResponseAttributes">HTTP Response Attributes</a></p></div></div></td></tr></tbody></table>

### For Configurations

- [Configurations](#configurations)

### Throws

- AMAZON-LAMBDA:BAD\_REQUEST

- AMAZON-LAMBDA:CLIENT\_ERROR

- AMAZON-LAMBDA:CONNECTIVITY

- AMAZON-LAMBDA:INTERNAL\_SERVER\_ERROR

- AMAZON-LAMBDA:NOT\_ACCEPTABLE

- AMAZON-LAMBDA:NOT\_FOUND

- AMAZON-LAMBDA:RETRY\_EXHAUSTED

- AMAZON-LAMBDA:SERVER\_ERROR

- AMAZON-LAMBDA:SERVICE\_UNAVAILABLE

- AMAZON-LAMBDA:TIMEOUT

- AMAZON-LAMBDA:TOO\_MANY\_REQUESTS

- AMAZON-LAMBDA:UNAUTHORIZED

- AMAZON-LAMBDA:UNSUPPORTED\_MEDIA\_TYPE

## Get Function

`<amazon-lambda:get20150331-functions-by-function-name>`

Returns information about the function or function version, with a link to download the deployment
package that’s valid for 10 minutes. If you specify a function version, only details that are
specific to that version are returned.

This operation makes an HTTP GET request to the `/2015-03-31/functions/{FunctionName}` endpoint.

### Parameters

<table><colgroup><col> <col> <col> <col> <col></colgroup><thead><tr><th>Name</th><th>Type</th><th>Description</th><th>Default Value</th><th>Required</th></tr></thead><tbody><tr><td><p>Configuration</p></td><td><p>String</p></td><td><p>Name of the configuration to use.</p></td><td></td><td><p>x</p></td></tr><tr><td><p>Function Name</p></td><td><div><div><p>String</p></div></div></td><td><div><div><p>The name of the Lambda function, version, or alias. Name formats:</p></div><div><ul><li><p>Function name: my-function (name-only), my-function:v1 (with alias).</p></li><li><p>Function ARN: arn:aws:lambda:us-west-2:123456789012:function:my-function.</p></li><li><p>Partial ARN: 123456789012:function:my-function.</p></li></ul></div><div><p>You can append a version number or alias to any of the formats. The length constraint applies only to the full ARN. If you specify only the function name, it is limited to 64 characters in length.</p></div></div></td><td></td><td><p>x</p></td></tr><tr><td><p>Qualifier</p></td><td><div><div><p>String</p></div></div></td><td><p>Specify a version or alias to get details about a published version of the function.</p></td><td></td><td></td></tr><tr><td><p>Config Ref</p></td><td><div><div><p>ConfigurationProvider</p></div></div></td><td><p>Name of the configuration to use to execute this component</p></td><td></td><td><p>x</p></td></tr><tr><td><p>Streaming Strategy</p></td><td><div><div><ul><li><p><a href="#RepeatableInMemoryStream">Repeatable In Memory Stream</a></p></li><li><p><a href="#RepeatableFileStoreStream">Repeatable File Store Stream</a></p></li><li><p>non-repeatable-stream</p></li></ul></div></div></td><td><p>Configures how Mule processes streams. The default is to use repeatable streams.</p></td><td></td><td></td></tr><tr><td><p>Custom Query Parameters</p></td><td><div><div><p>Object</p></div></div></td><td><p>Custom query parameters to include in the request. The specified query parameters are merged with the default query parameters that are specified in the configuration.</p></td><td><p>#[null]</p></td><td></td></tr><tr><td><p>Custom Headers</p></td><td><div><div><p>Object</p></div></div></td><td><p>Custom headers to include in the request. The specified custom headers are merged with the default headers that are specified in the configuration.</p></td><td></td><td></td></tr><tr><td><p>Response Timeout</p></td><td><div><div><p>Number</p></div></div></td><td><p>Timeout for requests to the remote service. This value is qualified by the <strong>Response Timeout Unit</strong>.</p></td><td></td><td></td></tr><tr><td><p>Response Timeout Unit</p></td><td><div><div><p>Enumeration, one of:</p></div><div><ul><li><p>NANOSECONDS</p></li><li><p>MICROSECONDS</p></li><li><p>MILLISECONDS</p></li><li><p>SECONDS</p></li><li><p>MINUTES</p></li><li><p>HOURS</p></li><li><p>DAYS</p></li></ul></div></div></td><td><p>Time unit for the <strong>Response Timeout</strong> field.</p></td><td></td><td></td></tr><tr><td><p>Target Variable</p></td><td><div><div><p>String</p></div></div></td><td><p>Name of the variable that stores the operation’s output.</p></td><td></td><td></td></tr><tr><td><p>Target Value</p></td><td><div><div><p>String</p></div></div></td><td><p>Expression that evaluates the operation’s output. The outcome of the expression is stored in the <strong>Target Variable</strong>.</p></td><td><p>#[payload]</p></td><td></td></tr><tr><td><p>Reconnection Strategy</p></td><td><div><div><ul><li><p><a href="#Reconnect">Reconnect</a></p></li><li><p><a href="#ReconnectForever">Reconnect Forever</a></p></li></ul></div></div></td><td><p>A retry strategy in case of connectivity errors.</p></td><td></td><td></td></tr></tbody></table>

### Output

<table><colgroup><col> <col></colgroup><tbody><tr><td><p>Type</p></td><td><p>Any</p></td></tr><tr><td><p>Attributes Type</p></td><td><div><div><p><a href="#HttpResponseAttributes">HTTP Response Attributes</a></p></div></div></td></tr></tbody></table>

### For Configurations

- [Configurations](#configurations)

### Throws

- AMAZON-LAMBDA:BAD\_REQUEST

- AMAZON-LAMBDA:CLIENT\_ERROR

- AMAZON-LAMBDA:CONNECTIVITY

- AMAZON-LAMBDA:INTERNAL\_SERVER\_ERROR

- AMAZON-LAMBDA:NOT\_ACCEPTABLE

- AMAZON-LAMBDA:NOT\_FOUND

- AMAZON-LAMBDA:RETRY\_EXHAUSTED

- AMAZON-LAMBDA:SERVER\_ERROR

- AMAZON-LAMBDA:SERVICE\_UNAVAILABLE

- AMAZON-LAMBDA:TIMEOUT

- AMAZON-LAMBDA:TOO\_MANY\_REQUESTS

- AMAZON-LAMBDA:UNAUTHORIZED

- AMAZON-LAMBDA:UNSUPPORTED\_MEDIA\_TYPE

## Types

### Default Header

<table><colgroup><col> <col> <col> <col> <col></colgroup><thead><tr><th>Field</th><th>Type</th><th>Description</th><th>Default Value</th><th>Required</th></tr></thead><tbody><tr><td><p><strong>Key</strong></p></td><td><div><div><p>String</p></div></div></td><td><div></div></td><td><div></div></td><td><div><div><p>x</p></div></div></td></tr><tr><td><p><strong>Value</strong></p></td><td><div><div><p>String</p></div></div></td><td><div></div></td><td><div></div></td><td><div><div><p>x</p></div></div></td></tr></tbody></table>

### Default Query Param

<table><colgroup><col> <col> <col> <col> <col></colgroup><thead><tr><th>Field</th><th>Type</th><th>Description</th><th>Default Value</th><th>Required</th></tr></thead><tbody><tr><td><p><strong>Key</strong></p></td><td><div><div><p>String</p></div></div></td><td><div></div></td><td><div></div></td><td><div><div><p>x</p></div></div></td></tr><tr><td><p><strong>Value</strong></p></td><td><div><div><p>String</p></div></div></td><td><div></div></td><td><div></div></td><td><div><div><p>x</p></div></div></td></tr></tbody></table>

### Proxy

<table><colgroup><col> <col> <col> <col> <col></colgroup><thead><tr><th>Field</th><th>Type</th><th>Description</th><th>Default Value</th><th>Required</th></tr></thead><tbody><tr><td><p><strong>Host</strong></p></td><td><div><div><p>String</p></div></div></td><td><div></div></td><td><div></div></td><td><div><div><p>x</p></div></div></td></tr><tr><td><p><strong>Port</strong></p></td><td><div><div><p>Number</p></div></div></td><td><div></div></td><td><div></div></td><td><div><div><p>x</p></div></div></td></tr><tr><td><p><strong>Username</strong></p></td><td><div><div><p>String</p></div></div></td><td><div></div></td><td><div></div></td><td><div></div></td></tr><tr><td><p><strong>Password</strong></p></td><td><div><div><p>String</p></div></div></td><td><div></div></td><td><div></div></td><td><div></div></td></tr><tr><td><p><strong>Non Proxy Hosts</strong></p></td><td><div><div><p>String</p></div></div></td><td><div></div></td><td><div></div></td><td><div></div></td></tr></tbody></table>

### TLS

Configures TLS to provide secure communications for your Mule app.

<table><colgroup><col> <col> <col> <col> <col></colgroup><thead><tr><th>Field</th><th>Type</th><th>Description</th><th>Default Value</th><th>Required</th></tr></thead><tbody><tr><td><p><strong>Enabled Protocols</strong></p></td><td><div><div><p>String</p></div></div></td><td><div><div><p>A comma-separated list of protocols enabled for this context.</p></div></div></td><td><div></div></td><td><div></div></td></tr><tr><td><p><strong>Enabled Cipher Suites</strong></p></td><td><div><div><p>String</p></div></div></td><td><div><div><p>A comma-separated list of cipher suites enabled for this context.</p></div></div></td><td><div></div></td><td><div></div></td></tr><tr><td><p><strong>Trust Store</strong></p></td><td><div><div><p><a href="#TrustStore">Truststore</a></p></div></div></td><td><div></div></td><td><div></div></td><td><div></div></td></tr><tr><td><p><strong>Key Store</strong></p></td><td><div><div><p><a href="#KeyStore">Keystore</a></p></div></div></td><td><div></div></td><td><div></div></td><td><div></div></td></tr><tr><td><p><strong>Revocation Check</strong></p></td><td><div><div><ul><li><p><a href="#StandardRevocationCheck">Standard Revocation Check</a></p></li><li><p><a href="#CustomOcspResponder">Custom OCSP Responder</a></p></li><li><p><a href="#CrlFile">CRL File</a></p></li></ul></div></div></td><td><div></div></td><td><div></div></td><td><div></div></td></tr></tbody></table>

### Truststore

<table><colgroup><col> <col> <col> <col> <col></colgroup><thead><tr><th>Field</th><th>Type</th><th>Description</th><th>Default Value</th><th>Required</th></tr></thead><tbody><tr><td><p><strong>Path</strong></p></td><td><div><div><p>String</p></div></div></td><td><div><div><p>Path to the truststore. Mule resolves the path relative to the current classpath and file system, if possible.</p></div></div></td><td><div></div></td><td><div></div></td></tr><tr><td><p><strong>Password</strong></p></td><td><div><div><p>String</p></div></div></td><td><div><div><p>The password used to protect the truststore.</p></div></div></td><td><div></div></td><td><div></div></td></tr><tr><td><p><strong>Type</strong></p></td><td><div><div><p>String</p></div></div></td><td><div><div><p>The type of truststore used.</p></div></div></td><td><div></div></td><td><div></div></td></tr><tr><td><p><strong>Algorithm</strong></p></td><td><div><div><p>String</p></div></div></td><td><div><div><p>The algorithm used by the truststore.</p></div></div></td><td><div></div></td><td><div></div></td></tr><tr><td><p><strong>Insecure</strong></p></td><td><div><div><p>Boolean</p></div></div></td><td><div><div><p>If <code>true</code>, Mule stops performing certificate validations. This can make connections vulnerable to attacks.</p></div></div></td><td><div></div></td><td><div></div></td></tr></tbody></table>

### Keystore

<table><colgroup><col> <col> <col> <col> <col></colgroup><thead><tr><th>Field</th><th>Type</th><th>Description</th><th>Default Value</th><th>Required</th></tr></thead><tbody><tr><td><p><strong>Path</strong></p></td><td><div><div><p>String</p></div></div></td><td><div><div><p>Path to the keystore. Mule resolves the path relative to the current classpath and file system, if possible.</p></div></div></td><td><div></div></td><td><div></div></td></tr><tr><td><p><strong>Type</strong></p></td><td><div><div><p>String</p></div></div></td><td><div><div><p>Type of keystore used.</p></div></div></td><td><div></div></td><td><div></div></td></tr><tr><td><p><strong>Alias</strong></p></td><td><div><div><p>String</p></div></div></td><td><div><div><p>When the keystore contains many private keys, this attribute indicates the alias of the key to use. If not defined, the first key in the file is used by default.</p></div></div></td><td><div></div></td><td><div></div></td></tr><tr><td><p><strong>Key Password</strong></p></td><td><div><div><p>String</p></div></div></td><td><div><div><p>Password used to protect the private key.</p></div></div></td><td><div></div></td><td><div></div></td></tr><tr><td><p><strong>Password</strong></p></td><td><div><div><p>String</p></div></div></td><td><div><div><p>Password used to protect the keystore.</p></div></div></td><td><div></div></td><td><div></div></td></tr><tr><td><p><strong>Algorithm</strong></p></td><td><div><div><p>String</p></div></div></td><td><div><div><p>Algorithm used by the keystore.</p></div></div></td><td><div></div></td><td><div></div></td></tr></tbody></table>

### Standard Revocation Check

<table><colgroup><col> <col> <col> <col> <col></colgroup><thead><tr><th>Field</th><th>Type</th><th>Description</th><th>Default Value</th><th>Required</th></tr></thead><tbody><tr><td><p><strong>Only End Entities</strong></p></td><td><div><div><p>Boolean</p></div></div></td><td><div><div><p>Only verify the last element of the certificate chain.</p></div></div></td><td><div></div></td><td><div></div></td></tr><tr><td><p><strong>Prefer Crls</strong></p></td><td><div><div><p>Boolean</p></div></div></td><td><div><div><p>Try CRL instead of OCSP first.</p></div></div></td><td><div></div></td><td><div></div></td></tr><tr><td><p><strong>No Fallback</strong></p></td><td><div><div><p>Boolean</p></div></div></td><td><div><div><p>Do not use the secondary checking method (the one not selected before).</p></div></div></td><td><div></div></td><td><div></div></td></tr><tr><td><p><strong>Soft Fail</strong></p></td><td><div><div><p>Boolean</p></div></div></td><td><div><div><p>Avoid verification failure when the revocation server can not be reached or is busy.</p></div></div></td><td><div></div></td><td><div></div></td></tr></tbody></table>

### Custom OCSP Responder

<table><colgroup><col> <col> <col> <col> <col></colgroup><thead><tr><th>Field</th><th>Type</th><th>Description</th><th>Default Value</th><th>Required</th></tr></thead><tbody><tr><td><p><strong>Url</strong></p></td><td><div><div><p>String</p></div></div></td><td><div><div><p>The URL of the OCSP responder.</p></div></div></td><td><div></div></td><td><div></div></td></tr><tr><td><p><strong>Cert Alias</strong></p></td><td><div><div><p>String</p></div></div></td><td><div><div><p>Alias of the signing certificate for the OCSP response (must be in the trust store), if present.</p></div></div></td><td><div></div></td><td><div></div></td></tr></tbody></table>

### CRL File

<table><colgroup><col> <col> <col> <col> <col></colgroup><thead><tr><th>Field</th><th>Type</th><th>Description</th><th>Default Value</th><th>Required</th></tr></thead><tbody><tr><td><p><strong>Path</strong></p></td><td><div><div><p>String</p></div></div></td><td><div><div><p>The path to the CRL file.</p></div></div></td><td><div></div></td><td><div></div></td></tr></tbody></table>

### Reconnection

<table><colgroup><col> <col> <col> <col> <col></colgroup><thead><tr><th>Field</th><th>Type</th><th>Description</th><th>Default Value</th><th>Required</th></tr></thead><tbody><tr><td><p><strong>Fails Deployment</strong></p></td><td><div><div><p>Boolean</p></div></div></td><td><div><div><p>When the application is deployed, a connectivity test is performed on all connectors. If set to true, deployment fails if the test doesn’t pass after exhausting the associated reconnection strategy.</p></div></div></td><td><div></div></td><td><div></div></td></tr><tr><td><p><strong>Reconnection Strategy</strong></p></td><td><div><div><ul><li><p><a href="#Reconnect">Reconnect</a></p></li><li><p><a href="#ReconnectForever">Reconnect Forever</a></p></li></ul></div></div></td><td><div><div><p>The reconnection strategy to use.</p></div></div></td><td><div></div></td><td><div></div></td></tr></tbody></table>

### Reconnect

<table><colgroup><col> <col> <col> <col> <col></colgroup><thead><tr><th>Field</th><th>Type</th><th>Description</th><th>Default Value</th><th>Required</th></tr></thead><tbody><tr><td><p><strong>Frequency</strong></p></td><td><div><div><p>Number</p></div></div></td><td><div><div><p>How often in milliseconds to reconnect.</p></div></div></td><td><div></div></td><td><div></div></td></tr><tr><td><p><strong>Blocking</strong></p></td><td><div><div><p>Boolean</p></div></div></td><td><div><div><p>If false, the reconnection strategy will run in a separate, non-blocking thread.</p></div></div></td><td><div></div></td><td><div></div></td></tr><tr><td><p><strong>Count</strong></p></td><td><div><div><p>Number</p></div></div></td><td><div><div><p>How many reconnection attempts to make.</p></div></div></td><td><div></div></td><td><div></div></td></tr></tbody></table>

### Reconnect Forever

<table><colgroup><col> <col> <col> <col> <col></colgroup><thead><tr><th>Field</th><th>Type</th><th>Description</th><th>Default Value</th><th>Required</th></tr></thead><tbody><tr><td><p><strong>Frequency</strong></p></td><td><div><div><p>Number</p></div></div></td><td><div><div><p>How often in milliseconds to reconnect.</p></div></div></td><td><div></div></td><td><div></div></td></tr><tr><td><p><strong>Blocking</strong></p></td><td><div><div><p>Boolean</p></div></div></td><td><div><div><p>If false, the reconnection strategy will run in a separate, non-blocking thread.</p></div></div></td><td><div></div></td><td><div></div></td></tr></tbody></table>

### Expiration Policy

<table><colgroup><col> <col> <col> <col> <col></colgroup><thead><tr><th>Field</th><th>Type</th><th>Description</th><th>Default Value</th><th>Required</th></tr></thead><tbody><tr><td><p><strong>Max Idle Time</strong></p></td><td><div><div><p>Number</p></div></div></td><td><div><div><p>A scalar time value for the maximum amount of time a dynamic configuration instance should be allowed to be idle before it’s considered eligible for expiration.</p></div></div></td><td><div></div></td><td><div></div></td></tr><tr><td><p><strong>Time Unit</strong></p></td><td><div><div><p>Enumeration, one of:</p></div><div><ul><li><p>NANOSECONDS</p></li><li><p>MICROSECONDS</p></li><li><p>MILLISECONDS</p></li><li><p>SECONDS</p></li><li><p>MINUTES</p></li><li><p>HOURS</p></li><li><p>DAYS</p></li></ul></div></div></td><td><div><div><p>Time unit that qualifies the <strong>Max Idle Time</strong> attribute.</p></div></div></td><td><div></div></td><td><div></div></td></tr></tbody></table>

### HTTP Response Attributes

<table><colgroup><col> <col> <col> <col> <col></colgroup><thead><tr><th>Field</th><th>Type</th><th>Description</th><th>Default Value</th><th>Required</th></tr></thead><tbody><tr><td><p><strong>Status Code</strong></p></td><td><div><div><p>Number</p></div></div></td><td><div></div></td><td><div></div></td><td><div><div><p>x</p></div></div></td></tr><tr><td><p><strong>Headers</strong></p></td><td><div><div><p>Object</p></div></div></td><td><div></div></td><td><div></div></td><td><div><div><p>x</p></div></div></td></tr><tr><td><p><strong>Reason Phrase</strong></p></td><td><div><div><p>String</p></div></div></td><td><div></div></td><td><div></div></td><td><div><div><p>x</p></div></div></td></tr></tbody></table>

### Repeatable In Memory Stream

<table><colgroup><col> <col> <col> <col> <col></colgroup><thead><tr><th>Field</th><th>Type</th><th>Description</th><th>Default Value</th><th>Required</th></tr></thead><tbody><tr><td><p><strong>Initial Buffer Size</strong></p></td><td><div><div><p>Number</p></div></div></td><td><div><div><p>Initial amount of memory to allocate to the memory stream. If the stream data exceeds this value, the buffer expands by <strong>Buffer Size Increment</strong>, with an upper limit <strong>Max In Memory Size value</strong>.</p></div></div></td><td><div></div></td><td><div></div></td></tr><tr><td><p><strong>Buffer Size Increment</strong></p></td><td><div><div><p>Number</p></div></div></td><td><div><div><p>Amount by which the buffer size expands if it exceeds its initial size. Setting a value of <code>0</code> or lower specifies that the buffer can’t expand. Mule raises a <code>STREAM_MAXIMUM_SIZE_EXCEEDED</code> error when the buffer gets full.</p></div></div></td><td><div></div></td><td><div></div></td></tr><tr><td><p><strong>Max Buffer Size</strong></p></td><td><div><div><p>Number</p></div></div></td><td><div><div><p>Maximum size of the buffer. A value less than or equal to <code>0</code> means no limit.</p></div></div></td><td><div></div></td><td><div></div></td></tr><tr><td><p><strong>Buffer Unit</strong></p></td><td><div><div><p>Enumeration, one of:</p></div><div><ul><li><p>BYTE</p></li><li><p>KB</p></li><li><p>MB</p></li><li><p>GB</p></li></ul></div></div></td><td><div><div><p>The unit in which all these attributes are expressed</p></div></div></td><td><div></div></td><td><div></div></td></tr></tbody></table>

### Repeatable File Store Stream

<table><colgroup><col> <col> <col> <col> <col></colgroup><thead><tr><th>Field</th><th>Type</th><th>Description</th><th>Default Value</th><th>Required</th></tr></thead><tbody><tr><td><p><strong>In Memory Size</strong></p></td><td><div><div><p>Number</p></div></div></td><td><div><div><p>Defines the maximum memory that the stream should use to keep data in memory. If more than that is consumed content on the disk is buffered.</p></div></div></td><td><div></div></td><td><div></div></td></tr><tr><td><p><strong>Buffer Unit</strong></p></td><td><div><div><p>Enumeration, one of:</p></div><div><ul><li><p>BYTE</p></li><li><p>KB</p></li><li><p>MB</p></li><li><p>GB</p></li></ul></div></div></td><td><div><div><p>The unit in which maxInMemorySize is expressed</p></div></div></td><td><div></div></td><td><div></div></td></tr></tbody></table>

## See Also

- [Amazon Lambda Connector Overview](https://docs.mulesoft.com/amazon-lambda-connector/1.1/)

- [Salesforce Help](https://help.salesforce.com)

<!-- document id=c052e3ce7f2d3ef713ec21c302f837c875287e10c8fcb16ad7835cff6a87ee66 url=/mulesoft/current/en-us/amazon-lambda-connector/latest/index.md -->

---
product: Amazon Lambda Connector
version: 1.2
is-latest-version: true
---

# Amazon Lambda Connector 1.2

> For the full documentation index, see: https://docs.mulesoft.com/llms.txt

Anypoint Connector for Amazon Lambda (Amazon Lambda Connector) enables you to execute AWS Lambda
operations within your Mule flows. You can then use the response of the Lambda operation to process
another Mule flow as needed.

For compatibility information and fixed issues, see the Amazon Lambda Release Notes.

## Before You Begin

To use this connector, you must be familiar with:

- The AWS Lambda API

- Anypoint Connectors

- Mule runtime engine (Mule)

- Elements and global elements in a Mule flow

- Creating a Mule app using Anypoint Studio (Studio)

Before creating an app, you must have:

- AWS Identity and Access Management (IAM) access key credentials

- Access to the AWS Lambda target resource

- Anypoint Studio version 7.3 or later

## Common Use Case for the Connector

When your app manages large amounts of streaming data from various sources, Amazon Lambda Connector
enables you to send the data stream to an AWS Lambda application that is specifically designed to
quickly pull and process the required information. This enables you to manage necessary realtime
tasks without slowing down your main application.

## Authentication Types

AWS Lambda Connector supports AWS Lambda authentication.

## See Also

- [Introduction to Anypoint Connectors](https://docs.mulesoft.com/connectors/introduction/introduction-to-anypoint-connectors)

- [Use Exchange to Discover Connectors, Templates, and Examples](https://docs.mulesoft.com/connectors/introduction/intro-use-exchange)

- [Salesforce Help](https://help.salesforce.com)

<!-- document id=498ecbe0e7fb8d523045a3ca08df43875c41485319025484387d10b9c94793a7 url=/mulesoft/current/en-us/amazon-lambda-connector/latest/amazon-lambda-connector-xml-maven.md -->

---
product: Amazon Lambda Connector
version: 1.2
is-latest-version: true
---

# Amazon Lambda Connector 1.2 - XML and Maven Support

> For the full documentation index, see: https://docs.mulesoft.com/llms.txt

Although you can manually code a Mule app in XML, it is more efficient to use Anypoint Studio:

- If you manually code a Mule runtime engine (Mule) app in XML either from the Anypoint Studio XML
  editor or from a text editor, you can access the connector from your app by adding reference
  statements to both your XML Mule flow and the Apache Maven `pom.xml` file.

- If you add the connector in Studio, Studio automatically populates the XML code with the
  connector’s namespace and schema location and it also adds a dependency to the `pom.xml` file.

## Add a Namespace for the Connector

Paste the following code inside the `mule` tag of the header of your configuration XML:

```xml
http://www.mulesoft.org/schema/mule/amazon-lambda
http://www.mulesoft.org/schema/mule/amazon-lambda/current/mule-amazon-lambda.xsd
```

This example shows how the namespace statements are placed in the XML:

```xml
<mule xmlns:amazon-lambda="http://www.mulesoft.org/schema/mule/amazon-lambda"
	xmlns="http://www.mulesoft.org/schema/mule/core"
	xmlns:doc="http://www.mulesoft.org/schema/mule/documentation"
	xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
	xsi:schemaLocation="http://www.mulesoft.org/schema/mule/core
	http://www.mulesoft.org/schema/mule/core/current/mule.xsd
	http://www.mulesoft.org/schema/mule/amazon-lambda
	http://www.mulesoft.org/schema/mule/amazon-lambda/current/mule-amazon-lambda.xsd">
```

## Add a POM File Dependency

The Apache Maven `pom.xml` file generated by Anypoint Studio contains dependencies for a Mule app.
When you code a Mule app manually, include this XML snippet in your `pom.xml` file to enable access
to this connector:

```xml
<dependency>
  <groupId>com.mulesoft.connectors</groupId>
  <artifactId>mule4-amazon-lambda-connector</artifactId>
  <version>1.1.0</version>
  <classifier>mule-plugin</classifier>
</dependency>
```

Replace the value for `<version>` with the version that corresponds to the connector you are using.

To obtain the most up-to-date `pom.xml` file information:

1.  Go to [Anypoint Exchange](https://www.mulesoft.com/exchange/).

2.  In Exchange, click **Login** and supply your Anypoint Platform username and password.

3.  In Exchange, search for `amazon lambda`.

4.  Select the connector.

5.  Click **Dependency Snippets** near the upper right of the screen.

## See Also

- [Introduction to Anypoint Connectors](https://docs.mulesoft.com/connectors/introduction/introduction-to-anypoint-connectors)

- [Salesforce Help](https://help.salesforce.com)

<!-- document id=21752095de321fb564637ea9b9f0c3637404e11368acd1becb3490d5d59187cd url=/mulesoft/current/en-us/amazon-lambda-connector/latest/amazon-lambda-connector-examples.md -->

---
product: Amazon Lambda Connector
version: 1.2
is-latest-version: true
---

# Amazon Lambda Connector 1.2 Examples

> For the full documentation index, see: https://docs.mulesoft.com/llms.txt

This example shows how to use the Anypoint Connector for Amazon Lambda (Amazon Lambda Connector) to
invoke a synchronous call and get results from AWS Lambda.

## Before You Begin

Verify that Amazon Lambda Connector is added to your Mule project in Anypoint Studio. If it’s not,
follow the instructions in
[Add the Connector to Your Mule Project](https://docs.mulesoft.com/amazon-lambda-connector/latest/amazon-lambda-connector-studio#add-connector-to-project).

## Synchronous Invocation Flow

This example shows a simple AWS Lambda function call that is invoked using an HTTP listener. When
the `http://localhost:8081/invoke` URL is called, the Lambda **Invoke** operation is performed, and
the result is returned directly to you.

### Create the Configuration File

1.  In Studio, go to the **Package Explorer** view and right-click the `/src/main/resources` folder
    in your project.

2.  Select **New > File**.

3.  Name the file `environment.properties`.

4.  Edit the file to define the properties and values you need.

### Configure HTTP Listener

Configure an HTTP Listener source to initiate the Amazon Lambda Connector **Invoke** operation flow
each time it receives a request on the configured host (`localhost`) and port (`8081`):

1.  In **Mule Palette**, select **HTTP > Listener**.

2.  Drag **Listener** to the Studio canvas.

3.  Click **+** next to **Connector configuration** to configure a global element that can be used
    by all instances of the HTTP Listener source in the app.

4.  In the **General** tab, specify connection information for the connector.

5.  Click **Test Connection** to confirm that Mule can connect with the specified server.

6.  Click **OK**.

### Configure the Invoke Operation

1.  In **Mule Palette**, select **Amazon Lambda Connector > Invoke**.

2.  Drag **Invoke** to the Studio canvas to the right of the **Listener** source:

    ![Simple invoke example flow in Studio](/mulesoft/current/en-us/amazon-lambda-connector/latest/_images/amazon-lambda-simple-invoke-example.png)

3.  Configure the **Invoke** operation:

    ![Simple invoke operation General properties configuration](/mulesoft/current/en-us/amazon-lambda-connector/latest/_images/amazon-lambda-simple-invoke-example-properties.png)

    In this example, the function name is supplied in the `environment.properties` file as
    `$config.functionName`.

    The payload from the HTTP Listener is passed directly into the body of the **Invoke** operation,
    which is specified as `REQUEST_RESPONSE`. This tells AWS Lambda that it does not need to store
    any logs for this operation and effectively makes this a synchronous call, which waits until the
    AWS Lambda function is finished processing before it returns its results.

    Alternatively, you can set **Invocation Type** to `EVENT`, which acts like an asynchronous call
    and returns an empty response immediately while AWS Lambda performs its action in the
    background.

### Create an AWS Lambda Function

Depending on your Lambda function, when you run this flow, you might need to send in a request body.
For example, you can create a Python 3.8 Lambda function like this:

```python
def lambda_handler(event, context):
    message = 'Hello {} {}!'.format(event['first_name'], event['last_name'])

	return {'message' : message}
```

Consult the official AWS documentation if you don’t know how to create a new AWS Lambda function.

This function takes the fields `first_name` and `last_name` from the input in JSON format and sends
a greeting using the specified first and last names.

Call the `http://localhost:8081/invoke` endpoint with a JSON body like this:

```json
{
  "first_name": "<first_name>",
  "last_name": "<last_name>"
}
```

The Mule flow responds with a Code 200 message:

{ "message": "Hello <first\_name> <last\_name>!" }

## XML for the Invoke Example

Paste this code into the Studio XML editor to quickly load the flow for this example into your Mule
app:

```xml
<?xml version="1.0" encoding="UTF-8"?>

<mule xmlns:amazon-lambda="http://www.mulesoft.org/schema/mule/amazon-lambda" xmlns:http="http://www.mulesoft.org/schema/mule/http"
	xmlns="http://www.mulesoft.org/schema/mule/core"
	xmlns:doc="http://www.mulesoft.org/schema/mule/documentation" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.mulesoft.org/schema/mule/core http://www.mulesoft.org/schema/mule/core/current/mule.xsd
http://www.mulesoft.org/schema/mule/http http://www.mulesoft.org/schema/mule/http/current/mule-http.xsd
http://www.mulesoft.org/schema/mule/amazon-lambda http://www.mulesoft.org/schema/mule/amazon-lambda/current/mule-amazon-lambda.xsd">
	<flow name="amazon-lambda-invoke-example">
		<http:listener doc:name="Listener" config-ref="HTTP_Listener_config" path="/invoke"/>
		<amazon-lambda:create20150331-functions-invocations-by-function-name doc:name="Invoke" config-ref="Test_Aws_Config" functionName="${config.functionName}" xAmzInvocationType="REQUEST_RESPONSE">
		</amazon-lambda:create20150331-functions-invocations-by-function-name>
	</flow>
</mule>
```

### See Also

- [Introduction to Anypoint Connectors](https://docs.mulesoft.com/connectors/introduction/introduction-to-anypoint-connectors)

- [Anypoint Connector Configuration](https://docs.mulesoft.com/connectors/introduction/intro-connector-configuration-overview).

- [Amazon Lambda Connector Reference](https://docs.mulesoft.com/amazon-lambda-connector/latest/amazon-lambda-connector-reference).

- [Salesforce Help](https://help.salesforce.com)

<!-- document id=79f6d971c5353ee16715ec48d5024a50501d96bad7c9f73a34b2d553d8bd7fdf url=/mulesoft/current/en-us/amazon-lambda-connector/latest/amazon-lambda-connector-reference.md -->

---
product: Amazon Lambda Connector
version: 1.2
is-latest-version: true
---

# Amazon Lambda Connector 1.2 Reference

> For the full documentation index, see: https://docs.mulesoft.com/llms.txt

Anypoint Connector for Amazon Lambda (Amazon Lambda Connector) provides access to standard Amazon
Lambda operations using Anypoint Platform.

## Configurations

<table><colgroup><col> <col> <col> <col> <col></colgroup><thead><tr><th>Name</th><th>Type</th><th>Description</th><th>Default Value</th><th>Required</th></tr></thead><tbody><tr><td><p>Name</p></td><td><p>String</p></td><td><p>The name for this configuration. Connectors reference the configuration with this name.</p></td><td></td><td><p>x</p></td></tr><tr><td><p>Connection</p></td><td><div><div><p><a href="#Config_Connection">Amazon Lambda Connection</a></p></div></div></td><td><p>The connection types to provide to this configuration.</p></td><td></td><td><p>x</p></td></tr><tr><td><p>Response Timeout</p></td><td><div><div><p>Number</p></div></div></td><td><p>Timeout for requests to the remote service. This value is qualified by the <strong>Response Timeout Unit</strong> field.</p></td><td><p>1</p></td><td></td></tr><tr><td><p>Response Timeout Unit</p></td><td><div><div><p>Enumeration, one of:</p></div><div><ul><li><p>NANOSECONDS</p></li><li><p>MICROSECONDS</p></li><li><p>MILLISECONDS</p></li><li><p>SECONDS</p></li><li><p>MINUTES</p></li><li><p>HOURS</p></li><li><p>DAYS</p></li></ul></div></div></td><td><p>Time unit for the <strong>Response Timeout</strong> field.</p></td><td><p>MINUTES</p></td><td></td></tr><tr><td><p>Name</p></td><td><div><div><p>String</p></div></div></td><td><p>Identifier of this element, which is used to reference it in other components.</p></td><td></td><td><p>x</p></td></tr><tr><td><p>Expiration Policy</p></td><td><div><div><p><a href="#ExpirationPolicy">Expiration Policy</a></p></div></div></td><td><p>Minimum amount of time that a dynamic configuration instance can remain idle before Mule considers it eligible for expiration.</p></td><td></td><td></td></tr></tbody></table>

## Connection Types

### Amazon Lambda Connection

<table><colgroup><col> <col> <col> <col> <col></colgroup><thead><tr><th>Name</th><th>Type</th><th>Description</th><th>Default Value</th><th>Required</th></tr></thead><tbody><tr><td><p>Default Headers</p></td><td><div><div><p>Array of <a href="#DefaultHeader">Default Header</a></p></div></div></td><td></td><td></td><td></td></tr><tr><td><p>Query Parameters</p></td><td><div><div><p>Array of <a href="#DefaultQueryParam">Default Query Param</a></p></div></div></td><td></td><td></td><td></td></tr><tr><td><p>Connection Timeout</p></td><td><div><div><p>Number</p></div></div></td><td><p>Timeout for establishing connections to the remote service.</p></td><td><p>30</p></td><td></td></tr><tr><td><p>Connection Timeout Unit</p></td><td><div><div><p>Enumeration, one of:</p></div><div><ul><li><p>NANOSECONDS</p></li><li><p>MICROSECONDS</p></li><li><p>MILLISECONDS</p></li><li><p>SECONDS</p></li><li><p>MINUTES</p></li><li><p>HOURS</p></li><li><p>DAYS</p></li></ul></div></div></td><td><p>Time unit for the <strong>Connection Timeout</strong> field.</p></td><td><p>SECONDS</p></td><td></td></tr><tr><td><p>Use Persistent Connections</p></td><td><div><div><p>Boolean</p></div></div></td><td><p>If false, each connection is closed after the first request is completed.</p></td><td><p>true</p></td><td></td></tr><tr><td><p>Max Connections</p></td><td><div><div><p>Number</p></div></div></td><td><p>Maximum number of outbound connections to keep open at the same time.</p></td><td><p>-1</p></td><td></td></tr><tr><td><p>Connection Idle Timeout</p></td><td><div><div><p>Number</p></div></div></td><td><p>Timeout for how long a connection can remain idle before it is closed.</p></td><td><p>30</p></td><td></td></tr><tr><td><p>Connection Idle Timeout Unit</p></td><td><div><div><p>Enumeration, one of:</p></div><div><ul><li><p>NANOSECONDS</p></li><li><p>MICROSECONDS</p></li><li><p>MILLISECONDS</p></li><li><p>SECONDS</p></li><li><p>MINUTES</p></li><li><p>HOURS</p></li><li><p>DAYS</p></li></ul></div></div></td><td><p>Time unit for the <strong>Connection Idle Timeout</strong> field.</p></td><td><p>SECONDS</p></td><td></td></tr><tr><td><p>Proxy Config</p></td><td><div><div><p><a href="#Proxy">Proxy</a></p></div></div></td><td><p>Reusable configuration element for outbound connections through a proxy.</p></td><td></td><td></td></tr><tr><td><p>Stream Response</p></td><td><div><div><p>Boolean</p></div></div></td><td><p>Whether or not to stream received responses.</p></td><td><p>false</p></td><td></td></tr><tr><td><p>Response Buffer Size</p></td><td><div><div><p>Number</p></div></div></td><td><p>Space in bytes for the buffer where the HTTP response will be stored.</p></td><td><p>-1</p></td><td></td></tr><tr><td><p>Try Default AWSCredentials Provider Chain</p></td><td><div><div><p>Boolean</p></div></div></td><td><p>Set this field to <code>true</code> to obtain credentials from the AWS environment. See <a href="https://docs.aws.amazon.com/sdk-for-java/latest/developer-guide/credentials.html">Using credentials providers in the AWS SDK for Java 2.x</a>.</p></td><td><p>false</p></td><td></td></tr><tr><td><p>Access Key</p></td><td><div><div><p>String</p></div></div></td><td><p>The access key provided by Amazon.</p></td><td></td><td><p>x</p></td></tr><tr><td><p>Secret Key</p></td><td><div><div><p>String</p></div></div></td><td><p>The secret key provided by Amazon.</p></td><td></td><td><p>x</p></td></tr><tr><td><p>Role ARN</p></td><td><div><div><p>String</p></div></div></td><td><p>The ARN of the role to use.</p></td><td></td><td></td></tr><tr><td><p>External ID</p></td><td><div><div><p>String</p></div></div></td><td><p>A unique identifier used when assuming an IAM role in an external account. Provide the value specified by the administrator of the target account for added security.</p></td><td></td><td></td></tr><tr><td><p>Region</p></td><td><div><div><p>String</p></div></div></td><td><p>The region of the Amazon instance.</p></td><td><p>us-east-1</p></td><td></td></tr><tr><td><p>Custom Service Endpoint</p></td><td><div><div><p>String</p></div></div></td><td><p>Sets a custom service endpoint. Useful when a non-standard service endpoint is required, such as a VPC endpoint.</p></td><td></td><td></td></tr><tr><td><p>Custom STS Endpoint</p></td><td><div><div><p>String</p></div></div></td><td><p>Sets a custom STS endpoint. Useful when a non-standard service endpoint is required, such as a VPC endpoint. The custom STS endpoint might not work if <code>DefaultAWSCredentialsProviderChain</code> is used. Instead, use AWS environment variables such as <code>AWS_STS_REGIONAL_ENDPOINTS</code>, <code>AWS_REGION</code>, and <code>AWS_ENDPOINT_URL</code>.</p></td><td></td><td></td></tr><tr><td><p>Protocol</p></td><td><div><div><p>Enumeration, one of:</p></div><div><ul><li><p>HTTP</p></li><li><p>HTTPS</p></li></ul></div></div></td><td><p>Protocol to use for communication. Valid values are HTTP and HTTPS.</p></td><td><p>HTTP</p></td><td></td></tr><tr><td><p>TLS Configuration</p></td><td><div><div><p><a href="#Tls">TLS</a></p></div></div></td><td></td><td></td><td></td></tr><tr><td><p>Reconnection</p></td><td><div><div><p><a href="#Reconnection">Reconnection</a></p></div></div></td><td><p>When the application is deployed, a connectivity test is performed on all connectors. If set to true, deployment fails if the test doesn’t pass after exhausting the associated reconnection strategy.</p></td><td></td><td></td></tr></tbody></table>

## Operations

- [Invoke Async](#Create20141113FunctionsInvokeAsyncByFunctionName)

- [Invoke](#Create20150331FunctionsInvocationsByFunctionName)

- [List Functions](#Get20150331Functions)

- [Get Function](#Get20150331FunctionsByFunctionName)

## Invoke Async

`<amazon-lambda:create20141113-functions-invoke-async-by-function-name>`

For asynchronous function invocation, use Invoke. Invokes a function asynchronously. This operation
makes an HTTP POST request to the `/2014-11-13/functions/{FunctionName}/invoke-async/` endpoint.

### Parameters

<table><colgroup><col> <col> <col> <col> <col></colgroup><thead><tr><th>Name</th><th>Type</th><th>Description</th><th>Default Value</th><th>Required</th></tr></thead><tbody><tr><td><p>Configuration</p></td><td><p>String</p></td><td><p>The name of the configuration to use.</p></td><td></td><td><p>x</p></td></tr><tr><td><p>Function Name</p></td><td><div><div><p>String</p></div></div></td><td><div><div><p>Name of the Lambda function. Name formats:</p></div><div><ul><li><p>Function name: my-function.</p></li><li><p>Function ARN: arn:aws:lambda:us-west-2:123456789012:function:my-function.</p></li><li><p>Partial ARN: 123456789012:function:my-function.</p></li></ul></div><div><p>The length constraint applies only to the full ARN. If you specify only the function name, it is limited to 64 characters in length.</p></div></div></td><td></td><td><p>x</p></td></tr><tr><td><p>Body</p></td><td><div><div><p>Any</p></div></div></td><td><p>the content to use</p></td><td><p>#[payload]</p></td><td></td></tr><tr><td><p>Config Ref</p></td><td><div><div><p>ConfigurationProvider</p></div></div></td><td><p>The name of the configuration to use to execute this component.</p></td><td></td><td><p>x</p></td></tr><tr><td><p>Streaming Strategy</p></td><td><div><div><ul><li><p><a href="#RepeatableInMemoryStream">Repeatable In Memory Stream</a></p></li><li><p><a href="#RepeatableFileStoreStream">Repeatable File Store Stream</a></p></li><li><p>non-repeatable-stream</p></li></ul></div></div></td><td><p>Configures how Mule processes streams. The default is to use repeatable streams.</p></td><td></td><td></td></tr><tr><td><p>Custom Query Parameters</p></td><td><div><div><p>Object</p></div></div></td><td><p>Custom query parameters to include in the request. The specified query parameters are merged with the default query parameters that are specified in the configuration.</p></td><td></td><td></td></tr><tr><td><p>Custom Headers</p></td><td><div><div><p>Object</p></div></div></td><td><p>Custom headers to include in the request. The specified custom headers are merged with the default headers that are specified in the configuration.</p></td><td></td><td></td></tr><tr><td><p>Response Timeout</p></td><td><div><div><p>Number</p></div></div></td><td><p>Timeout for requests to the remote service. This value is qualified by the <strong>Response Timeout Unit</strong>.</p></td><td></td><td></td></tr><tr><td><p>Response Timeout Unit</p></td><td><div><div><p>Enumeration, one of:</p></div><div><ul><li><p>NANOSECONDS</p></li><li><p>MICROSECONDS</p></li><li><p>MILLISECONDS</p></li><li><p>SECONDS</p></li><li><p>MINUTES</p></li><li><p>HOURS</p></li><li><p>DAYS</p></li></ul></div></div></td><td><p>Time unit for the <strong>Response Timeout</strong> field.</p></td><td></td><td></td></tr><tr><td><p>Target Variable</p></td><td><div><div><p>String</p></div></div></td><td><p>Name of the variable that stores the operation’s output.</p></td><td></td><td></td></tr><tr><td><p>Target Value</p></td><td><div><div><p>String</p></div></div></td><td><p>Expression that evaluates the operation’s output. The outcome of the expression is stored in the <strong>Target Variable</strong>.</p></td><td><p>#[payload]</p></td><td></td></tr><tr><td><p>Reconnection Strategy</p></td><td><div><div><ul><li><p><a href="#Reconnect">Reconnect</a></p></li><li><p><a href="#ReconnectForever">Reconnect Forever</a></p></li></ul></div></div></td><td><p>A retry strategy in case of connectivity errors.</p></td><td></td><td></td></tr></tbody></table>

### Output

<table><colgroup><col> <col></colgroup><tbody><tr><td><p>Type</p></td><td><p>Any</p></td></tr><tr><td><p>Attributes Type</p></td><td><div><div><p><a href="#HttpResponseAttributes">HTTP Response Attributes</a></p></div></div></td></tr></tbody></table>

### For Configurations

- [Configurations](#configurations)

### Throws

- AMAZON-LAMBDA:BAD\_REQUEST

- AMAZON-LAMBDA:CLIENT\_ERROR

- AMAZON-LAMBDA:CONNECTIVITY

- AMAZON-LAMBDA:INTERNAL\_SERVER\_ERROR

- AMAZON-LAMBDA:NOT\_ACCEPTABLE

- AMAZON-LAMBDA:NOT\_FOUND

- AMAZON-LAMBDA:RETRY\_EXHAUSTED

- AMAZON-LAMBDA:SERVER\_ERROR

- AMAZON-LAMBDA:SERVICE\_UNAVAILABLE

- AMAZON-LAMBDA:TIMEOUT

- AMAZON-LAMBDA:TOO\_MANY\_REQUESTS

- AMAZON-LAMBDA:UNAUTHORIZED

- AMAZON-LAMBDA:UNSUPPORTED\_MEDIA\_TYPE

## Invoke

`<amazon-lambda:create20150331-functions-invocations-by-function-name>`

Invokes a Lambda function. You can invoke a function synchronously (and wait for the response), or
asynchronously.

To invoke a function asynchronously, set `InvocationType` to `Event`.

For synchronous invocation, details about the function response, including errors, are included in
the response body and headers. For either invocation type, you can find more information in the
execution log and trace.

When an error occurs, your function may be invoked multiple times. Retry behavior varies by error
type, client, event source, and invocation type. For example, if you invoke a function
asynchronously and it returns an error, Lambda executes the function up to two more times. For more
information, see Retry Behavior.

For asynchronous invocation, Lambda adds events to a queue before sending them to your function. If
your function does not have enough capacity to keep up with the queue, events may be lost.
Occasionally, your function might receive the same event multiple times, even if no error occurs.

To retain events that were not processed, configure your function with a dead-letter queue. The
status code in the API response doesn’t reflect function errors. Error codes are reserved for errors
that prevent your function from executing, such as permissions errors, limit errors, or issues with
your function’s code and configuration. For example, Lambda returns `TooManyRequestsException` if
executing the function causes you to exceed a concurrency limit at either the account level
(`ConcurrentInvocationLimitExceeded`) or function level
(`ReservedFunctionConcurrentInvocationLimitExceeded`).

For functions with a long timeout, your client might be disconnected during synchronous invocation
while it waits for a response. Configure your HTTP client, SDK, firewall, proxy, or operating system
to allow for long connections with timeout or keep-alive settings.

This operation requires permission for the lambda:InvokeFunction action.

This operation makes an HTTP POST request to the `/2015-03-31/functions/{FunctionName}/invocations`
endpoint.

### Parameters

<table><colgroup><col> <col> <col> <col> <col></colgroup><thead><tr><th>Name</th><th>Type</th><th>Description</th><th>Default Value</th><th>Required</th></tr></thead><tbody><tr><td><p>Configuration</p></td><td><p>String</p></td><td><p>Name of the configuration to use.</p></td><td></td><td><p>x</p></td></tr><tr><td><p>Function Name</p></td><td><div><div><p>String</p></div></div></td><td><div><div><p>Name of the Lambda function, version, or alias. Name formats:</p></div><div><ul><li><p>Function name: my-function (name-only), my-function:v1 (with alias).</p></li><li><p>Function ARN: arn:aws:lambda:us-west-2:123456789012:function:my-function.</p></li><li><p>Partial ARN: 123456789012:function:my-function.</p></li></ul></div><div><p>You can append a version number or alias to any of the formats. The length constraint applies only to the full ARN. If you specify only the function name, it is limited to 64 characters in length.</p></div></div></td><td></td><td><p>x</p></td></tr><tr><td><p>Qualifier</p></td><td><div><div><p>String</p></div></div></td><td><p>Specify a version or alias to invoke a published version of the function.</p></td><td></td><td></td></tr><tr><td><p>X Amz Invocation Type</p></td><td><div><div><p>Enumeration, one of:</p></div><div><ul><li><p>EVENT</p></li><li><p>REQUEST_RESPONSE</p></li><li><p>DRY_RUN</p></li></ul></div></div></td><td><div><div><p>Choose from the following options:</p></div><div><ul><li><p>RequestResponse (default): Invoke the function synchronously. Keep the connection open until the function returns a response or times out. The API response includes the function response and additional data.</p></li><li><p>Event: Invoke the function asynchronously. Send events that fail multiple times to the function’s dead-letter queue (if it’s configured). The API response only includes a status code.</p></li><li><p>DryRun: Validate parameter values and verify that the user or role has permission to invoke the function.</p></li></ul></div></div></td><td></td><td></td></tr><tr><td><p>X Amz Log Type</p></td><td><div><div><p>Enumeration, one of:</p></div><div><ul><li><p>NONE</p></li><li><p>TAIL</p></li></ul></div></div></td><td><p>Set to <code>TAIL</code> to include the execution log in the response.</p></td><td></td><td></td></tr><tr><td><p>X Amz Client Context</p></td><td><div><div><p>String</p></div></div></td><td><p>Up to 3583 bytes of Base64-encoded data about the invoking client to pass to the function in the context object.</p></td><td></td><td></td></tr><tr><td><p>Body</p></td><td><div><div><p>Any</p></div></div></td><td><p>Content to use.</p></td><td><p>#[payload]</p></td><td></td></tr><tr><td><p>Config Ref</p></td><td><div><div><p>ConfigurationProvider</p></div></div></td><td><p>Name of the configuration to use to execute this component.</p></td><td></td><td><p>x</p></td></tr><tr><td><p>Streaming Strategy</p></td><td><div><div><ul><li><p><a href="#RepeatableInMemoryStream">Repeatable In Memory Stream</a></p></li><li><p><a href="#RepeatableFileStoreStream">Repeatable File Store Stream</a></p></li><li><p>non-repeatable-stream</p></li></ul></div></div></td><td><p>Configures how Mule processes streams. The default is to use repeatable streams.</p></td><td></td><td></td></tr><tr><td><p>Custom Query Parameters</p></td><td><div><div><p>Object</p></div></div></td><td><p>Custom query parameters to include in the request. The specified query parameters are merged with the default query parameters that are specified in the configuration.</p></td><td></td><td></td></tr><tr><td><p>Custom Headers</p></td><td><div><div><p>Object</p></div></div></td><td><p>Custom headers to include in the request. The specified custom headers are merged with the default headers that are specified in the configuration.</p></td><td></td><td></td></tr><tr><td><p>Response Timeout</p></td><td><div><div><p>Number</p></div></div></td><td><p>Timeout for requests to the remote service. This value is qualified by the <strong>Response Timeout Unit</strong>.</p></td><td></td><td></td></tr><tr><td><p>Response Timeout Unit</p></td><td><div><div><p>Enumeration, one of:</p></div><div><ul><li><p>NANOSECONDS</p></li><li><p>MICROSECONDS</p></li><li><p>MILLISECONDS</p></li><li><p>SECONDS</p></li><li><p>MINUTES</p></li><li><p>HOURS</p></li><li><p>DAYS</p></li></ul></div></div></td><td><p>Time unit for the <strong>Response Timeout</strong> field.</p></td><td></td><td></td></tr><tr><td><p>Target Variable</p></td><td><div><div><p>String</p></div></div></td><td><p>Name of the variable that stores the operation’s output.</p></td><td></td><td></td></tr><tr><td><p>Target Value</p></td><td><div><div><p>String</p></div></div></td><td><p>Expression that evaluates the operation’s output. The outcome of the expression is stored in the <strong>Target Variable</strong>.</p></td><td><p>#[payload]</p></td><td></td></tr><tr><td><p>Reconnection Strategy</p></td><td><div><div><ul><li><p><a href="#Reconnect">Reconnect</a></p></li><li><p><a href="#ReconnectForever">Reconnect Forever</a></p></li></ul></div></div></td><td><p>A retry strategy in case of connectivity errors.</p></td><td></td><td></td></tr></tbody></table>

### Output

<table><colgroup><col> <col></colgroup><tbody><tr><td><p>Type</p></td><td><p>Any</p></td></tr><tr><td><p>Attributes Type</p></td><td><div><div><p><a href="#HttpResponseAttributes">HTTP Response Attributes</a></p></div></div></td></tr></tbody></table>

### For Configurations

- [Configurations](#configurations)

### Throws

- AMAZON-LAMBDA:BAD\_REQUEST

- AMAZON-LAMBDA:CLIENT\_ERROR

- AMAZON-LAMBDA:CONNECTIVITY

- AMAZON-LAMBDA:INTERNAL\_SERVER\_ERROR

- AMAZON-LAMBDA:NOT\_ACCEPTABLE

- AMAZON-LAMBDA:NOT\_FOUND

- AMAZON-LAMBDA:RETRY\_EXHAUSTED

- AMAZON-LAMBDA:SERVER\_ERROR

- AMAZON-LAMBDA:SERVICE\_UNAVAILABLE

- AMAZON-LAMBDA:TIMEOUT

- AMAZON-LAMBDA:TOO\_MANY\_REQUESTS

- AMAZON-LAMBDA:UNAUTHORIZED

- AMAZON-LAMBDA:UNSUPPORTED\_MEDIA\_TYPE

## List Functions

`<amazon-lambda:get20150331-functions>`

Returns a list of Lambda functions, with the version-specific configuration of each function. Lambda
returns up to 50 functions per call. Set `FunctionVersion` to `ALL` to include all published
versions of each function in addition to the unpublished version. The ListFunctions action returns a
subset of the FunctionConfiguration fields.

To get the additional fields (State, StateReasonCode, StateReason, LastUpdateStatus,
LastUpdateStatusReason, LastUpdateStatusReasonCode) for a function or version, use GetFunction.

This operation makes an HTTP GET request to the `/2015-03-31/functions` endpoint.

### Parameters

<table><colgroup><col> <col> <col> <col> <col></colgroup><thead><tr><th>Name</th><th>Type</th><th>Description</th><th>Default Value</th><th>Required</th></tr></thead><tbody><tr><td><p>Configuration</p></td><td><p>String</p></td><td><p>Name of the configuration to use.</p></td><td></td><td><p>x</p></td></tr><tr><td><p>Master Region</p></td><td><div><div><p>String</p></div></div></td><td><p>For Lambda@Edge functions, the AWS Region of the master function. For example, us-east-1 filters the list of functions to include only Lambda@Edge functions replicated from a master function in US East (N. Virginia). If specified, you must set FunctionVersion to ALL.</p></td><td></td><td></td></tr><tr><td><p>Function Version</p></td><td><div><div><p>Enumeration, one of:</p></div><div><ul><li><p>ALL</p></li></ul></div></div></td><td><p>Set to ALL to include entries for all published versions of each function.</p></td><td></td><td></td></tr><tr><td><p>Marker</p></td><td><div><div><p>String</p></div></div></td><td><p>Specify the pagination token that’s returned by a previous request to retrieve the next page of results.</p></td><td></td><td></td></tr><tr><td><p>Max Items</p></td><td><div><div><p>Number</p></div></div></td><td><p>The maximum number of functions to return in the response. Note that ListFunctions returns a maximum of 50 items in each response, even if you set the number higher.</p></td><td></td><td></td></tr><tr><td><p>Config Ref</p></td><td><div><div><p>ConfigurationProvider</p></div></div></td><td><p>Name of the configuration to use to execute this component.</p></td><td></td><td><p>x</p></td></tr><tr><td><p>Streaming Strategy</p></td><td><div><div><ul><li><p><a href="#RepeatableInMemoryStream">Repeatable In Memory Stream</a></p></li><li><p><a href="#RepeatableFileStoreStream">Repeatable File Store Stream</a></p></li><li><p>non-repeatable-stream</p></li></ul></div></div></td><td><p>Configures how Mule processes streams. The default is to use repeatable streams.</p></td><td></td><td></td></tr><tr><td><p>Custom Query Parameters</p></td><td><div><div><p>Object</p></div></div></td><td><p>Custom query parameters to include in the request. The specified query parameters are merged with the default query parameters that are specified in the configuration.</p></td><td><p>#[null]</p></td><td></td></tr><tr><td><p>Custom Headers</p></td><td><div><div><p>Object</p></div></div></td><td><p>Custom headers to include in the request. The specified custom headers are merged with the default headers that are specified in the configuration.</p></td><td></td><td></td></tr><tr><td><p>Response Timeout</p></td><td><div><div><p>Number</p></div></div></td><td><p>Timeout for requests to the remote service. This value is qualified by the <strong>Response Timeout Unit</strong>.</p></td><td></td><td></td></tr><tr><td><p>Response Timeout Unit</p></td><td><div><div><p>Enumeration, one of:</p></div><div><ul><li><p>NANOSECONDS</p></li><li><p>MICROSECONDS</p></li><li><p>MILLISECONDS</p></li><li><p>SECONDS</p></li><li><p>MINUTES</p></li><li><p>HOURS</p></li><li><p>DAYS</p></li></ul></div></div></td><td><p>Time unit for the <strong>Response Timeout</strong> field.</p></td><td></td><td></td></tr><tr><td><p>Target Variable</p></td><td><div><div><p>String</p></div></div></td><td><p>Name of the variable that stores the operation’s output.</p></td><td></td><td></td></tr><tr><td><p>Target Value</p></td><td><div><div><p>String</p></div></div></td><td><p>Expression that evaluates the operation’s output. The outcome of the expression is stored in the <strong>Target Variable</strong>.</p></td><td><p>#[payload]</p></td><td></td></tr><tr><td><p>Reconnection Strategy</p></td><td><div><div><ul><li><p><a href="#Reconnect">Reconnect</a></p></li><li><p><a href="#ReconnectForever">Reconnect Forever</a></p></li></ul></div></div></td><td><p>A retry strategy in case of connectivity errors.</p></td><td></td><td></td></tr></tbody></table>

### Output

<table><colgroup><col> <col></colgroup><tbody><tr><td><p>Type</p></td><td><p>Any</p></td></tr><tr><td><p>Attributes Type</p></td><td><div><div><p><a href="#HttpResponseAttributes">HTTP Response Attributes</a></p></div></div></td></tr></tbody></table>

### For Configurations

- [Configurations](#configurations)

### Throws

- AMAZON-LAMBDA:BAD\_REQUEST

- AMAZON-LAMBDA:CLIENT\_ERROR

- AMAZON-LAMBDA:CONNECTIVITY

- AMAZON-LAMBDA:INTERNAL\_SERVER\_ERROR

- AMAZON-LAMBDA:NOT\_ACCEPTABLE

- AMAZON-LAMBDA:NOT\_FOUND

- AMAZON-LAMBDA:RETRY\_EXHAUSTED

- AMAZON-LAMBDA:SERVER\_ERROR

- AMAZON-LAMBDA:SERVICE\_UNAVAILABLE

- AMAZON-LAMBDA:TIMEOUT

- AMAZON-LAMBDA:TOO\_MANY\_REQUESTS

- AMAZON-LAMBDA:UNAUTHORIZED

- AMAZON-LAMBDA:UNSUPPORTED\_MEDIA\_TYPE

## Get Function

`<amazon-lambda:get20150331-functions-by-function-name>`

Returns information about the function or function version, with a link to download the deployment
package that’s valid for 10 minutes. If you specify a function version, only details that are
specific to that version are returned.

This operation makes an HTTP GET request to the `/2015-03-31/functions/{FunctionName}` endpoint.

### Parameters

<table><colgroup><col> <col> <col> <col> <col></colgroup><thead><tr><th>Name</th><th>Type</th><th>Description</th><th>Default Value</th><th>Required</th></tr></thead><tbody><tr><td><p>Configuration</p></td><td><p>String</p></td><td><p>Name of the configuration to use.</p></td><td></td><td><p>x</p></td></tr><tr><td><p>Function Name</p></td><td><div><div><p>String</p></div></div></td><td><div><div><p>The name of the Lambda function, version, or alias. Name formats:</p></div><div><ul><li><p>Function name: my-function (name-only), my-function:v1 (with alias).</p></li><li><p>Function ARN: arn:aws:lambda:us-west-2:123456789012:function:my-function.</p></li><li><p>Partial ARN: 123456789012:function:my-function.</p></li></ul></div><div><p>You can append a version number or alias to any of the formats. The length constraint applies only to the full ARN. If you specify only the function name, it is limited to 64 characters in length.</p></div></div></td><td></td><td><p>x</p></td></tr><tr><td><p>Qualifier</p></td><td><div><div><p>String</p></div></div></td><td><p>Specify a version or alias to get details about a published version of the function.</p></td><td></td><td></td></tr><tr><td><p>Config Ref</p></td><td><div><div><p>ConfigurationProvider</p></div></div></td><td><p>Name of the configuration to use to execute this component</p></td><td></td><td><p>x</p></td></tr><tr><td><p>Streaming Strategy</p></td><td><div><div><ul><li><p><a href="#RepeatableInMemoryStream">Repeatable In Memory Stream</a></p></li><li><p><a href="#RepeatableFileStoreStream">Repeatable File Store Stream</a></p></li><li><p>non-repeatable-stream</p></li></ul></div></div></td><td><p>Configures how Mule processes streams. The default is to use repeatable streams.</p></td><td></td><td></td></tr><tr><td><p>Custom Query Parameters</p></td><td><div><div><p>Object</p></div></div></td><td><p>Custom query parameters to include in the request. The specified query parameters are merged with the default query parameters that are specified in the configuration.</p></td><td><p>#[null]</p></td><td></td></tr><tr><td><p>Custom Headers</p></td><td><div><div><p>Object</p></div></div></td><td><p>Custom headers to include in the request. The specified custom headers are merged with the default headers that are specified in the configuration.</p></td><td></td><td></td></tr><tr><td><p>Response Timeout</p></td><td><div><div><p>Number</p></div></div></td><td><p>Timeout for requests to the remote service. This value is qualified by the <strong>Response Timeout Unit</strong>.</p></td><td></td><td></td></tr><tr><td><p>Response Timeout Unit</p></td><td><div><div><p>Enumeration, one of:</p></div><div><ul><li><p>NANOSECONDS</p></li><li><p>MICROSECONDS</p></li><li><p>MILLISECONDS</p></li><li><p>SECONDS</p></li><li><p>MINUTES</p></li><li><p>HOURS</p></li><li><p>DAYS</p></li></ul></div></div></td><td><p>Time unit for the <strong>Response Timeout</strong> field.</p></td><td></td><td></td></tr><tr><td><p>Target Variable</p></td><td><div><div><p>String</p></div></div></td><td><p>Name of the variable that stores the operation’s output.</p></td><td></td><td></td></tr><tr><td><p>Target Value</p></td><td><div><div><p>String</p></div></div></td><td><p>Expression that evaluates the operation’s output. The outcome of the expression is stored in the <strong>Target Variable</strong>.</p></td><td><p>#[payload]</p></td><td></td></tr><tr><td><p>Reconnection Strategy</p></td><td><div><div><ul><li><p><a href="#Reconnect">Reconnect</a></p></li><li><p><a href="#ReconnectForever">Reconnect Forever</a></p></li></ul></div></div></td><td><p>A retry strategy in case of connectivity errors.</p></td><td></td><td></td></tr></tbody></table>

### Output

<table><colgroup><col> <col></colgroup><tbody><tr><td><p>Type</p></td><td><p>Any</p></td></tr><tr><td><p>Attributes Type</p></td><td><div><div><p><a href="#HttpResponseAttributes">HTTP Response Attributes</a></p></div></div></td></tr></tbody></table>

### For Configurations

- [Configurations](#configurations)

### Throws

- AMAZON-LAMBDA:BAD\_REQUEST

- AMAZON-LAMBDA:CLIENT\_ERROR

- AMAZON-LAMBDA:CONNECTIVITY

- AMAZON-LAMBDA:INTERNAL\_SERVER\_ERROR

- AMAZON-LAMBDA:NOT\_ACCEPTABLE

- AMAZON-LAMBDA:NOT\_FOUND

- AMAZON-LAMBDA:RETRY\_EXHAUSTED

- AMAZON-LAMBDA:SERVER\_ERROR

- AMAZON-LAMBDA:SERVICE\_UNAVAILABLE

- AMAZON-LAMBDA:TIMEOUT

- AMAZON-LAMBDA:TOO\_MANY\_REQUESTS

- AMAZON-LAMBDA:UNAUTHORIZED

- AMAZON-LAMBDA:UNSUPPORTED\_MEDIA\_TYPE

## Types

### Default Header

<table><colgroup><col> <col> <col> <col> <col></colgroup><thead><tr><th>Field</th><th>Type</th><th>Description</th><th>Default Value</th><th>Required</th></tr></thead><tbody><tr><td><p><strong>Key</strong></p></td><td><div><div><p>String</p></div></div></td><td><div></div></td><td><div></div></td><td><div><div><p>x</p></div></div></td></tr><tr><td><p><strong>Value</strong></p></td><td><div><div><p>String</p></div></div></td><td><div></div></td><td><div></div></td><td><div><div><p>x</p></div></div></td></tr></tbody></table>

### Default Query Param

<table><colgroup><col> <col> <col> <col> <col></colgroup><thead><tr><th>Field</th><th>Type</th><th>Description</th><th>Default Value</th><th>Required</th></tr></thead><tbody><tr><td><p><strong>Key</strong></p></td><td><div><div><p>String</p></div></div></td><td><div></div></td><td><div></div></td><td><div><div><p>x</p></div></div></td></tr><tr><td><p><strong>Value</strong></p></td><td><div><div><p>String</p></div></div></td><td><div></div></td><td><div></div></td><td><div><div><p>x</p></div></div></td></tr></tbody></table>

### Proxy

<table><colgroup><col> <col> <col> <col> <col></colgroup><thead><tr><th>Field</th><th>Type</th><th>Description</th><th>Default Value</th><th>Required</th></tr></thead><tbody><tr><td><p><strong>Host</strong></p></td><td><div><div><p>String</p></div></div></td><td><div></div></td><td><div></div></td><td><div><div><p>x</p></div></div></td></tr><tr><td><p><strong>Port</strong></p></td><td><div><div><p>Number</p></div></div></td><td><div></div></td><td><div></div></td><td><div><div><p>x</p></div></div></td></tr><tr><td><p><strong>Username</strong></p></td><td><div><div><p>String</p></div></div></td><td><div></div></td><td><div></div></td><td><div></div></td></tr><tr><td><p><strong>Password</strong></p></td><td><div><div><p>String</p></div></div></td><td><div></div></td><td><div></div></td><td><div></div></td></tr><tr><td><p><strong>Non Proxy Hosts</strong></p></td><td><div><div><p>String</p></div></div></td><td><div></div></td><td><div></div></td><td><div></div></td></tr></tbody></table>

### TLS

Configures TLS to provide secure communications for your Mule app.

<table><colgroup><col> <col> <col> <col> <col></colgroup><thead><tr><th>Field</th><th>Type</th><th>Description</th><th>Default Value</th><th>Required</th></tr></thead><tbody><tr><td><p><strong>Enabled Protocols</strong></p></td><td><div><div><p>String</p></div></div></td><td><div><div><p>A comma-separated list of protocols enabled for this context.</p></div></div></td><td><div></div></td><td><div></div></td></tr><tr><td><p><strong>Enabled Cipher Suites</strong></p></td><td><div><div><p>String</p></div></div></td><td><div><div><p>A comma-separated list of cipher suites enabled for this context.</p></div></div></td><td><div></div></td><td><div></div></td></tr><tr><td><p><strong>Trust Store</strong></p></td><td><div><div><p><a href="#TrustStore">Truststore</a></p></div></div></td><td><div></div></td><td><div></div></td><td><div></div></td></tr><tr><td><p><strong>Key Store</strong></p></td><td><div><div><p><a href="#KeyStore">Keystore</a></p></div></div></td><td><div></div></td><td><div></div></td><td><div></div></td></tr><tr><td><p><strong>Revocation Check</strong></p></td><td><div><div><ul><li><p><a href="#StandardRevocationCheck">Standard Revocation Check</a></p></li><li><p><a href="#CustomOcspResponder">Custom OCSP Responder</a></p></li><li><p><a href="#CrlFile">CRL File</a></p></li></ul></div></div></td><td><div></div></td><td><div></div></td><td><div></div></td></tr></tbody></table>

### Truststore

<table><colgroup><col> <col> <col> <col> <col></colgroup><thead><tr><th>Field</th><th>Type</th><th>Description</th><th>Default Value</th><th>Required</th></tr></thead><tbody><tr><td><p><strong>Path</strong></p></td><td><div><div><p>String</p></div></div></td><td><div><div><p>Path to the truststore. Mule resolves the path relative to the current classpath and file system, if possible.</p></div></div></td><td><div></div></td><td><div></div></td></tr><tr><td><p><strong>Password</strong></p></td><td><div><div><p>String</p></div></div></td><td><div><div><p>The password used to protect the truststore.</p></div></div></td><td><div></div></td><td><div></div></td></tr><tr><td><p><strong>Type</strong></p></td><td><div><div><p>String</p></div></div></td><td><div><div><p>The type of truststore used.</p></div></div></td><td><div></div></td><td><div></div></td></tr><tr><td><p><strong>Algorithm</strong></p></td><td><div><div><p>String</p></div></div></td><td><div><div><p>The algorithm used by the truststore.</p></div></div></td><td><div></div></td><td><div></div></td></tr><tr><td><p><strong>Insecure</strong></p></td><td><div><div><p>Boolean</p></div></div></td><td><div><div><p>If <code>true</code>, Mule stops performing certificate validations. This can make connections vulnerable to attacks.</p></div></div></td><td><div></div></td><td><div></div></td></tr></tbody></table>

### Keystore

<table><colgroup><col> <col> <col> <col> <col></colgroup><thead><tr><th>Field</th><th>Type</th><th>Description</th><th>Default Value</th><th>Required</th></tr></thead><tbody><tr><td><p><strong>Path</strong></p></td><td><div><div><p>String</p></div></div></td><td><div><div><p>Path to the keystore. Mule resolves the path relative to the current classpath and file system, if possible.</p></div></div></td><td><div></div></td><td><div></div></td></tr><tr><td><p><strong>Type</strong></p></td><td><div><div><p>String</p></div></div></td><td><div><div><p>Type of keystore used.</p></div></div></td><td><div></div></td><td><div></div></td></tr><tr><td><p><strong>Alias</strong></p></td><td><div><div><p>String</p></div></div></td><td><div><div><p>When the keystore contains many private keys, this attribute indicates the alias of the key to use. If not defined, the first key in the file is used by default.</p></div></div></td><td><div></div></td><td><div></div></td></tr><tr><td><p><strong>Key Password</strong></p></td><td><div><div><p>String</p></div></div></td><td><div><div><p>Password used to protect the private key.</p></div></div></td><td><div></div></td><td><div></div></td></tr><tr><td><p><strong>Password</strong></p></td><td><div><div><p>String</p></div></div></td><td><div><div><p>Password used to protect the keystore.</p></div></div></td><td><div></div></td><td><div></div></td></tr><tr><td><p><strong>Algorithm</strong></p></td><td><div><div><p>String</p></div></div></td><td><div><div><p>Algorithm used by the keystore.</p></div></div></td><td><div></div></td><td><div></div></td></tr></tbody></table>

### Standard Revocation Check

<table><colgroup><col> <col> <col> <col> <col></colgroup><thead><tr><th>Field</th><th>Type</th><th>Description</th><th>Default Value</th><th>Required</th></tr></thead><tbody><tr><td><p><strong>Only End Entities</strong></p></td><td><div><div><p>Boolean</p></div></div></td><td><div><div><p>Only verify the last element of the certificate chain.</p></div></div></td><td><div></div></td><td><div></div></td></tr><tr><td><p><strong>Prefer Crls</strong></p></td><td><div><div><p>Boolean</p></div></div></td><td><div><div><p>Try CRL instead of OCSP first.</p></div></div></td><td><div></div></td><td><div></div></td></tr><tr><td><p><strong>No Fallback</strong></p></td><td><div><div><p>Boolean</p></div></div></td><td><div><div><p>Do not use the secondary checking method (the one not selected before).</p></div></div></td><td><div></div></td><td><div></div></td></tr><tr><td><p><strong>Soft Fail</strong></p></td><td><div><div><p>Boolean</p></div></div></td><td><div><div><p>Avoid verification failure when the revocation server can not be reached or is busy.</p></div></div></td><td><div></div></td><td><div></div></td></tr></tbody></table>

### Custom OCSP Responder

<table><colgroup><col> <col> <col> <col> <col></colgroup><thead><tr><th>Field</th><th>Type</th><th>Description</th><th>Default Value</th><th>Required</th></tr></thead><tbody><tr><td><p><strong>Url</strong></p></td><td><div><div><p>String</p></div></div></td><td><div><div><p>The URL of the OCSP responder.</p></div></div></td><td><div></div></td><td><div></div></td></tr><tr><td><p><strong>Cert Alias</strong></p></td><td><div><div><p>String</p></div></div></td><td><div><div><p>Alias of the signing certificate for the OCSP response (must be in the trust store), if present.</p></div></div></td><td><div></div></td><td><div></div></td></tr></tbody></table>

### CRL File

<table><colgroup><col> <col> <col> <col> <col></colgroup><thead><tr><th>Field</th><th>Type</th><th>Description</th><th>Default Value</th><th>Required</th></tr></thead><tbody><tr><td><p><strong>Path</strong></p></td><td><div><div><p>String</p></div></div></td><td><div><div><p>The path to the CRL file.</p></div></div></td><td><div></div></td><td><div></div></td></tr></tbody></table>

### Reconnection

<table><colgroup><col> <col> <col> <col> <col></colgroup><thead><tr><th>Field</th><th>Type</th><th>Description</th><th>Default Value</th><th>Required</th></tr></thead><tbody><tr><td><p><strong>Fails Deployment</strong></p></td><td><div><div><p>Boolean</p></div></div></td><td><div><div><p>When the application is deployed, a connectivity test is performed on all connectors. If set to true, deployment fails if the test doesn’t pass after exhausting the associated reconnection strategy.</p></div></div></td><td><div></div></td><td><div></div></td></tr><tr><td><p><strong>Reconnection Strategy</strong></p></td><td><div><div><ul><li><p><a href="#Reconnect">Reconnect</a></p></li><li><p><a href="#ReconnectForever">Reconnect Forever</a></p></li></ul></div></div></td><td><div><div><p>The reconnection strategy to use.</p></div></div></td><td><div></div></td><td><div></div></td></tr></tbody></table>

### Reconnect

<table><colgroup><col> <col> <col> <col> <col></colgroup><thead><tr><th>Field</th><th>Type</th><th>Description</th><th>Default Value</th><th>Required</th></tr></thead><tbody><tr><td><p><strong>Frequency</strong></p></td><td><div><div><p>Number</p></div></div></td><td><div><div><p>How often in milliseconds to reconnect.</p></div></div></td><td><div></div></td><td><div></div></td></tr><tr><td><p><strong>Blocking</strong></p></td><td><div><div><p>Boolean</p></div></div></td><td><div><div><p>If false, the reconnection strategy will run in a separate, non-blocking thread.</p></div></div></td><td><div></div></td><td><div></div></td></tr><tr><td><p><strong>Count</strong></p></td><td><div><div><p>Number</p></div></div></td><td><div><div><p>How many reconnection attempts to make.</p></div></div></td><td><div></div></td><td><div></div></td></tr></tbody></table>

### Reconnect Forever

<table><colgroup><col> <col> <col> <col> <col></colgroup><thead><tr><th>Field</th><th>Type</th><th>Description</th><th>Default Value</th><th>Required</th></tr></thead><tbody><tr><td><p><strong>Frequency</strong></p></td><td><div><div><p>Number</p></div></div></td><td><div><div><p>How often in milliseconds to reconnect.</p></div></div></td><td><div></div></td><td><div></div></td></tr><tr><td><p><strong>Blocking</strong></p></td><td><div><div><p>Boolean</p></div></div></td><td><div><div><p>If false, the reconnection strategy will run in a separate, non-blocking thread.</p></div></div></td><td><div></div></td><td><div></div></td></tr></tbody></table>

### Expiration Policy

<table><colgroup><col> <col> <col> <col> <col></colgroup><thead><tr><th>Field</th><th>Type</th><th>Description</th><th>Default Value</th><th>Required</th></tr></thead><tbody><tr><td><p><strong>Max Idle Time</strong></p></td><td><div><div><p>Number</p></div></div></td><td><div><div><p>A scalar time value for the maximum amount of time a dynamic configuration instance should be allowed to be idle before it’s considered eligible for expiration.</p></div></div></td><td><div></div></td><td><div></div></td></tr><tr><td><p><strong>Time Unit</strong></p></td><td><div><div><p>Enumeration, one of:</p></div><div><ul><li><p>NANOSECONDS</p></li><li><p>MICROSECONDS</p></li><li><p>MILLISECONDS</p></li><li><p>SECONDS</p></li><li><p>MINUTES</p></li><li><p>HOURS</p></li><li><p>DAYS</p></li></ul></div></div></td><td><div><div><p>Time unit that qualifies the <strong>Max Idle Time</strong> attribute.</p></div></div></td><td><div></div></td><td><div></div></td></tr></tbody></table>

### HTTP Response Attributes

<table><colgroup><col> <col> <col> <col> <col></colgroup><thead><tr><th>Field</th><th>Type</th><th>Description</th><th>Default Value</th><th>Required</th></tr></thead><tbody><tr><td><p><strong>Status Code</strong></p></td><td><div><div><p>Number</p></div></div></td><td><div></div></td><td><div></div></td><td><div><div><p>x</p></div></div></td></tr><tr><td><p><strong>Headers</strong></p></td><td><div><div><p>Object</p></div></div></td><td><div></div></td><td><div></div></td><td><div><div><p>x</p></div></div></td></tr><tr><td><p><strong>Reason Phrase</strong></p></td><td><div><div><p>String</p></div></div></td><td><div></div></td><td><div></div></td><td><div><div><p>x</p></div></div></td></tr></tbody></table>

### Repeatable In Memory Stream

<table><colgroup><col> <col> <col> <col> <col></colgroup><thead><tr><th>Field</th><th>Type</th><th>Description</th><th>Default Value</th><th>Required</th></tr></thead><tbody><tr><td><p><strong>Initial Buffer Size</strong></p></td><td><div><div><p>Number</p></div></div></td><td><div><div><p>Initial amount of memory to allocate to the memory stream. If the stream data exceeds this value, the buffer expands by <strong>Buffer Size Increment</strong>, with an upper limit <strong>Max In Memory Size value</strong>.</p></div></div></td><td><div></div></td><td><div></div></td></tr><tr><td><p><strong>Buffer Size Increment</strong></p></td><td><div><div><p>Number</p></div></div></td><td><div><div><p>Amount by which the buffer size expands if it exceeds its initial size. Setting a value of <code>0</code> or lower specifies that the buffer can’t expand. Mule raises a <code>STREAM_MAXIMUM_SIZE_EXCEEDED</code> error when the buffer gets full.</p></div></div></td><td><div></div></td><td><div></div></td></tr><tr><td><p><strong>Max Buffer Size</strong></p></td><td><div><div><p>Number</p></div></div></td><td><div><div><p>Maximum size of the buffer. A value less than or equal to <code>0</code> means no limit.</p></div></div></td><td><div></div></td><td><div></div></td></tr><tr><td><p><strong>Buffer Unit</strong></p></td><td><div><div><p>Enumeration, one of:</p></div><div><ul><li><p>BYTE</p></li><li><p>KB</p></li><li><p>MB</p></li><li><p>GB</p></li></ul></div></div></td><td><div><div><p>The unit in which all these attributes are expressed</p></div></div></td><td><div></div></td><td><div></div></td></tr></tbody></table>

### Repeatable File Store Stream

<table><colgroup><col> <col> <col> <col> <col></colgroup><thead><tr><th>Field</th><th>Type</th><th>Description</th><th>Default Value</th><th>Required</th></tr></thead><tbody><tr><td><p><strong>In Memory Size</strong></p></td><td><div><div><p>Number</p></div></div></td><td><div><div><p>Defines the maximum memory that the stream should use to keep data in memory. If more than that is consumed content on the disk is buffered.</p></div></div></td><td><div></div></td><td><div></div></td></tr><tr><td><p><strong>Buffer Unit</strong></p></td><td><div><div><p>Enumeration, one of:</p></div><div><ul><li><p>BYTE</p></li><li><p>KB</p></li><li><p>MB</p></li><li><p>GB</p></li></ul></div></div></td><td><div><div><p>The unit in which maxInMemorySize is expressed</p></div></div></td><td><div></div></td><td><div></div></td></tr></tbody></table>

## See Also

- [Amazon Lambda Connector Overview](https://docs.mulesoft.com/amazon-lambda-connector/latest/)

- [Salesforce Help](https://help.salesforce.com)

<!-- document id=45137f5d7b6d51af802e43fd6189727427e3c2335c0f7ed5ce8d3765263b857b url=/mulesoft/current/en-us/amazon-lambda-connector/1.0/amazon-lambda-connector-studio.md -->

---
product: Amazon Lambda Connector
version: 1.0
---

# Using Anypoint Studio to Configure Amazon Lambda Connector 1.0

> For the full documentation index, see: https://docs.mulesoft.com/llms.txt

Anypoint Studio (Studio) editors help you design and update your Mule applications, properties, and
configuration files.

To add and configure a connector in Studio:

1.  [Create a Mule project](#create-mule-project).

2.  [Add the connector to your Mule project](#add-connector-to-project).

3.  [Configure a source for the connector’s flow](#configure-source).

4.  [Add a connector operation to the flow](#add-connector-operation).

5.  [Configure a global element for the connector](#configure-global-element).

6.  [Configure the other connector fields](#configure-other-fields).

When you run the connector, you can view the app log to check for problems in real time, as
described in [View the App Log](#view-app-log).

If you are new to configuring connectors in Studio, see
[Using Anypoint Studio to Configure a Connector](https://docs.mulesoft.com/connectors/introduction/intro-config-use-studio).
If, after reading this topic, you need additional information about the connector fields, see the
[Amazon Lambda Reference](https://docs.mulesoft.com/amazon-lambda-connector/1.0/amazon-lambda-connector-reference).

## Create a Mule Project

In Studio, create a new Mule project in which to add and configure the connector:

1.  In Studio, select **File > New > Mule Project**.

2.  Enter a name for your Mule project and click **Finish**.

## Add the Connector to Your Mule Project

Add Amazon Lambda Connector to your Mule project to automatically populate the XML code with the
connector’s namespace and schema location and add the required dependencies to the project’s
`pom.xml` file:

1.  In the **Mule Palette** view, click **(X) Search in Exchange**.

2.  In the **Add Dependencies to Project** window, type `lambda` in the search field.

3.  Click **Amazon Lambda Connector** in **Available modules**.

4.  Click **Add**.

5.  Click **Finish**.

Adding a connector to a Mule project in Studio does not make that connector available to other
projects in your Studio workspace.

## Configure a Source

A source initiates a flow when a specified condition is met. You can configure one of these sources
to use with Amazon Lambda Connector:

- HTTP Listener

  Initiates a flow each time it receives a request on the configured host and port

- Scheduler

  Initiates a flow when a time-based condition is met

For example, to configure an HTTP Listener source, follow these steps:

1.  In **Mule Palette**, select **HTTP > Listener**.

2.  Drag **Listener** to the Studio canvas.

3.  In the **Listener** configuration screen, optionally change the value of the **Display Name**
    field.

4.  Specify a value for the **Path** field.

5.  Click **+** next to **Connector configuration** to configure a global element that can be used
    by all instances of the HTTP Listener source in the app.

6.  In the **General** tab, specify connection information for the connector.

7.  In the **TLS** tab, optionally specify the TLS information for the connector.

8.  In the **Advanced** tab, optionally specify reconnection information, including a reconnection
    strategy.

9.  Click **Test Connection** to confirm that Mule can connect with the specified server.

10. Click **OK**.

## Add a Connector Operation to the Flow

When you add a connector operation to your flow, you are specifying an action for that connector to
perform.

To add an operation for Amazon Lambda Connector, follow these steps:

1.  In **Mule Palette**, select **Amazon Lambda** and then select the desired operation.

2.  Drag the operation onto the Studio canvas to the right of the input source.

## Configure a Global Element for the Connector

When you configure a connector, configure a global element that all instances of that connector in
the app can use. Configuring a global element requires you to provide the authentication credentials
that the connector requires to access the target Amazon Lambda system.

To configure the global element for Amazon Lambda Connector, follow these steps:

1.  Select the operation in the Studio canvas.

2.  In the configuration screen for the operation, click **+** next to **Connector configuration**
    to access the global element configuration fields.

3.  In the **General** tab, in **Connection**, select the authentication method to configure.

    You can reference a configuration file that contains ANT-style property placeholders
    (recommended), or you can enter your authorization credentials in the global configuration
    properties. For information about the benefits of using property placeholders and how to
    configure them, see
    [Anypoint Connector Configuration](https://docs.mulesoft.com/connectors/introduction/intro-connector-configuration-overview).

4.  In the **Advanced** tab, optionally specify reconnection information, including a reconnection
    strategy.

5.  Click **Test Connection** to confirm that Mule can connect with the specified server.

6.  Click **OK**.

## Configure Additional Connector Fields

After you configure a global element for Amazon Lambda Connector, configure the other required
fields for the connector. The required fields vary depending on which connector operation you use.

## View the App Log

To check for problems, you can view the app log as follows:

- If you’re running the app from Anypoint Platform, the app log output is visible in the Anypoint
  Studio console window.

- If you’re running the app using Mule from the command line, the app log output is visible in your
  OS console.

Unless the log file path is customized in the app’s log file (`log4j2.xml`), you can also view the
app log in the default location `MULE_HOME/logs/<app-name>.log`. You can configure the location of
the log path in the app log file `log4j2.xml`.

## See Also

- [Introduction to Anypoint Connectors](https://docs.mulesoft.com/connectors/introduction/introduction-to-anypoint-connectors)

- [Using Anypoint Studio to Configure a Connector](https://docs.mulesoft.com/connectors/introduction/intro-config-use-studio)

- [Amazon Lambda Connector Reference](https://docs.mulesoft.com/amazon-lambda-connector/1.0/amazon-lambda-connector-reference)

- [Salesforce Help](https://help.salesforce.com)

<!-- document id=2523f110061d3cb9f167f10fa206fea51f0eb17e9359a2a43700a87884002841 url=/mulesoft/current/en-us/amazon-lambda-connector/1.1/amazon-lambda-connector-studio.md -->

---
product: Amazon Lambda Connector
version: 1.1
---

# Using Anypoint Studio to Configure Amazon Lambda Connector 1.1

> For the full documentation index, see: https://docs.mulesoft.com/llms.txt

Anypoint Studio (Studio) editors help you design and update your Mule applications, properties, and
configuration files.

To add and configure a connector in Studio:

1.  [Create a Mule project](#create-mule-project).

2.  [Add the connector to your Mule project](#add-connector-to-project).

3.  [Configure a source for the connector’s flow](#configure-source).

4.  [Add a connector operation to the flow](#add-connector-operation).

5.  [Configure a global element for the connector](#configure-global-element).

6.  [Configure the other connector fields](#configure-other-fields).

When you run the connector, you can view the app log to check for problems in real time, as
described in [View the App Log](#view-app-log).

If you are new to configuring connectors in Studio, see
[Using Anypoint Studio to Configure a Connector](https://docs.mulesoft.com/connectors/introduction/intro-config-use-studio).
If, after reading this topic, you need additional information about the connector fields, see the
[Amazon Lambda Reference](https://docs.mulesoft.com/amazon-lambda-connector/1.1/amazon-lambda-connector-reference).

## Create a Mule Project

In Studio, create a new Mule project in which to add and configure the connector:

1.  In Studio, select **File > New > Mule Project**.

2.  Enter a name for your Mule project and click **Finish**.

## Add the Connector to Your Mule Project

Add Amazon Lambda Connector to your Mule project to automatically populate the XML code with the
connector’s namespace and schema location and add the required dependencies to the project’s
`pom.xml` file:

1.  In the **Mule Palette** view, click **(X) Search in Exchange**.

2.  In the **Add Dependencies to Project** window, type `lambda` in the search field.

3.  Click **Amazon Lambda Connector** in **Available modules**.

4.  Click **Add**.

5.  Click **Finish**.

Adding a connector to a Mule project in Studio does not make that connector available to other
projects in your Studio workspace.

## Configure a Source

A source initiates a flow when a specified condition is met. You can configure one of these sources
to use with Amazon Lambda Connector:

- HTTP Listener

  Initiates a flow each time it receives a request on the configured host and port

- Scheduler

  Initiates a flow when a time-based condition is met

For example, to configure an HTTP Listener source, follow these steps:

1.  In **Mule Palette**, select **HTTP > Listener**.

2.  Drag **Listener** to the Studio canvas.

3.  In the **Listener** configuration screen, optionally change the value of the **Display Name**
    field.

4.  Specify a value for the **Path** field.

5.  Click **+** next to **Connector configuration** to configure a global element that can be used
    by all instances of the HTTP Listener source in the app.

6.  In the **General** tab, specify connection information for the connector.

7.  In the **TLS** tab, optionally specify the TLS information for the connector.

8.  In the **Advanced** tab, optionally specify reconnection information, including a reconnection
    strategy.

9.  Click **Test Connection** to confirm that Mule can connect with the specified server.

10. Click **OK**.

## Add a Connector Operation to the Flow

When you add a connector operation to your flow, you are specifying an action for that connector to
perform.

To add an operation for Amazon Lambda Connector, follow these steps:

1.  In **Mule Palette**, select **Amazon Lambda** and then select the desired operation.

2.  Drag the operation onto the Studio canvas to the right of the input source.

## Configure a Global Element for the Connector

When you configure a connector, configure a global element that all instances of that connector in
the app can use. Configuring a global element requires you to provide the authentication credentials
that the connector requires to access the target Amazon Lambda system.

To configure the global element for Amazon Lambda Connector, follow these steps:

1.  Select the operation in the Studio canvas.

2.  In the configuration screen for the operation, click **+** next to **Connector configuration**
    to access the global element configuration fields.

3.  In the **General** tab, in **Connection**, select the authentication method to configure.

    You can reference a configuration file that contains ANT-style property placeholders
    (recommended), or you can enter your authorization credentials in the global configuration
    properties. For information about the benefits of using property placeholders and how to
    configure them, see
    [Anypoint Connector Configuration](https://docs.mulesoft.com/connectors/introduction/intro-connector-configuration-overview).

4.  In the **Advanced** tab, optionally specify reconnection information, including a reconnection
    strategy.

5.  Click **Test Connection** to confirm that Mule can connect with the specified server.

6.  Click **OK**.

## Configure Additional Connector Fields

After you configure a global element for Amazon Lambda Connector, configure the other required
fields for the connector. The required fields vary depending on which connector operation you use.

## View the App Log

To check for problems, you can view the app log as follows:

- If you’re running the app from Anypoint Platform, the app log output is visible in the Anypoint
  Studio console window.

- If you’re running the app using Mule from the command line, the app log output is visible in your
  OS console.

Unless the log file path is customized in the app’s log file (`log4j2.xml`), you can also view the
app log in the default location `MULE_HOME/logs/<app-name>.log`. You can configure the location of
the log path in the app log file `log4j2.xml`.

## See Also

- [Introduction to Anypoint Connectors](https://docs.mulesoft.com/connectors/introduction/introduction-to-anypoint-connectors)

- [Using Anypoint Studio to Configure a Connector](https://docs.mulesoft.com/connectors/introduction/intro-config-use-studio)

- [Amazon Lambda Connector Reference](https://docs.mulesoft.com/amazon-lambda-connector/1.1/amazon-lambda-connector-reference)

- [Salesforce Help](https://help.salesforce.com)

<!-- document id=b9e4276d04db9f1817df270ac058b0bdab004f997b19f3c2da6c3cdbc45d304a url=/mulesoft/current/en-us/amazon-lambda-connector/latest/amazon-lambda-connector-studio.md -->

---
product: Amazon Lambda Connector
version: 1.2
is-latest-version: true
---

# Using Anypoint Studio to Configure Amazon Lambda Connector 1.2

> For the full documentation index, see: https://docs.mulesoft.com/llms.txt

Anypoint Studio (Studio) editors help you design and update your Mule applications, properties, and
configuration files.

To add and configure a connector in Studio:

1.  [Create a Mule project](#create-mule-project).

2.  [Add the connector to your Mule project](#add-connector-to-project).

3.  [Configure a source for the connector’s flow](#configure-source).

4.  [Add a connector operation to the flow](#add-connector-operation).

5.  [Configure a global element for the connector](#configure-global-element).

6.  [Configure the other connector fields](#configure-other-fields).

When you run the connector, you can view the app log to check for problems in real time, as
described in [View the App Log](#view-app-log).

If you are new to configuring connectors in Studio, see
[Using Anypoint Studio to Configure a Connector](https://docs.mulesoft.com/connectors/introduction/intro-config-use-studio).
If, after reading this topic, you need additional information about the connector fields, see the
[Amazon Lambda Reference](https://docs.mulesoft.com/amazon-lambda-connector/latest/amazon-lambda-connector-reference).

## Create a Mule Project

In Studio, create a new Mule project in which to add and configure the connector:

1.  In Studio, select **File > New > Mule Project**.

2.  Enter a name for your Mule project and click **Finish**.

## Add the Connector to Your Mule Project

Add Amazon Lambda Connector to your Mule project to automatically populate the XML code with the
connector’s namespace and schema location and add the required dependencies to the project’s
`pom.xml` file:

1.  In the **Mule Palette** view, click **(X) Search in Exchange**.

2.  In the **Add Dependencies to Project** window, type `lambda` in the search field.

3.  Click **Amazon Lambda Connector** in **Available modules**.

4.  Click **Add**.

5.  Click **Finish**.

Adding a connector to a Mule project in Studio does not make that connector available to other
projects in your Studio workspace.

## Configure a Source

A source initiates a flow when a specified condition is met. You can configure one of these sources
to use with Amazon Lambda Connector:

- HTTP Listener

  Initiates a flow each time it receives a request on the configured host and port

- Scheduler

  Initiates a flow when a time-based condition is met

For example, to configure an HTTP Listener source, follow these steps:

1.  In **Mule Palette**, select **HTTP > Listener**.

2.  Drag **Listener** to the Studio canvas.

3.  In the **Listener** configuration screen, optionally change the value of the **Display Name**
    field.

4.  Specify a value for the **Path** field.

5.  Click **+** next to **Connector configuration** to configure a global element that can be used
    by all instances of the HTTP Listener source in the app.

6.  In the **General** tab, specify connection information for the connector.

7.  In the **TLS** tab, optionally specify the TLS information for the connector.

8.  In the **Advanced** tab, optionally specify reconnection information, including a reconnection
    strategy.

9.  Click **Test Connection** to confirm that Mule can connect with the specified server.

10. Click **OK**.

## Add a Connector Operation to the Flow

When you add a connector operation to your flow, you are specifying an action for that connector to
perform.

To add an operation for Amazon Lambda Connector, follow these steps:

1.  In **Mule Palette**, select **Amazon Lambda** and then select the desired operation.

2.  Drag the operation onto the Studio canvas to the right of the input source.

## Configure a Global Element for the Connector

When you configure a connector, configure a global element that all instances of that connector in
the app can use. Configuring a global element requires you to provide the authentication credentials
that the connector requires to access the target Amazon Lambda system.

To configure the global element for Amazon Lambda Connector, follow these steps:

1.  Select the operation in the Studio canvas.

2.  In the configuration screen for the operation, click **+** next to **Connector configuration**
    to access the global element configuration fields.

3.  In the **General** tab, in **Connection**, select the authentication method to configure.

    You can reference a configuration file that contains ANT-style property placeholders
    (recommended), or you can enter your authorization credentials in the global configuration
    properties. For information about the benefits of using property placeholders and how to
    configure them, see
    [Anypoint Connector Configuration](https://docs.mulesoft.com/connectors/introduction/intro-connector-configuration-overview).

4.  In the **Advanced** tab, optionally specify reconnection information, including a reconnection
    strategy.

5.  Click **Test Connection** to confirm that Mule can connect with the specified server.

6.  Click **OK**.

## Configure Additional Connector Fields

After you configure a global element for Amazon Lambda Connector, configure the other required
fields for the connector. The required fields vary depending on which connector operation you use.

## View the App Log

To check for problems, you can view the app log as follows:

- If you’re running the app from Anypoint Platform, the app log output is visible in the Anypoint
  Studio console window.

- If you’re running the app using Mule from the command line, the app log output is visible in your
  OS console.

Unless the log file path is customized in the app’s log file (`log4j2.xml`), you can also view the
app log in the default location `MULE_HOME/logs/<app-name>.log`. You can configure the location of
the log path in the app log file `log4j2.xml`.

## See Also

- [Introduction to Anypoint Connectors](https://docs.mulesoft.com/connectors/introduction/introduction-to-anypoint-connectors)

- [Using Anypoint Studio to Configure a Connector](https://docs.mulesoft.com/connectors/introduction/intro-config-use-studio)

- [Amazon Lambda Connector Reference](https://docs.mulesoft.com/amazon-lambda-connector/latest/amazon-lambda-connector-reference)

- [Salesforce Help](https://help.salesforce.com)