OS Config agent

Related topics

• Cloud Logging works with OS Config agent From the official documentation: “When debug logging is enabled, the OS Config agent writes log entries to Cloud Logging and the serial port console.”
• OS Config agent works with OS Config API From the official documentation: “Then the VM Manager API notifies the OS Config agent that is running on the target VMs to start patching.”
• OS Config agent depends on OS Config API From the official documentation: “The network settings on the VPC network or the instance didn't allow the OS Config agent to communicate with the OS Config API.”
• OS Config agent works with Patch From the official documentation: “The Patch service is unable to communicate with the OS Config agent on the VM.”
• Patch depends on OS Config agent From the official documentation: “To use the Patch feature, you must set up the OS Config API and install the OS Config agent.”
• VM Manager depends on OS Config agent From the official documentation: “If the OS config agent is not available for a particular operating system, you cannot enable VM Manager for a VM that runs this operating system.”
• Cloud Logging works with Compute Engine From the official documentation: “Compute Engine sends you Cloud Logging events for scheduled, started, or completed maintenance.”
• Cloud Logging works with Security Command Center From the official documentation: “Viewing findings in Cloud Logging is only available if you activate the Premium or Enterprise tier of Security Command Center.”
• Patch is part of VM Manager From the official documentation: “This page describes the Patch feature in VM Manager and how it works.”
• 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 works with Private Google Access From the official documentation: “Cloud Logging captures all API requests made from VM instances in subnets that have Private Google Access enabled.”
• Security Command Center works with VM Manager From the official documentation: “If you [enable VM Manager](/compute/docs/manage-os), it<br>automatically writes findings from its vulnerability reports to Security Command Center.”
• 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.”
• 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).”
• Cloud Asset Inventory works with Cloud Logging From the official documentation: “When real-time feeds fail to send resources or IAM policy updates through Pub/Sub, Cloud Asset Inventory logs the error status and message in Logging.”
• 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 Logging is an alternative to Security Command Center From the official documentation: “After you revoke compromised credentials and restore your service, review all access to your Google Cloud resources. You can use Cloud Logging or Security Command Center.”
• Cloud Logging works with VPC Service Controls From the official documentation: “This page describes how you can find VPC Service Controls errors using Cloud Logging.”
• Compute Engine depends on Private Google Access From the official documentation: “Enable [Private Google Access](/database-migration/docs/postgresql-to-alloydb/vpc/docs/configure-private-google-access#enabling-pga) on the subnet used for the proxy. This is required to allow the Compute Engine instance to download the necessary Docker images from the Google…”
• Compute Engine works with Private Google Access From the official documentation: “Compute Engine instance with only an internal IP address tries to reach the external IP address of Google APIs and services, but Private Google Access is not enabled in the instance's subnet.”
• Compute Engine works with Security Command Center From the official documentation: “After you activate Security Command Center, it starts to analyze, or scan, your resources for Compute Engine and other Google Cloud services.”
• OS Config API works with Private Google Access From the official documentation: “If your VM is running within a private VPC network and does not have public internet access, check that you have enabled [Private Google Access](/vpc/docs/configure-private-google-access). After you enable Private Google Access, check that the VM can communicate with the OS…”
• Patch depends on OS Config API From the official documentation: “To use the Patch feature, you must set up the OS Config API and install the OS Config agent.”
• Security Command Center depends on Cloud Asset Inventory From the official documentation: “Security Command Center uses Cloud Asset Inventory as its primary source of truth for assets.”
• Security Command Center depends on Cloud Logging From the official documentation: “By using Security Command Center, you can see when high-risk threats such as malware, cryptomining, unauthorized access to Google Cloud resources, outgoing DDoS attacks, port scanning, and brute-force SSH have been detected based on your Cloud Logging logs.”
• Security Command Center secures Compute Engine From the official documentation: “Security Command Center performs [agentless](#runtime) and [log-based](#log-based) monitoring of Compute Engine resources.”
• Security Command Center works with VPC Service Controls From the official documentation: “[Enable Security Command Center with VPC Service Controls](/vpc-service-controls/docs/supported-products#table_security_command_center).”
• 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.”
• VPC Service Controls secures Cloud Logging From the official documentation: “The API for Cloud Logging can be protected by VPC Service Controls and the product can be used normally inside service perimeters.”
• VPC Service Controls secures Security Command Center From the official documentation: “VPC Service Controls protects project-level Security Command Center API resources.”