Claude Platform on AWS Announced (Coming Soon)
AWS announced Claude Platform on AWS — a new way to use Anthropic's native Claude Platform with AWS credentials, billing, and access controls. It sits alongside Claude on Amazon Bedrock as a second path with different data-residency tradeoffs.
This article is a summary based on official documentation.
What was announced
AWS published a “Coming Soon” page for Claude Platform on AWS — a new offering that lets organizations use Anthropic’s native Claude Platform through their existing AWS account, without separate Anthropic contracts or API keys.
Until now the cloud-native path to Claude on AWS was accessing Claude models in Amazon Bedrock. This announcement adds a second path that wraps the Claude Platform itself (the same APIs, console, and beta features Anthropic ships directly) with AWS authentication and billing. Pricing, GA date, and supported regions are not disclosed yet; an interest-registration form is provided.
Resources
- AWS landing page: Claude Platform on AWS
- Interest form: pages.awscloud.com — Claude Platform on AWS 2026 interest
- Compare with: Claude on Amazon Bedrock
Highlights
-
AWS authentication for Claude Platform
Use existing AWS IAM users, roles, and policies to access the Claude Platform. No separate Anthropic accounts or API keys to provision and rotate.
-
Native Anthropic experience preserved
The same APIs, console, and beta features Anthropic ships directly — not the Bedrock multi-model abstraction. This is the path to receive new Claude features on Anthropic’s release cadence.
-
One audit trail — straight into AWS CloudTrail
Claude Platform activity flows into CloudTrail alongside other AWS service events, so existing security and audit workflows apply unchanged.
-
Consolidated billing — one AWS invoice
Claude Platform usage is billed through AWS. No separate Anthropic invoice or procurement track, which simplifies enterprise purchasing.
How it differs from Claude on Bedrock
The AWS FAQ draws a clean line between the two options:
| Aspect | Claude Platform on AWS | Claude on Amazon Bedrock |
|---|---|---|
| Operator | Anthropic | AWS |
| Where data is processed | Anthropic infrastructure (outside AWS) | Inside AWS infrastructure |
| Model catalog | Claude only (native) | Many foundation models, unified |
| AWS-managed features | CloudTrail, IAM, consolidated billing | + Guardrails, Knowledge Bases, regional residency |
| Beta-feature access | At Anthropic’s release cadence | Dependent on Bedrock onboarding |
| Best fit | No strict regional residency; want native experience and beta features | Need data inside AWS, multi-model access, or AWS-managed safety controls |
Short version: Claude Platform on AWS = fastest feature access + simplest procurement, Claude on Bedrock = stronger data residency + AWS-managed safety.
Notes
- Data residency is the first decision point. If prompts and responses can leave AWS boundaries, Claude Platform on AWS is viable. If not, Bedrock is the right choice.
- Beta features arrive sooner on Platform. Bedrock onboards new Anthropic features on its own schedule, so a freshly-released Claude beta is not immediately usable through Bedrock.
- The two options aren’t mutually exclusive. A single organization can run developer workloads on Platform on AWS and regulated workloads on Bedrock — both roll up to the same AWS bill.
- Distinct from the Claude Cowork announcement. The April 21 post on running Claude Cowork in Amazon Bedrock is a deployment model that routes Claude Desktop traffic to Bedrock for knowledge workers. This announcement is about wrapping the Claude Platform itself in AWS authentication and billing.
- No GA date yet — interest registration only. Specific GA timing, regions, pricing, and supported models are not published. The interest form is the way to get early information.