[[["容易理解","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-09-05 (世界標準時間)。"],[],[],null,["# Use SSL/TLS certificates to encrypt network connections\n\nEvery connection Database Migration Service makes to your source database\ncan be configured to use Secure Socket Layer/Transport Security Layer (SSL/TLS) encryption.\nThis page provides an overview of available SSL/TLS encryption variants and the steps\nrequired to use them for your migration job.\n\nSSL/TLS is mainly recommended for connections created over public\nnetworks where you need to expose a public IP address and port for your database.\nRegardless of which network connectivity method you use, your scenario might\nrequire that you use additional encryption.\n\nDestination database connections are always encrypted by Database Migration Service.\nYou don't need to configure additional certificates for those connections.\n\nTo understand how Database Migration Service uses SSL/TLS encryption, it's important to\nremember that with regards to\n[network connectivity](/database-migration/docs/oracle-to-postgresql/networking-overview), Database Migration Service is considered the\n**client** and your database (either source or destination database) is the\n**server**. Database Migration Service supports the following encryption variants:\n\nNone\n: When Database Migration Service establishes a connection with your database,\n it doesn't send any SSL configuration string. It doesn't present any client\n certificates to the server, and it also doesn't verify any server certificates.\n\nTLS\n\n: When Database Migration Service connects to your database, it declares that the\n connection is established over a secured channel. Database Migration Service doesn't\n present a client certificate to the server, but it does validate the server\n certificate authority (CA) to make sure that it's connecting to the right host.\n This prevents person-in-the-middle attacks.\n\n To use TLS authentication, you must provide the x509 PEM-encoded\n certificate of the certificate authority (CA) that signed your database\n server certificate.\n\nWhat's next\n-----------\n\n- Learn about encrypting source database connections. See\n [Configure encryption for source database connections](/database-migration/docs/oracle-to-postgresql/encrypt-source-connections).\n\n- To get a complete, step-by-step migration walkthrough, see\n [Oracle to AlloyDB for PostgreSQL migration guide](/database-migration/docs/oracle-to-postgresql/guide)."]]
