I'm a big fan of using Claude and Claude Code for development.
Many organizations are currently using these tools to improve developer productivity and ultimately build better products.
Our role and our tools have changed — we went from powerful autocomplete to autonomous agents that can refactor, review, and implement features, most of the time better than we can on our own.
Authentication methods There are several authentication methods, each with different billing, cost tracking, and governance options.
Depending on your organization, you will choose the one that fits best.
Personal development — Anthropic API key I use this for experimenting with the Anthropic library for learning and prototyping.
You set in your environment (or a file), and the SDK picks it up automatically.
Pay-as-you-go per token, no infrastructure needed.
Claude Code with Amazon Bedrock This is my preferred option for organizations.
With Bedrock you get inference profiles, IAM roles, and solid audit trails through CloudTrail — no floating API key to rotate or leak.
The same credential chain you use for any other AWS SDK call works here.
Configuration is just a few lines in : The prefix on the model IDs uses cross-region inference profiles, which route to the lowest-latency region automatically and give higher throughput limits than a single-region endpoint.
Claude Platform on AWS This is the option for organizations that want AWS Marketplace billing combined with the full Anthropic API feature set.
Unlike Bedrock (which routes requests through AWS's own inference infrastructure), Claude Platform on AWS sends requests directly to Anthropic's API — giving you the latest models on the same release schedule as the direct Claude API — while billing consolidates into your existing AWS spend through Marketplace.
It's a great fit when your organization has SSO set up through IAM Identity Center and wants a single sign-on experience without managing separate Anthropic credentials.
Step 1 — log in with SSO: Step 2 — configure automatic credential refresh so Claude Code re-authenticates when your SSO session expires, rather than dying mid-session.
Add this to : Step 3 — point Claude Code at the platform: is required on every request — it identifies your organization's workspace and isn't inferred from your AWS credentials.
Bonus: pin your model versions Regardless of which auth method you use, always pin model versions before rolling out to a team.
Without pinning, model aliases like and resolve to Claude Code's built-in defaults, which can change when Claude Code updates — and on Bedrock, that can silently move a Sonnet deployment to Opus pricing.
Run inside Claude Code to confirm which provider and models are actually active.
Bonus: AWS Guardrails Amazon Bedrock Guardrails let you implement content filtering for Claude Code.
Create a guardrail in the Amazon Bedrock console, publish a version, then add the guardrail headers to your settings file.
Enable cross-region inference on your guardrail if you're using cross-region inference profiles.
Conclusion Each authentication method reflects a different stage of adoption and governance maturity: Personal API key — the fastest way to start experimenting.
Zero infrastructure, pay per token, ideal for learning and prototyping.
Claude subscription (Pro/Max) — best for individual developers who want flat pricing and access to Claude on the web alongside Claude Code.
Amazon Bedrock — the right choice for teams already inside AWS.
IAM authentication, CloudTrail audit logs, inference profiles, and no standalone API keys to manage.
This is where I'd start for any production team deployment.
Claude Platform on AWS — best when your organization wants AWS Marketplace billing and SSO, but also needs the latest models on Anthropic's release schedule without waiting for Bedrock to catch up.
Pick the option that matches your organization's current security and billing requirements — and remember that you can always migrate later.