연결 클라이언트는 AUTH 명령어와 Redis 인스턴스의 AUTH 문자열 전송으로 시작됩니다. 모든 AUTH 문자열은 범용 고유 식별자(UUID)입니다.
AUTH가 사용 설정된 각 Redis 인스턴스에 고유한 AUTH 문자열이 있습니다.
Memorystore 인스턴스에서 AUTH 기능을 사용 설정하면 들어오는 클라이언트 연결이 인증되어야 연결이 가능합니다. 이전에 인증되지 않은 기존 연결에서 계속 명령어를 실행하려면 먼저 이 연결이 올바르게 인증되어야 합니다. 클라이언트가 AUTH 문자열로 인증되면 AUTH 문자열을 변경하더라도 연결 수명 동안 인증된 상태로 유지됩니다.
Memorystore for Redis의 경우 인스턴스에 AUTH가 사용 설정 된 후 AUTH 문자열이 자동으로 생성됩니다. AUTH 문자열은 각 Memorystore 인스턴스에 배타적인 무작위로 생성되는 36자 문자열입니다. AUTH 문자열은 AUTH가 사용 설정될 때마다 고유하게 생성됩니다. 따라서 필요에 따라 AUTH를 해제하고 다시 설정으로 토글하여 AUTH 문자열을 변경할 수 있습니다.
[[["이해하기 쉬움","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(UTC)"],[],[],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."]]
