👀 Views: 94 💬 Answers: 1 📅 Created: 2025-06-09

aws step-functions lambda json JavaScript

I'm updating my dependencies and I am working on an AWS Step Function that orchestrates several Lambda functions. However, I'm working with an 'InvalidExecutionInput' behavior when trying to pass dynamic inputs to my Lambda function. My Step Function is defined using the AWS SDK for JavaScript (v3) and I am using the `inputPath` to modify the input before it reaches the Lambda. Here’s the relevant part of my Step Function definition: ```json { "Comment": "A Hello World example of the Amazon States Language", "StartAt": "SayHello", "States": { "SayHello": { "Type": "Task", "Resource": "arn:aws:lambda:us-east-1:123456789012:function:HelloWorld", "InputPath": "$.greeting", "ResultPath": "$.result", "Next": "ProcessResult" }, "ProcessResult": { "Type": "Task", "Resource": "arn:aws:lambda:us-east-1:123456789012:function:ProcessResult", "InputPath": "$.result" } } } ``` The input I'm trying to send to the Step Function looks like this: ```json { "greeting": "Hello, World!" } ``` Despite this, when I start the execution, I receive the following behavior message: ``` "behavior": "InvalidExecutionInput", "Cause": "Input does not match the expected input schema." ``` I verified that both Lambda functions are correctly defined and are working fine when invoked directly with static inputs. I also checked the IAM permissions and they seem to be in order. Could this be an scenario with how I am trying to format the input using `InputPath`? I’ve tried adjusting the paths and adding default values, but it hasn’t resolved the behavior. Any insights on how I can troubleshoot this scenario or correctly format my input would be greatly appreciated! Any pointers in the right direction?