Live data from Hacker News

Claude Platform on AWS

claude.com

41–50 of 99 posts

Re: Claude Platform on AWS

#42
post #26
post #17

Earlier quoted context omitted.

Hide some of your ballooning AI spend behind your ballooning AWS bill

But then how would I be able to brag about how much I'm doing the AI?

Don't worry, you can still get on linkedin and write a bragging post about how many tokens your engineers are spending.

Re: Claude Platform on AWS

#44
post #25

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 acc…

Are you sure those credits apply to this usage. Many forms of AWS credits dont cover usage of Claude models on Amazon Bedrock for instance, as all of them are billed as third party / marketplace consumption.

Re: Claude Platform on AWS

#46
post #4

> 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 seve…

> I think the idea is that you can launder your team or product AI spend through your AWS account.

This is exactly it. For any reasonably sized org, setting up new contracts with new vendors involves a lot of procurement, lawyers, negotiations, etc.

If a team can just click a button in AWS, there’s no issue.

This is a product / solution that solves an organizational problem, not a technical one.

I wouldn’t even call it a hack as much as extremely common a strategy.

Re: Claude Platform on AWS

#47
post #4

> 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

> 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.

Seems like there are two different options.

Re: Claude Platform on AWS

#49
post #4

> 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

At this point I can only assume that AWS wants to have this naming issue. It’s an issue they have everywhere. Sagemaker is the worst offender. Only a solution architect can guide through such confusion…
Post reply on HN