[[["わかりやすい","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-03 UTC。"],[],[],null,["# About in-transit encryption\n\nThis page gives an overview of in-transit encryption for Memorystore for Valkey.\n\nFor instructions on how to encrypt a connection with in-transit encryption, see [Manage in-transit encryption](/memorystore/docs/valkey/manage-in-transit-encryption).\n\nMemorystore for Valkey only supports TLS protocol versions 1.2 or higher.\n\nIntroduction\n------------\n\nMemorystore for Valkey supports encrypting all Valkey traffic using the [Transport Layer Security (TLS)](https://en.wikipedia.org/wiki/Transport_Layer_Security) protocol. When\nin-transit encryption is enabled Valkey clients communicate exclusively across a\nsecure connection. Valkey clients that are not configured for TLS are\nblocked. If you choose to enable in-transit encryption you are responsible for\nensuring that your Valkey client is capable of using the TLS protocol.\n| **Note:** For instances with replicas, replicated data is fully encrypted at the network level based on Google Cloud encryption standards.\n\nIn-transit encryption prerequisites\n-----------------------------------\n\nIn order to use in-transit encryption with Memorystore for Valkey, you need:\n\n1. A Valkey client that supports TLS or a third-party TLS sidecar\n\n2. [Certificate Authorities](/memorystore/docs/valkey/about-in-transit-encryption#certificate_authorities)\n installed on the client machine accessing your Valkey instance\n\nNot every Valkey client library supports TLS. If you are using a client\nthat does not support TLS, we recommend using the [Stunnel](https://www.stunnel.org/)\nthird-party plugin that enables TLS for your client. See [Securely connecting to a Valkey instance using Stunnel and telnet](/memorystore/docs/valkey/connect-instance#securely_connect_to_a_memorystore_instance_using_stunnel_and_telnet)\nfor an example of how to connect to a Valkey instance with Stunnel.\n\nCertificate Authorities\n-----------------------\n\nA Valkey instance that uses in-transit encryption has unique\nCertificate Authorities (CAs) that are used to authenticate the certificates of\nthe machines in your instance. Each CA is identified by a certificate that you\nmust download and install on the client accessing your Valkey instance.\n| **Note:** CAs are valid for ten years from the date they are created. To ensure service continuity, new CAs must be installed on clients of the Valkey instance before the previous CAs expire.\n\n### Certificate authority rotation\n\nCAs are valid for 10 years upon instance creation. In addition, a new CA will\nbecome available prior to CA expiration.\n\nOld CAs are valid until their expiration date. This gives you a window in which\nto download and install the new CA to clients connecting to the Valkey instance.\nAfter the old CAs expire you can uninstall them from clients.\n\nFor instructions on rotating the CA, see [Managing Certificate Authority rotation](/memorystore/docs/valkey/manage-in-transit-encryption#manage_certificate_authority_rotation).\n\n### Server certificate rotation\n\nServer-side certificate rotation occurs every week. New server certificates\napply to new connections only, and existing connections remain alive during\nrotation.\n\nPerformance impact of enabling in-transit encryption\n----------------------------------------------------\n\nThe in-transit encryption feature encrypts and decrypts data, which comes with\nprocessing overhead. As a result, enabling in-transit encryption can reduce\nperformance. Also, when using in-transit encryption, each additional connection\ncomes with an associated resource cost. To determine the latency associated with\nusing in-transit encryption, compare application performance by benchmarking\napplication performance with both an instance that has in-transit encryption\nenabled and an instance that has it disabled.\n\n### Guidelines for improving performance\n\n- Decrease the number of client connections when possible. Establish and reuse\n long-running connections rather than creating on-demand short-lived\n connections.\n\n- Increase the size of your Memorystore for Valkey instance.\n\n- Increase the CPU resources of the Memorystore client host\n machine. Client machines with a higher CPU count yields better performance. If\n using a Compute Engine VM, we recommend compute optimized instances.\n\n- Decrease the payload size associated with application traffic because larger\n payloads require more round trips."]]