1 Answer
- Newest
- Most votes
- Most comments
0
You could write your connection code in the following manner to fix the issue: documentdb_write_uri = 'mongodb://yourdocumentdbcluster.amazonaws.com:27017' write_documentdb_options = { "uri": documentdb_write_uri, "database": "yourdbname", "collection": "yourcollectionname", "username": "###", "password": "###" }
You can follow the below mentioned reference document for further information : https://docs.aws.amazon.com/glue/latest/dg/aws-glue-programming-etl-connect.html#aws-glue-programming-etl-connect-documentdb
answered 10 months ago
Relevant content
- Accepted Answerasked a year ago
- Accepted Answerasked a year ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 6 months ago
- AWS OFFICIALUpdated a year ago
Even I have the same problem. I believe it has to do with whether TLS is enabled or not for your mongoDB cluster. To determine if TLS is enabled or not , see https://docs.aws.amazon.com/documentdb/latest/developerguide/connect_programmatically.html#connect_programmatically-tls_enabled. My added question to yours is, how to pass the public key for Amazon DocumentDB named rds-combined-ca-bundle.pem so I can use create_dynamic_frame_from_catalog method. Is it at all possible? FYI, I am able to connect to my MongoDB Cluster (v 4.0) using create_dynamic_frame_from_options function, but then the credentials and other parameters need to be passed, and the benefit of using the catalog is lost.