1 Answer
- Newest
- Most votes
- Most comments
0
This document may help you debug the issue - https://aws.amazon.com/premiumsupport/knowledge-center/documentdb-cannot-connect/
In particular, the first thing to check would be that the security group for DocumentDB allows incoming traffic from the security group of the EC2 machine on the documentDB port, which by default is 27017
In my case it dint work though Port 27017, was configured with Security group of EC2 instance in the Inbound rule of the Regional Cluster.
Relevant content
- Accepted Answer
asked 10 months ago - asked 4 years ago
- Accepted Answerasked a year ago
AWS OFFICIALUpdated 7 months ago- AWS OFFICIALUpdated 8 months ago
- AWS OFFICIALUpdated 8 months ago
- AWS OFFICIALUpdated 8 months ago
You can choose between two options. The first option is to create a single security group and allow all traffic (0.0.0.0) to attach both resources. The second option involves using two security groups: one for DocumentDB and another for the EC2 instance. For the DocumentDB security group, enable port 27017 with custom TCP, specifying the source as the EC2 security group name. Additionally, for the EC2 instance security group, allow SSH access by specifying the SSH port along with either your specific IP or your organization's IP.