This website uses Cookies. Click Accept to agree to our website's cookie use as described in our Privacy Policy. Click Preferences to customize your cookie settings.
Hi. My database migration project is to import from an AWS RDS
Postgresql cluster to AlloyDB. I've connected the AWS and GCP VPCs using
a VPN well enough that I can reach both the AWS and GCP instances using
psql (or telnet hostname 5423, etc, etc.) ...
I've resolved the issue - the root cause was a AWS Security Group
filter. Its needs to be expanded to also allow the IP range(s) for the
Google "Private Services Access" in your GCP VPC. The route tables in
AWS and GCP were being updated automaticall...
I'd like to double-check something just as one step by itself.The last
two replies mentioned specifically a "DMS Connectivity Test". I used the
Connectivity Test which exists in the Network Intelligence service. Is
there a specific Database Migration...
Hello. Thanks for the help.To cover the parts in "1. Network
Accessibility" I could run telnet, traceroute etc. without issue. As I
was able to use the psql client that was already implied though. DNS is
also working well, even resolving the hostname...
