PrivateSrv connection string not present

According to mongodb atlas cluster api, the get request should return connection strings with the following property “privateSrv”, if : Atlas returns this parameter only if you created a network peering connection to this cluster.

I have created network peering between my AWS vpc and atlas mongodb created network container (VPC) On both sides the vpc connection shows Active/Available state. I have also upgraded to M10 dedicated cluster.

However the get request only returns “standard” and “standardSrv” connection strings in “connectionStrings” object.

Is there anything else I can do (any step I have forgotten to do)? Is there a way to make cluster aware of the peering? Without privateSrv connectionString the whole peering is useless.


Hi @Simon_Obetko.

AWS Atlas clusters use the same DNS for private and standard connections.

With GCP and Azure it is different.

Best regards,


Perfect, tested this and works well even when I am using lambda joined into VPC (meaning without internet connection). Pretty nice solution. I was afraid that the DNS record would not be resolvable from lambda joined in VPC, but it seems to be working well.
Thanks for clearing things out.


This topic was automatically closed 5 days after the last reply. New replies are no longer allowed.