[DOCS-15951] [Atlas] Improvement for AWS section on setting up a network peering connection documentation Created: 08/Mar/23 Updated: 29/Oct/23 Resolved: 21/Mar/23 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | Atlas |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Anthony Retana | Assignee: | Carrie Kim |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | CTSA | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Participants: | |
| Days since reply: | 48 weeks ago |
| Story Points: | 2 |
| Description |
DescriptionAfter some customer scenarios w/ confusion, it seems that customers have confused point 4.b in the Set up a Network Peering Connection docs and faced issues with setting the right table. Some customers may need to use the route table for the VPC or in some cases customers have route tables per subnet.
Scope of changeshttps://www.mongodb.com/docs/atlas/security-vpc-peering/ Instead of step 4.b reading: It might bring more clarity to this section by adding this: Impact to Other DocsNone |