-
Notifications
You must be signed in to change notification settings - Fork 328
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Don't bind Elasticsearch or Mongo to public network interface by default
If you were running API Umbrella on an unprotected network without firewall rules in place, this could have allowed external access to these databases. Now if you're setting up a multi-server environment, then you must explicitly change these settings so that the servers are listening on a public interface (eg, 0.0.0.0 so cross-server communication can happen). By making this configuration explicit, it should hopefully ensure the appropriate firewall/network rules get put in place to protect these services in a multi-server environment (but a default single-server environment won't be open if running on an unprotected network). This also aligns with the newer defaults in Elasticsearch 2 (https://www.elastic.co/guide/en/elasticsearch/reference/current/breaking_20_network_changes.html) and MongoDB's default rpm/deb package installations (https://jira.mongodb.org/browse/SERVER-792). See #287
- Loading branch information
Showing
3 changed files
with
64 additions
and
6 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters