[DOCS-12699] [Atlas] Explain how to get info on Atlas hosts to improve Firewall Requirements Docs Created: 14/May/19  Updated: 29/Oct/23  Resolved: 08/Feb/20

Status: Closed
Project: Documentation
Component/s: Atlas
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Brian Leonard Assignee: Tahiya Chowdhury (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:
Days since reply: 4 years, 4 days ago
Epic Link: DOCSP-6053
Story Points: 3

 Description   

Description

The current documentation on Network and Firewall Requirements is very limited, consisting of:

"If you use a whitelist on your firewall for network ports, open ports 27015 to 27017 to TCP and UDP traffic on Atlas hosts. This grants your applications access to databases stored on Atlas."
 
 It would be helpful to include information on how to get information on the Atlas hosts, as well as how to support new cluster hosts. The Atlas Networking section of the Atlas Security FAQ contains some helpful information, such as: 

  1. If customers need to configure their application-side networks to accept Atlas traffic, we recommend using the Atlas API clusters-get-all method to retrieve mongoURI or the processes-get-all method to retrieve hostname results containing cluster hostnames (mongo-shard-00-00.mongodb.net, mongo-shard-00-01.mongodb.net etc). These hostname values can be parsed and the IPs programmatically fed into customers' app-tier orchestration automation, including pushing firewall updates.

 

Scope of changes

Impact to Other Docs

MVP (Work and Date)

Resources (Scope or Design Docs, Invision, etc.)



 Comments   
Comment by Anthony Sansone (Inactive) [ 08/Feb/20 ]

Issue was merged in June 2019.

Comment by Tahiya Chowdhury (Inactive) [ 19/Jun/19 ]

https://github.com/10gen/cloud-docs/pull/861

Comment by Tahiya Chowdhury (Inactive) [ 17/Jun/19 ]

https://github.com/10gen/cloud-docs/pull/861

Generated at Thu Feb 08 08:05:53 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.