데이터 암호화는 특별한 구성이 필요하지 않습니다. 하지만 기본 키를 대체하는 자체 암호화 키를 사용하고 싶은 경우 이 주제에 설명된 대로 하면 됩니다.
암호화 키 범위
Apigee Hybrid 암호화 키에는 범위가 있습니다. 예를 들어 KMS 키에는 조직 범위가 있습니다. 이는 키가 전체 조직의 KMS 데이터를 암호화하는 데 사용됨을 의미합니다.
다음 표에는 각 키 유형의 범위가 나열되어 있습니다.
암호화 키
범위
계약
조직만
KMS
조직만
KVM
조직 또는 환경
KVM 정책이 apiproxy 또는 policy(API 프록시 버전) 범위를 지정하면, 조직 수준 키가 데이터를 암호화하는 데 사용됩니다. Apigee Edge에서 KVM을 사용하는 방법에 대한 일반적인 개요는 키-값 맵 다루기를 참조하세요.
캐시
환경만
기본 암호화 키 정보
기본적으로 Apigee Hybrid는 계약, KVM, KMS, 캐시 데이터를 암호화하는 데 사용되는 Base64 인코딩 키 모음을 제공합니다. Apigee Hybrid 설치 프로그램은 런타임 영역에 키를 Kubernetes 보안 비밀로 저장하고 이를 사용하여 AES-128 표준 암호화로 데이터를 암호화합니다.
키는 개발자가 제어할 수 있으며, 하이브리드 관리 영역을 항상 인식하지 못합니다.
기본 키는 만들 때 생성되는 모든 새로운 Apigee Hybrid 구성요소에 적용됩니다.
기본 암호화 키 변경
필수는 아니지만 기본 암호화 키를 원하는 경우 변경할 수 있습니다.
하나 이상의 기본 키를 바꾸려면 다음 단계를 따르세요.
다음 스탠자를 재정의 파일에 복사합니다.
이 구성을 통해 조직 수준의 KMS 및 KVM 암호화 키와 환경 수준의 KVM 및 캐시 암호화 키를 변경할 수 있습니다.
Apigee Hybrid를 처음 설치할 때 재정의 파일에서 암호화 키를 삭제한 경우 암호화를 효과적으로 사용 중지할 수 있으며 값은 암호화되지 않은 상태로 저장됩니다.
나중에 키를 제공하여 암호화를 사용 설정하면 종료되는 데이터는 암호화되지 않은 상태로 유지됩니다. 그러나 이후에 추가되는 데이터는 모두 암호화됩니다. 시스템은 암호화되지 않은 데이터와 새로운 암호화된 데이터와 함께 정상적으로 계속 작동합니다.
또한 런타임 데이터가 암호화되면 나중에 암호화 키를 변경할 수 없습니다.
인코딩된 키를 만드는 방법
KVM, KMS, 캐시 암호화에는 올바른 형식의 Base-64 인코딩 키가 필요합니다.
이러한 용도로 사용되는 키는 아래에 설명된 대로 16, 24 또는 32바이트 길이의 문자열에서 Base-64로 인코딩되어야 합니다.
다음 예시 명령어는 무작위 생성되고 Base64로 인코딩된 32자의 적합한 문자열을 생성합니다.
[[["이해하기 쉬움","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,["# Data encryption\n\nBy default, the following data is stored *encrypted* in the hybrid\nruntime plane:\n\n- Cache data\n- Contract key data\n- Key management system (KMS) data\n- Key-value map (KVM) data\n\n\nData encryption does not require any special configuration on your part. However, if\nfor some reason you want to use your own encryption keys (replacing the default ones) you can\ndo so, as explained in this topic.\n\nEncryption key scope\n--------------------\n\n\nApigee hybrid encryption keys have scope. For example, KMS keys have *organization*\nscope. This means that the key is used to encrypt KMS data for the entire organization.\nThe following table lists the scope for\neach type of key:\n\nAbout the default encryption keys\n---------------------------------\n\n\nBy default, Apigee hybrid provides a set of Base64-encoded keys that are used to\nencrypt contract, KVM, KMS, and cache data. The Apigee hybrid installer stores the keys in the\nruntime plane as\n[Kubernetes\nSecrets](https://kubernetes.io/docs/concepts/configuration/secret/), and uses them to encrypt your data with AES-128 standard encryption.\nThe keys are under your control;\nthe hybrid management plane is never aware of them at any time.\n\n\nThe default keys are applied to all new Apigee hybrid components when you create them.\n| The default keys will work for most use cases. If you want to change the default encryption keys, do so when you initially install Apigee hybrid into a new cluster. If you change the encryption keys after the runtime is created in your cluster, previously encrypted data can no longer work (it cannot be decrypted); only new data added after the change will be encrypted and function as expected.\n\nChanging the default encryption keys\n------------------------------------\n\n\nAlthough not required, you can change any of the default encryption keys if you wish.\nTo replace one or more default keys, follow these steps:\n| If you change the encryption keys after the runtime is created in your cluster, previously encrypted data can no longer work (it cannot be decrypted); only new data added after the change will be encrypted and function as expected. For this reason, Apigee hybrid does not support key rotation for these keys.\n\n1. Copy the following stanzas into your overrides file. This configuration lets you change the KMS and KVM encryption keys for the organization level and the KVM and cache encryption keys for the environment level: \n\n ```actionscript-3\n defaults:\n org:\n kmsEncryptionKey: base64-encoded-key\n kvmEncryptionKey: base64-encoded-key\n contractEncryptionKey: base64-encoded-key\n\n env:\n kvmEncryptionKey: base64-encoded-key\n cacheEncryptionKey: base64-encoded-key\n ```\n2. Generate a new key for each key you wish to replace. Each key must be a Base64-encoded string that is exactly **16, 24, or 32 bytes long** . See also [How to create an encoded\n key](#how-to-create-an-encoded-key).\n3. Replace the default keys with new ones. In this example, all of the default keys are replaced with keys: \n\n ```actionscript-3\n defaults:\n org:\n kmsEncryptionKey: \"JVpTb1FwI0otUHo2RUdRN3pnVyQqVGlMSEFAJXYmb1c=\"\n kvmEncryptionKey: \"T3VkRGM1U3cpOFgtNk9fMnNZU2NaSVA3I1BtZWxkaUU=\"\n contractEncryptionKey: \"RDEyMzQ1Njc4OTAxMjM0NQ==\"\n env:\n kvmEncryptionKey: \"Q3h6M3R6OWdBeipxTURfKjQwQVdtTng2dU5mODFHcyE=\"\n cacheEncryptionKey: \"b2NTVXdKKjBzN0NORF9XSm9tWFlYKGJ6NUhpNystJVI=\"\n ```\n\nOverride the default keys\n-------------------------\n\nYou can override the keys for the org or specific envs named in your overrides file. When you create the components, keys you specify for the org or individual envs will be override the defaults.\n| If you change the encryption keys after the runtime is created in your cluster, previously encrypted data can no longer work (it cannot be decrypted); only new data added after the change will be encrypted and function as expected. For this reason, Apigee hybrid does not support key rotation for these keys.\n\n1. Copy the following stanzas into your overrides file. This configuration lets you change the KMS and KVM encryption keys for the organization level and the KVM and cache encryption keys for the environment level: \n\n ```actionscript-3\n org:YOUR_ORG_NAME\n\n kmsEncryptionKey: base64-encoded-key\n kvmEncryptionKey: base64-encoded-key\n contractEncryptionKey: base64-encoded-key\n\n envs\n - name: ENV_NAME\n kvmEncryptionKey: base64-encoded-key\n kmsEncryptionKey: base64-encoded-key\n cacheEncryptionKey: base64-encoded-key\n\n - name: 2ND_ENV_NAME\n kvmEncryptionKey: base64-encoded-key\n kmsEncryptionKey: base64-encoded-key\n cacheEncryptionKey: base64-encoded-key\n ```\n2. Generate a new key for each key you wish to override. Each key must be a Base64-encoded string that is exactly **16, 24, or 32 bytes long** . See also [How to create an encoded key](#how-to-create-an-encoded-key).\n3. Specify the keys you want to override. In this example, all of the default keys are replaced with keys: \n\n ```actionscript-3\n org:hybrid-org\n\n kmsEncryptionKey: \"QTEyMz1b2jc4OTAxMjM0NQ==\"\n kvmEncryptionKey: \"QzEyM2c3Njc4OTAxMjM0NQ==\"\n contractEncryptionKey: \"RDEyMzQ1Njc4OTAxMjM0NQ==\"\n\n envs:\n - name: prod\n kvmEncryptionKey: \"QzEyM2c3Njc4OTAxMjM0NQ==\"\n kmsEncryptionKey: \"QTEyMz1b2jc4OTAxMjM0NQ==\"\n cacheEncryptionKey: \"QjEyAvC1Njc4OTAxMjM0NQ==\"\n\n envs:\n - name: test\n kvmEncryptionKey: \"A1b2C3d4E5f6G7h8I9j10K==\"\n kmsEncryptionKey: \"QTEyMz1b2jc4OTAxMjM0NQ==\"\n cacheEncryptionKey: \"B1c2D3e4F5f6H7i8J9k10L==\"\n ```\n\nApply the key changes\n---------------------\n\nApply the overrides file to your cluster as with the following Helm commands:\n\n- If you change the contract key or the KVM key for the org, update the org: \n\n ```\n helm upgrade ORG_NAME apigee-org/ \\\n --namespace apigee \\\n --atomic \\\n -f OVERRIDES_FILE.yaml\n ```\n- If you change Cache key or the KVM key for an environment, update the environment: \n\n ```\n helm upgrade ENV_NAME apigee-env/ \\\n --namespace apigee \\\n --atomic \\\n --set env=ENV_NAME \\\n -f OVERRIDES_FILE.yaml\n ```\n- If you change KMS key, update both the org and environment: \n\n ```\n helm upgrade ORG_NAME apigee-org/ \\\n --namespace apigee \\\n --atomic \\\n -f OVERRIDES_FILE.yaml\n ``` \n\n ```\n helm upgrade ENV_NAME apigee-env/ \\\n --namespace apigee \\\n --set env=ENV_NAME \\\n --atomic \\\n -f OVERRIDES_FILE.yaml\n ```\n\n| **Note:** If you see an error saying `Error: UPGRADE FAILED: \"`*ENV_NAME*`\" has no deployed releases`, replace `upgrade` with `install` and try the command again.\n\nA note about backward compatibility\n-----------------------------------\n\n\nIf you were to remove the encryption keys in your overrides file the first\ntime you install Apigee hybrid, you would\neffectively disable encryption and values would be stored unencrypted.\nIf at a later\ntime you enable encryption by providing keys,\nexiting data remains unencrypted; however, any future data that is added will\nbe encrypted. The system\nwill continue working normally with the unencrypted data and the new encrypted\ndata.\n\n\nAlso, note that\nyou cannot later change the encryption keys\nonce the runtime data is encrypted.\n\nHow to create an encoded key\n----------------------------\n\n\nA properly formatted Base-64-encoded key is required for KVM, KMS, and cache encryption.\nThe key used for any of these purposes must be Base-64 encoded from a string that is 16, 24, or\n32 bytes long, as explained below:\n| The key string length requirement exists because the [Advanced\n| Encryption Standard](https://en.wikipedia.org/wiki/Advanced_Encryption_Standard) (AES) cipher works on a block size of 128 bits, but can take three different key lengths: 128, 192, and 256 bits (16, 24, or 32 bytes).\n\n\nThe following example command generates a suitable, randomly generated, 32 character,\nBase64-encoded string: \n\n```\nhead -c 32 /dev/random | openssl base64\n```"]]
