> 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…
"mostly about billing" NO. People, this is about your data .
Claude Platform on AWS
71–80 of 99 posts
Re: Claude Platform on AWS
#72So confusing. Are they with AWS for the checkout? Because none of sentences make sense to me
Re: Claude Platform on AWS
#73Earlier quoted context omitted.
No, "This is exactly not it." They are buying your data on a cheap.
Do you have experience selling to fortune 100 sized organizations? “I don’t have the budget for this but we have AWS credits” is something teams beg for all the time. When people beg to give you money, you accept it. Why? It’s not some conspiracy theory. You accept the money because it’s money.
Re: Claude Platform on AWS
#74Earlier quoted context omitted.
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…
The Bedrock models, at least, have additional click through EULAs for Anthropic models. You’re going to need to review and agree to those as well.
Claude is going to be marketplace spend and that’s usually capped towards your PPA at 25%.
Re: Claude Platform on AWS
#75It sounds like an “official” Anthropic API billed from an AWS account?
Re: Claude Platform on AWS
#76> 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…
Re: Claude Platform on AWS
#77> 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
#78Re: Claude Platform on AWS
#79Re: Claude Platform on AWS
#80> 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…