Birbla

Join the discussion

Write your take first — we'll ask for email only when you're ready to publish.

Sign in
  • Hacker News
  • So confusing. Are they with AWS for the checkout? Because none of sentences make sense to me
    by abhik24
  • Yes. You can pay your Anthropic bill thru AWS, and use AWS access controls to manage access to Anthropic APIs. For companies all in on AWS this lowers the friction to adopt Anthropic tools significantly.
    by skywhopper
  • 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 future codex + GPT on Bedrock plans. The harder it is for you to migrate, the better for Anthropic.
    by hibikir
  • 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.

    by cavemanDigAI
  • How to obscure your wasteful LLM usage behind your already massive AWS expenditure with this one tip.
    by xyst
  • I use Claude Code, the max plan, for 200$ a month. Privately. So if I convince my peers at work to use this, will it cost significantly more? Because it's token usage based? Not flat rate? And if so, how much more? I think I burned through 400m tokens in two months in Codex. Can someone shed on light on this?
    by submeta
  • 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?
    by niwtsol
  • > Claude Platform on AWS will be available in most AWS commercial regions and support global and U.S. inference geographies.

    Isn't there the possibility to have EU-based inference?

    by Lucasoato
  • 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.

    by whatever1
  • Might be for enterprise customers (with slow procurement departments) who already have AWS accounts but not Anthropic ones.
    by wafisher
  • > 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/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.

    by robot-wrangler
  • "mostly about billing" NO. People, this is about your data.
    by pbgcp2026
  • it's mostly about procurement. a lot of companies use AWS IAM for single sign on in a multitude of services.
    by jahller
  • It allows one to conveniently hide your claude expense in your big ass AWS bill.
    by notaharvardmba
  • I tried that with Bedrock but Claude models are billed through Marketplace and generate a completely separate invoice.

    Suspect this is probably the same.

    by nijave
  • I dont think this is about billing as other comments mentioned. AWS bedrock already does that.

    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.

    by Galanwe
  • Bedrock provides model inference as well as a few hosted things like agent core. This certainly provides more than bedrock, but it implies inference while fronted by aws policy and management will be farmed out to spacex and other providers. Anthropic already announced managed agents prior to this.

    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.

    by fnordpiglet
  • 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

    by ceuk
  • 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.
    by albert_e
  • > 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

    by ldoughty
  • 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). There's not really a good solution, as AgentCore runtime sucks and is expensive. You basically have to build this yourself because nobody is solving for self-hosted managed infra for agents, and we don't really have the time to build this sort of system on top of building our actual product. It's very frustrating for them to put this out as a win, when it doesn't help the people who are using AWS Bedrock to begin with.
    by pacoWebConsult
  • 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
    by foolfoolz
  • 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…
    by tietjens
  • Yeah i think this could backfire. At the moment they have such a clear messsage with Bedrock about data governance. You now have to ask a question and probalby get approval where previously there was no question and hence no barriers.
    by zmmmmm
  • > 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.

    by l5870uoo9y
  • Yeah its a "marketplace private offer"

    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.

    by KaiserPro
  • 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.

    by xyzzy123