Describe the issue/error/question
" Problem running workflow
Bad request - please check your parameters" error appears when I click ‘Listen for events’ on AWS SNS node.
What is the error message (if any)?
Problem running workflow
Bad request - please check your parameters
Please share the workflow
Share the output returned by the last node
N/A, it’s the first node in the workflow, as it’s a trigger
Information on your n8n setup
-
n8n version: 0.187.2
-
Database you’re using (default: SQLite): SQLite
-
Running n8n with the execution process [own(default), main]: guess it’s own
-
Running n8n via [Docker, npm, n8n.cloud, desktop app]: Docker
Hi @alexander-potemkin, I am sorry to hear you’re having trouble.
I just tried this on my own end and didn’t run into any problems with “Standard” topics:
I could, however, reproduce the problem for “FIFO” topics and I believe this could be related to the age of the respective node. The “FIFO” topics appear to use a proprietary protocol and were only introduced after this node was created from the looks of it. I’ll add this to our internal backlog for a closer look, perhaps we can support such topics going forward or at least hide them from the selection if they are unsupported.
In the meantime, would you perhaps be able to use a SNS “Standard” topic for your use case?
@MutedJam , thank you for the prompt reaction and confirmation of the issue!
Yes, I do need FIFO for my case.
Is there any other no-code approach for the queue management you would recommend?
My understanding is that RabbitMQ seems to be the easiest one in ‘normal’ programming, but I didn’t find any easy way to get and use it from within n8n.
Yes, I do need FIFO for my case. Is there any other no-code approach for the queue management you would recommend?
n8n does also have an Apache Kafka node, though I haven’t used it myself and can’t say whether it would meet your needs I am afraid. Might still be worth checking out though until the AWS SNS functionality can be looked at.
Thank you. I have some idea in my mind, so I’d like to check with you, if you don’t mind - does the queue is requested / used often? And/or AWS SNS/SQS is considered complicated by many users?
These aren’t particularly popular nodes in the grand scheme of things (presumably because you’d only need them in rather advanced use cases). The most popular trigger nodes are general purpose ones like the Webhook or Cron node.
In general AWS is trying to simplify things a lot and I think the nodes reflect that (at least when they work 
).
Managing Kafka (and also Redis to some extent) manually is way more painful in my experience. Internally we’re using RabbitMQ for some operations and I haven’t heard any complaints about that, but I am just the guy trying to help out on the forum.
1 Like
Thank you! Would it be possible to bring a bit more light into the way you setup and manage RabbitMQ and if you have any GUI to manage the queue on itself?
