← Back to Videos
AnthropicClaudeAWSAIArchitecture

Anthropic Just Put Claude On AWS Directly — IAM Auth, AWS Billing

Anthropic has launched direct Claude access on AWS — not through Bedrock, but natively with IAM authentication and AWS billing. What this means, how it differs from Bedrock, and how to set it up.

📅 15 June 202612:55✍️ Rahul Kumar

What Just Happened

Anthropic has launched a new way to access Claude directly through AWS — distinct from Amazon Bedrock. This new integration means Claude API calls can be authenticated using AWS IAM, billed directly through your AWS account, and accessed from within your AWS network without going through Bedrock's model hub.

Claude on AWS Direct vs Claude on Bedrock — What's Different?

  • Authentication — Direct: AWS IAM roles and credentials (no separate Anthropic API key). Bedrock: AWS Bedrock access with model access requests
  • Billing — Direct: appears on your AWS bill as an Anthropic line item. Bedrock: appears as Bedrock usage
  • Network path — Direct: can use PrivateLink to stay entirely within AWS network. Bedrock: routes through Bedrock endpoints
  • Model access — Direct: potentially faster access to latest Claude models without waiting for Bedrock availability. Bedrock: model releases follow Bedrock's schedule
  • Consolidation — Direct: consolidates onto your AWS bill and IAM governance, ideal for AWS-first enterprises

Why This Matters for Enterprise Architecture

For enterprises that are AWS-first and have invested in IAM governance, this is significant. Managing a separate Anthropic API key introduces a credential management burden. IAM-based auth means Claude access follows the same identity controls as every other AWS service — RBAC, CloudTrail logging, SCP policies — all automatically.

How to Set It Up

In the video I walk through the complete setup:

  • Enabling the Anthropic direct integration in your AWS account
  • Creating an IAM role with the appropriate Claude access policy
  • Making your first authenticated API call using AWS SDK credentials
  • Configuring PrivateLink for network-private access
  • Viewing Claude usage in AWS Cost Explorer

Should You Migrate from Bedrock?

Not necessarily — Bedrock remains excellent for multi-model workloads (if you use Titan, Llama, Mistral, or others alongside Claude). The direct integration is ideal if Claude is your primary or only model and you want maximum simplicity in auth and billing. Evaluate based on your specific architecture, not just the novelty of the new option.

For Azure Users

Azure already has Azure AI Foundry which provides similar consolidated access to models including Claude through a native Azure experience. If you are Azure-first, Azure AI Foundry remains the recommended path for Claude access in Azure workloads.

Watch on YouTube

▶ Watch Now

Opens in YouTube

Share on LinkedIn

One click — copies a ready-to-post update about this video

About the Author

Rahul Kumar is a Senior Cloud and AI Architect at Microsoft with 13+ years of enterprise experience across Azure, AWS, and GCP.

Book a Discussion