[[["容易理解","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-19 (世界標準時間)。"],[],[],null,["# About Redis AUTH\n\n| **Note:** If you are looking for the Memorystore for Redis Cluster documentation, see [About IAM authentication](/memorystore/docs/cluster/about-iam-auth).\n\nThis page gives an overview of [AUTH](https://redis.io/commands/auth)\non Memorystore for Redis.\n\nFor instructions on managing AUTH for your Redis instance, see [Managing Redis AUTH](/memorystore/docs/redis/managing-auth).\n\nAUTH behavior\n-------------\n\nUsing AUTH is optional for Memorystore for Redis.\n\nA connecting client starts by sending the [AUTH](https://redis.io/commands/auth)\ncommand followed by the Redis instance's AUTH string. Every AUTH string is a [Universally Unique Identifier (UUID)](https://en.wikipedia.org/wiki/Universally_unique_identifier).\nEach Redis instance with AUTH enabled has a unique AUTH string.\n\nIf you enable the AUTH feature on your Memorystore instance,\nincoming client connections must authenticate in order to connect. Existing\nconnections that had not previously authenticated need to properly authenticate\nbefore they can continue issuing commands. Once a client authenticates with an\nAUTH string, it remains authenticated for the lifetime of that connection, even\nif you change the AUTH string.\n\nFor Memorystore for Redis, the AUTH string is automatically generated after AUTH is\nenabled on the instance. The AUTH string is a randomly generated string of 36\ncharacters that is exclusive to each Memorystore instance. The\nAUTH string is uniquely generated each time that AUTH is enabled. Therefore, the\nAUTH string can be changed if necessary by toggling AUTH from off to on.\n\nLike every command, if [in-transit encryption](/memorystore/docs/redis/about-in-transit-encryption)\nis not enabled, there is no guarantee that the command is encrypted in-transit\nend to end. This is because there is no guarantee that the client traffic is\nmeeting the [VPC network level based encryption on Google Cloud encryption standards](/docs/security/encryption-in-transit#virtual-network).\n\nSecurity and privacy\n--------------------\n\nAUTH helps you ensure that known entities in your organization do not\nunintentionally access and modify your Redis instance. AUTH does not provide\nsecurity during data transportation. Also, AUTH does not protect your instance\nagainst any malicious entities that have access to your VPC network.\n\nMake sure to limit access to your VPC network to known users and clients. See\n[Redis security](https://redis.io/topics/security)\nfor additional details.\n\nUsing AUTH with read replica enabled instances\n----------------------------------------------\n\nIf AUTH is enabled on an instance that also has [read replicas](/memorystore/docs/redis/read-replicas)\nenabled, any connection to the Redis instance requires initial authentication\nusing the AUTH string.\n\nWhat's next\n-----------\n\n- Perform common tasks associated with [Redis AUTH](/memorystore/docs/redis/managing-auth)\n- See the [permissions](/memorystore/docs/redis/access-control#redis_authentication_permissions) required to perform Redis AUTH tasks."]]