[DOCS-62] Document how to secure your mongo servers (common best practices) Created: 06/Oct/11 Updated: 08/Jun/12 Resolved: 08/Jun/12 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Ryan Nitz | Assignee: | Sam Kleinman (Inactive) |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Days since reply: | 12 years, 19 weeks, 6 days ago | ||||||||
| Description |
|
We are finding/seeing more and more unsecured mongo instances in AWS and in private datacenters. Since we recommend using the server without auth, a lot of these databases are completely open to the public #scary As a result, this is causing problems with MMS. We are taking steps to work around this problem in MMS, but it is probably a good idea to write an article/post/wiki page about how to do this. It seems inane, but people are operating their databases with unsecured environments. Topics to cover: |