You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, afraid I can't connect to AWS DocumentDB.
Since SSH Tunnel is not available, I use ssh -L and run locally.
Problem is - the AWS CA cert will consider the hostname invalid, and AllowInvalidHostnames option cannot be set, so connection will timeout.
(note: Could be overcome by running inside AWS for now)
Describe the solution you'd like
Optimally, allow selecting SSL options in UI -
tlsAllowInvalidHostnames
tlAllowInvalidCertificates (will probably be useful to users)
Alternatively or additionally - allow users to set the MongoDB Connection String: mongodb://<user>:<Password>@docdb.us-east-1.docdb.amazonaws.com:27017/?tls=true&tlsCAFile=<CAcert>&tlsAllowInvalidHostname=true
The Connection String workaround is common in tools that don't allow setting the SSL, and also allows setting other MongoDB options (i.e readSecondary and such).
Cheers!
Additional context
No response
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem?
Hi, afraid I can't connect to AWS DocumentDB.
Since SSH Tunnel is not available, I use
ssh -L
and run locally.Problem is - the AWS CA cert will consider the hostname invalid, and
AllowInvalidHostnames
option cannot be set, so connection will timeout.(note: Could be overcome by running inside AWS for now)
Describe the solution you'd like
Optimally, allow selecting SSL options in UI -
Alternatively or additionally - allow users to set the MongoDB Connection String:
mongodb://<user>:<Password>@docdb.us-east-1.docdb.amazonaws.com:27017/?tls=true&tlsCAFile=<CAcert>&tlsAllowInvalidHostname=true
The Connection String workaround is common in tools that don't allow setting the SSL, and also allows setting other MongoDB options (i.e readSecondary and such).
Cheers!
Additional context
No response
The text was updated successfully, but these errors were encountered: