Anthropic launches Claude Platform on AWS with native billing, IAM, and Managed Agents

• Anthropic made the Claude Platform on AWS generally available, and claudeai's launch post says AWS customers now get the full Claude API feature set with AWS authentication, billing, and commitment retirement.
• The AWS version exposes native Claude features, and claudeai's feature thread says Managed Agents, advisor strategy, code execution, and web search ship there the same day they land on the native Claude API.
• The split from Bedrock is operational, not model-level: claudeai's follow-up says Claude remains on Amazon Bedrock, while kimmonismus's summary notes the new service is operated by Anthropic rather than AWS.
• The included feature list is broader than the first announcement tweet suggests, because WesRoth's screenshot surfaces Skills, MCP connectors, prompt caching, citations, Files API, and batch processing alongside the agent stack.
• Day-one ecosystem evidence showed this was already handling live traffic, with OpenRouter's partner post saying the AWS-backed deployment had seen production OpenRouter traffic before the public announcement.

You can read Anthropic's announcement, skim WesRoth's feature-list screenshot for the full inventory, and compare it with claudeai's Bedrock note, which makes the boundary explicit: this is native Claude inside AWS procurement and governance plumbing, not a rebrand of Bedrock.

Anthropic's core pitch is procurement and governance, not a new model. claudeai's announcement frames the GA around AWS authentication, billing, and commitment retirement, while ai_for_success's summary adds IAM integration and enterprise deployment support.

That packaging matters because it gives AWS buyers a way to purchase the native Claude platform through existing AWS spend. kimmonismus's post describes it as access to Claude with AWS billing and governance tooling, without routing teams into Bedrock.

The feature story is simple: Anthropic says the AWS version gets the same surface area as the native API, on the same day. In claudeai's thread, the company names Managed Agents, advisor strategy, code execution, and web search as first-class parts of the launch.

WesRoth's screenshot expands that list into a more useful inventory:

• Claude Managed Agents (beta)
• Advisor strategy (beta)
• Web search and web fetch
• Code execution
• Files API (beta)
• Skills (beta)
• MCP connector (beta)
• Prompt caching
• Citations
• Batch processing

That makes this less of a narrow hosting option and more of a full native Claude control plane delivered through AWS enterprise rails.

Anthropic did not replace its Bedrock relationship. claudeai's follow-up says Claude remains available on Amazon Bedrock, where AWS is the data processor.

The new AWS-hosted Claude Platform keeps a different operating model. claudeai's thread says Anthropic operates the service, and kimmonismus's summary spells out the tradeoff directly: customers get the native Claude experience, but data is processed outside the AWS boundary that defines Bedrock.

The most concrete day-one ecosystem detail came from OpenRouter. In OpenRouter's partner post, the company said the AWS release had already seen production OpenRouter traffic and was now labeled accordingly across applicable Claude models.

That prelaunch traffic lines up with a quieter signal from the broader market. Two days before GA, nummanali's post called Claude Managed Agents "really good" while asking for an open source alternative, which suggests at least some developers had already been kicking the managed agent stack hard enough to want a clone.