Back to News
Advertisement
Advertisement

⚡ Community Insights

Discussion Sentiment

67% Positive

Analyzed from 754 words in the discussion.

Trending Topics

#aws#claude#anthropic#bedrock#more#already#might#platform#data#spend

Discussion (23 Comments)Read Original on HackerNews

ceuk•29 minutes ago
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

ldoughty•about 1 hour 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

xyzzy123•about 1 hour 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.

foolfoolz•17 minutes ago
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
robot-wrangler•37 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.

niwtsol•about 1 hour 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?
cavemanDigAI•about 1 hour 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.

whatever1•about 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.

wafisher•about 1 hour ago
Might be for enterprise customers (with slow procurement departments) who already have AWS accounts but not Anthropic ones.
LPisGood•about 1 hour ago
So then they could use Bedrock, no?
ZeroCool2u•10 minutes ago
Bedrock is both more expensive, less feature complete, and less reliable in terms of raw volume of 500 errors.
harrall•31 minutes ago
A lot of tools, community and Anthropic’s, have zero support for Bedrock.

Anthropic’s offerings for Bedrock lag behind their main platform by months, maybe up to a year or more.

nryoo•about 1 hour ago
So what's the good point?
Jabrov•about 1 hour ago
Hide some of your ballooning AI spend behind your ballooning AWS bill
dodu_•22 minutes ago
But then how would I be able to brag about how much I'm doing the AI?
SilverElfin•about 1 hour ago
Couldn’t you already do that with Claude via AWS?
rohansood15•32 minutes ago
But you couldn't do it with the Claude app or the recently announced Claude Managed Agents I think.
notaharvardmba•about 1 hour ago
It allows one to conveniently hide your claude expense in your big ass AWS bill.
nijave•about 1 hour 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.

xyst•about 1 hour ago
How to obscure your wasteful LLM usage behind your already massive AWS expenditure with this one tip.
breckenedge•about 2 hours ago
Nice, might give managed agents a try now.
geedelgado•about 1 hour ago
Might be good?
Advertisement
rohansood15•43 minutes ago
Umm, why could this not just be Claude on AWS marketplace?

Seems intentionally deceitful.

SilverElfin•about 1 hour 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?
8note•15 minutes ago
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

vivzkestrel•about 1 hour 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
Jabrov•about 1 hour 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