Allow to Peer with VPC's that doesn't follow Private Networks Ranges
Allow to Peer with VPC's that doesn't follow Private Networks Ranges
Currently I have one infrastructure based on a VPC with the CIDR range of 30.0.0.0/16, and I'm unable to make it safe with VPC peering because of the restrictions on this.
https://docs.atlas.mongodb.com/security-vpc-peering/
I thinl that allowing to peer with any AWS VPC's that do not overlap would be nice, as it is difficult to change the VPC when you have a running infrastructure, just to integrate safely with MongoDB Atlas
![](https://secure.gravatar.com/avatar/9aa94ce0472dd5ef427afe7e920dc158?size=40&default=https%3A%2F%2Fassets.uvcdn.com%2Fpkg%2Fadmin%2Ficons%2Fuser_70-6bcf9e08938533adb9bac95c3e487cb2a6d4a32f890ca6fdc82e3072e0ea0368.png)
-
Hi Daniel,
I'm sorry you're running into this, but it's a nuanced one: peering with public ranges means giving up internet access which could potentially alter the manageability of the Atlas-side cluster and this is not something we can consider.
If you're using public ranges in a private VPC, I strongly suggest that you either move to a private range and if that's not palatable, consider using either selective public IP Whitelisting or Atlas Private Endpoints (powered by AWS PrivateLink).
Cheers
-Andrew