Claude Platform on AWS Goes GA: Full Feature Parity, IAM Auth, Single Invoice
Anthropic launched the Claude Platform on AWS into general availability on May 11, making the full first-party Claude API accessible through existing AWS accounts for the first time.
The product is distinct from Amazon Bedrock in a critical way: on Bedrock, AWS acts as the data processor. On Claude Platform on AWS, Anthropic is the data processor — customers get the same privacy and data handling guarantees as direct Claude API users, with AWS handling only the identity and billing layer.
What’s Different From Bedrock
Authentication runs through AWS IAM. Audit logs flow through CloudTrail. Billing consolidates onto a single AWS invoice that retires against existing AWS commitments — relevant for enterprises sitting on large Enterprise Discount Programs or credit reserves.
Every Claude API feature and beta ships to Claude Platform on AWS on the same day it goes live on the native Claude API. That parity commitment is the headline: enterprise customers no longer face a lag between what Anthropic ships and what AWS customers can access.
Managed Agents Now Available at Scale
Claude Managed Agents — Anthropic’s hosted agent runtime that charges $0.08/hour per running agent — is included from day one. Teams can deploy code execution, skills, and the advisor strategy through the AWS integration without maintaining their own agent infrastructure.
The offering is available across most AWS commercial regions with both global and US inference geographies supported.
The Amazon Deal Paying Off
Amazon committed $25B to Anthropic in April, an expansion that included a $100B AWS spend commitment. Claude Platform on AWS is the first major product-layer output of that deal: enterprise teams get Claude without a separate Anthropic account, procurement cycle, or billing relationship.
Early customers include ReliaQuest, which cited the integration as simplifying access for Claude Code engineers, and OpenRouter, which noted it now accesses the latest native API features while controlling access through the same IAM credentials it uses across AWS.
For organizations already standardised on AWS, the friction of adopting Claude just dropped considerably. The question is whether native Claude’s data-processor model — versus Bedrock’s — becomes a meaningful differentiator in enterprise procurement conversations, or whether most buyers treat the two as interchangeable.