We’ve been trying to get our custom agent desktop to call an AWS Lambda function directly from Genesys Cloud Architect. The goal is to send some interaction metadata to our backend service. I’ve got the Data Action configured with the POST method pointing to the Lambda Invoke URL. The payload looks correct, just a simple JSON object with the contact ID and queue name.
Here is the JSON body we are sending:
{
"contactId": "12345",
"queueName": "Support"
}
The issue is we keep getting a 403 Forbidden error back from the Lambda. The error message in the response body says InvalidSignatureException. We thought it was an IAM role issue on the Genesys side, but we’ve already granted the lambda:InvokeFunction permission to the Genesys Cloud IAM user. We also checked the Lambda function’s resource-based policy to make sure it allows the Genesys account ID.
The Lambda function itself is public for testing purposes right now, so there shouldn’t be any auth issues. We’re using the .NET SDK to handle the webhook responses in our desktop app, but the call never reaches the Lambda. Is there a specific header or signature we need to include in the Architect Data Action request? Or is this a known issue with the Genesys Cloud integration?