Claude Opus 4.7 and Haiku 4.5 Generally Available on Amazon Bedrock: 27 Regions and Self-Serve Enterprise Access

Anthropic has officially moved Claude Opus 4.7 and Claude Haiku 4.5 to general availability (GA) status within Amazon Bedrock. The move eliminates the previous invite-only access and opens both model variants to all AWS customers through a standard self-serve process in the console — no waitlist, no need to contact the sales team.

According to the company’s platform release notes, the models are now active in 27 AWS regions, including key European locations (Frankfurt, Dublin, Paris, Stockholm), all US regions, and much of Asia-Pacific. This makes Bedrock the most geographically broad managed endpoint for Claude — critical for enterprise customers with regulatory requirements around data residency (data must remain within a specific jurisdiction).

Why Is GA on Bedrock a Bigger Deal Than It Looks?

The previous access model for Claude through Bedrock was hybrid. Smaller models like Haiku 3.5 had long been generally available, but the latest and most capable models (Opus generation) required AWS approval along with a use-case justification, projected token volume, and contract review. That process could take anywhere from a few days to a couple of weeks.

By moving Opus 4.7 to GA, Anthropic removes that barrier. An enterprise customer who already has an AWS contract and IAM roles can activate the model in the Bedrock console within minutes, set quotas, and start sending production traffic. For regulated industries (finance, insurance, pharma), this matters because all billing, audit logs, and security controls happen within the AWS perimeter already covered under contract.

The other side of the equation is Haiku 4.5 — the fast, cost-efficient model for high-volume agentic workflows. Having both models in GA simultaneously means there is now a complete “ladder” from cheapest-first routing (Haiku for simple steps) to the strongest reasoning (Opus for complex decisions) within a single runtime.

How Does the New API Endpoint and Cross-Regional Routing Work?

The integration uses the standard Anthropic Messages API format, identical to that of the native Anthropic endpoint. Development teams that already have code for Claude can run it against Bedrock with only a change of base URL and authentication (IAM instead of API key). This radically reduces friction when migrating from the development phase (typically direct to Anthropic) to enterprise production (Bedrock).

Additionally, Bedrock now supports two routing modes for Claude:

• Regional routing — the request stays within the selected region, respecting data residency
• Global routing — the request is automatically balanced across multiple regions for lowest latency and resilience against regional quota limits

Global routing works especially well for stateless batch pipelines — say, each morning’s processing of new documents that doesn’t care where exactly the token-generation pass-through goes, as long as the result arrives quickly and reliably.

Which Customers Benefit Most From This Move?

Three segments will feel the benefit most strongly. First are AWS-centric financial institutions — banks and insurers that already run nearly their entire stack on AWS and were reluctant to add another external LLM vendor (Anthropic directly) due to additional contractual and vendor-risk processes. For them, GA on Bedrock is the equivalent of “already approved, ready for production.”

The second segment is healthcare and life sciences, where HIPAA obligations and BAA agreements with AWS already exist. Bedrock GA means Claude queries immediately enter the existing compliance perimeter, without additional BAA signing with Anthropic directly.

The third segment is large SaaS vendors running agentic pipelines who want Haiku 4.5 for massively parallel execution of small steps (e.g., classification, extraction), with infrequent calls to Opus 4.7 for complex decisions. GA enables that cost-tier routing to sit within a single AWS infrastructure and a single billing account.

For Anthropic and AWS, the move makes strategic sense — Bedrock is positioned as a mature multi-model marketplace, and Anthropic gains a distribution channel that requires no dedicated enterprise sales effort. Next steps will be visible through usage metrics and eventual new regions joining the list of 27.