SQS pipeline troubles

Hi there,

Been testing out pipelines and hacked one of the examples to build an SQS pipeline:

  path: "*"
  content_type: application/json
steps:
  - name: step-0
    destination:
      type: batch
      version: v1
  - name: step-1
    transformer:
      type: extract-timestamp
      version: v1
  - name: step-2
    transformer:
      type: inject-path
      version: v1
    destination:
      type: aws-sqs
      version: v1
      parameters:
        url: https://sqs.ap-southeast-2.amazonaws.com/123456789012/Golioth.fifo
        access_key: <my_api_key>
        access_secret: $AWS_SQS_ACCESS_SECRET
        region: ap-southeast-2
  - name: step-3
    destination:
      type: lightdb-stream
      version: v1

Note that I have tried this with both my SQS server and the Golioth example. I have also confirmed that $AWS_SQS_ACCESS_SECRET is saved in the secrets manager.

When I run this using the simulator, I never see the message either in AWS, nor LightDB. I do however get two LightDB entries if I replace the SQS destination with a copy of the LightDB destination details, suggesting the SQS portion is failing somewhere, and the pipeline is terminating.

It feels like a pretty trivial example and should be straightforward. It also feels like something is bombing out on the Golioth side.

Any guidance is appreciated!

Hey @Zigenz,

AWS SQS FIFO queues are not currently supported, but support will be added soon. Until then, we encourage you to use the Standard Queue.