0

So I have 2 AWS MQ RabbitMQ clusters in the same vpc without public accessibility. Both are multi az Clusters with 3 nodes.

Lets say

  • rabbitmq-1
  • rabbitmq-2

Now I want to create a dynamic shovel from 1 to 2 in the Rabbitmq management console.

I'm trying to create with

  • source_protocol = amqp091
  • source_uri = amqps://user1:pass1@b-1xxxx:5671
  • destination_protocol = amqp091
  • destination_uri = amqps://user2:pass2@b-2xxxx:5671

But the shovel status is stuck in starting:
Shovel Status

Also in cloudwatch sometimes I see the following error :

Shovel with the name 'test-bill ' was not found on the target node 'rabbit@ip-10-0-20-90.eu-central-1.compute.internal' and / or virtual host '/'

I don't get what exactly happens with the shovel creation and the 3 nodes. Sometimes I can't even delete shovel from the console. I think it is randomly distributed between nodes. Any ideas on what is the issue and shovel doesn't connect successfully?

Masoud Keshavarz
  • 2,166
  • 9
  • 36
  • 48
Vasilis Markopoulos
  • 21
  • 6
  • 1
    https://docs.aws.amazon.com/amazon-mq/latest/developer-guide/rabbitmq-basic-elements-plugins.html#rabbitmq-shovel-plugin The docs state that this is currently not possible `You cannot configure shovel between queues or exchanges if the shovel destination is a private broker. You can only configure shovel between queues or exchanges in public brokers, or between a source in a private broker, and a destination in a public broker.` Same applies for federation unfortunately. – crasp Jun 24 '22 at 06:16

1 Answers1

0

So With AWS Support help , it seems that 2 private AWS MQ RabbitMQ clusters cannot connect via shovel.

Vasilis Markopoulos
  • 21
  • 6