Currently, we've got RabbitMQ's management interface exposed over HTTPS via nginx. Only a subset of the users are tagged as admin users and all of them were created with strong, random passwords. Because of that, this isn't automatically insecure.
However, configuration-wise it simplifies things to just split RabbitMQ off and treat it as its own piece of infrastructure capable of serving its own management interface without nginx being involved.
Currently, we've got RabbitMQ's management interface exposed over HTTPS via nginx. Only a subset of the users are tagged as admin users and all of them were created with strong, random passwords. Because of that, this isn't automatically insecure.
However, configuration-wise it simplifies things to just split RabbitMQ off and treat it as its own piece of infrastructure capable of serving its own management interface without nginx being involved.