VM Manager

Related topics

• Ops Agent works with VM Manager From the official documentation: “Use VM Manager to automatically install the Ops Agent during VM creation.”
• patch is part of VM Manager From the official documentation: “In the Google Cloud console, go to the **Compute Engine** > **VM Manager** > **Patch** page.”
• OS Config is part of VM Manager From the official documentation: “Both types of policies rely on [OS Config](/compute/docs/os-configuration-management) features provided by [VM Manager](/compute/docs/vm-manager), but the implementations are different.”
• Cloud Asset Inventory works with VM Manager From the official documentation: “By exporting VM Manager data from Cloud Asset Inventory to BigQuery, you can run advanced queries to check whether VM Manager is enabled, view OS Config agent versions, and inspect operating system details across all projects in your organization.”
• Cloud Monitoring API works with VM Manager From the official documentation: “When a patch job is created, VM Manager posts the aggregate VM state to the Cloud Monitoring API.”
• Google Cloud CLI configures VM Manager From the official documentation: “Overview Learn about the Google Cloud CLI, which enables you to easily manage your VM Manager resources.”
• Ops Agent depends on VM Manager From the official documentation: “Ops Agent installation uses VM Manager and requires permissions to activate the VM Manager API and create a policy.”
• patch job works with VM Manager From the official documentation: “**Description**: A patch job ran by VM Manager.”
• Terraform provider for Google Cloud configures VM Manager From the official documentation: “You can use the *Terraform provider for Google Cloud* to provision and manage Google Cloud resources, including VM Manager.”
• VM Manager is part of Compute Engine From the official documentation: “Agent policies use the [VM Manager](/compute/docs/vm-manager) suite of tools in Compute Engine to manage [OS policies](/compute/docs/os-configuration-management), which can automate the deployment and maintenance of software configurations like the Ops Agent.”
• VM Manager works with VPC Service Controls From the official documentation: “VM Manager supports projects in [VPC Service Controls](/vpc-service-controls/docs/supported-products#table_vm_manager) service perimeters.”
• Compute Engine works with Ops Agent From the official documentation: “In Compute Engine VMs, the Ops Agent can collect logs and most metrics.”
• Application Default Credentials secures Bigtable From the official documentation: “To authenticate to Bigtable, set up Application Default Credentials.”
• Application Default Credentials works with Cloud Storage From the official documentation: “To authenticate to Cloud Storage, set up Application Default Credentials.”
• Cloud Logging works with Ops Agent From the official documentation: “Is the agent sending logs to Cloud Logging?”
• 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.”
• Bigtable depends on Application Default Credentials From the official documentation: “To authenticate to Bigtable, set up Application Default Credentials.”
• Cloud Monitoring depends on Application Default Credentials From the official documentation: “To authenticate to Monitoring, set up Application Default Credentials.”
• Cloud Monitoring works with Ops Agent From the official documentation: “The Ops Agent sends metrics to Cloud Monitoring.”
• Cloud Storage works with Google Cloud CLI From the official documentation: “The gcloud CLI is the preferred command line tool for accessing Cloud Storage.”
• Application Default Credentials works with Bigtable From the official documentation: “To authenticate to Bigtable, set up Application Default Credentials.”
• Application Default Credentials secures Compute Engine From the official documentation: “To authenticate to Compute Engine, set up Application Default Credentials.”
• Google Cloud CLI configures Application Default Credentials From the official documentation: “To configure ADC with a user account, you use the Google Cloud CLI:”
• Cloud Logging works with Cloud Monitoring From the official documentation: “You can store and view query-response activity logs in Cloud Logging and set up logs-based monitoring by using Cloud Monitoring.”
• 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 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.”
• VPC Service Controls secures Artifact Registry From the official documentation: “If your VPC Service Controls settings are blocking access to Artifact Registry, you must add the Artifact Registry service to the service perimeter of your VPC Service Controls.”
• Cloud Asset Inventory depends on Application Default Credentials From the official documentation: “To authenticate to Cloud Asset Inventory, set up Application Default Credentials.”
• 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 depends on Application Default Credentials From the official documentation: “To authenticate to Cloud Storage, set up Application Default Credentials.”
• Compute Engine works with Google Cloud CLI From the official documentation: “Some applications might use commands from the gcloud CLI, which is included by default in most Compute Engine images.”
• Ops Agent depends on Cloud Monitoring API From the official documentation: “To use the Ops Agent to write logs and metrics, you must enable the Cloud Logging API and Cloud Monitoring API on your Google Cloud project.”
• VPC Service Controls secures Cloud Storage From the official documentation: “Storage Transfer Service supports transfers to Cloud Storage buckets protected by VPC Service Controls.”
• Application Default Credentials works with Cloud Asset Inventory From the official documentation: “To authenticate to Cloud Asset Inventory, set up Application Default Credentials.”
• Application Default Credentials secures Cloud Asset Inventory From the official documentation: “To authenticate to Cloud Asset Inventory, set up Application Default Credentials.”
• Application Default Credentials secures Cloud Monitoring From the official documentation: “To authenticate to Monitoring, set up Application Default Credentials.”
• 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 Google Cloud CLI From the official documentation: “To do so, provide your user credentials to ADC by using the Google Cloud CLI.”
• Artifact Registry works with Google Cloud CLI From the official documentation: “Before you can push or pull images, configure Docker to use the Google Cloud CLI to authenticate requests to Artifact Registry.”
• Bigtable is an alternative to Cloud Storage From the official documentation: “If the joining data is in the gigabyte or terabyte range, use either Bigtable or Cloud Storage to merge the joining data to the driving data, depending on the nature of the data.”
• Cloud Asset Inventory works with Cloud Storage From the official documentation: “To analyze changes, export your asset metadata to BigQuery or Cloud Storage.”
• Cloud Asset Inventory works with VPC Service Controls From the official documentation: “VPC Service Controls can be used with Cloud Asset Inventory to provide additional security for your assets.”
• 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.”
• Cloud Monitoring API is part of Cloud Monitoring From the official documentation: “The Cloud Monitoring API, client libraries, metric and resource type references, and MCP tools let you programmatically access and manage Cloud Monitoring.”
• Google Cloud CLI depends on Application Default Credentials From the official documentation: “To authenticate with the gcloud CLI, generate a local Application Default Credentials (ADC) file by running this command.”
• Ops Agent depends on Compute Engine From the official documentation: “The agents run only on Compute Engine VMs; these procedures apply only to that platform.”
• VPC Service Controls secures Compute Engine From the official documentation: “To further protect your Compute Engine resources, you can protect them using [VPC Service Controls](/vpc-service-controls/docs/overview).”
• Application Default Credentials works with Cloud Logging From the official documentation: “To authenticate to Logging, set up Application Default Credentials.”
• Application Default Credentials configures Compute Engine From the official documentation: “To authenticate to Compute Engine, set up Application Default Credentials.”
• Application Default Credentials is an alternative to Google Cloud CLI From the official documentation: “You can authenticate to [the Vision API](/vision/docs/reference/rest) by using your [gcloud CLI credentials](/sdk/docs/authenticate) or by using [Application Default Credentials](/docs/authentication/application-default-credentials).”
• Artifact Registry works with Cloud Logging From the official documentation: “Artifact Registry sends the following types of audit log data to Cloud Logging:”
• Artifact Registry works with Cloud Monitoring From the official documentation: “By default, Artifact Registry is configured to do the following: - Send system logs and audit logs to Cloud Logging - Send system metrics and resource metrics to Cloud Monitoring”
• Artifact Registry depends on Cloud Storage From the official documentation: “The registry service hosts your custom images in Cloud Storage under your Google Cloud project.”
• Artifact Registry works with Cloud Storage From the official documentation: “| Artifact Registry | Stored in Cloud Storage, for each data chunk | |”
• Artifact Registry works with Compute Engine From the official documentation: “Compute Engine can pull containers directly from Artifact Registry repositories so you can run containerized workloads on virtual machine (VM) instances.”
• Bigtable works with Cloud Asset Inventory From the official documentation: “Cloud Asset Inventory, which provides inventory services based on a time series database, supports and returns Bigtable resources types.”
• Bigtable works with Cloud Monitoring From the official documentation: “Bigtable exports [usage metrics](/monitoring/api/metrics_gcp_a_b#gcp-bigtable) to [Cloud Monitoring](/monitoring).”
• Bigtable works with Cloud Monitoring API From the official documentation: “You can monitor Bigtable visually, using charts that are available in the [Google Cloud console](https://console.cloud.google.com/), or you can programmatically call the Cloud Monitoring API.”