1 réponse
- Le plus récent
- Le plus de votes
- La plupart des commentaires
0
Hello.
Where is the application hosted?
Is it hosted within the same VPC as the newly restored DocumentDB?
If the VPCs are different, you will need to connect with VPC peering and configure routing.
https://docs.aws.amazon.com/vpc/latest/peering/what-is-vpc-peering.html
If the VPCs are the same, there seems to be a problem with the settings around the security group.
Contenus pertinents
- demandé il y a 8 mois
- demandé il y a un an
- Réponse acceptéedemandé il y a 2 ans
- AWS OFFICIELA mis à jour il y a 9 mois
- Pourquoi le plug-in CNI de mon VPC ne parvient-il pas à atteindre le serveur d'API dans Amazon EKS ?AWS OFFICIELA mis à jour il y a 2 ans
- AWS OFFICIELA mis à jour il y a un an
the newly restored DocumentDB is in new VPC. as the newly restored DocumentDB is created using snapshot of old db, do we still new VPC peering?
just to be clear: old DB(in old VPC) snapshot is used to create new cluster in new VPC
In which VPC is the application accessing DocumentDB hosted? If it is not hosted within a new VPC, settings such as VPC peering are required.
yes the applications are within the new VPC. i also tried to create a EC2 instance in the new VPC(configured security group as well) and connect to DocumentDB, and i still get connection timeout. this concluded me that not just my application but any of the servers are unable to connect to the DocumentDB cluster created via the restored snapshot