Connecting DMS to our local source endpoint

Question

I'm sure the answer to this is trivial. We have an on premise source Oracle 11 DB that I'd like to migrate to RDS Aurora. I can convert the schema without a problem using SCT. But to move the data it seems that I need a DMS instance. That requires that I create a source endpoint for my Oracle instance. But given that we don't have direct connect, how will the DMS service ever see my OnPremise Oracle source which is located in our private network?

Answer

Please take a look at the AWS documentation "Setting up a network for a replication instance" - https://docs.aws.amazon.com/dms/latest/userguide/CHAP_ReplicationInstance.VPC.html

These two sections talk about how you can connect your on-prem database to the DMS instance

1) Configuration for a network to a VPC using AWS Direct Connect or a VPN

2) Configuration for a network to a VPC using the internet

Answer

You can use use Client VPN 
https://docs.aws.amazon.com/vpn/latest/clientvpn-admin/cvpn-working-endpoints.html

Make sure the local firewall are open for the dms replication to all allow connections.

Connecting DMS to our local source endpoint

Relevant questions

Connecting DMS to our local source endpoint

DMS Migration MongoDB source and RDS Postgres as destination

Reason for providing the 'source-dbi-resource-id' parameter in the AWS RDS CLI command 'restore-db-instance-to-point-in-time'?

S3 Integration Oracle RDS and DMS

How to migrate DB on premise Oracle to Microsoft SQL Server DB in AWS. We see SCT will not allow MS SQL Server as Target when source is Oracle. Looking for tools like SCT to move Schema from Oracle.

Migrate MySQL 8 to Aurora MySQL 8

aurora serverless as source and destination for DMS

RDS Postgresql migrate to Aurora Postgresql. Not showing "Aurora read replica" & "Migrate snapshot" options.

Do source filters speed up DMS from AWS RDS to S3?

DMS: From on-premise to RDS + NAT Gateway - Best Practices