Allow multiple VPC CIDR ranges in Peering connection
Allow multiple VPC CIDR for a single Peering connection from Atlas to AWS.
Our AWS account has two CIDR ranges for a single VPC. Atlas peering connection only allows connection to a single CIDR range.
Today, I need to create a separate private link connection to be able to connect to the second CIDR range.
Radhika KV
shared this idea
-
Pankaj
commented
wonder why is it not there when you have such a complete solution in place supporting multiple cloud provider(s)
-
Paul
commented
This is a critical missing feature for using Atlas with modern AWS VPC's. Allowing multiple CIDR's in as single VPC is now a fundamental part of AWS VPC architecture. Not being able to address multiple ranges from Atlas makes it impossible for us to make use of this feature, which we need to be able to support enough IP's in our VPC's for all the resources they contain.
-
Michael Gerlach
commented
I don't see how you end up with multiple CIDRs.
Every VPC has a single main CIDR block. Even if you have multiple subnets distributed across availability zones, you still have a single CIDR block assigned to your VPC.
-
Manoj
commented
This is absolutely critical for our situation at the State of Utah account. We hope that it's implemented as quickly as possible. Thanks.
-
Jean
commented
Kindly request that your development team prioritize the implementation of the feature allowing support for multiple VPC CIDR ranges. This enhancement would greatly streamline our network architecture and improve the efficiency of our operations.
Please help! -
Ivan
commented
It is common to have a secondary CIDR in a VPC, atlas should consider to make it possible as soon as quickly.
-
Andy
commented
I really need this feature for our secondary CIDR connection.