Connecting MongoDB Atlas to Kubernetes EKS Cluster on AWS

Question

I'm trying to setup an VPC Peering from my MongoDB Atlas Cluster to my Kubernetes EKS Cluster on AWS. The Peering is established successfully but i get no connection to the cluster on my pod's.

The peering is setup.

The default entry for the whitelist ist added as well. Once the connection works i will replace it with a security Group.

The peering on AWS is accepted and "DNS resolution from requester VPC to private IP" is enabled.

The route as been added to the Public Route Table of the K8S Cluster.

When i connect to a pod and try to establish a connection with the following command:

# mongo "mongodb://x.mongodb.net:27017,y.mongodb.net:27017,z.mongodb.net:27017/test?replicaSet=Cluster0-shard-0" --ssl --authenticationDatabase admin --username JackBauer

I get "CONNECT_ERROR" for every endpoint.

What am I missing?

NOTE: I've just created a new paid cluster and the VPC is working perfectly. Might this feature be limited to paid clusters only?

Adding --verbose may give you some more info on what is the reason of the connection error — esboych
– esboych, Commented Aug 26, 2019 at 8:00
@esboych this is an output with --verbose: NETWORK [thread1] creating new connection to:x.mongodb.net:27017 NETWORK [thread1] connected to server x.mongodb.net:27017 (108.x.y.z) NETWORK [thread1] SocketException: remote: (NONE):0 error: 9001 socket exception [CONNECT_ERROR] [thread1] User Assertion: 6:network error while attempting to run command 'isMaster' on host 'x.mongodb.net:27017' — Thomas Spycher
– Thomas Spycher, Commented Aug 26, 2019 at 9:23
@thomas-spycher your case might look like an ssl issue. The connected to server x.mongodb.net:27017 means you have connectivity on the network level. To clarify further you may run nc -v x.mongodb.net 27017 in advance. If you'll got something like x.mongodb.net (108.x.y.z) 27017 (?) open then you do have a connection at least on the network level. So as a next step you may check ssl-related stuff like key/cert files or so. — esboych
– esboych, Commented Aug 26, 2019 at 11:51

Thomas Spycher · Accepted Answer · 2019-08-26 14:42:28Z

3

Well... as the documentation states:

You cannot configure Set up a Network Peering Connection on M0 Free Tier or M2/M5 shared clusters.

Peering is not working on shared Cluster. Which makes, after i think about it, totally sense.

answered Aug 26, 2019 at 14:42

Thomas Spycher

97615 silver badges34 bronze badges

Sign up to request clarification or add additional context in comments.

1 Comment

esboych Over a year ago

Ohh ok then it's about to be clear now. Btw you may consider DocumentDB of AWS which advertised as Mongo API-compatible and probably will have less trouble to connect from private IPs.

Collectives™ on Stack Overflow

Connecting MongoDB Atlas to Kubernetes EKS Cluster on AWS

1 Answer 1

1 Comment

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

1 Comment

Your Answer

Sign up or log in

Post as a guest

Related