[DOCS-10613] Fix VPC Peering Setup Step 6 to match AWS UI Created: 01/Aug/17  Updated: 29/Oct/23  Resolved: 03/Oct/18

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

Type: Bug Priority: Major - P3
Reporter: Henning Sprang Assignee: Robert Justice (Inactive)
Resolution: Fixed Votes: 0
Labels: atlas-vpc, collector-298ba4e7
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

AWS

Location: https://docs.atlas.mongodb.com/security-vpc-peering/
Referrer: https://www.google.de/
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3071.115 Safari/537.36
Screen Resolution: 1440 x 900


Attachments: PNG File AWS-UI-for-routes.png    
Issue Links:
Duplicate
is duplicated by DOCS-10723 Comment on: "atlas/security-vpc-peering" Closed
Participants:
Days since reply: 5 years, 20 weeks, 2 days ago
Epic Link: DOCSP-3142
Story Points: 0.1

 Description   

In the Rules tab of "Routing tables" page there is no "add rule" button. It only appears after first pressing "edit".

Then, I have not only to add the ATlas CIDR Block, but also the peering connection ID.



 Comments   
Comment by Anthony Sansone (Inactive) [ 24/Sep/18 ]

Change Step 6 to match AWS Route Table UI.

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