Cloud SQL

Related topics

• Cloud SQL works with Cloud SQL Auth Proxy From the official documentation: “The Cloud SQL Auth Proxy uses the Cloud SQL API to interact with your SQL instance.”
• Cloud SQL works with Database Migration Service From the official documentation: “Gives Cloud Database Migration service account access to Cloud SQL resources.”
• Cloud SQL Auth Proxy secures Cloud SQL From the official documentation: “The Cloud SQL proxy provides encryption between the proxy and instance”
• BigQuery works with Cloud SQL From the official documentation: “Add credentials to connect BigQuery to Cloud SQL.”
• Cloud SQL works with Vertex AI From the official documentation: “[Integrate Cloud SQL with Vertex AI](/sql/docs/mysql/integrate-cloud-sql-with-vertex-ai)”
• 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.”
• Cloud SQL works with Compute Engine From the official documentation: “This page describes how to use the mysql client, installed on a Compute Engine instance, to connect to Cloud SQL.”
• point-in-time recovery is part of Cloud SQL From the official documentation: “Cloud SQL provides the following options to restore your instance using PITR:”
• authorized networks is part of Cloud SQL From the official documentation: “Remove all `Authorized Networks` entries from the Cloud SQL<br>instance if you can.”
• Cloud Logging works with Cloud SQL From the official documentation: “Cloud SQL uses Cloud Logging.”
• read replica is part of Cloud SQL From the official documentation: “This page applies to replicas of a Cloud SQL instance.”
• 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 SQL depends on Compute Engine From the official documentation: “Cloud SQL uses Compute Engine virtual machines (VMs) with persistent storage disks.”
• Cloud SQL works with Identity and Access Management From the official documentation: “This page describes how Cloud SQL is integrated with IAM .”
• customer-managed encryption keys secures Cloud SQL From the official documentation: “Enable CMEK for Cloud SQL Databases”
• IAM database authentication is part of Cloud SQL From the official documentation: “For more information, see [Manage users with IAM database authentication for Cloud SQL](/sql/docs/postgres/add-manage-iam-users).”
• 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).”
• VPC Service Controls secures Cloud SQL From the official documentation: “VPC Service Controls perimeters protect the Cloud SQL Admin API.”
• Database Migration Service depends on Cloud SQL From the official documentation: “For heterogeneous Oracle migrations to Cloud SQL, Database Migration Service requires that you first create and configure your Cloud SQL destination instance.”
• IAM database authentication secures Cloud SQL From the official documentation: “Make sure that the `cloudsql.iam_authentication` flag is set to `on` in your Cloud SQL for MySQL instance.”
• authorized networks configures Cloud SQL From the official documentation: “Non-RFC 1918 address ranges must be configured in Cloud SQL as [authorized networks](/sql/docs/mysql/authorize-networks).”
• authorized networks secures Cloud SQL From the official documentation: “Non-RFC 1918 address ranges must be configured in Cloud SQL as [authorized networks](/sql/docs/sqlserver/authorize-networks).”
• Bigtable is an alternative to Cloud SQL From the official documentation: “If you're interested in evaluating how the performance of your on-premises databases compares to [Cloud SQL](/sql), [Spanner](/spanner), [Firestore](/firestore), or [Bigtable](/bigtable), you could implement a PoC where the same business logic uses different databases.”
• 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 SQL works with customer-managed encryption keys From the official documentation: “To learn more about using customer-managed encryption keys with Cloud SQL, see [Overview of customer-managed encryption keys](/sql/docs/postgres/cmek).”
• Cloud SQL works with IAM database authentication From the official documentation: “For Cloud SQL, both IAM database authentication and built-in database authentication are supported.”
• Cloud SQL works with VPC Service Controls From the official documentation: “Make sure that you configure VPC Service Controls so that the project that hosts the CA Service CA pool and CA<br>and the project that hosts Cloud SQL belong to the same service perimeter.”
• customer-managed encryption keys is part of Cloud SQL From the official documentation: “Cloud SQL also lets you add another layer of encryption to data using [customer-managed encryption keys (CMEK)](/sql/docs/postgres/cmek).”
• BigQuery is an alternative to Cloud Storage From the official documentation: “The `import_result_sink` must be a Cloud Storage path or a BigQuery table.”
• BigQuery works with Cloud Logging From the official documentation: “BigQuery utilizes Cloud Logging for some of your log data.”
• BigQuery works with Cloud Storage From the official documentation: “External BigQuery data source backed by Cloud Storage”
• BigQuery works with Dataflow From the official documentation: “Read from BigQuery to Dataflow”
• VPC Service Controls secures BigQuery From the official documentation: “BigQuery data is protected with VPC Service Controls”
• BigQuery works with Bigtable From the official documentation: “External BigQuery data source backed by Bigtable”
• Cloud Logging works with customer-managed encryption keys From the official documentation: “To use Cloud Logging with Customer-managed encryption keys (CMEK), you must complete the steps in the [Enable CMEK for an organization](/logging/docs/routing/managed-encryption#enable) page in the Cloud Logging documentation.”
• customer-managed encryption keys secures Cloud Storage From the official documentation: “CMEKs encrypt data at rest in Cloud SQL, Cloud Storage, and within GKE clusters.”
• Cloud Storage works with Database Migration Service From the official documentation: “Database Migration Service replicates data from SQL Server backup and transaction log files that you upload to a Cloud Storage bucket.”
• Cloud Storage works with Dataflow From the official documentation: “Write from Dataflow to Cloud Storage”
• Cloud Build works with Cloud Storage From the official documentation: “Create the Cloud Storage bucket for Cloud Build logs:”
• customer-managed encryption keys secures BigQuery From the official documentation: “You can either create CMEKs manually to protect your BigQuery resources or use Cloud KMS Autokey.”
• Identity and Access Management secures Database Migration Service From the official documentation: “You can get and set permissions for Database Migration Service using the Google Cloud console, the IAM methods of the API, or the Google Cloud CLI.”
• 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 Storage works with customer-managed encryption keys From the official documentation: “Cloud Storage supports CMEK for routing logs.”
• Identity and Access Management secures BigQuery From the official documentation: “Access to BigQuery data from AlloyDB is managed through IAM.”
• VPC Service Controls secures Cloud Storage From the official documentation: “Storage Transfer Service supports transfers to Cloud Storage buckets protected by VPC Service Controls.”
• BigQuery works with Vertex AI From the official documentation: “Token usage directly correlates with your Vertex AI billing for BigQuery generative AI functions that use Gemini models.”
• Cloud Logging works with Database Migration Service From the official documentation: “Database Migration Service uses Cloud Logging.”
• Cloud Storage works with Identity and Access Management From the official documentation: “To learn how to use IAM with Cloud Storage, see [Using IAM Permissions](/storage/docs/access-control/using-iam-permissions).”
• customer-managed encryption keys secures Bigtable From the official documentation: “In a CMEK-protected instance, Bigtable uses your CMEK key to protect your data at rest.”
• Identity and Access Management secures Cloud Storage From the official documentation: “Cloud Storage uses Identity and Access Management (IAM) for authorization.”
• Identity and Access Management secures Vertex AI From the official documentation: “A Vertex AI model with an active endpoint that you have Identity and Access Management (IAM) permission to access.”
• 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 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 Storage works with point-in-time recovery From the official documentation: “For data retention needs beyond 14 weeks, you can use PITR to create an export of your entire database and save this data in Cloud Storage indefinitely.”
• customer-managed encryption keys works with Database Migration Service From the official documentation: “Database Migration Service supports CMEK in the migration job to secure the data at rest.”
• Database Migration Service depends on Cloud Logging From the official documentation: “Database Migration Service uses Cloud Logging.”
• AlloyDB works with BigQuery From the official documentation: “By integrating AlloyDB and BigQuery, you can achieve a seamless flow of data between your transactional database and your data warehouse, which supports real-time analytics and helps you build powerful interactive applications.”
• AlloyDB works with Database Migration Service From the official documentation: “Database Migration Service supports continuous migrations from source databases to AlloyDB destination databases.”
• AlloyDB works with Vertex AI From the official documentation: “Reference architecture for a RAG-capable generative AI application using Vertex AI and AlloyDB for PostgreSQL.”
• 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).”