'Shovel Configuration between 2 AWS MQ private RabbitMQ clusters

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 '[email protected]' 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?



Solution 1:[1]

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

Sources

This article follows the attribution requirements of Stack Overflow and is licensed under CC BY-SA 3.0.

Source: Stack Overflow

Solution Source
Solution 1 Vasilis Markopoulos