Anda dapat membuat profil koneksi sendiri atau dalam konteks membuat
tugas migrasi tertentu. Apa pun yang Anda pilih, semua profil koneksi tersedia untuk
peninjauan dan perubahan di halaman Profil koneksi, dan dapat digunakan kembali
di berbagai tugas migrasi.
Membuat profil koneksi sumber sendiri berguna jika
orang yang memiliki informasi akses sumber bukan orang yang sama dengan yang membuat
tugas migrasi. Anda juga dapat menggunakan kembali definisi profil koneksi sumber
dalam beberapa tugas migrasi. Jika menggunakan profil yang sama untuk beberapa migrasi, Anda perlu memperbarui parameter max_replication_slots
di database sumber untuk memperhitungkan jumlah replika yang Anda buat.
Untuk membuat profil koneksi sumber, ikuti langkah-langkah berikut:
Di halaman Buat profil koneksi, berikan informasi berikut yang diperlukan untuk terhubung ke sumber Anda:
Dari daftar Profile role, pilih Source.
Dari daftar Mesin database, pilih mesin database sumber Anda.
Masukkan Nama profil koneksi. Ini digunakan
dalam daftar profil koneksi serta saat profil koneksi
yang ada dipilih dalam pembuatan tugas migrasi.
Simpan ID profil koneksi yang dibuat secara otomatis.
Masukkan Nama host atau Alamat IP.
Jika database sumber dihosting di Google Cloud atau jika tunnel SSH terbalik
digunakan untuk menghubungkan database tujuan ke database sumber,
tentukan alamat IP pribadi (internal) untuk database sumber. Alamat ini akan dapat diakses oleh tujuan Cloud SQL. Untuk mengetahui informasi selengkapnya, lihat Mengonfigurasi konektivitas menggunakan peering VPC.
Masukkan Port yang digunakan untuk mengakses host. Port PostgreSQL default adalah 5432.
Masukkan nama pengguna dan sandi untuk database sumber. Pengguna harus memiliki hak istimewa ini.
Di bagian Connection profile region pada halaman, pilih region tempat Anda ingin menyimpan profil koneksi.
Opsional: Jika koneksi dilakukan melalui jaringan publik (dengan menggunakan daftar IP yang diizinkan), sebaiknya gunakan enkripsi SSL/TLS untuk koneksi antara database sumber dan tujuan.
Di bagian Amankan koneksi Anda, dari daftar Jenis enkripsi, Anda dapat memilih salah satu opsi konfigurasi SSL/TLS berikut:
Tidak ada: Instance tujuan Cloud SQL terhubung ke database sumber tanpa enkripsi. Sebaiknya jangan gunakan opsi ini jika database Anda memerlukan koneksi terenkripsi.
Dasar: Instance tujuan Cloud SQL terhubung ke database sumber dengan enkripsi, tetapi tidak memverifikasi Certificate Authority (CA).
Autentikasi TLS: Saat instance tujuan Cloud SQL
terhubung ke database sumber, instance akan mengautentikasi sumber,
memastikan bahwa instance terhubung ke host yang benar dengan aman.
Tindakan ini mencegah serangan person-in-the-middle (PITM). Untuk autentikasi TLS,
sumber tidak mengautentikasi instance.
Untuk menggunakan autentikasi TLS, Anda harus memberikan
sertifikat berenkode PEM x509 dari CA yang
menandatangani sertifikat server eksternal.
Autentikasi mTLS: Saat instance tujuan terhubung ke
sumber, instance akan mengautentikasi sumber dan sumber
akan mengautentikasi instance.
Autentikasi mTLS memberikan keamanan terkuat. Namun,
jika tidak ingin memberikan sertifikat klien dan kunci pribadi saat
membuat instance tujuan Cloud SQL, Anda masih dapat menggunakan
autentikasi TLS.
Untuk menggunakan autentikasi mTLS, Anda harus memberikan item berikut saat membuat profil koneksi tujuan:
Sertifikat CA yang menandatangani sertifikat server database sumber (sertifikat CA).
Sertifikat yang digunakan oleh instance untuk melakukan autentikasi terhadap server database sumber (sertifikat klien).
Kunci pribadi yang terkait dengan sertifikat klien (kunci klien).
Klik Create di bagian bawah halaman.
Halaman Profil koneksi akan muncul, dan profil koneksi yang baru dibuat akan ditampilkan.
[[["Mudah dipahami","easyToUnderstand","thumb-up"],["Memecahkan masalah saya","solvedMyProblem","thumb-up"],["Lainnya","otherUp","thumb-up"]],[["Sulit dipahami","hardToUnderstand","thumb-down"],["Informasi atau kode contoh salah","incorrectInformationOrSampleCode","thumb-down"],["Informasi/contoh yang saya butuhkan tidak ada","missingTheInformationSamplesINeed","thumb-down"],["Masalah terjemahan","translationIssue","thumb-down"],["Lainnya","otherDown","thumb-down"]],["Terakhir diperbarui pada 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."]]
