Your Agent Pilot Just Cleared Security Review
AWS and Google shipped the same primitive this quarter: live web retrieval for agents where the query never leaves your cloud account. Here is what it unblocks, and what it quietly buys you into.
AWS and Google shipped the same primitive this quarter: live web retrieval for agents where the query never leaves your cloud account. Here is what it unblocks, and what it quietly buys you into. What happened AWS has taken Web Search on Amazon Bedrock AgentCore to general availability. AWS's own announcement says it lets agents "ground responses in current, accurate web knowledge while keeping data residency within your secured AWS environment with zero data egress " — that phrase is AWS's, not ours. The tool is exposed as a built-in connector target on the AgentCore gateway using the Model Context Protocol (MCP), and it is generally available in exactly one region: US East (N. Virginia). AWS dates the announcement to June 2026 on its own page; later dates circulating in aggregator coverage do not match the primary, so we cite the primary. Google Cloud, in the same cycle, launched the Gemini Enterprise Agent Platform, described in its announcement as "our new, comprehensive platform to build, scale, govern, and optimize agents." The consolidation is the headline: "all Vertex AI services and roadmap evolutions will be delivered exclusively through the Agent Platform, rather than as a standalone service". Governance arrives as three named primitives — Agent Identity, Agent Registry and Agent Gateway — with the gateway acting as "the air traffic control for your agent ecosystem," carrying "Model Armor protections to safeguard against prompt injection and data leakage". Google claims first-class access to more than 200 models through Model Garden, including third-party models such as Anthropic's Claude Opus, Sonnet and Haiku — a vendor-reported figure, unaudited. Neither company published pricing for these capabilities. Secondary commentary also claims Google folded Agentspace into the new platform; Google's own announcement does not mention Agentspace by name, so we treat that as unverified. Why it matters The objection that killed most enterprise agent pilots was never about model quality. It was one line in a security questionnaire: our users' queries would be sent to a third-party search index. That line triggered a DPA negotiation, a vendor security review, and a legal read of somebody else's terms of service. Two hyperscalers have now answered it with the same architecture — operate the index themselves, keep the call inside the account boundary — which means the objection is no longer yours to solve. It is a clause in a contract you already signed. For a CPO, that reprices a whole class of roadmap items. Anything parked behind "we would need grounded, cited, current answers" moves from a build to a configuration. For a founder selling into regulated buyers, it is a sales asset: your customer's security team gets a first-party document from AWS or Google instead of a diagram of your architecture. For a CTO, the interesting detail is protocol-level: AWS shipped this over MCP, an open protocol, while Google's Agent Gateway is proprietary. That d