Summary
When leveraging Dynatrace Workflows to automate your AWS infrastructure using AWS Connector, you can target a rich set of services, such as Amazon Web Services S3 (Simple Storage Service), AWS EC2 (Elastic Compute Cloud) or AWS Lambda.
If you want to invoke AWS Lambda Functions, you may run into timeout issues. This article will walk you through this problem and explain how to resolve it.
Problem
When running an AWS Connector Action with the goal to invoke a Lambda Function, the execution might abort with an error such as:
Error: Unable to run Lambda: Invoke - Operation timed out.When a Lambda: Invoke Workflows Action times out like in the error message shown, the targeted Lambda Function might simply be running for too long, surpassing the execution time limit of 100 seconds imposed by the AWS Connector.
This can only happen if the used InvocationType parameter in your Action Input is set to RequestResponse like in the screenshot shown above.
Resolution
The Lambda: Invoke Workflows Action offers the ability to configure the way a Lambda Function is invoked using the InvocationType parameter. In order to not make the Workflow execution wait for the Lambda Function to finish, you can set this parameter to either DryRun or Event like in the screenshots shown below. Keep in mind that the Workflows Action will not be able to access the result of the Lambda Function this way.
Please refer to the official Dynatrace documentation to learn more about the configuration options.
Another possibility to resolve this issue would be to keep the RequestResponse invocation type and adjusting the targeted Lambda Function to make it finish within the execution time limit of 100 seconds.
What's next
If this article did not help, please open a support ticket, mention that this article was used and provide the following in the ticket:
