Urgent.News

What's breaking now, across thousands of outlets.

Tech

AgentCore and Foundry Wall Off the Session. Google Walls Off the Code.

An analyst uploads a spreadsheet to a shared analysis agent, the agent writes a script nobody reviewed, and whether that script can reach another analyst's session, or the agent's own credentials, depends on which cloud runs the agent. A platform engineer who runs that agent for a few hundred analysts has to pick a cloud before Monday's architecture review, and the three clouds give different…

Three major cloud providers, Amazon, Microsoft, and Google, recently announced updated AI agent platform services for analysts. Each service offers distinct default settings that protect user sessions and associated credentials in unique ways.

Amazon Bedrock's AgentCore defaults to isolating each session in a Firecracker microVM, ensuring no user or credential sharing. This setup uses a 1:1 mapping between sessions and EC2 instances, with a maximum runtime of 8 hours. The cost structure is based on vCPU and GB-hour usage, with a new runtime option priced at $0.1276/vCPU-hr.

Microsoft's Foundry Agent Service takes a different approach. Agents run within isolated VM-isolated sandboxes, preventing credential sharing across sessions. Sandboxes can scale per session, with a maximum of 2 vCPU and 4 GiB. Sessions persist for up to 14 days, after which idle timeout releases compute resources. Foundry offers a lower hourly rate of $0.085/vCPU-hr for its services.

Google's Gemini Enterprise Agent Platform differs by focusing on code execution isolation. Agent loops share a container with concurrent requests, while generated code runs in a separate gVisor-isolated sandbox that does not inherit the agent's credentials. Sandboxes can support up to 9 concurrent requests by default, with a maximum of 32 GB of memory per sandbox.

Google does not document whether concurrent requests within the same container can see each other's memory or files. Hourly billing is applied to containers, with no charges for idle time waiting for prompts.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

More from Thursday 19 November →