Cloud SQL Auth Proxy

Related topics

• Cloud SQL works with Cloud SQL Auth Proxy From the official documentation: “Download the Cloud SQL Auth Proxy.”
• Cloud SQL Auth Proxy secures Cloud SQL From the official documentation: “The Cloud SQL proxy provides encryption between the proxy and instance”
• Cloud Run works with Cloud SQL Auth Proxy From the official documentation: “- [Cloud Run](/sql/docs/sqlserver/connect-run)”
• Cloud Build works with Cloud SQL Auth Proxy From the official documentation: “You can use the Cloud SQL Auth Proxy in a Cloud Build step to allow connections to your database.”
• Cloud SQL Auth Proxy depends on gcloud CLI From the official documentation: “The Cloud SQL Auth Proxy uses the Cloud SQL API to interact with your SQL instance. To do this, it requires application authentication through the [gcloud CLI](/sdk/gcloud).”
• Cloud SQL Auth Proxy depends on IAM permissions From the official documentation: “The Cloud SQL Auth Proxy uses IAM permissions to control who and what can connect to your Cloud SQL instances.”
• Cloud SQL Auth Proxy works with Compute Engine From the official documentation: “If you are connecting to a Cloud SQL instance from a Compute Engine instance using [Cloud SQL Auth Proxy](/sql/docs/mysql/connect-auth-proxy#create-service-account), you can use the default Compute Engine service account associated with the Compute Engine instance.”
• Cloud SQL Auth Proxy works with IAM database authentication From the official documentation: “**IAM database authentication**. Optionally, the Cloud SQL Auth Proxy supports an automatic refresh of OAuth 2.0 access tokens.”
• Cloud SQL Auth Proxy works with service account From the official documentation: “If you are using a service account to authenticate the Cloud SQL Auth Proxy, note the location on your client machine of the private key file that was created when you created the service account.”
• Cloud SQL Auth Proxy works with SSL/TLS encryption From the official documentation: “If you connect by using Cloud SQL Auth Proxy or Cloud SQL Connectors, then the connections are automatically encrypted with SSL/TLS.”
• Cloud SQL Auth Proxy depends on VPC network From the official documentation: “To connect to a Cloud SQL instance using [private IP](/sql/docs/mysql/private-ip), the Cloud SQL Auth Proxy must be on a resource with access to the same VPC network as the instance.”
• authorized networks is an alternative to Cloud SQL Auth Proxy From the official documentation: “You must configure all the non-RFC 1918 IP address ranges as [authorized networks](/sql/docs/mysql/authorize-networks) of the Cloud SQL for MySQL instances. Alternatively, you can connect to your instance using the [Cloud SQL Auth Proxy client](/sql/docs/mysql/sql-proxy).”
• Cloud SQL Auth Proxy is part of Cloud Run From the official documentation: “When deployed, your app uses the Cloud SQL Auth Proxy that is built into the Cloud Run environment to communicate with your Cloud SQL instance.”
• Cloud SQL Auth Proxy is part of Cloud SQL From the official documentation: “In addition, Cloud SQL provides different authorization options to control who is allowed to connect to your instance, such as the [Cloud SQL Auth Proxy](/sql/docs/mysql/sql-proxy).”
• Cloud SQL Auth Proxy is an alternative to gcloud CLI From the official documentation: “You can now connect to your instance by using either [gcloud CLI](/sdk/gcloud) or the Cloud SQL Auth Proxy.”
• Cloud SQL Auth Proxy works with GKE From the official documentation: “When you install the operator in your GKE cluster and configure your workloads and Cloud SQL instances, the Cloud SQL Auth Proxy Operator automatically configures the Cloud SQL Auth Proxy and connects the GKE workloads to your Cloud SQL instances.”
• Cloud SQL Auth Proxy works with private IP From the official documentation: “To connect to a Cloud SQL instance using private IP, the Cloud SQL Auth Proxy must be on a resource with access to the same VPC network as the instance.”
• Cloud SQL Auth Proxy is an alternative to private IP From the official documentation: “While not as secure, it is possible to connect from a [VPC-native GKE cluster](/kubernetes-engine/docs/how-to/alias-ips) to a Cloud SQL instance on the same VPC using private IP without the Cloud SQL Auth Proxy.”
• Cloud SQL Auth Proxy secures SSL/TLS encryption From the official documentation: “If you connect by using Cloud SQL Auth Proxy or Cloud SQL Connectors, then the connections are automatically encrypted with SSL/TLS.”
• Cloud SQL works with Cloud Storage From the official documentation: “Exports data from a Cloud SQL instance to a Cloud Storage bucket as a SQL dump or CSV file.”
• Application Default Credentials works with Cloud Storage From the official documentation: “To authenticate to Cloud Storage, set up Application Default Credentials.”
• Application Default Credentials secures Cloud Storage From the official documentation: “To authenticate to Cloud Storage, set up Application Default Credentials.”
• Application Default Credentials works with Compute Engine From the official documentation: “To authenticate to Compute Engine, set up Application Default Credentials.”
• Cloud Logging works with GKE From the official documentation: “Enable Cloud Logging on GKE Clusters”
• Compute Engine works with service account From the official documentation: “A common method is to attach a service account to a resource like a Compute Engine instance.”
• Cloud Build works with Cloud Storage From the official documentation: “Cloud Build then stores Terraform files and the Terraform State File in a Cloud Storage bucket.”
• Cloud Run works with Cloud SQL From the official documentation: “Connecting from Cloud Run (fully managed) to Cloud SQL”
• Cloud SQL works with Compute Engine From the official documentation: “Cloud SQL uses Compute Engine virtual machines (VMs) with persistent storage disks.”
• Compute Engine is an alternative to GKE From the official documentation: “You can also deploy a third-party model to either Vertex AI Model Garden or self-host on GKE or Compute Engine.”
• Application Default Credentials secures Compute Engine From the official documentation: “To authenticate to Compute Engine, 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.”
• Cloud SQL works with GKE From the official documentation: “The app uses Cloud SQL, Vertex AI, and either Google Kubernetes Engine (GKE) or Cloud Run.”
• Application Default Credentials works with Secret Manager From the official documentation: “To authenticate to Secret Manager, set up Application Default Credentials.”
• Cloud Build works with Cloud Run From the official documentation: “Cloud Build - create container images and deploy to Cloud Run.”
• Cloud Logging works with Cloud SQL From the official documentation: “Database Migration Service and Cloud SQL use Cloud Logging.”
• Cloud Logging works with Cloud Storage From the official documentation: “Cloud Storage writes various log entries to Cloud Logging in the Google Cloud console.”
• Cloud SQL works with private IP From the official documentation: “`--private-ip` Connect to the Cloud SQL instance using private IP.”
• Cloud Storage works with Compute Engine From the official documentation: “For example, you can create a service account that your Compute Engine instances use to access objects stored in Cloud Storage buckets.”
• 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.”
• Application Default Credentials works with Cloud Run From the official documentation: “To authenticate to Cloud Run, set up Application Default Credentials.”
• Cloud Build works with Cloud SQL From the official documentation: “This page contains information and examples for connecting to a Cloud SQL instance from a service running in Cloud Build.”
• Cloud Build works with Secret Manager From the official documentation: “The secret is configured to be accessible by Cloud Run and Cloud Build.”
• Cloud Logging works with Compute Engine From the official documentation: “Compute Engine sends you Cloud Logging events for scheduled, started, or completed maintenance.”
• Cloud Run works with Cloud Storage From the official documentation: “Receive events from Cloud Storage in a Cloud Run service”
• Cloud Run is an alternative to GKE From the official documentation: “For your containerized websites, you can also deploy them to [Cloud Run](/run) in addition to [using GKE](#kubernetes-engine).”
• 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.”
• Cloud Storage depends on Application Default Credentials From the official documentation: “To authenticate to Cloud Storage, set up Application Default Credentials.”
• GKE depends on Compute Engine From the official documentation: “For example, GKE deploys clusters on Compute Engine VMs.”
• 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.”
• Identity and Access Management secures Cloud Storage From the official documentation: “Cloud Storage uses Identity and Access Management (IAM) for authorization.”
• 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 Cloud SQL From the official documentation: “Application Default Credentials are part of the client libraries you can use to access Cloud SQL.”
• Application Default Credentials configures Cloud Storage From the official documentation: “To authenticate to Cloud Storage, set up Application Default Credentials. For more information, see [Set up authentication for client libraries](/storage/docs/authentication#client-libs).”
• 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 Build works with GKE From the official documentation: “Remove the permission granted to Cloud Build to connect to GKE.”
• Cloud Build depends on Secret Manager From the official documentation: “Previously, for GitLab Enterprise and Bitbucket Data Center connections, when Secret Manager secrets were retrieved, permissions were checked against the Cloud Build service agent (P4SA) credentials only.”
• Cloud Logging depends on Application Default Credentials From the official documentation: “To authenticate to Logging, set up Application Default Credentials.”
• Cloud Logging is an alternative to Cloud Storage From the official documentation: “Instead, they are routed to either Cloud Storage (recommended) or Cloud Logging, depending on your organization's configuration.”