[DOCS-4835] Update AWS Subnet requirement Created: 17/Feb/15 Updated: 16/Mar/15 Resolved: 03/Mar/15 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | Cloud Manager |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Eric Daniels (Inactive) | Assignee: | Bob Grabar |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Participants: | |||||
| Days since reply: | 9 years, 1 day ago | ||||
| Description |
|
On https://docs.mms.mongodb.com/tutorial/configure-aws-settings/#vpc we require that the user make their subnet in their vpc have Enable auto-assign Public IP checked. As of v20150217 we no longer have this requirement. We should remove that language but notify the user that we will give instances we create on any subnet a public IP. |