conductor icon indicating copy to clipboard operation
conductor copied to clipboard

Could not work with sqs , got: unknown queue type: sqs

Open johnico opened this issue 3 years ago • 2 comments

Trying to work with SQS and did not manage due to error : unknown queue type: sqs

1- how to fix it ? 2- how do i know i connected succsessfuly to aws ?

I defined the following code in conductor :

/server/src/main/resources/application.properties 

# Default event queue type to listen on for wait task
conductor.default-event-queue.type=sqs
conductor.event-queues.sqs.enabled=true
conductor.event-queues.sqs.authorized-accounts={your AWS account number}

added

 annotations-processor/awssqs-event-queue/src/main/java/com/netflix/conductor/SQSEventQueueConfiguration.java
 
  @Bean
    AWSCredentialsProvider createAWSCredentialsProvider() {
        return new DefaultAWSCredentialsProviderChain();
    }

and put ENV vars on docker-compose

AWS_ACCESS_KEY_ID="{key_id}"
AWS_SECRET_ACCESS_KEY="{access_key}"
AWS_REGION= us-east-1

i did not put AWS_SESSION_TOKEN="{token_value}}". , do i need it ?

Details Conductor version: 3.10 Persistence implementation: Postgres, Queue implementation: SQS Event handler definition:

definetion:

{
  "createTime": 1658911776331,
  "updateTime": 1658913499975,
  "name": "sqs_message_testing",
  "description": "sqs messages testing",
  "version": 1,
  "tasks": [
    {
      "name": "send_sqs_message",
      "taskReferenceName": "send_sqs_message_ref",
      "inputParameters": {},
      "type": "EVENT",
      "decisionCases": {},
      "defaultCase": [],
      "forkTasks": [],
      "startDelay": 0,
      "joinOn": [],
      "sink": "sqs:conductor_test_queue",
      "optional": false,
      "defaultExclusiveJoinTask": [],
      "asyncComplete": false,
      "loopOver": []
    },
    {
      "name": "sqs_message_wait_task",
      "taskReferenceName": "sqs_message_wait_task_ref",
      "inputParameters": {
        "duration": "10 seconds"
      },
      "type": "WAIT",
      "decisionCases": {},
      "defaultCase": [],
      "forkTasks": [],
      "startDelay": 0,
      "joinOn": [],
      "optional": false,
      "defaultExclusiveJoinTask": [],
      "asyncComplete": false,
      "loopOver": []
    }
  ],
  "inputParameters": [],
  "outputParameters": {},
  "schemaVersion": 2,
  "restartable": true,
  "workflowStatusListenerEnabled": false,
  "ownerEmail": "[email protected]",
  "timeoutPolicy": "ALERT_ONLY",
  "timeoutSeconds": 0,
  "variables": {},
  "inputTemplate": {}
}

johnico avatar Jul 27 '22 09:07 johnico

Please refer to this guide from @dougsillars from our last meetup about setting up Conductor to work with AWS SQS.

apanicker-nflx avatar Aug 01 '22 21:08 apanicker-nflx

I'm pretty sure you need that session token. Did you message REACH the SQS queue on AWS? you can poll for messages - see if it arrived.

To end the WAIT task, you'll need an EVENT. The event listens for the SQS and feeds the result to the WAIT task. https://orkes.io/content/docs/how-tos/Tasks/SQS-event-task

dougsillars avatar Aug 02 '22 13:08 dougsillars

This issue is stale, because it has been open for 45 days with no activity. Remove the stale label or comment, or this will be closed in 7 days.

github-actions[bot] avatar Sep 30 '22 00:09 github-actions[bot]

This issue was closed, because it has been stalled for 7 days with no activity.

github-actions[bot] avatar Oct 08 '22 00:10 github-actions[bot]