Claude Platform on AWS is now generally available

Overview

The Claude Platform on AWS is now generally available. What Anthropic previewed as “Coming Soon” on April 27 is now live: AWS customers can use the full Claude Platform — operated by Anthropic — through their existing AWS IAM credentials, CloudTrail audit logging, and a single AWS invoice, with no separate Anthropic contract or API key required.

Unlike the Bedrock path — where AWS operates as the data processor within its infrastructure — Claude Platform on AWS keeps Anthropic as the operator and processes data outside the AWS boundary. In exchange, all new features from the native Claude API ship on the same day they launch elsewhere.

Key features

• AWS IAM authentication — no separate API key

  Previously, using the Claude Platform meant issuing and rotating API keys in an Anthropic account. Now, AWS IAM users, roles, and policies grant direct access — key rotation and permission delegation follow your existing AWS operational standards.

• Single AWS invoice — commitment retirement included

  Splitting billing across Anthropic and AWS meant two procurement and payment workflows. Claude Platform usage now consolidates onto your AWS invoice and applies toward AWS commitments (including EDP), with no separate invoicing.

• CloudTrail audit logging — one audit pipeline

  Security teams previously had to track Anthropic console activity and AWS service events separately. Claude Platform actions now land in CloudTrail alongside other AWS service events, so your existing audit pipeline applies as-is.

• Day-one access to native Claude API beta features

  Bedrock’s onboarding cadence created a gap before new beta features became usable. With this GA, the following ship on launch day:

  • Claude Managed Agents (beta) — deploy agents at scale
  • Advisor strategy (beta) — boost reasoning quality via advisor model consultation
  • Web search and web fetch tools — augment knowledge with current web data
  • Code execution — run Python directly within API calls
  • Files API (beta) — upload and reference documents across conversations
  • Skills (beta) — teach Claude best practices for consistent results
  • MCP connector (beta) — connect Claude to remote MCP servers without client code
  • Prompt caching, Citations, and Batch processing are also included

• Model lineup — same launch day as the native API

  Claude Opus 4.7, Sonnet 4.6, and Haiku 4.5 are all available at GA, and future models will ship on the same day they launch on the native Claude API — eliminating the lag that exists on Bedrock.

How it compares to Bedrock — at a glance

Running Claude on AWS actually splits into three paths: the new Claude Platform on AWS, the current Claude in Amazon Bedrock (Messages API), and Amazon Bedrock legacy (InvokeModel / Converse). “How does this compare to Bedrock?” depends on which Bedrock — migration cost varies accordingly.

Aspect	Claude Platform on AWS	Claude in Amazon Bedrock	Amazon Bedrock (legacy)
Operator · Inference data processor	Anthropic (outside AWS boundary)	AWS (inside AWS)	AWS (inside AWS)
API surface · Base URL	/v1/messages · aws-external-anthropic.{region}.api.aws	/anthropic/v1/messages · bedrock-mantle.{region}.api.aws	Converse/InvokeModel · bedrock-runtime.{region}.amazonaws.com
Model ID format	claude-opus-4-7	anthropic.claude-opus-4-7	anthropic.claude-opus-4-7-v1
SDK client	AnthropicAWS (beta)	AnthropicBedrockMantle	AnthropicBedrock / Bedrock SDK
Authentication	SigV4 or API key	SigV4	SigV4 or bearer token (limited SDKs)
New-feature availability	Typically same-day as Claude API	Per Amazon Bedrock release schedule	Per Amazon Bedrock release schedule
anthropic-beta header	Supported	Not supported	Not supported
Agent Skills · Code execution	Available	Not available	Not available
Zero Data Retention	Opt-in via Anthropic account rep	Not applicable (AWS is the processor)	Not applicable (AWS is the processor)
FedRAMP High · IL4 · IL5 · HIPAA-ready	Not available	Available	Available
Streaming format	SSE	SSE	AWS EventStream
Billing	AWS Marketplace	AWS (native service)	AWS (native service)
Capacity pool	Separate from first-party API and Bedrock	—	—

Choosing between them

• Choose Bedrock if you have FedRAMP High, IL4, IL5, or HIPAA-ready requirements, or if AWS must be the sole data processor.
• Choose Platform on AWS if you want day-one access to Anthropic’s beta features, Agent Skills, and code execution, and your policy allows inference to be processed outside the AWS boundary.
• Run both — Claude Platform on AWS uses a separate capacity pool from both the first-party Claude API and Amazon Bedrock, so failing over between paths is supported.

Getting started

1. Visit the Claude Platform on AWS page to start enrollment.
2. Follow the setup guide in the official documentation.
3. Configure AWS IAM roles and policies that grant Claude Platform access.
4. Choose a global or U.S. inference geography across most AWS commercial regions.

Heads-up for existing Bedrock private offer holders: discounts will not apply retroactively after migration. Contact your Anthropic or AWS account executive before migrating to ensure your discount continues to apply.

Notes

• Data residency drives the first decision — confirm whether prompts and responses can leave the AWS boundary. If they can, Claude Platform on AWS fits; if they can’t, Bedrock is the appropriate path.
• The two options are not mutually exclusive — an organization can run developer workloads on Claude Platform on AWS while keeping regulated workloads on Bedrock. Both consolidate onto the same AWS invoice.
• GovCloud is not included in this GA — the announcement covers AWS commercial regions. Support for GovCloud or other partitions was not stated.
• This is a separate milestone from the April pre-announcement — the April 27 Claude Platform on AWS announcement (Coming Soon) had no firm GA date, pricing, or region list. This post confirms general availability with concrete coverage.