region

Related topics

• zone is part of region From the official documentation: “Finally, regions are divided into *zones*.”
• Cloud SQL configures region From the official documentation: “When you create a Cloud SQL instance, you choose a [region](/docs/geography-and-regions) where the instance and its data are stored.”
• organization policy configures region From the official documentation: “Backups fail if they are in a region the organization policy does not allow.”
• Cloud KMS key depends on region From the official documentation: “The Cloud KMS key ring location must match the region where you want to create Cloud SQL instance. A multi-region or global region key **will not** work. The Cloud SQL instance create request fails if the regions don't match.”
• region configures Cloud Build From the official documentation: “`--region`=`REGION` - The region of the Cloud Build Service to use.”
• region configures regional secret From the official documentation: “- **Region**: Stores the secret in a single region for minimal latency.”
• 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 Storage From the official documentation: “Sample to load Avro data from Cloud Storage into a new BigQuery table”
• Cloud SQL works with Cloud SQL Auth Proxy From the official documentation: “Download the Cloud SQL Auth Proxy.”
• BigQuery works with Cloud SQL From the official documentation: “Add credentials to connect BigQuery to Cloud SQL.”
• 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 Auth Proxy secures Cloud SQL From the official documentation: “The Cloud SQL proxy provides encryption between the proxy and 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.”
• BigQuery works with Cloud Key Management Service From the official documentation: “A Cloud KMS key is considered available and accessible by BigQuery under the following conditions:”
• 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 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 Build works with Secret Manager From the official documentation: “The secret is configured to be accessible by Cloud Run and Cloud Build.”
• 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 Key Management Service works with Cloud SQL From the official documentation: “Cloud KMS integrates with Cloud SQL.”
• Cloud Key Management Service works with service account From the official documentation: “When your Database Migration Service migration jobs have CMEK enabled, you need to use a service account to request key access from Cloud Key Management Service.”
• Cloud SQL works with Secret Manager From the official documentation: “This page describes four use cases for using Secret Manager to manage secrets with Cloud SQL:”
• 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 Storage works with service account From the official documentation: “The service account can manage objects in the Cloud Storage bucket.”
• Secret Manager secures Cloud SQL From the official documentation: “Secret Manager provides centralized and secure storage of sensitive data such as Cloud SQL configuration.”
• Secret Manager works with service account From the official documentation: “The service account can access the secret data.”
• 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.”
• BigQuery depends on Cloud Storage From the official documentation: “BigQuery relies on Cloud Storage for staging file data and supports reading from and writing to several other sources and Google Cloud services.”
• BigQuery works with service account From the official documentation: “The service account can be used by services, such as Cloud Run, to read and modify data in the BigQuery dataset.”
• Cloud Build works with Cloud Key Management Service From the official documentation: “This page explains how to use encrypted information from Cloud KMS in Cloud Build.”
• Cloud Build depends on Cloud Storage From the official documentation: “Cloud Build uses Cloud Storage to store build resources.”
• Cloud Build depends on service account From the official documentation: “Cloud Build uses a service account to execute builds on your behalf.”
• Cloud Key Management Service works with Cloud KMS key From the official documentation: “To change the **Encryption** option to use your own cryptographic key with the [Cloud Key Management Service](/kms/docs/key-management-service), select **Cloud KMS key**.”
• Cloud Key Management Service works with Secret Manager From the official documentation: “If you want to control your encryption keys, then you can use customer-managed encryption keys (CMEKs) in [Cloud KMS](/kms/docs) with CMEK-integrated services including Secret Manager.”
• Cloud Key Management Service is an alternative to Secret Manager From the official documentation: “Secret Manager is the recommended technique for managing sensitive data with Cloud Build. For existing projects, you can continue using Cloud KMS, but for new projects, use Secret Manager.”
• Cloud KMS key secures BigQuery From the official documentation: “Protect a new table with a customer-managed encryption key by setting the [Table.encryption_configuration](/python/docs/reference/bigquery/latest/google.cloud.bigquery.table.Table#google_cloud_bigquery_table_Table_encryption_configuration) property to an…”
• Cloud KMS key is part of Cloud Key Management Service From the official documentation: “Decrypt ciphertext (to a plaintext file) using a Cloud Key Management Service (Cloud KMS) key.”
• Cloud KMS key secures Cloud Storage From the official documentation: “Run the [`gcloud storage batch-operations jobs create`](/sdk/gcloud/reference/storage/batch-operations/jobs/create) command to [create a Storage batch operations job by using the manifest…”
• 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 is part of zone From the official documentation: “Zones are sub-locations in a region where you can create zonal resources such as Cloud SQL instances.”
• Cloud SQL works with zone From the official documentation: “Zones are sub-locations in a region where you can create zonal resources such as Cloud SQL instances.”
• 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).”
• regional secret is part of Secret Manager From the official documentation: “To authenticate, use a [built-in database user](/sql/docs/sqlserver/built-in-authentication) account. Store the user's password in a [regional secret](/secret-manager/regional-secrets/create-regional-secret) in Secret Manager in the same region as your Cloud SQL instance, and…”
• service account depends on BigQuery From the official documentation: “Each feature view uses a service account to access the source data in BigQuery during sync.”
• service account depends on Cloud Key Management Service From the official documentation: “When your Database Migration Service migration jobs have CMEK enabled, you need to use a service account to request key access from Cloud Key Management Service.”
• service account depends on Cloud KMS key From the official documentation: “When you create a Cloud SQL instance with CMEK, the service account for the project that will contain your instance must be granted access to the key.”
• service account secures Cloud SQL From the official documentation: “Cloud SQL uses service accounts for authentication between Cloud SQL and other Google Cloud products.”