- Newest
- Most votes
- Most comments
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.
Relevant content
- asked 2 years ago
- asked 9 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 7 months ago
- AWS OFFICIALUpdated 2 years ago
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.