Claude Platform on AWS(claude.com) |
Claude Platform on AWS(claude.com) |
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
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.
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.
Through AWS, assuming the underlying data governance is reasonable, this will be a much easier pill to swallow.
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.
Can confirm that this is the one and only reason that we use Claude through AWS
As other people have pointed out, it makes contract signing much easier.
THe other side effect is that it bumps up your spend, possibly to the point where you are eligible for "private pricing" ie global discount.
So its a win-win for most people.
Seems like there are two different options.
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
Initially that wasn’t the case, until April 2024.
https://aws.amazon.com/blogs/startups/aws-activate-credits-n...
I think AWS proposes to host actual agents, meaning you can customize their MCP servers, have them fetch and issue arbitrary requests, etc. Essentially a hosted minimal harness.
This is very much needed, as a form of "hosted claude code", allowing you to actually have the agent code, push, test from e.g. your phone.
I would note that I don’t think I would lean towards Anthropic (operating with one 9 currently) over aws (operating with an implied 5 9’s within a region and arbitrary 9’s by composing across regions). Anthropic makes good models. They’ve yet to prove they make good operations.
Suspect this is probably the same.
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.
Claude itself was almost from the very beginning available in bedrock.
Isn't there the possibility to have EU-based inference?
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.
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?
Right now, local LLMs are too expensive to run and not smart enough to matter much.
Anthropic’s offerings for Bedrock lag behind their main platform by months, maybe up to a year or more.
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 ..."
“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.
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.
Once a vendor has entered into a contract, that could change - e.g. "any change orders must be approved by $EMPLOYEE_SET".
It's absolutely wild that every W-2 employee can expose their employer to essentially unlimited liability, but AFAIK, that's the truth.