[DOCS-10770] Update Setup VPC Peering Connection (Atlas) with I.P Address Ranges Created: 07/Sep/17  Updated: 29/Oct/23  Resolved: 06/Feb/18

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

Type: Task Priority: Major - P3
Reporter: Robert Justice (Inactive) Assignee: Robert Justice (Inactive)
Resolution: Fixed Votes: 0
Labels: atlas-vpc, triage
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:
Days since reply: 6 years, 1 week, 1 day ago
Epic Link: DOCSP-1743
Story Points: 0.2

 Description   

Fell out of DOCS-10381. Procedure at https://docs.atlas.mongodb.com/security-vpc-peering/ has the following errors and omission:

  • Step 3 suggests illegal VPC cider blocks for the VPC ID. AWS will not accept 10.0.0.0/8 and
    172.16.0.0/12. /16 is the lowest acceptable prefix.
  • Separately, step 6 neglects to inform the user that they must also associate the peering connection id from Atlas with the Atlas Cidr id.


 Comments   
Comment by Robert Justice (Inactive) [ 06/Feb/18 ]

Kay merged!

Comment by Robert Justice (Inactive) [ 06/Feb/18 ]

Fixed typo.

Comment by Robert Justice (Inactive) [ 06/Feb/18 ]

Kay found a typo.

Comment by Ravind Kumar (Inactive) [ 07/Sep/17 ]

The second point is being fixed, but I can resolve the first as a part of ongoing work. Thanks!

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