AWS Lambda

1 Introduction

The AWS Lambda connector provides a way for your app to trigger AWS Lambda functions.

1.1 Typical Use Cases

AWS Lambda is a serverless, event-driven compute service that lets you run code for virtually any type of application or backend service without provisioning or managing servers. You can trigger Lambda from over 200 AWS services and software as a service (SaaS) applications, and only pay for what you use.

1.2 Prerequisites

The AWS Lambda connector requires Mendix Studio Pro 9.18.0 or above.

To authenticate with Amazon Web Service (AWS), you must also install and configure the AWS authentication connector. If you are using the Amazon Lambda connector version 2.0 or higher, it requires the AWS Authentication connector version 3.0 or higher. It is crucial for the Amazon S3 connector to function correctly For more information about installing and configuring the AWS Authentication connector, see AWS Authentication.

1.3 Licensing and Cost

This connector is available as a free download from the Mendix Marketplace, but the AWS service to which is connects may incur a usage cost. For more information, refer to AWS documentation.

Depending on your use case, your deployment environment, and the type of app that you want to build, you may also need a license for your Mendix app. For more information, refer to Licensing Apps.

2 Installation

Follow the instructions in Using Marketplace Content to import the AWS Lambda connector into your app.

3 Configuration

After you install the connector, you can find it in the App Explorer, in the AWSLambdaConnector section. The connector provides a domain model and several microflows which you can use to quickly configure the Lambda connector for your use case. Each activity can be implemented by using it in a microflow. To ensure that your app can connect to the AWS service, you must also configure AWS authentication for the connector.

3.1 Configuring AWS Authentication

In order to use the AWS Lambda service, you must authenticate with AWS. To do so, you must set up a configuration profile in your Mendix app. After you set up the configuration profile, the connector module handles the authentication internally.

As of version 3.0.0 of the AWS Authentication Connector, all the resources and logic required to set up authentication are centralized inside the AWS Authentication Connector module.

The AWS Authentication Connector supports both static credentials and temporary credentials. For more information and detailed instructions please refer to the AWS Authentication Connector documentation page.

3.2 Configuring a Microflow for an AWS Service

To quickly configure the connection to AWS Lambda by configuring a microflow, perform the following steps:

1. In the App Explorer, in App > Marketplace modules > AWSAuthentication > ConnectionDetails, configure the required authentication credentials. For more information about the difference between static and temporary credentials, see AWS Authentication.

2. Create a new microflow.

3. In AWSLambdaConnector > Operations, find the microflow activty for the operation you want to perform. For example, if you want to get the list of available Lambda functions, find the ListFunctions activity and drag it to your microflow. For more information about the activities that the microflows can perform, see Activities.

4. Configure the required parameters:

   1. For the ListFunctionsRequest parameter, create a new ListFunctionsRequest object at the start of the microflow and pass it to the ListFunctions activity.
   2. In the Toolbox, depending on the type of credentials you want to use, search for the GetStaticCredentials activity or the GetTemporaryCredentials activity and drag it to the start of your microflow. Then select it as the value for the Credentials parameter of the ListFunctions activity.
   3. For the ENUM_Region parameter, choose a Region from the AWSAuthentication.ENUM_Region enumeration. For example, AWSAuthentication.ENUM_Region.us_east_1 for the US_East_1 Region.
   4. The ListFunctions activity will return a ListFunctionsResponse with details about the retrieved lambda functions.

4 Technical Reference

To help you work with the AWS Lambda connector, the following sections of this document list the available entities and activities that you can use in your application.

4.1 Domain Model

The domain model is a data model that describes the information in your application domain in an abstract way. For more information, see Domain Model.

4.2 Activities

Activities define the actions that are executed in a microflow or a nanoflow. For the AWS Lambda connector, they represent the actions that can be performed with Lambda functions.

4.2.1 ListFunctions

This activity lists all the Lambda functions which are available for the supplied AWS credentials.

Parameters

• Parameter of the type ListFunctionsRequest – Requesting a list of available Lambda functions

Returns

• List of objects of entity type FunctionResponse

4.2.2 InvokeFunction

This activity invokes a Lambda function. By default, this function invokes Lambda functions synchronously. To invoke a Lambda function, make sure to set the InvocationType attribute of the InvokeFunctionRequest entity to the preferred value. See section 4.3.1 for more information on the available options.

Parameters

• Parameter of the type InvokeFunctionRequest – the function that you are invoking

Returns

• Function invocation payload response in the InvokeFunctionResponse entity

4.2.3 DeleteFunction

This activity deletes a single Lambda function.

Parameters

• Parameter of the type DeleteFunctionRequest – the Lambda function which you want to delete

Returns

• Boolean – true if function was successfully deleted, otherwise false

4.3 Enumerations

An enumeration is a predefined list of values that can be used as an attribute type. For the AWS Lambda connector, the list of available invocation types is provided as an enumeration.

4.3.1 ENUM_InvocationType