Description

----------------------------

Original Description

In 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.
----------------------------

Description

I and sergio.castro did some testing on VPC today and reached the conclusion that:

1. VPC peering cannot be done for the M0, M2 and M5 clusters.
2. VPC peering can be setup in a project which has M0, M2 and M5 clusters along with other clusters of size M10 and above. But, the VPC Peering is not applicable on M0, M2 and M5 and that the public IP addresses of the client will have to be whitelisted to access M0, M2 and M5 clusters.

MVP (work and date?)

Resources (e.g. Scope Docs, Invision)

Scope of changes

Impact to Other Docs