Why place DMS replication instance in target VPC instead of source VPC

0

Hi guys, I'm working on a project that requires migrate the database cross region. A source VPC in the US West (Oregon) region, and a target VPC in the US East (Virginia) region. I read some articles about DMS and I see that AWS recommend placing the DMS replication instance in target VPC instead of source VPC. I don't know the reason why should we place the DMS replication instance in target VPC. If you know, please share with me. Thanks

Steven
已提問 1 年前檢視次數 1146 次
1 個回答
2

Amazon Database Migration Service (DMS) replication instances are typically placed in the target VPC rather than the source VPC for several reasons:

Security: By placing the replication instance in the target VPC, you can control access to the replication instance and limit the exposure of your source database to the public internet. Performance: Placing the replication instance in the target VPC reduces the distance that the data must travel to reach the target database. This can improve the overall replication performance and reduce latency. Connectivity: The target VPC is typically where your applications and target database reside. Placing the replication instance in the same VPC as the target database ensures that the replication traffic stays within the VPC and does not need to traverse multiple VPCs or over the public internet, which can improve the reliability of the replication process.

And to add on this, you may have multiple source DB for a replication instance.

已回答 1 年前
  • Hi, Thanks for your answer. However, I think this answer still not clear. About the performance and connectivity: placing the replication instance in target VPC will increase distance from DMS replication instance to source Database. Moreover, if we use VPC Peering, the traffic will go through AWS backbone network, not Internet.

您尚未登入。 登入 去張貼答案。

一個好的回答可以清楚地回答問題並提供建設性的意見回饋,同時有助於提問者的專業成長。

回答問題指南