Secret Manager에서 Cloud 외부 키 관리자(Cloud EKM) 키를 사용하여 보안 비밀을 암호화하고 복호화할 수 있습니다. 키 액세스 근거는 모든 요청이 외부 관리 키에 액세스하는 이유를 볼 수 있는 추가 필드를 Cloud EKM 요청에 추가하는 방식으로 작동합니다. 이 근거에 따라 액세스 요청을 승인하거나 거부할 수 있습니다. 일부 외부 키 관리 파트너를 사용하면 근거에 따라 이러한 요청을 자동으로 승인하거나 거부할 수 있습니다.
자세한 내용은 키 액세스 근거 문서를 참조하세요.
[[["이해하기 쉬움","easyToUnderstand","thumb-up"],["문제가 해결됨","solvedMyProblem","thumb-up"],["기타","otherUp","thumb-up"]],[["이해하기 어려움","hardToUnderstand","thumb-down"],["잘못된 정보 또는 샘플 코드","incorrectInformationOrSampleCode","thumb-down"],["필요한 정보/샘플이 없음","missingTheInformationSamplesINeed","thumb-down"],["번역 문제","translationIssue","thumb-down"],["기타","otherDown","thumb-down"]],["최종 업데이트: 2024-12-21(UTC)"],[],[],null,["# Use Secret Manager with other products\n\nThis topic provides resources for using Secret Manager with other\nGoogle Cloud services.\n\nCloud Build\n-----------\n\nAccess Secret Manager secrets using environment variables in build\nsteps on Cloud Build. See\n[using Secret Manager secrets with Cloud Build](/build/docs/securing-builds/use-encrypted-secrets-credentials) for\nmore information.\n\nCloud Code\n----------\n\nCreate, view, update, and use secrets within [VS Code](/code/docs/vscode/secret-manager),\n[IntelliJ](/code/docs/intellij/secret-manager), or [Cloud Shell](/code/docs/shell/secret-manager) with\nCloud Code's Secret Manager integration.\n\nCloud Run functions\n-------------------\n\nAccess Secret Manager secrets and expose them as environment variables\nor using the file system from Cloud Run functions. See\n[using Secret Manager secrets with Cloud Run functions](/functions/docs/configuring/secrets) for\nmore information.\n\nYou can also use Secret Manager with\nCloud Run functions by using a [Secret Manager client library](/secret-manager/docs/reference/libraries)\nor by [accessing the Secret Manager API directly](/secret-manager/docs/accessing-the-api).\n\nCloud Run\n---------\n\nAccess Secret Manager secrets and expose them as environment variables\nor using the file system from Cloud Run services. See\n[using Secret Manager secrets with Cloud Run](/run/docs/configuring/secrets) for\nmore information.\n\nYou can also use Secret Manager with\nCloud Run services by using a\n[Secret Manager client library](/secret-manager/docs/reference/libraries) or by\n[accessing the Secret Manager API directly](/secret-manager/docs/accessing-the-api).\n\nCompute Engine\n--------------\n\n\n| **Important:** To use Secret Manager with workloads running on Compute Engine or Google Kubernetes Engine, the underlying instance or node must have the `cloud-platform` OAuth scope. See [accessing the Secret Manager API](/secret-manager/docs/accessing-the-api#oauth-scopes) for more information.\n\n\u003cbr /\u003e\n\nUse Secret Manager with workloads running on Compute Engine by using a\n[Secret Manager client library](/secret-manager/docs/reference/libraries) or by\n[accessing the Secret Manager API directly](/secret-manager/docs/accessing-the-api).\n\nGoogle Kubernetes Engine\n------------------------\n\n\n| **Important:** To use Secret Manager with workloads running on Compute Engine or Google Kubernetes Engine, the underlying instance or node must have the `cloud-platform` OAuth scope. See [accessing the Secret Manager API](/secret-manager/docs/accessing-the-api#oauth-scopes) for more information.\n\n\u003cbr /\u003e\n\nUse Secret Manager with workloads running on Google Kubernetes Engine (GKE)\nusing one of the following options:\n\n- Client libraries: The recommended way to access Secret Manager secrets from\n workloads running on Google Kubernetes Engine is to use a [Secret Manager client library](/secret-manager/docs/reference/libraries)\n authenticated using [Workload Identity Federation for GKE](/kubernetes-engine/docs/tutorials/workload-identity-secrets).\n For more information, see [Secret Manager best practices](/secret-manager/docs/best-practices).\n\n- Secret Manager add-on: You can\n use the Secret Manager add-on to access Secret Manager secrets\n as volumes mounted in Kubernetes Pods. For information, see\n [Use Secret Manager add-on with Google Kubernetes Engine](/secret-manager/docs/secret-manager-managed-csi-component).\n\nConfig Connector\n----------------\n\nCreate and manage Secret Manager secrets with Config Connector using a\ndeclarative syntax. See the\n[Secret Manager Config Connector resource documentation](/config-connector/docs/reference/resource-docs/secretmanager/secretmanagersecret) for more\ninformation.\n\nKey Access Justifications\n-------------------------\n\nIn Secret Manager, you can use Cloud External Key Manager (Cloud EKM) keys to encrypt and\ndecrypt secrets. Key Access Justifications works by adding an additional field to the\nCloud EKM requests that lets you view the reason for every request to\naccess the externally managed keys. It lets you approve or deny the access request\nbased on that justification. With select external key management partners, you\ncan automatically approve or deny these requests, based on the justification.\nSee the [Key Access Justifications\ndocumentation](/assured-workloads/key-access-justifications/docs/overview) for\nmore information."]]
