5 - Verifications and Troubleshooting

Updated 3 weeks ago by Michael Cretzman

This topic discusses how to verify your Lambda deployments, the live, production Lambda functions, and troubleshooting steps for issues you might encounter during deployment.

Lambda Verifications

You can verify your live, production Lambda functions using Harness 24/7 Service Guard or your Lambda deployments using Deployment Verifications. In both cases, you use AWS CloudWatch.

For steps on setting up CloudWatch Verification in Harness, see CloudWatch Verification.


The following troubleshooting steps should help address common issues.

User is not authorized to perform: lambda:GetFunction

When you deploy your Workflow you might receive this error:

Exception: User: arn:aws:sts::XXXXXXXXXXXX:assumed-role/iamRole_forDelegate/i-XXXXXXXXXXXX 
is not authorized to perform: lambda:GetFunction on resource:
(Service: AWSLambda; Status Code: 403; Error Code: AccessDeniedException;
Request ID: 1e93ab96-985f-11e9-92b1-f7629978142c) while deploying function: ExampleApp-aws-lambda-Lambda-test

This error occurs because the IAM role attached to your EC2 or ECS Delegate host does not have the AWSLambdaRole (arn:aws:iam::aws:policy/service-role/AWSLambdaRole) role attached. The role contains the lambda:InvokeFunction needed:

"Version": "2012-10-17",
"Statement": [
"Effect": "Allow",
"Action": [
"Resource": [

Attach the AWSLambdaRole (arn:aws:iam::aws:policy/service-role/AWSLambdaRole) policy to the IAM role used by your Delegate host(s).

For more information, see Identity-based IAM Policies for AWS Lambda from AWS.

Exception: The runtime parameter of nodejs6.10 is no longer supported

If you choose Node,js version 6.10 as the runtime for your Lambda function, you might receive this error.

AWS Lambda no longer supports Node,js version 6.10. Use a newer version.

Next Steps

  • CloudWatch Verification - Learn how to use AWS CloudWatch to verify your deployments and monitor your production services.

How did we do?