연결 프로필을 단독으로 만들거나 특정 마이그레이션 작업을 만드는 맥락에서 만들 수 있습니다. 어느 쪽이든 모든 연결 프로필은 연결 프로필 페이지에서 검토 및 수정할 수 있으며 마이그레이션 작업 전반에서 재사용할 수 있습니다.
소스 액세스 정보가 있는 사용자가 마이그레이션 작업을 만드는 사용자가 아닌 경우 소스 연결 프로필을 직접 만드는 것이 유용합니다. 여러 마이그레이션 작업에서 소스 연결 프로필 정의를 재사용할 수도 있습니다. 여러 이전에 동일한 프로필을 사용하는 경우 소스 데이터베이스의 max_replication_slots 매개변수를 업데이트하여 만드는 복제본 수를 고려해야 합니다.
연결 프로필 이름을 입력합니다. 이 이름은 연결 프로필 목록과 마이그레이션 작업 생성 시 기존 연결 프로필을 선택할 때 사용됩니다.
자동 생성된 연결 프로필 ID를 그대로 둡니다.
호스트 이름 또는 IP 주소를 입력합니다.
소스 데이터베이스가 Google Cloud 에 호스팅되거나 역방향 SSH 터널을 사용하여 대상 데이터베이스를 소스 데이터베이스에 연결하는 경우 소스 데이터베이스의 비공개 (내부) IP 주소를 지정합니다. Cloud SQL 대상에서 이 주소에 액세스할 수 있습니다. 자세한 내용은 VPC 피어링을 사용하여 연결 구성을 참고하세요.
호스트에 액세스하는 데 사용되는 포트를 입력합니다. 기본 PostgreSQL 포트는 5432입니다.
소스 데이터베이스의 사용자 이름과 비밀번호를 입력합니다. 사용자에게 이러한 권한이 있어야 합니다.
페이지의 연결 프로필 리전 섹션에서 연결 프로필을 저장할 리전을 선택합니다.
선택사항: 공개 네트워크(IP 허용 목록 사용)를 통해 연결하는 경우 소스 데이터베이스와 대상 데이터베이스 간의 연결에 SSL/TLS 암호화를 사용하는 것이 좋습니다.
연결 보호 섹션의 암호화 유형 목록에서 다음 SSL/TLS 구성 옵션 중 하나를 선택할 수 있습니다.
없음: Cloud SQL 대상 인스턴스가 암호화 없이 소스 데이터베이스에 연결됩니다. 데이터베이스에 암호화된 연결이 필요한 경우 이 옵션을 사용하지 않는 것이 좋습니다.
기본: Cloud SQL 대상 인스턴스가 암호화로 소스 데이터베이스에 연결되지만 인증 기관 (CA)을 확인하지 않습니다.
TLS 인증: Cloud SQL 대상 인스턴스가 소스 데이터베이스에 연결되면 인스턴스가 소스를 인증하여 인스턴스가 올바른 호스트에 안전하게 연결되는지 확인합니다.
이렇게 하면 중간자 (PITM) 공격을 방지할 수 있습니다. TLS 인증의 경우 소스가 인스턴스를 인증하지 않습니다.
TLS 인증을 사용하려면 외부 서버의 인증서에 서명한 CA의 x509 PEM 인코딩 인증서를 제공해야 합니다.
[[["이해하기 쉬움","easyToUnderstand","thumb-up"],["문제가 해결됨","solvedMyProblem","thumb-up"],["기타","otherUp","thumb-up"]],[["이해하기 어려움","hardToUnderstand","thumb-down"],["잘못된 정보 또는 샘플 코드","incorrectInformationOrSampleCode","thumb-down"],["필요한 정보/샘플이 없음","missingTheInformationSamplesINeed","thumb-down"],["번역 문제","translationIssue","thumb-down"],["기타","otherDown","thumb-down"]],["최종 업데이트: 2025-08-18(UTC)"],[[["\u003cp\u003eConnection profiles can be created independently or during the setup of a migration job, and are reusable across multiple jobs, allowing for efficient management of database connections.\u003c/p\u003e\n"],["\u003cp\u003eWhen creating a source connection profile, you must specify details such as the profile role, database engine, connection name, ID, hostname or IP address, and the port, as well as the source database's username and password.\u003c/p\u003e\n"],["\u003cp\u003eThe choice of connection profile region does not affect which migration jobs can utilize the profile or the regions that can access the data but can impact the availability of the profile.\u003c/p\u003e\n"],["\u003cp\u003eSecure connections via SSL/TLS are recommended for public network connections and offer options including no encryption, basic encryption, TLS authentication, and mTLS authentication for enhanced security.\u003c/p\u003e\n"],["\u003cp\u003eDepending on the security level required, the setup may require the x509 PEM-encoded certificate of the Certificate Authority (CA), the client certificate, and the associated client key for secure source and destination authentications.\u003c/p\u003e\n"]]],[],null,["# Create a source connection profile\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\n[MySQL](/database-migration/docs/mysql/create-source-connection-profile \"View this page for the MySQL version of Database Migration Service.\") \\| PostgreSQL \\| [PostgreSQL to AlloyDB](/database-migration/docs/postgresql-to-alloydb/create-source-connection-profile \"View this page for the PostgreSQL to AlloyDB version of Database Migration Service.\")\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\nYou can create a connection profile on its own or in the context of creating a\nspecific migration job. Either way, all connection profiles are available for\nreview and modification on the Connection profiles page, and can be reused\nacross migration jobs.\n\nCreating a source connection profile on its own is useful if the\nperson who has the source access information is not the same person who creates\nthe migration job. You can also reuse a source connection profile\ndefinition in multiple migration jobs. If you use the same profile for multiple migrations, you need to update the `max_replication_slots` parameter\nin the source database to account for the number of replicas you're creating.\n| To see which source databases Database Migration Service supports, see [Supported source and destination databases](/database-migration/docs/postgres/migration-src-and-dest).\n\nTo create a source connection profile, follow these steps:\n\n1. Go to the [Connection profiles](https://console.cloud.google.com/dbmigration/connection-profiles) page in the Google Cloud Console.\n2. Click **Create profile**.\n3. On the **Create a connection profile** page, provide the following information required to connect to your source:\n 1. From the **Profile role** list, select **Source**.\n 2. From the **Database engine** list, select your source database engine.\n\n | If you select **Cloud SQL for PostgreSQL** from this list, then a **Cloud SQL instance** list appears. Select the Cloud SQL instance that you want to migrate.\n 3. Enter a **Connection profile name**. This is used in the connection profile list as well as when an existing connection profile is selected in the creation of a migration job.\n 4. Keep the auto-generated **Connection profile ID**.\n 5. Enter a **Hostname** or **IP address**.\n\n If the source database is hosted in Google Cloud or if a reverse SSH\n tunnel is used to connect the destination database to the source database,\n then specify the private (internal) IP address for the source database. This address will be accessible by the Cloud SQL destination. For more information, see [Configure connectivity using VPC peering](/database-migration/docs/postgres/configure-connectivity-vpc-peering).\n\n For other connectivity methods, such as [IP allowlist](/database-migration/docs/postgres/networking-methods), provide the public IP address.\n 6. Enter the **Port** that's used to access the host. The default PostgreSQL port is 5432.\n4. Enter a username and password for the source database. The user must have [these privileges](/database-migration/docs/postgres/configure-source-database).\n5. In the **Connection profile region** section of the page, select the region where you want to save the connection profile.\n\n | Connection profiles, like all resources, are saved in a region. Region selection doesn't impact which migration jobs can use them, or which regions can connect to the data location itself, but can impact availability in the case of regional downtime.\n6. Optional: If the connection is made over a public network\n (by using IP allowlists), then we recommend that you use [SSL/TLS](https://en.wikipedia.org/wiki/Transport_Layer_Security) encryption for the\n connection between the source and destination databases.\n\n In the **Secure your connection** section, from the **Encryption type** list, you can select one of the following SSL/TLS configuration options:\n - **None**: The Cloud SQL destination instance connects to the source database without encryption. We recommend that you don't use this option if your database requires encrypted connections.\n - **Basic** : The Cloud SQL destination instance connects to the source database with encryption but doesn't verify the certificate authority (CA). This option is the default for Microsoft Azure sources. Microsoft Azure sources [require that all client connections use SSL/TLS encryption](https://learn.microsoft.com/en-us/previous-versions/azure/mysql/single-server/concepts-security#information-protection-and-encryption). At minimum, Microsoft Azure connection profiles must use basic encryption. If you don't want to use encryption to connect to the source, set `require_secure_transport` to `off`. For more information about the `require_secure_transport` setting, see [Configure your source](/database-migration/docs/mysql/create-source-connection-profile).\n - **TLS** authentication: When the Cloud SQL destination instance\n connects to the source database, the instance authenticates the source,\n ensuring that the instance is connecting to the correct host securely.\n This prevents person-in-the-middle (PITM) attacks. For TLS authentication,\n the source doesn't authenticate the instance.\n\n To use TLS authentication, you must provide the\n x509 PEM-encoded certificate of the CA that\n signed the external server's certificate.\n | For more information about creating certificates and keys for your external server, see [Creating SSL and RSA Certificates and Keys using MySQL](https://dev.mysql.com/doc/refman/5.7/en/creating-ssl-rsa-files-using-mysql.html).\n - **mTLS** authentication: When the destination instance connects to the source, the instance authenticates the source and the source authenticates the instance.\n\n mTLS authentication provides the strongest security. However,\n if you don't want to provide the client certificate and private key when\n you create the Cloud SQL destination instance, you can still use\n TLS authentication.\n\n To use mTLS authentication, you must provide the following\n items when you create the destination connection profile:\n - The certificate of the CA that signed the source database server's certificate (the CA certificate).\n - The certificate used by the instance to authenticate against the source database server (the client certificate).\n - The private key associated with the client certificate (the client key).\n| For more information about creating certificates and keys for your source database server, see [Secure TCP/IP Connections with SSL](https://www.postgresql.org/docs/current/ssl-tcp.html).\n|\n| If you're having trouble uploading the key, then select the **Enter manually** option, and copy and paste the key into the text area.\n7. Click **Create** at the bottom of the page.\n\n The **Connection\n profiles** page appears, and the newly created connection profile is displayed."]]
