A connection profile can be created on its own, or in the context of creating a specific migration job. Either way, all connection profiles are available for review and modification on the connection profiles page, and can be reused across migration jobs.
Creating a connection profile on its own is meaningful in the event that the person who has the source access information is not the same person who will be creating the migration, or to enable reuse of the source connection profile definition in multiple migration jobs (such as POC or test migration job, followed by a production migration job).
Create a new connection profile
Go to the Database Migration Service Connection profiles page in the Google Cloud console.
Go to the Database Migration Service Connection Profiles Page
A list of any existing connection profiles is displayed, and you can create a new connection profile by clicking Create Connection Profile.
Supply the required info for a connection profile:
Name: The friendly name of the connection profile. This will be used in the connection profile list as well as when an existing connection profile is selected in the creation of a migration job.
ID: the unique instance ID of the source. This must be a unique string, comprised of lower-case letters, digits, and hyphens. There's no need to include the project ID; this is done automatically where appropriate (for example, in the log files).
Database engine: The type of database of the source.
The version of the database is automatically detected when used by a migration job.
Connectivity information:
For self-hosted sources, provide the hostname and port:
Hostname (IP or domain) of the source.
If the source is hosted in Google's Cloud or if reverse SSH tunnel is used to connect the destination to the source, specify the source's PRIVATE (internal) IP here. For other connectivity methods, provide the PUBLIC IP.
MySQL limits the hostname to 60 characters. Amazon RDS databases hostnames will typically be longer than 60 characters. If this is the case for the database you are migrating, you will need to configure a DNS redirect to create a CNAME record that associates your domain name with the domain name of your RDS DB instance. You can read more about setting up DNS CNAME in the Cloud DNS documentation or in the AWS Route53 documentation.
Port to access the host (MySQL default is 3306, PostgreSQL default is 5432).
For Cloud SQL sources, select the Cloud SQL instance from the dropdown list.
Username and password of the source.
(PostgreSQL only) Select the database to replicate.
(Optional) If the connection will be made over a public network (by using IP whitelisting), we recommend using SSL/TLS encryption for the connection between the data source and destination. There are two options for the SSL/TLS configuration:
Server-only authentication
When the Cloud SQL instance connects to the source, the instance authenticates the source, ensuring that the instance is connecting to the correct host and preventing man-in-the-middle attacks. The source does not authenticate the instance.
Server-client authentication
When the instance connects to the source, the instance authenticates the source and the source authenticates the instance.
For more information about setting up SSL, see SSL/TLS configuration.
Create the connection profile. The page will navigate to the connection profiles list which displays the newly created connection profile.