Secret Manager Secret Accessor

Related topics

• Secret Manager Secret Accessor is part of IAM From the official documentation: “In order for the Cloud Build service account to access this secret, you have to grant it the [Secret Manager Secret Accessor](/iam/docs/roles-permissions/secretmanager) role in [IAM](https://console.cloud.google.com/iam-admin/iam).”
• Secret Manager Secret Accessor is part of Identity and Access Management From the official documentation: “Grant the [`Secret Manager Secret Accessor`](/secret-manager/docs/access-control#secretmanager.secretAccessor) IAM role to the agent identity.”
• Secret Manager Secret Accessor secures Secret Manager From the official documentation: “Grant permissions to the AlloyDB cluster to access the secret. ``` gcloud secrets add-iam-policy-binding 'SECRET_NAME' \ --member="serviceAccount:SERVICE_ACCOUNT_ID" \ --role="roles/secretmanager.secretAccessor" ```”
• Secret Manager Secret Accessor secures secret version From the official documentation: “To get the permissions that you need to access a secret version, ask your administrator to grant you the [Secret Manager Secret Accessor](/iam/docs/roles-permissions/secretmanager#secretmanager.secretAccessor) (`roles/secretmanager.secretAccessor`) IAM role on a secret.”
• service agent depends on Secret Manager Secret Accessor From the official documentation: “Grant the service agent the Secret Manager Secret Accessor (`roles/secretmanager.secretAccessor`) role.”
• Cloud Run depends on Pub/Sub From the official documentation: “Cloud Run function triggered by Pub/Sub to fetch HYPR MFA logs and write to GCS.”
• Application Default Credentials works with Pub/Sub From the official documentation: “To authenticate to Pub/Sub, set up Application Default Credentials.”
• Application Default Credentials secures Pub/Sub From the official documentation: “To authenticate to Pub/Sub, set up Application Default Credentials.”
• Pub/Sub depends on Application Default Credentials From the official documentation: “To authenticate to Pub/Sub, set up Application Default Credentials.”
• Cloud Run depends on service account From the official documentation: “The Cloud Run function needs a service account with permissions to write to GCS bucket and be invoked by Pub/Sub.”
• Pub/Sub works with Secret Manager From the official documentation: “Receive notifications via Pub/Sub when Secret Manager resources change.”
• Storage Transfer Service depends on service agent From the official documentation: “Storage Transfer Service uses a [service agent](/iam/docs/service-account-types#service-agents) to move your data.”
• Application Default Credentials works with Secret Manager From the official documentation: “To authenticate to Secret Manager, set up Application Default Credentials.”
• Application Default Credentials works with Cloud Run From the official documentation: “To authenticate to Cloud Run, set up Application Default Credentials.”
• Application Default Credentials secures IAM From the official documentation: “To authenticate to IAM, set up Application Default Credentials.”
• Cloud Run works with Identity and Access Management From the official documentation: “For example, a remote backend deployed on Cloud Run can use Identity and Access Management (IAM) to:”
• Cloud Run works with Secret Manager From the official documentation: “The secret is configured to be accessible by Cloud Run and Cloud Build.”
• Identity and Access Management works with Workload Identity Federation for GKE From the official documentation: “Instead, your GKE cluster directly authenticates workloads using Google Cloud IAM.”
• Secret Manager works with Workload Identity Federation for GKE From the official documentation: “Kubernetes Pods use Workload Identity Federation for GKE to authenticate to the Secret Manager API.”
• service account is part of Identity and Access Management From the official documentation: “Service accounts function as both principals and resources within IAM.”
• Application Default Credentials works with Identity and Access Management From the official documentation: “To authenticate to IAM, set up Application Default Credentials.”
• Application Default Credentials works with service account From the official documentation: “You can authenticate the service account using Application Default Credentials (ADC) or a service account key.”
• Cloud Run depends on Application Default Credentials From the official documentation: “To authenticate to Cloud Run, set up Application Default Credentials.”
• Cloud Run works with Pub/Sub From the official documentation: “A Cloud Run app receives the Pub/Sub message.”
• IAM works with Workload Identity Federation for GKE From the official documentation: “The cluster you are using for this tutorial is configured to use Workload Identity Federation for GKE, which allows you to grant IAM roles directly to Kubernetes ServiceAccounts.”
• Identity and Access Management secures Secret Manager From the official documentation: “Secret Manager uses Identity and Access Management (IAM) for authorization.”
• Pub/Sub works with service account From the official documentation: “5. Creates a service account to represent the Pub/Sub subscription identity.”
• Pub/Sub works with Storage Transfer Service From the official documentation: “Storage Transfer Service provides [Pub/Sub notifications](/storage-transfer/docs/pub-sub-transfer) on a variety of events.”
• Secret Manager depends on Application Default Credentials From the official documentation: “To authenticate to Secret Manager, set up Application Default Credentials.”
• Secret Manager works with service account From the official documentation: “The service account can access the secret data.”
• Secret Manager works with Storage Transfer Service From the official documentation: “Storage Transfer Service can leverage Secret Manager to protect your AWS access credentials.”
• service account depends on Secret Manager From the official documentation: “Make sure that the service account that AlloyDB Omni uses has the `secretmanager.secretAccessor` permission to read the secret from Secret Manager.”
• Storage Transfer Service depends on Application Default Credentials From the official documentation: “To authenticate to Storage Transfer Service, set up Application Default Credentials.”
• Application Default Credentials configures Cloud Run From the official documentation: “To authenticate to Cloud Run, set up Application Default Credentials.”
• Application Default Credentials works with IAM From the official documentation: “To authenticate to IAM, set up Application Default Credentials.”
• Application Default Credentials secures Secret Manager From the official documentation: “To authenticate to Secret Manager, set up Application Default Credentials.”
• Application Default Credentials depends on service account From the official documentation: “If your `BidiProcessOrder` client runs in a secure environment that can be configured with service account credentials (such as Compute Engine, Google Kubernetes Engine, or your on-premise servers), it can use [Application Default Credentials…”
• Application Default Credentials is an alternative to service account From the official documentation: “There are two ways to obtain credentials for the agent to use: - Let the agent use a service account with private-key authentication - Let the agent use application default credentials (ADC).”
• Cloud Run works with service account From the official documentation: “Map a custom Service Account to a Cloud Run service”
• IAM depends on Application Default Credentials From the official documentation: “To authenticate to IAM, set up Application Default Credentials.”
• IAM secures Cloud Run From the official documentation: “Authenticated services are [protected by IAM](/run/docs/securing/managing-access).”
• IAM works with Pub/Sub From the official documentation: “Pub/Sub relies on a standard OAuth authentication used by other Google Cloud products and supports granular IAM, enabling access control for individual resources.”
• IAM secures Pub/Sub From the official documentation: “Access control with IAM Learn how Pub/Sub uses IAM for access control.”
• IAM configures Secret Manager From the official documentation: “Configuring proper IAM permissions when using secret backends like Secret Manager so that the environment's service account has access to it.”
• IAM secures Secret Manager From the official documentation: “Access to the Secret Manager API is protected by IAM.”
• Identity and Access Management depends on Application Default Credentials From the official documentation: “To authenticate to IAM, set up Application Default Credentials.”
• Identity and Access Management secures Cloud Run From the official documentation: “Cloud Run services are secured by IAM.”
• Identity and Access Management secures Pub/Sub From the official documentation: “Pub/Sub uses Identity and Access Management (IAM) for authorization.”
• Identity and Access Management configures service account From the official documentation: “Learn more about using Identity and Access Management to [create a service account](/iam/docs/creating-managing-service-accounts) and [manage the access granted to a service account](/iam/docs/granting-changing-revoking-access).”
• Identity and Access Management works with Storage Transfer Service From the official documentation: “Storage Transfer Service uses [Identity and Access Management (IAM)](https://cloud.google.com/iam/) permissions and roles to control who can access Storage Transfer Service resources.”
• Secret Manager secures Cloud Run From the official documentation: “Store sensitive credentials in Secret Manager for secure access by the Cloud Run function.”
• secret version is part of Secret Manager From the official documentation: “A secret in Secret Manager contains a collection of secret versions.”
• service account works with Workload Identity Federation for GKE From the official documentation: “use [Workload Identity Federation for GKE](/kubernetes-engine/docs/how-to/workload-identity#authenticating_to) to attach service accounts to Kubernetes pods.”
• service account is an alternative to Workload Identity Federation for GKE From the official documentation: “If you do not enable Workload Identity Federation for GKE, you need to register the cluster with a Google Cloud service account for authentication, and complete the additional steps in [Authenticating service accounts](#authenticating).”
• service agent depends on Pub/Sub From the official documentation: “Your service agent must have [publishing access](/pubsub/docs/access-control#console) on the Pub/Sub topic.”
• service agent depends on service account From the official documentation: “The BigQuery Data Transfer Service uses a [*service agent*](/iam/docs/service-account-types#service-agents) to get the access token for the user-provided service account (transfer owner).”