OpenAI's Agent Harness Moved Into AWS, and the Paperwork Is the Point

AWS made OpenAI models generally available on Bedrock back on June 1, and that was the model-access story: GPT-5.5 and Codex on Bedrock's inference engine, pricing matched to OpenAI's first-party rates, usage counting toward existing AWS commitments. The more interesting move came four months later. On September 29, AWS and OpenAI opened the public preview of Bedrock Managed Agents (BMA), and what relocated is not another model endpoint — it's the agent loop itself. The harness that preserves state, selects tools, executes code, and coordinates multi-step work now runs inside your AWS account.

Read the primary docs and you'll notice what they lead with, because it isn't reasoning quality — it's chain of command. Each agent operates with its own IAM role. Authentication is SigV4 credentials instead of an API key living in somebody's .env file. Human approval gates sit in front of consequential actions, and supported API activity gets recorded in CloudTrail. Sessions are durable: messages, tool calls, and intermediate results persist, so a half-finished task can be resumed days later with new information. You pick where the work actually runs — Bedrock AgentCore Runtime or your own compute — and the harness compacts context as conversations grow, which is a direct answer to the context-bloat problem agent builders have been fighting all year. MCP servers plug in for tools, and reusable skills can be attached for specialized procedures — the same building blocks the OpenAI-side Agents API pushes, just with AWS plumbing underneath. For a platform team, this is the first time "run an OpenAI agent in production" arrives with the same audit primitives as everything else in the account: the agent is an identity you can revoke, not a cron job you hope stays well-behaved.

An abstract image
Source image 1

Two asterisks, though, and both are in OpenAI's own documentation. First: shared concepts don't imply identical API contracts — the Bedrock build is a customized Agents API, an AWS-flavored dialect, and porting code between the two is not a find-and-replace job. Second: preview pricing is "no additional charge beyond the underlying AWS resources," which is precisely how a cloud service earns a permanent place in your architecture before real pricing shows up at general availability. The strategic read is that model access is already commoditized; what's being sold now is governance. AWS is betting that the buyer of production agents is the compliance team, not the prompt engineer. If you already run agents somewhere, does moving the loop into AWS for IAM roles and CloudTrail trails change your risk posture enough to accept a forked API dialect — or is the audit trail something you'd rather keep owning yourself?

Source article image
Source image 2

Sources

Comments

Post a Comment

Popular posts from this blog

AI Is Starting to Feel Less Like a Gadget and More Like Infrastructure

Image
Modern AI doesn't replace infrastructure — it runs on top of it. (Photo: Unsplash) For a while, AI coverage had the energy of a mall demo kiosk: very shiny, slightly chaotic, and usually one prompt away from embarrassment. Lately, though, the more interesting story is less about flashy demos and more about infrastructure. A useful CNBC piece argued that AI is not simply going to vaporize enterprise software overnight, and that sounds about right. In real companies, software does not disappear just because a model can summarize a meeting or write a decent SQL query. What actually happens is messier and more practical: AI starts sneaking into the plumbing. It shows up in search, support workflows, procurement tools, analytics dashboards, and data pipelines. The real winners may not be the loudest chatbot wrappers, but the vendors that make enterprise systems easier to operate, easier to query, and slightly less soul-crushing for the humans trapped inside them. That is less cinematic ...
Read more

When Two AI Bots Finally Learned to Talk in Discord

I spent part of the day doing something that sounds like the setup for a bad joke: getting two local AI assistants to talk to each other in the same Discord channel. Not through a web UI. Not by bouncing prompts manually between windows like a human message queue. In the actual shared channel, where both could see the conversation and react to each other. The funny part is that the problem was not intelligence. It was manners. Both bots were defensive by default around bot-authored messages, which is the sensible setting if you do not want your infrastructure turning into a recursive support group. The downside is obvious: if both assistants treat other bots as suspicious background noise, they will never coordinate on anything more useful than silence. The fix was to make both sides accept bot-authored messages only when they were explicitly mentioned. That detail matters more than it sounds. Blanket bot acceptance is how you end up with two enthusiastic systems discovering each oth...
Read more

Enterprise AI Is Quietly Becoming a Systems Integration Problem

The funniest thing about enterprise AI in 2026 is that the flashy part is basically over. The demos are still shiny, sure, but the real story now looks a lot less like science fiction and a lot more like infrastructure planning, governance, and somebody in IT asking who exactly is paying for all these agents. Over the past few weeks, Microsoft has been pitching Agent 365 and a bundled Microsoft 365 E7 “Frontier Suite” aimed at governing and securing fleets of workplace agents, Google has introduced a new Workspace add-on for higher AI usage tiers, and Anthropic has thrown $100 million behind a partner network to help companies move Claude deployments from pilot mode into something that can survive contact with procurement, compliance, and existing systems. That cluster of announcements says something pretty clear: enterprise AI is no longer mainly a model race. It is becoming a packaging, controls, and implementation race. The clever model still matters, obviously, but once every vendo...
Read more