The same agent and the same two tools built with Microsoft Agent Framework, LangGraph and Google ADK, run against a scripted model that calls missing tools, sends wrong types, repeats a refund and never stops. The defaults differ, and a few lines of configuration bring them into line.
Read more →Tag: AI Agents
Step Functions as Agent Tools: Putting the Rules Where a Prompt Cannot Move Them
Step Functions workflows can now be exposed to agents as tools through AgentCore Gateway. What the connector offers, how to write a workflow that is safe to hand to a model, where the IAM boundary sits, and eighteen scenarios tested on Step Functions Local.
Read more →Hosting Remote MCP Servers Securely on AWS and Azure: Token Validation, Gateways and Network Placement
A remote MCP server is an API that a language model can drive. This article covers the three things that decide whether it is safe: what the MCP authorization specification requires of the server, where to host it on AWS and Azure and who validates the token in each case, and where the endpoint belongs on the network. Includes a tested Python resource server and an ASP.NET Core version for Entra ID.
Read more →A2A and MCP Across Clouds: Connecting a .NET Agent Framework Agent to an Agent on Bedrock AgentCore
MCP connects an agent to its tools; A2A connects an agent to another agent. This article wires a .NET Microsoft Agent Framework coordinator on Azure to a Python agent and MCP tool server laid out for Amazon Bedrock AgentCore Runtime, and reports what broke: A2A 0.3 versus 1.0 version skew, identity across the cloud boundary, and task lifecycle handling.
Read more →Bedrock AgentCore Runtime vs. Lambda for Hosting Agents: Isolation, State and the Idle Bill
The same agent runs on AWS Lambda and on Amazon Bedrock AgentCore Runtime with two thin adapters. The differences are isolation, where conversation state lives and what is billed while the agent waits. AgentCore is cheaper for I/O-bound agents only if sessions are ended deliberately: left at defaults, idle memory makes it the more expensive option.
Read more →Breaking the 29-Second Wall: Serverless GenAI & Agent Backends on AWS
The API Gateway 29-second timeout is now a default, not a wall: REST APIs can stream for 15 minutes, and Lambda durable functions and Bedrock AgentCore handle work that runs for hours. This article sets out the current limits, three production patterns for long-running GenAI requests with tested code, and the concurrency and cost consequences of each.
Read more →