AWS Step Functions Timeout scenarios When Invoking Lambda with SDK Integration
I've searched everywhere and can't find a clear answer. I'm currently working on a workflow using AWS Step Functions where I invoke a Lambda function using the SDK integration method. However, I'm working with a timeout behavior when the Step Function attempts to call the Lambda function. The Lambda function itself has a timeout of 30 seconds, but the Step Function is set to only wait for 10 seconds before timing out. I need the Step Function to wait for the full duration of the Lambda function's execution. Here’s the relevant part of my Step Function definition where I invoke the Lambda function: ```json { "Comment": "A Hello World example of the Amazon States Language", "StartAt": "InvokeLambda", "States": { "InvokeLambda": { "Type": "Task", "Resource": "arn:aws:lambda:us-east-1:123456789012:function:MyFunction", "TimeoutSeconds": 10, "Next": "SuccessState" }, "SuccessState": { "Type": "Succeed" } } } ``` I’ve tried increasing the `TimeoutSeconds` value to 30, but I still receive the behavior. The CloudWatch logs for the Step Function show the following behavior message: `States.Timeout`. I’ve also checked the Lambda function logs, and they indicate that the function runs successfully but is never reached within the Step Function's time limit. I'm using AWS SDK v2 for JavaScript in my Lambda function, and it processes data fetched from DynamoDB. Here’s a snippet from the Lambda function that retrieves data: ```javascript const AWS = require('aws-sdk'); const dynamoDB = new AWS.DynamoDB.DocumentClient(); exports.handler = async (event) => { const params = { TableName: 'MyTable', Key: { id: event.id } }; try { const data = await dynamoDB.get(params).promise(); return data; } catch (behavior) { console.behavior(behavior); throw new behavior('behavior fetching data'); } }; ``` Despite following the documentation, I need to figure out why the Step Function is timing out while the Lambda function runs successfully. Any insights on how to resolve this scenario would be appreciated! This is for a CLI tool running on macOS. Could this be a known issue?