> 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 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.
yes it sounds like a hack to get access to untracked spend in corporate accounts.
In my org, I have to file a form for reimbursement if I bought a pencil for $0.25 but in AWS? spend varies by +/- $5k per month and nobody even questions it. This will definitely make it trivially easy for me to build on Anthropic's services without even telling anybody vs the hoops I would have to jump to get it paid for another way.
Yeah i think this could backfire. At the moment they have such a clear messsage with Bedrock about data governance. You now have to ask a question and probalby get approval where previously there was no question and hence no barriers.
there’s a top level feature in aws for investors to give out credits of like $120k of AWS spend during funding rounds. there’s min commits of spend for cheaper prices (RI). funneling costs and invoicing though aws has real benefits. aws spend monitoring is literally a sub industry with billion dollar players
The credits you get from aws in their startup program are typically not spendable on marketplace. At least what we got through YC we could not spend there. Not sure how claude is integrating, maybe it’s different here
> 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.
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
There's companies out there with mid 8, possibly low 9 figure monthly AWS bills. In that world, letting people pay through said AWS pipeline gets rid of so much red tape. Supporting Bedrock was already a big winner vs OpenAI in the race for big enterprise, and Anthropic desperately wants to find any way to be sticky, as opposed to risking companies flipping a switch and telling entire departments to switch to any future codex + GPT on Bedrock plans. The harder it is for you to migrate, the better for Anthropic.
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?
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.
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?
anthropic and aws have been pretty close from the start
i think the more interesting part is that anthropic is to aws what target was to amazon
this feels like there's a coming 5-10 year change from aws acting as a cloud, to being a cloud entrypoint/marketplace, separately from the cloud marketplace they already have as cfn snippets you can deploy
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
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
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.
In my org, I have to file a form for reimbursement if I bought a pencil for $0.25 but in AWS? spend varies by +/- $5k per month and nobody even questions it. This will definitely make it trivially easy for me to build on Anthropic's services without even telling anybody vs the hoops I would have to jump to get it paid for another way.
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.
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
Claude itself was almost from the very beginning available in bedrock.
Anthropic’s offerings for Bedrock lag behind their main platform by months, maybe up to a year or more.
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.
Suspect this is probably the same.
Seems intentionally deceitful.
i think the more interesting part is that anthropic is to aws what target was to amazon
this feels like there's a coming 5-10 year change from aws acting as a cloud, to being a cloud entrypoint/marketplace, separately from the cloud marketplace they already have as cfn snippets you can deploy