Lambda HTTP-triggered functions are Lambda functions that can be invoked through an HTTP(s) endpoint remotely instead of a typical trigger type such as queue, EventBridge.
Below are GeneXus objects that can be deployed as HTTP Functions:
- HTTP services
- Procedures, Business Components, Data Providers exposed as Rest services.
- API objects.
- Mobile back-end services (Angular, iOS, Android)
- An entire back-end service can be deployed as a Lambda HTTP-triggered function. However, the recommeded way for deploying is HTTP APIs using Lambda & API Gateway.
First, read How to: create a GeneXus procedure to be deployed as an Azure Function or an AWS Lambda Function.
To deploy the function, use the deployment tool. See Deploy to AWS Lambda Function.
In the Deployment Unit, set the following properties as shown below:
- AWS Access Key ID/AWS Secret Access Key: Enter your AWS Access Key.
- AWS Default Region: Select your preferred region (localization) for your Deployment.
- Function Name: It's the name used to display the application.
- Trigger type: Select Http.
- IAM Execution Role ARN property: Enter the Amazon Resource Names (ARNs) path.
The configuration settings are as shown in the following image taken from an example:
Note: You must have previously created an IAM Execution Role with the minimum permissions required for the function to execute.
From the AWS Console UI, you must attach the trigger type for the function to be executed automatically on a timed basis.
- Go to AWS Lambda Console UI.
- Select the AWS Lambda Function
- Go to Tab “Configuration” and select “Function URL.”
- Click on “Create function URL”.
- Click on Save
After this step is completed, AWS will show the endpoint URL. Typically, the endpoint has the following pattern: