By using AWS re:Post, you agree to the AWS re:Post Terms of Use
AWS re:Postre:Post

DocumentDB connection timeout after restoring snapshot to new VPC

0

I had VPC("nonshima") and documentDB("nonshima-db-int") which had about 10GB of data in it. I created a new VPC("nonshima-124") with same configuration of nonshima including route-table. I wanted to move my nonshima-db-int into nonshima-124, i realized that i can not once a DocumentDB cluster is created, the VPC cannot be changed. Source: 2nd answer provided by Mihai A

So i created a manual snapshot and restored it with nonshima-124 VPC. Now my applications are not able to connect to the new cluster that was created using the snapshot

Note: security group and subnet group are prefect for newly created cluster using snapshot.

I also noticed that if i create a new cluster in nonshima-124, my applications are able to connect.

Topics
Networking & Content DeliveryMigration & ModernizationDatabase
Tags
Amazon VPCAWS Database Migration ServiceAmazon DocumentDBDatabase
Language
English
rePost-User-3467093
asked 5 months ago326 views
1 Answer
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.

profile picture
EXPERT
Riku_Kobayashi
answered 5 months ago
  • rePost-User-3467093
    5 months ago

    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

  • Riku_Kobayashi EXPERT
    5 months ago

    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.

  • rePost-User-3467093
    5 months ago

    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

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions

Relevant content