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

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

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.

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

Claude itself was almost from the very beginning available in bedrock.

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.

Seems intentionally deceitful.