AWS Rekognition node isn't working

I have a typeform picture upload trigger connected to an AWS Rekognition node as I want to ensure pictures are kept friendly (moderation labels).

The output is empty, but there is no error. Please help

++++++++++++workflow pasted below

{
“meta”: {
“instanceId”: “e6c13242d687e0dee6e02ce02520a360aef556c7e1d2b8332c5e15093c3d0dd5”
},
“nodes”: [
{
“parameters”: {
“formId”: “k6E4Iv7Q”
},
“id”: “d36210b6-28c8-4d05-9bf1-596f34ad9e62”,
“name”: “Typeform Trigger”,
“type”: “n8n-nodes-base.typeformTrigger”,
“typeVersion”: 1,
“position”: [
460,
300
],
“webhookId”: “1305094f-9d83-45f9-81c8-d24acf38eddc”,
“credentials”: {
“typeformApi”: {
“id”: “1”,
“name”: “Typeform account”
}
}
},
{
“parameters”: {
“url”: “={{$json["UPLOAD PIC"]}}”,
“responseFormat”: “file”,
“options”: {}
},
“id”: “f953e7e6-1d75-4c27-8c90-831e10de628a”,
“name”: “HTTP Request”,
“type”: “n8n-nodes-base.httpRequest”,
“typeVersion”: 2,
“position”: [
680,
300
]
},
{
“parameters”: {
“binaryData”: true,
“additionalFields”: {}
},
“id”: “14a59be6-4a98-4727-a186-94cfafe31e4d”,
“name”: “AWS Rekognition”,
“type”: “n8n-nodes-base.awsRekognition”,
“typeVersion”: 1,
“position”: [
900,
300
],
“credentials”: {
“aws”: {
“id”: “14”,
“name”: “AWS account”
}
}
}
],
“connections”: {
“Typeform Trigger”: {
“main”: [
[
{
“node”: “HTTP Request”,
“type”: “main”,
“index”: 0
}
]
]
},
“HTTP Request”: {
“main”: [
[
{
“node”: “AWS Rekognition”,
“type”: “main”,
“index”: 0
}
]
]
}
}
}

+++++++++

Share the output returned by the last node

[
{
“UPLOAD PIC”: “https://api.typeform.com/responses/files/bfb0ea7b4fdca637fe771d4f7a6230a4dbc712b32e386cf5802d4cb2b7341da0/IMG_4806.jpg
}
]

Information on your n8n setup

  • n8n version: cloud
  • Database (default: SQLite): none
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app): cloud
  • Operating system: windows

Hi @Nikoleon265, I am very sorry for the trouble. Unfortunately this is a known issue first reported here: Amazon Rekognition Node Issue

I’ve checked the current status of the bug ticket, but it unfortunately does not have a high priority for the team. Seeing there already is an open thread for this bug, I’ll close this duplicate thread.