regional secrets

Related topics

• automatic rotation of Cloud SQL secrets depends on regional secrets From the official documentation: “Automatic rotation for Cloud SQL credentials is available only for regional secrets in Secret Manager.”
• regional secrets is part of Secret Manager From the official documentation: “Automatic rotation for Cloud SQL credentials is available only for regional secrets in Secret Manager.”
• CMEK secures regional secrets From the official documentation: “Add CMEK encryption to regional secrets”
• Cloud Run works with Cloud SQL From the official documentation: “Learn how to connect to Cloud SQL from Cloud Run”
• Cloud SQL works with Cloud Storage From the official documentation: “When ingesting data from Cloud SQL, data is first staged to a Cloud Storage bucket.”
• Cloud Run works with Pub/Sub From the official documentation: “Route Cloud Pub/Sub events to Cloud Run”
• Cloud SQL works with Compute Engine From the official documentation: “Create a Compute Engine VM Instance to host a sample web app that connects to Cloud SQL.”
• Cloud Run works with Cloud Storage From the official documentation: “Route Cloud Storage events to Cloud Run”
• Cloud Run works with Secret Manager From the official documentation: “You can integrate Secret Manager with other Google Cloud products such as Cloud Run.”
• Pub/Sub works with Secret Manager From the official documentation: “Receive notifications via Pub/Sub when Secret Manager resources change.”
• CMEK secures Pub/Sub From the official documentation: “Encrypt Pub/Sub topic with CMEK”
• Compute Engine is an alternative to GKE From the official documentation: “To use TPU7x, you can use Google Kubernetes Engine (GKE) or Compute Engine.”
• Cloud Run depends on Pub/Sub From the official documentation: “Create a Pub/Sub topic that Cloud Scheduler will publish to and the Cloud Run function will subscribe to.”
• CMEK secures Cloud SQL From the official documentation: “Enable CMEK for Cloud SQL Databases”
• Compute Engine works with Secret Manager From the official documentation: “To use Secret Manager with workloads running on Compute Engine or GKE, the underlying instance or node must have the `cloud-platform` OAuth scope.”
• Cloud Run is an alternative to GKE From the official documentation: “The app uses Cloud SQL, Vertex AI, and either Google Kubernetes Engine (GKE) or Cloud Run.”
• Cloud SQL depends on Compute Engine From the official documentation: “Cloud SQL uses Compute Engine virtual machines (VMs) with persistent storage disks.”
• GKE works with Secret Manager From the official documentation: “To use Secret Manager with workloads running on Compute Engine or GKE, the underlying instance or node must have the `cloud-platform` OAuth scope.”
• Cloud SQL works with Secret Manager From the official documentation: “Secret Manager attempts to update the credentials in your Cloud SQL instance.”
• Cloud Storage works with Pub/Sub From the official documentation: “| **Google Cloud** | Cloud Storage | Pub/Sub |”
• Cloud Storage is an alternative to Pub/Sub From the official documentation: “To keep audit logs for a longer period of time or to use more powerful search capabilities, you can route copies of your audit logs to Cloud Storage, BigQuery, or Pub/Sub.”
• CMEK secures Cloud Storage From the official documentation: “Enable CMEK for Cloud Storage Buckets”
• Cloud SQL works with GKE From the official documentation: “[From an application running on GKE](/sql/docs/postgres/connect-kubernetes-engine)”
• Cloud Storage works with Compute Engine From the official documentation: “You can use a web browser, the Google Cloud CLI, or a programming language to transfer files between Cloud Storage and Compute Engine VMs.”
• GKE depends on Compute Engine From the official documentation: “For example, GKE deploys clusters on Compute Engine VMs.”
• GKE works with Pub/Sub From the official documentation: “Route Cloud Pub/Sub events to GKE”
• automatic rotation of Cloud SQL secrets works with Cloud SQL From the official documentation: “This page describes how to configure automatic rotation for your Cloud SQL database credentials in Secret Manager.”
• Cloud Run works with GKE From the official documentation: “Leverage Google Kubernetes Engine (GKE) and Cloud Run to deploy applications to the Google Cloud, optimizing costs, performance, and management overhead.”
• CMEK secures Compute Engine From the official documentation: “Enable CMEK on Compute Engine Persistent Disks”
• CMEK secures GKE From the official documentation: “Enable CMEK on GKE Node Pool Boot Disks”
• automatic rotation of Cloud SQL secrets is part of Secret Manager From the official documentation: “This document describes the automatic rotation of Cloud SQL secrets in Secret Manager.”
• automatic rotation of Cloud SQL secrets works with Secret Manager From the official documentation: “This page describes how to configure automatic rotation for your Cloud SQL database credentials in Secret Manager.”
• Cloud Run works with Compute Engine From the official documentation: “This lets Cloud Run clients use this backend service route to send requests directly to Compute Engine instances.”
• Cloud Run is an alternative to Compute Engine From the official documentation: “The decision of whether to use Cloud Run, GKE, or Compute Engine as your application host involves trade-offs between configuration flexibility and management effort.”
• Cloud SQL depends on Cloud Storage From the official documentation: “When ingesting data from Cloud SQL, data is first staged to a Cloud Storage bucket.”
• Cloud Storage works with GKE From the official documentation: “Route Cloud Storage events to GKE”
• Cloud Storage is an alternative to Secret Manager From the official documentation: “Your provisioning tools might need to be adapted to use Google Cloud Storage or Secret Manager to read such custom configuration lists.”
• CMEK secures Cloud Run From the official documentation: “You use the CMEK keys to help protect your data in Artifact Registry and in Cloud Run.”
• CMEK works with Pub/Sub From the official documentation: “By using Pub/Sub with CMEK, you are able to meet locality rules about encryption while still maintaining high availability.”
• Compute Engine works with GKE From the official documentation: “For example, Google Kubernetes Engine (GKE) can cause usage in Compute Engine.”