> 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 Platform on AWS
81–90 of 99 posts
Re: Claude Platform on AWS
#82> 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
Yeah, as someone with strict export compliance concerns which forces us to use Bedrock because its exclusively us-based inference in our AWS account, this does nothing for me. Frankly, nothing Anthropic has shipped over the past 6 months besides the models themselves has been useful to our company, despite running into the same problems they're trying to solve with all of those features (managed, remote agents). Ther…
Re: Claude Platform on AWS
#83Earlier quoted context omitted.
> 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…
Sadly it’s going to be more nuanced. 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%.
Every year "don't agree to things on behalf of the company"
Every day "click here to agree that ..."
Re: Claude Platform on AWS
#84Earlier quoted context omitted.
Sadly it’s going to be more nuanced. 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%.
> click through EULAs Every year "don't agree to things on behalf of the company" Every day "click here to agree that ..."
Re: Claude Platform on AWS
#85Re: Claude Platform on AWS
#86Re: Claude Platform on AWS
#87Earlier 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…
Also you can spend your commitment contracts :p
Re: Claude Platform on AWS
#88So confusing. Are they with AWS for the checkout? Because none of sentences make sense to me
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 fut…
What's the point of having all those loops to onboard vendors if you can just buy from AWS marketplace (which AFIAK is not a particularly high bar to achieve for SaaS options)?
Like imagine $POOR_QUALITY_VENDOR. If they go through the normal channels they might get shot down. If they get procured on AWS Marketplace, then it feels to me in many organisations 'its fine', though AWS does minimal checking?
Re: Claude Platform on AWS
#89Earlier quoted context omitted.
> click through EULAs Every year "don't agree to things on behalf of the company" Every day "click here to agree that ..."
I've always wondered how this plays out in practice. I might certify that I have signing authority but I most certainly do not. What happens in the US (in Delaware?) when there's a dispute?
Legally it didn't matter whether the signer had authority because the way the signer's company behaved during the signing process implied that the signer had authority.
E.g. If the CTO at a company tells a vendor to "send the contract over to my product manager" then the CTO created the impression with the counterparty that the product manager has authority, and the company will be hound to the contract based on that fact regardless of whether the product manager actually has authority or not.
I'm sure it's more nuanced than this, but my understanding is actual authority is less relevant than implied authority. E.g. if you have your board of directors take away the CEO's authority to sign a contract, it doesn't automatically invalidate everything the CEO signs, since a counterparty can reasonably assume that the CEO has authority just based on their job title.