So I’m seeing a very odd bug with the Architect Data Action configured to invoke a Lambda function via the aws:lambda:Invoke integration. The IAM role attached to the Genesys Cloud integration has lambda:InvokeFunction permissions on the target ARN, yet the Data Action execution logs consistently return a 403 Forbidden with errorMessage: "User: arn:aws:iam::123456789:role/gc-integration-role is not authorized to perform: lambda:InvokeFunction". I’ve verified the role trust policy allows genesyscloud.amazonaws.com as the principal, and the Lambda function’s resource-based policy also permits the role, but the invocation still fails with the signature error. Is there a specific header or payload structure required in the Data Action’s request mapping that affects the SigV4 signing process?