[DOCS-12852] Changes required in the VPC peering documentation Created: 04/Jul/19 Updated: 05/Jul/19 Resolved: 05/Jul/19 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | Atlas |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Nikhil Singh | Assignee: | Anthony Sansone (Inactive) |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: | |
| Days since reply: | 4 years, 31 weeks, 5 days ago |
| Epic Link: | DOCSP-3142 |
| Story Points: | 0.1 |
| Description |
Description---------------------------- Original DescriptionIn the below documentation it used to be mentioned that AWS doesn't support VPC Peering for M0, M2 and M5 instances. https://docs.atlas.mongodb.com/security-vpc-peering/ But this text has been removed now, and it creates confusion that VPC Peering is possible for the M0, M2 and M5 clusters.
Please verify once and make the changes in the documentation so that the customers and the CTSAs are much clear on this. DescriptionI and sergio.castro did some testing on VPC today and reached the conclusion that:
MVP (work and date?)Resources (e.g. Scope Docs, Invision)Scope of changesImpact to Other Docs |
| Comments |
| Comment by Anthony Sansone (Inactive) [ 05/Jul/19 ] |
|
This is a duplicate of DOCSP-6063. Please refer to that ticket for further updates. |