2 Respuestas
- Más nuevo
- Más votos
- Más comentarios
0
Had the same issue.. not sure if this breaks with the change in cert to 2019 .. anyway I had to get around this with a code change and removal of the ssl cert location from the connection string.
connect(uri, {useNewUrlParser: true,
useFindAndModify: false,
sslCA: [fs.readFileSync("rds-combined-ca-bundle.pem")]}, (err: any)
Edited by: zshack on Jan 6, 2020 8:29 AM
respondido hace 4 años
0
zshack, thanks for the info. My current work-around was to turn off ssl for the instance and remove cert from connect string. Not too concerned about it at the moment as this project is still in development and also since DocumentDB is only accessible from within the AWS VPC I think the risk is minimal.
respondido hace 4 años
Contenido relevante
- OFICIAL DE AWSActualizada hace 8 meses
- OFICIAL DE AWSActualizada hace 3 años
- OFICIAL DE AWSActualizada hace 3 años