By using AWS re:Post, you agree to the AWS re:Post Terms of Use
AWS re:Postre:Post

I am encountering the 'connect ETIMEDOUT Private IP:27017' error when attempting to connect to DocumentDB using MongoDB Compass.

0

I have deployed a DocumentDB cluster on AWS, utilizing the default VPC. The VPC Network ACL has been configured to allow 0.0.0.0 access, and the security groups are set to permit all traffic, including 0.0.0.0 access. The cluster is in the 'available' stage and is healthy. I have verified that my credentials are correct. However, I am still encountering the 'connect ETIMEDOUT Private IP:27017' error. I would appreciate assistance in resolving this issue.

  • Kyle_B SUPPORT ENGINEER
    5 months ago

    Where are you attempting to connect from? From within the VPC or outside of the VPC?

    If you are connecting from outside the VPC, do you have a bastion in place? [1]

    [1] Outside the VPC: https://docs.aws.amazon.com/documentdb/latest/developerguide/connect-from-outside-a-vpc.html

  • KARTHIK
    5 months ago

    Let's consider a scenario where I am within an internal Virtual Private Cloud (VPC). In this case, is it necessary to have a bastion server? Additionally, if I launch DocumentDB, can I connect directly without requiring a bastion server?

Topics
Database
Tags
Amazon DocumentDB
Language
English
KARTHIK
asked 5 months ago82 views
No Answers

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions

Relevant content