Claude Platform on AWS
43 points by matrixhelix 3 hours ago | 22 comments

robot-wrangler 7 minutes ago
> 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. 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.

reply
ldoughty 58 minutes ago
> 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

reply
xyzzy123 18 minutes ago
I think the idea is that you can launder your team or product AI spend through your AWS account. This matters in Enterprise. It looks like the difference with Bedrock is that you access more "Claude platform" stuff than just the model.

More charitably, this lets an org heavy on AWS use their existing IAM / SSO / Finops processes to manage Claude stuff, this is genuinely helpful when otherwise you have to go thru several teams and build out whole new rails to adopt.

reply
niwtsol 41 minutes ago
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?
reply
cavemanDigAI 23 minutes ago
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.

reply
whatever1 2 hours ago
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.

reply
wafisher 35 minutes ago
Might be for enterprise customers (with slow procurement departments) who already have AWS accounts but not Anthropic ones.
reply
LPisGood 32 minutes ago
So then they could use Bedrock, no?
reply
harrall 2 minutes ago
A lot of tools, community and Anthropic’s, have zero support for Bedrock.
reply
nryoo 40 minutes ago
So what's the good point?
reply
Jabrov 18 minutes ago
Hide some of your ballooning AI spend behind your ballooning AWS bill
reply
SilverElfin 16 minutes ago
Couldn’t you already do that with Claude via AWS?
reply
rohansood15 3 minutes ago
But you couldn't do it with the Claude app or the recently announced Claude Managed Agents I think.
reply
xyst 26 minutes ago
How to obscure your wasteful LLM usage behind your already massive AWS expenditure with this one tip.
reply
notaharvardmba 51 minutes ago
It allows one to conveniently hide your claude expense in your big ass AWS bill.
reply
nijave 47 minutes ago
I tried that with Bedrock but Claude models are billed through Marketplace and generate a completely separate invoice.

Suspect this is probably the same.

reply
geedelgado 19 minutes ago
Might be good?
reply
breckenedge 2 hours ago
Nice, might give managed agents a try now.
reply
rohansood15 14 minutes ago
Umm, why could this not just be Claude on AWS marketplace?

Seems intentionally deceitful.

reply
SilverElfin 17 minutes ago
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?
reply
vivzkestrel 24 minutes ago
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
reply
Jabrov 19 minutes ago
I think you might have misunderstood the headline and maybe not read the article, because that's not really relevant to what's being announced here
reply