You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 28, 2021. It is now read-only.
lat: vocms53 is in firewalled territory where accesses are allowed only from front-ends and the host itself. Fortunately this machine isn't one of the reallocated systems with high ports available to half the world.
The access to MongoDB from front-end does concern me, although it's not a direct risk. Is it possible for you to configure MongoDB to listen only on localhost interface, not on 0.0.0.0 = all interfaces? This would be the exact reverse we've done to our own services, as you might recall.
So as long as DAS + MongoDB will run in restricted port range actually verified not to be accessible from other hosts, and MongoDB itself is not listening on outward facing network interfaces, you don't need to add extra layer of security in front.
(Copied from HN, as it was possibly relevant to other people there too.)
--bind_ip Specifies a single IP that the database server will listen for
which we can use to setup which host it should listen to. In our case it should be localhost, since DAS cache server runs on the same node as MongoDB. And as we agreed (I hope we're) I will run MongoDB on specific allocated port range.
Clarify with HTTP group if I need to put login/pw for mongodb.
The text was updated successfully, but these errors were encountered: