1 個回答
- 最新
- 最多得票
- 最多評論
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!
相關內容
- 已提問 10 個月前
- AWS 官方已更新 2 年前
- AWS 官方已更新 2 年前
- AWS 官方已更新 10 個月前
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)