AlloyDB

Related topics

• CMEK secures AlloyDB From the official documentation: “Enable CMEK for AlloyDB Clusters”
• 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 federated queries From the official documentation: “Federated queries let you send a query statement to AlloyDB, Spanner, or Cloud SQL databases and get the result back as a temporary table.”
• 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.”
• AlloyDB works with Compute Engine From the official documentation: “This page describes how to connect the `psql` client tool from Compute Engine to an AlloyDB instance.”
• customer-managed encryption keys secures AlloyDB From the official documentation: “Enable customer-managed encryption keys (CMEK) in the AlloyDB cluster to gain more control over data encryption and key management.”
• IVFFlat is part of AlloyDB From the official documentation: “You can create `ScaNN`, `IVF`, `IVFFlat`, and `HNSW` indexes with AlloyDB.”
• pgvector is part of AlloyDB From the official documentation: “This example requires: 1. An AlloyDB instance with pgvector extension and PUBLIC IP enabled”
• Access Transparency secures AlloyDB From the official documentation: “You can use Access Approval and Access Transparency to control access to AlloyDB instances by Google personnel who support the service.”
• AlloyDB works with Cloud Logging From the official documentation: “Database Migration Service and AlloyDB use Cloud Logging.”
• AlloyDB works with Cloud Storage From the official documentation: “For example, if you frequently write data to AlloyDB from a Cloud Storage bucket in the `us-central1` (Iowa) region, create your AlloyDB cluster in the `us-central1` region.”
• AlloyDB works with Dataflow From the official documentation: “Demonstrates how to generate embeddings from data and ingest them into AlloyDB using Apache Beam and Dataflow for scalable data processing.”
• AlloyDB works with IAM database authentication From the official documentation: “For AlloyDB, only Identity and Access Management (IAM) database authentication is supported.”
• AlloyDB works with VPC Service Controls From the official documentation: “This page provides an overview of VPC Service Controls, a Google Cloud feature that integrates with AlloyDB to secure data and resources.”
• IAM database authentication secures AlloyDB
• VPC Service Controls secures AlloyDB From the official documentation: “VPC Service Controls helps mitigate the risk of data exfiltration from AlloyDB instances.”
• customer-managed encryption keys depends on Cloud Key Management Service From the official documentation: “These keys are created and managed using Cloud KMS.”
• Cloud SQL works with Database Migration Service From the official documentation: “Gives Cloud Database Migration service account access to Cloud SQL resources.”
• 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 Cloud SQL From the official documentation: “Add credentials to connect BigQuery to Cloud SQL.”
• 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”
• 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 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.”
• 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.”
• Cloud Key Management Service works with customer-managed encryption keys From the official documentation: “With CMEK, Cloud Key Management Service wraps your stored volume keys.”
• Cloud Logging works with Cloud SQL From the official documentation: “Cloud SQL uses Cloud Logging.”
• 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 SQL depends on Compute Engine From the official documentation: “Cloud SQL uses Compute Engine virtual machines (VMs) with persistent storage disks.”
• 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 SQL works with Identity and Access Management From the official documentation: “This page describes how Cloud SQL is integrated with IAM .”
• CMEK secures Cloud SQL From the official documentation: “Enable CMEK for Cloud SQL Databases”
• 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 Key Management Service works with Cloud SQL From the official documentation: “Cloud KMS integrates with Cloud SQL.”
• Cloud Storage works with customer-managed encryption keys From the official documentation: “Cloud Storage supports CMEK for routing logs.”
• CMEK secures BigQuery From the official documentation: “Enable CMEK for BigQuery Tables”
• 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).”
• 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).”
• CMEK secures Cloud Storage From the official documentation: “Enable CMEK for Cloud Storage Buckets”
• customer-managed encryption keys is part of Cloud Key Management Service From the official documentation: “The Cloud KMS keys that you create are customer-managed keys.”
• 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 works with federated queries From the official documentation: “BigQuery Cloud SQL federation enables BigQuery to query data residing in Cloud SQL in real time, without copying or moving data.”
• 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.”
• VPC Service Controls secures Cloud SQL From the official documentation: “VPC Service Controls perimeters protect the Cloud SQL Admin API.”
• BigQuery works with Cloud Key Management Service From the official documentation: “Checks if BigQuery tables are encrypted using CustomerManaged Encryption Keys (CMEK) in Cloud KMS.”
• BigQuery depends on Cloud Logging From the official documentation: “BigQuery utilizes Cloud Logging for some of your log data.”