Committed Use Discounts

Related topics

• Committed Use Discounts is part of Compute Engine From the official documentation: “Commitments are not affected by future changes to [on-demand prices](https://cloud.google.com/compute/vm-instance-pricing) of your committed Compute Engine resources.”
• Committed Use Discounts depends on Cloud Billing From the official documentation: “You can purchase CUDs from any Cloud Billing account, and the discount applies to any eligible usage in projects that the Cloud Billing account pays for.”
• Committed Use Discounts is part of Cloud SQL From the official documentation: “*Committed use discounts (CUDs)* for Cloud SQL provide deeply discounted prices in exchange for your commitment to continuously use database instances in a particular region for a one- or three-year term.”
• 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.”
• 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”
• 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.”
• BigQuery works with Cloud Billing From the official documentation: “[Export your Cloud Billing pricing data to BigQuery](/billing/docs/how-to/export-data-bigquery)”
• 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 Logging works with Cloud SQL From the official documentation: “Cloud SQL uses Cloud Logging.”
• 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 .”
• Identity and Access Management secures BigQuery From the official documentation: “Access to BigQuery data from AlloyDB is managed through IAM.”
• 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 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).”
• 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 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 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.”
• BigQuery depends on Cloud Logging From the official documentation: “BigQuery utilizes Cloud Logging for some of your log data.”
• BigQuery works with Identity and Access Management From the official documentation: “BigQuery uses Identity and Access Management (IAM) for authorization.”
• Cloud Logging works with Compute Engine From the official documentation: “Compute Engine sends you Cloud Logging events for scheduled, started, or completed maintenance.”
• 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.”
• 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.”
• 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.”
• Identity and Access Management secures Cloud Billing From the official documentation: “Cloud Billing uses Identity and Access Management (IAM) for authorization.”
• Identity and Access Management secures Compute Engine From the official documentation: “Compute Engine uses Identity and Access Management (IAM) for authorization.”
• BigQuery works with Compute Engine From the official documentation: “Compute Engine integrates with Google Cloud technologies such as Cloud Storage, Google Kubernetes Engine, and BigQuery, to extend beyond the basic computational capability to create more complex and sophisticated applications.”
• Cloud Billing works with Compute Engine From the official documentation: “To report usage to Cloud Billing, you can use any of the following services: - A Google Cloud service, such as Compute Engine that measures the life of a virtual machine (VM).”
• Cloud Billing works with Vertex AI From the official documentation: “Cloud Billing bills overages for Gemini Enterprise and AI developer tools under Vertex AI API.”
• Cloud Logging works with Identity and Access Management From the official documentation: “This document helps you understand how Cloud Logging uses [Identity and Access Management (IAM)](/iam/docs/overview) roles and permissions to control access to Logging resources.”
• 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 Auth Proxy depends on Compute Engine From the official documentation: “To establish this connection, a Compute Engine VM in the connector network runs the Cloud SQL Auth Proxy.”