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!
関連するコンテンツ
- 質問済み 6年前
- AWS公式更新しました 2年前
- AWS公式更新しました 8ヶ月前
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)