1 Answer
- Newest
- Most votes
- Most comments
0
Hi there! As a workaround, you can create separate VPCs, in each participant account, for RabbitMQ, and peer them with the shared VPC. Or you can create RabbitMQ in non-shared subnets in the shared VPC (in the owner account). Hope this helps!
Relevant content
- asked 2 days ago
- asked 2 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 7 months ago
- AWS OFFICIALUpdated 2 years ago
Hi,
We have already been using rabbitmq this way only but this is not efficient to manage. Just wanted to know if there is any timeline where we can have rabbitmq with shared subnets (Shared via RAM service)