Claude Platform on AWS

> The Claude Platform on AWS is a first of its kind offering for Anthropic, giving you all native Claude API features from day one. Anthropic operates the service and data is processed outside the AWS boundary.

So it's not... On AWS... ?

This statement sounds.... Backwards?

I get they have another option that is in AWS, but this continues the cryptic naming problem AWS already is overloaded with

I dont think this is about billing as other comments mentioned. AWS bedrock already does that.

I think AWS proposes to host actual agents, meaning you can customize their MCP servers, have them fetch and issue arbitrary requests, etc. Essentially a hosted minimal harness.

This is very much needed, as a form of "hosted claude code", allowing you to actually have the agent code, push, test from e.g. your phone.

> The Claude Platform on AWS .. giving you all native Claude API features .. Anthropic operates the service and data is processed outside the AWS boundary. This is a good option for companies that want the full Claude Platform experience.

Does seem to be mostly about billing like others said. But it might mean cloudformation / terraform providers for claude-platform, guess that's nice.

It might make strict networking/firewall things slightly easier somehow. But for everyone who thinks the new offering is about jurisdictional matters, it's not, that's the old one:

> Claude on Amazon Bedrock keeps AWS as the data processor and operates within the AWS boundary. This is a good fit for companies that have strict regional data residency requirements or need their data processed exclusively within AWS's infrastructure.

A little startup I'm part of is on the AWS startup program giving us £10k in AWA credits so the more we can "proxy" through AWS the better.

We already heavily rely on anthropic models via Bedrock but I'll be interested to see if the tok/s throughout is better on this new service (or worse).

To be honest though after a quick skim, I'm unclear what other advantages this might offer over Bedrock where we can already access the models including vision etc. Will it be worth refactoring our services, all our terraform etc? Unclear at this stage, especially since Bedrock allows us to use more than just the anthropic models if needed

So claude.bedrock is where you run if you want complete data privacy, this - claude.aws - is just claude on/in AWS - is that the right core difference?

I wonder how Anthropic will adjust their models as local models compete more closely with API models.

Anthropic operates the service and data is processed outside the AWS boundary.

So is this effectively a way for aws customers to more easily access Claude code?

Claude itself was almost from the very beginning available in bedrock.

So confusing. Are they with AWS for the checkout? Because none of sentences make sense to me

It allows one to conveniently hide your claude expense in your big ass AWS bill.

How's this work? Like if I want to self host claude on my gpu's? Do I just pay a one time lease?

Waiting for them to launch Google Claude Platform (GCP).

It sounds like an “official” Anthropic API billed from an AWS account?

Interesting timing - been building with Claude API locally and hit AWS infra questions.

Anyone know if this solves cross-region failover? Main pain point I have is US vs EU latency differences when running agents in parallel. Local orchestration helps but cloud fallback would be useful.

"Claude in the cloud" has a nice ring to it.

Nice, might give managed agents a try now.

How to obscure your wasteful LLM usage behind your already massive AWS expenditure with this one tip.

So what's the good point?

Might be good?

Umm, why could this not just be Claude on AWS marketplace?

Seems intentionally deceitful.

[flagged]

[flagged]

[dead]

Is this a bunch of AI coded slop? I feel like everyone should be skeptical of how quickly Anthropic is throwing random things out there. Why would anyone use this instead of using Claude directly on AWS?

this is a bad bad idea people, i highly recommend not falling for this one. You dont wanna see your production database get deleted by mistake or spawn 464135453452 ec2 instances due to a mistake in autoscaling configuration