跳到正文
InfoQ· Renato Losio·· 8 小時前AI 評分51

Google 宣佈 Agent Compute Engine,讓 AI 智能體在隔離 microVM 中執行

Google Announces Agent Compute Engine for Secure AI Agent Execution

AI 導讀

Google 宣佈 Agent Compute Engine,這項託管服務會在隔離 microVM 中執行 AI 智能體,並支援透過檢查點暫停及恢復執行環境。服務把憑證、API keys 和 OAuth refresh tokens 留在沙箱外,由外部 Agent Gateway 驗證請求並注入所需憑證。服務尚未推出,Google 預計未來數月提供預覽,價格尚未公佈。

正文

Google recently announced Agent Compute Engine, a managed service that runs AI agents in isolated microVMs, with checkpointing capabilities to suspend and resume execution environments. The design keeps credentials, API keys, and OAuth refresh tokens outside the agent sandbox, using an external Agent Gateway to authenticate requests and inject the required secrets.

Google designed Agent Compute Engine to address three requirements at global scale: keeping sandboxes free of exploitable credentials, even when agents make mistakes; minimizing the cost and latency of resuming idle agents; and preserving persistent workspaces across sessions and operating system updates. The infrastructure team writes:

Agent Compute Engine achieves this by using copy-on-write memory sharing to run multiple agents on a single operating system template, and pausing idle microVMs via fast checkpoint and restore.

In the deep dive "Inside Agent Compute Engine," Ramanathan Venkatapathy and Rohit Jnagal, distinguished engineers at Google, describe the service’s architecture, covering microVM isolation, credential management, agent identity, storage, and scheduling at scale. They explain the strict separation between the agent harness and sandbox:

The orchestration harness (the brain) runs completely outside the execution sandbox (the hands), helping ensure that untrusted guest environments only execute explicit commands dispatched by the harness and stream output back. This boundary establishes a deterministic audit trail correlating every harness-initiated tool call with expected compute activity inside the sandbox.

Google Agent Compute Engine

Source: Google blog

The architecture supports four main workload categories: interactive consumer and enterprise agents that execute code, browse the web, and perform actions; persistent Linux workspaces for autonomous software engineering; large-scale parallel environments for model evaluation and reinforcement learning; and lightweight, sandboxed execution environments for dynamic logic in Google services.

Venkatapathy and Jnagal also describe how the cloud provider uses the platform internally for Gemini, Gemini for Business, the agentic development platform Antigravity, and model evaluation workloads.

Separately, Google offers Agent Substrate, an open-source, Kubernetes-native runtime for running AI agents in isolated environments. Agent Substrate manages sandbox lifecycles independently of the underlying compute infrastructure, allowing idle agents to be suspended while preserving their state and resuming execution on available workers when needed.

In the article "Google's Agent Compute Engine: A MicroVM Sandbox With No Credentials Inside, and What Google Has Not Shipped Yet," Harel Asaf, AI specialist at Elementor, examines the security architecture, the separation of credentials from agent execution environments, and the gaps between Google's announcement and what is currently available. Asaf warns:

The deep dive gives no boot time, price or density figure for Agent Compute Engine itself. It says developers will control each environment's image, identity, network access and lifecycle, while Google manages the fleet, and that the service is targeted for preview in the coming months. The numbers in the announcement belong to Agent Substrate.

Google is not the only provider offering managed, isolated execution environments for AI agents, with AWS and Azure providing similar capabilities through Bedrock AgentCore and Foundry Agent Service. However, Google’s approach keeps credentials outside agent sandboxes and injects them through an external gateway.

Google also expanded its agent governance capabilities with centralized identity and policy enforcement: the governance stack includes Agent Gateway for traffic control and policy enforcement, Agent Registry for tracking approved agents and tools, SPIFFE-based Agent Identity for authentication and auditing, and OpenTelemetry-compatible observability for monitoring model calls and tool invocations.

Agent Compute Engine is not yet available, and pricing has not been announced. The cloud provider is targeting a preview in the coming months. While Agent Substrate is portable across Kubernetes environments, Agent Compute Engine itself is limited to Google Cloud.

About the Author

Renato Losio

Show moreShow less

來源:InfoQ · infoq.com