Allow multiple private endpoints (Private Link Service) per region in multi-region cluster
Some situations require multiple private endpoints (using the Private Link service) to be created per region. This is not currently supported for multi-region replica sets.
One scenario is especially for when there is a shared VPC/VNet for initial transit from on-prem to cloud plus another VPC/VNet for an application. Both of those VPC/VNets would want a Private Endpoint to connect directly to the Atlas cluster. Even if it is possible (sometimes is not), routing traffic via multiple VPC/VNets would mean 3 hops to Atlas from on-prem
Matt
shared this idea
-
Benjamin
commented
Critical customer needs this multiple unpeered private endpoints, and currently the work around requires introducing a single shard - which is confusing and expensive. It would be best if Atlas support multiple unpeered private endpoints for multi-region clusters without having to shard, or toggle Regionalized Private Endpoints for Multi-Region Sharded Clusters
-
Balaji Prasad
commented
Hi Team,
We are waiting for this feature to be enabled for few of the below reason:
If multi-cloud environments need to establish private endpoints to the replica sets, with the current architecture all the connections need to go through one single Private endpoint which means huge traffic congestion and multiple network hops. This is contributing to huge amounts of latency and if I have to tell in terms of query latencies, each query is taking 10 times more time than a direct connection through Private Endpoint.
-
Aram
commented
This is very critical to us as well.