[DOCS-10155] Clarify Atlas VPC CIDR Block /21 Requirement Created: 20/Apr/17 Updated: 29/Oct/23 Resolved: 21/Apr/17 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | Atlas |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Luke Phillippi | Assignee: | Ravind Kumar (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: | |
| Days since reply: | 6 years, 42 weeks, 1 day ago |
| Description |
|
When peering VPCs with their Atlas VPC, users are able to modify their group's Atlas CIDR block if there are not any active clusters within their Atlas group. However, it's a strict requirement that the Atlas CIDR block end with /21. If users attempt to modify the Atlas CIDR block to end in anything other than /21, they will receive the following error:
It may be important to include this requirement within the Set up VPC Peering Connection and VPC API sections of the Atlas documentation. |
| Comments |
| Comment by Ravind Kumar (Inactive) [ 25/Apr/17 ] |
|
Merged: https://github.com/10gen/cloud-docs/commit/7059789854b211b2352f5cf4b305e4311a89492e |
| Comment by Ravind Kumar (Inactive) [ 21/Apr/17 ] |
|
RFM pending final pass |