Overview
The AWS Lambda plugin provides the integrations to invoke and list the available functions in the AWS Lambda service in the AWS instance.
To connect with the AWS instance, the connected system must be authenticated with the Access Key ID and the Secret Access Key.
Key Features & Functionality
Hi Mike S ,
We are currently preoccupied with other plugins. We will add this to our backlog and let you know once we find a solution.
Regards,
Praveen Santhosh
Praveen Santhosh see my response above.
The timeout configuration of the lambda function is 15 minutes, max time, and the lambda continues to function after the Appian process dies
Apologies for the delay. We are currently working on multiple plugins and were not able to look into this.
But, as I asked earlier, what was the timeout configured in the Lambda function's configuration. I believe you have shared the timeout configuration which you have used for the integration.
Also, please note that the execution timeout configuration in the integration controls only the session timeout value so that the connection will not be abruptly cut off. This timeout value has no relation to the Lambda function's timeout.
Hello Praveen. Is this no longer maintained?
Praveen Santhosh Did you ever get a chance to look in to this.
execution timeout: 600
Can you please share the timeout configuration for the function in Lambda?
Praveen Santhosh any thoughts or updates on this?
Hello Praveen Santhosh
connected system is pointed to our aws environment in us-east-2
Operation: invoke function
function name: name of our function (built using a constants and concatenation)
inputs:
a!toJson({ "input1": ri!input1, "input2": {ri!input2}, "input3": ri!input3, "input4": ri!input4, "input5": ri!input5, "input6": ri!input6, "input7" : {ri!input7} } )
execution timeout: 600Execution gets kicked off just fine and runs just fine, the node just dies early with the above error