Buat, lihat, perbarui, dan gunakan secret dalam VS Code,
IntelliJ, atau Cloud Shell dengan
integrasi Secret Manager Cloud Code.
Fungsi Cloud Run
Akses secret Secret Manager dan ekspos sebagai variabel lingkungan
atau menggunakan sistem file dari fungsi Cloud Run. Lihat artikel menggunakan secret Secret Manager dengan fungsi Cloud Run untuk mengetahui informasi selengkapnya.
Akses secret Secret Manager dan tampilkan sebagai variabel lingkungan atau menggunakan sistem file dari layanan Cloud Run. Lihat
menggunakan secret Secret Manager dengan Cloud Run untuk
mengetahui informasi selengkapnya.
Di Secret Manager, Anda dapat menggunakan kunci Cloud External Key Manager (Cloud EKM) untuk mengenkripsi dan
mendekode secret. Key Access Justifications berfungsi dengan menambahkan kolom tambahan ke permintaan Cloud EKM yang memungkinkan Anda melihat alasan setiap permintaan untuk mengakses kunci yang dikelola secara eksternal. Dengan begitu, Anda dapat menyetujui atau menolak permintaan akses berdasarkan justifikasi tersebut. Dengan partner pengelolaan kunci enkripsi eksternal tertentu, Anda
dapat otomatis menyetujui atau menolak permintaan ini, berdasarkan justifikasi.
Lihat dokumentasi Key Access Justifications untuk mengetahui informasi selengkapnya.
[[["Mudah dipahami","easyToUnderstand","thumb-up"],["Memecahkan masalah saya","solvedMyProblem","thumb-up"],["Lainnya","otherUp","thumb-up"]],[["Sulit dipahami","hardToUnderstand","thumb-down"],["Informasi atau kode contoh salah","incorrectInformationOrSampleCode","thumb-down"],["Informasi/contoh yang saya butuhkan tidak ada","missingTheInformationSamplesINeed","thumb-down"],["Masalah terjemahan","translationIssue","thumb-down"],["Lainnya","otherDown","thumb-down"]],["Terakhir diperbarui pada 2025-09-04 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."]]
