What teams building AI features on Amazon Bedrock report, with every finding tied to its evidence.
Read the findingsPractitioner sentiment, teams and leaders
+9 Mixed from 57 sources that take a side
How this figure is madeFrom 57 authors in 52 discussions. Run a pilot on your own prompts to measure output quality and cost per task.
Feb 2025 to Oct 2026.
149 sources from practitioners, by month and sentiment.
Teams and leaders lean positive. Most buy through Bedrock because the AWS agreement, compliance approvals, and data boundary are already in place, and several keep it beside a vendor API as a second route. All 7 who discuss AWS integration praise it. Quotas and capacity are the most frequent concern, followed by data terms, account setup and model access.
Positive, mixed and negative sources
The score counts each source once, as the split does. See How the numbers work.
See the evidenceBelow: 4 praise themes, 5 concerns, 1 point of agreement and 1 disagreement.
Counted for Teams and technical leaders, from 70 sources. Change group
Every capability practitioners describe positively, ranked by how many sources say so. Open one to read who said it.
Counted for Teams and technical leaders.
Positive, 9
Positive
elpakal, Hacker News commenter
Comment on: Decisions API is in public betaHacker News comment
On Bedrock, the team just switched from OpenAI to Anthropic models because of the zero data retention guarantee.
Positive
Shaurya Kethireddy, Lead Member of Technical Staff, Slack
Slack AI: The Path to Multi-CloudEngineering blog post, Slack Engineering
Slack moved Slack AI from its own SageMaker GPU endpoints to Bedrock in 2024 to reach new models sooner and stop managing GPUs, then shifted bursty features to on-demand capacity. In 2026 it added Vertex AI so a single provider outage cannot take Slack AI down, and matching models to features cut latency about 67% on high-velocity, low-token workloads.
"Rollout: Implemented gradual traffic shifts via feature flags and instant rollback capabilities, ensuring 100% availability during the switch."
Positive
Founder of OutcomeOps
You're Probably Using the Wrong Bedrock Model. Here's How to Tell.Engineering blog post, OutcomeOps blog
Running eight models from five providers on Bedrock through the same RAG pipeline, OutcomeOps found Claude Haiku 4.5 gave the most complete answer, ahead of Sonnet 4.6.
Positive
ceuk, Hacker News commenter
Comment on: Claude Platform on AWSHacker News comment
The startup relies heavily on Anthropic models via Bedrock, partly to spend its AWS startup credits, and values that Bedrock offers more than Anthropic's models.
Positive
InvidFlower, Hacker News commenter
Comment on: OpenAI models coming to Amazon Bedrock: Interview with OpenAI and AWS CEOsHacker News comment
With Claude Code on Bedrock and most systems on AWS under SOC 2, the team expects trying Codex to be simple once OpenAI models are on Bedrock.
Positive
azath92, Hacker News commenter
Comment on: Qwen3.5 Fine-Tuning GuideHacker News comment
Benchmarking a document classification task the team sends to Haiku, the author found several small models on Bedrock matched Haiku closely at a fraction of the input price.
Positive
Ravindra Pandya, reviewing a client's Bedrock project
5 Hard-Earned Lessons from Building a Production App on Amazon BedrockPersonal blog post, DEV Community
A client's document extraction ran as accurately on Claude Haiku as on Opus at about a fifteenth of the cost; logging costs and missing rate-limit handling caused the incidents.
Positive
mparis, Hacker News commenter
Comment on: Structured outputs on the Claude Developer PlatformHacker News comment
The team has run JSON-schema structured output with Claude on Bedrock in production for a year, using a schema, a prefilled brace, and light parsing.
Mixed
Mandy Gu, engineering leader, Wealthsimple
Launching GenAI Productivity Tools: Insights and LessonsEngineering article, InfoQ
Wealthsimple's gateway began with OpenAI and Cohere, added Gemini for its 1M-token context, then added Amazon Bedrock. Integrating each provider's interface caused friction, so in September 2024 the team rebuilt the gateway API to mirror OpenAI's specification.
"After supporting multi-modal inputs, the next thing we added to our platform was Amazon Bedrock. Bedrock is AWS's managed service for interacting with foundational large language models.It also provides the ability to deploy and fine-tune these models at scale."
Mixed or negative, 2
Negative
hoo29, r/aws
Suspension of Anthropic Models on BedrockReddit post
AWS revoked a UK team's Anthropic model access on Anthropic's direction, and could not say which prompts broke the policy because AWS does not receive the details.
Positive
Hypertrail engineering team
Migrating from Legacy Bedrock Agents to Strands Agents powered by Amazon Bedrock AgentCore RuntimeEngineering blog post, Hypertrail blog
Hypertrail moved its agent platform from Bedrock Agents to Strands on AgentCore Runtime in about a month; only Anthropic models first passed its cross-model tests.
Counted for Teams and technical leaders.
Positive
CorpOverreach, Hacker News commenter
Comment on: Push events into a running session with channelsHacker News comment
The company proxies Claude Code through Bedrock, and Bedrock logs have been instrumental in tracing what led a user to repeated risky software installs.
Positive
Ravindra Pandya, reviewing a client's Bedrock project
5 Hard-Earned Lessons from Building a Production App on Amazon BedrockPersonal blog post, DEV Community
A client's document extraction ran as accurately on Claude Haiku as on Opus at about a fifteenth of the cost; logging costs and missing rate-limit handling caused the incidents.
Positive
kingslayerer, r/aws
Comment on: GLM 5.3 on Bedrock still not available?Reddit comment
Connected the Zed editor to Bedrock because it is the only provider the author trusts not to train on the team's code, helped by the team's AWS credits.
Mixed
Siddharth Kodwani, Software Engineer, GenAI Platform, DoorDash, with Swaroop Chitlur
Building a GenAI Platform at DoorDashConference talk, InfoQ
DoorDash's gateway calls the Claude API endpoint with Amazon Bedrock as its fallback, and OpenAI with Azure, so services stay up when one route fails. As usage grew, the gateway added workspaces that attribute cost to each department.
"We actually had to go understand what the fallback should be, what kind of routing should be. At one point, I remember we had OpenAI endpoint, but we also had a fallback on Azure endpoint. Or, we had Claude model API endpoint, then we had a fallback on Bedrock, so that the services can rely on us from the reliability point of view. We went in that direction. We quickly realized that as the usage is going up, then we need a way to track, because now finance got involved. Like, you guys have one API key for multiple teams, how do I track who is using what? We quickly realized we need workspaces where we have cost attribution. We can actually drill down on who is using how much. We can attribute cost back to those departments. That's what basically we did with LLM Gateway."
Negative
Piotr6543, r/aws
New account with quota 0 on aws bedrock frontier modelsReddit post
A startup moved its infrastructure to AWS on US$5,000 in credits, then found its quota for frontier models set to zero and its increase request auto-denied.
Positive
ErsiHoxholli, MedPolaris on GitHub
[EXT-04] Configure Claude API via AWS Bedrock eu-central-1: EU data residency confirmedGitHub issue
MedPolaris routes Claude through Bedrock in eu-central-1 to keep health data in the EU, with an IAM role in place of API keys. It avoids Anthropic's API.
Positive
alach11, Hacker News commenter
Comment on: Amazon introduces Nova ChatHacker News comment
At the commenter's Fortune 500 non-tech company, Anthropic models are bought through Bedrock with a click-through EULA.
Counted for Teams and technical leaders.
Positive
Engineer at Neradot
Case Study: Cutting LLM Cost by 36% with Prompt CachingEngineering blog post, Neradot blog
Neradot cut a production support agent's inference cost by 36% with prompt caching on Claude via Bedrock, placing its own cache breakpoints.
"Two passes later the bill was down 36%, with no measurable change in output quality."
Mixed
indemnity, Hacker News commenter
Comment on: Orchestrate teams of Claude Code sessionsHacker News comment
At work the team runs Claude Code through a proxy to Bedrock: slower than Anthropic direct and later to get new models, but much cheaper by its stats.
Positive
Ravindra Pandya, reviewing a client's Bedrock project
5 Hard-Earned Lessons from Building a Production App on Amazon BedrockPersonal blog post, DEV Community
A client's document extraction ran as accurately on Claude Haiku as on Opus at about a fifteenth of the cost; logging costs and missing rate-limit handling caused the incidents.
Positive
Ancapistani, Hacker News commenter
Comment on: Anyone who trusts an AI therapist needs their head examinedHacker News comment
Rolling out AI features on a mental health platform, the author found Bedrock prompt caching brought per-conversation cost down to where it is no longer a concern.
Positive
Shaurya Kethireddy, Lead Member of Technical Staff, Slack
Slack AI: The Path to Multi-CloudEngineering blog post, Slack Engineering
Slack moved Slack AI from its own SageMaker GPU endpoints to Bedrock in 2024 to reach new models sooner and stop managing GPUs, then shifted bursty features to on-demand capacity. In 2026 it added Vertex AI so a single provider outage cannot take Slack AI down, and matching models to features cut latency about 67% on high-velocity, low-token workloads.
"Rollout: Implemented gradual traffic shifts via feature flags and instant rollback capabilities, ensuring 100% availability during the switch."
Counted for Teams and technical leaders.
Positive, 3
Positive
Hypertrail engineering team
Migrating from Legacy Bedrock Agents to Strands Agents powered by Amazon Bedrock AgentCore RuntimeEngineering blog post, Hypertrail blog
Hypertrail moved its agent platform from Bedrock Agents to Strands on AgentCore Runtime in about a month; only Anthropic models first passed its cross-model tests.
Positive
valbaca, Hacker News commenter
Comment on: Ask HN: Anyone is an "AI Engineer"? What does your job tasks include?Hacker News comment
As the team's AI expert, the author builds RAG on Knowledge Bases with Guardrails and Bedrock Reranker, runs accuracy evaluations, and adds rate limiters around tool limits.
Positive
Ravindra Pandya, reviewing a client's Bedrock project
5 Hard-Earned Lessons from Building a Production App on Amazon BedrockPersonal blog post, DEV Community
A client's document extraction ran as accurately on Claude Haiku as on Opus at about a fifteenth of the cost; logging costs and missing rate-limit handling caused the incidents.
Mixed or negative, 3
No opinion stated
Jose Enrique Hernandez (@_josehelps), Prevention Engineering at MagicSword, former Splunk Threat Research director
Post on stealing a Bedrock AgentCore agent's cloud identityX post
One chat prompt to a public Bedrock AgentCore agent was enough to steal its cloud identity, a warning to scope the permissions an agent's role carries.
"One chat prompt to a public AWS Bedrock AgentCore agent was enough to steal its cloud identity."
Mixed
fennecfoxy, Hacker News commenter
Comment on: Beating GPT-5.6 Sol on retrieval with 100x cheaper open modelsHacker News comment
On Bedrock Knowledge Bases the team is locked into a basic RAG implementation, with hybrid search hard to use, although it works reliably.
Negative
pacoWebConsult, Hacker News commenter
Comment on: Claude Platform on AWSHacker News comment
Export compliance forces the company onto Bedrock for US-only inference, and with AgentCore Runtime judged poor and expensive, it has to build agent infrastructure itself.
Every concern practitioners raise, most raised first.
Counted for Teams and technical leaders.
Raised as a concern, 12
Negative
Professional-Sir7048, r/aws
Comment on: Are GPT 5.6 models down?Reddit comment
Sees high error rates on GPT-6.1 Sol and GPT-6 Luna on Bedrock, inconsistent between the Mantle and regular endpoints, with no published downtime metrics.
Negative
HKChad, r/aws
Comment on: Absolutely bonkers that Bedrock is blocked for newer accountsReddit comment
After six months of monthly quota requests went unanswered or denied, the team moved to the model provider's own API.
Negative
Mik_Mik_Mik, r/aws
TPM Quota Increase Request Denied with No Clear Reason (Bedrock)Reddit post
After six months of US$300 to US$500 a month on Activate credits, the company's tokens-per-minute increase for Bedrock agents keeps being denied over billing history.
Negative
jdgoesmarching, Hacker News commenter
Comment on: Stripe will reportedly acquire OpenRouter for US$7B+Hacker News comment
After a year of rate limiting, slowness, and Bedrock lagging on new open models and their API features, the commenter decided OpenRouter is worth its cut.
Negative
Piotr6543, r/aws
New account with quota 0 on aws bedrock frontier modelsReddit post
A startup moved its infrastructure to AWS on US$5,000 in credits, then found its quota for frontier models set to zero and its increase request auto-denied.
Negative
Ziva, AI agent for game engines
16 days, 4 channels, no AWS Bedrock quota fixEngineering blog post, Ziva blog
Ziva's Bedrock quotas sat 1,000 to 2,000 times below AWS's documented defaults, throttling 14 to 16% of requests, and four escalation channels over 16 days failed to raise them.
"TL;DR: AWS is throttling our Bedrock usage at 1,000x below the minimum quota and won’t increase it."
Negative
sarathyweb, Hacker News poster
Tell HN: Claude Opus 4.7 quota suddenly changed to 0 TPM in BedrockHacker News post
The team's Claude Opus 4.7 quota on Bedrock was set to zero without warning, and AWS support could not guarantee restoration and suggested moving to Opus 4.6.
Negative
kgeist, Hacker News commenter
Comment on: Anthropic takes US$5B from Amazon and pledges US$100B in cloud spending in returnHacker News comment
A feature cannot launch in regions where the team must use Bedrock for legal reasons because latency is too poor; self-hosted models respond about three times faster.
Negative
ZeroCool2u, Hacker News commenter
Comment on: Amazon introduces new frontier Nova modelsHacker News comment
The commenter's team saw too many 500 errors while well below its service quotas, which pushed it toward OpenRouter.
Positive
Shaurya Kethireddy, Lead Member of Technical Staff, Slack
Slack AI: The Path to Multi-CloudEngineering blog post, Slack Engineering
Slack moved Slack AI from its own SageMaker GPU endpoints to Bedrock in 2024 to reach new models sooner and stop managing GPUs, then shifted bursty features to on-demand capacity. In 2026 it added Vertex AI so a single provider outage cannot take Slack AI down, and matching models to features cut latency about 67% on high-velocity, low-token workloads.
"Rollout: Implemented gradual traffic shifts via feature flags and instant rollback capabilities, ensuring 100% availability during the switch."
Mixed
indemnity, Hacker News commenter
Comment on: Orchestrate teams of Claude Code sessionsHacker News comment
At work the team runs Claude Code through a proxy to Bedrock: slower than Anthropic direct and later to get new models, but much cheaper by its stats.
Positive
Ravindra Pandya, reviewing a client's Bedrock project
5 Hard-Earned Lessons from Building a Production App on Amazon BedrockPersonal blog post, DEV Community
A client's document extraction ran as accurately on Claude Haiku as on Opus at about a fifteenth of the cost; logging costs and missing rate-limit handling caused the incidents.
Discussed without concern, 3
Mixed
7thpower, Hacker News commenter
Comment on: OpenAI models coming to Amazon Bedrock: Interview with OpenAI and AWS CEOsHacker News comment
The team left Azure OpenAI's small quotas and provisioned-throughput push for Claude 3 on Bedrock, though that experience was also rough.
Positive
jedwhite, Hacker News commenter
Comment on: Show HN: Executable Markdown files with Unix pipesHacker News comment
By the team's own evals, Bedrock is steady when a model version is pinned, after earlier performance degradation at peak load.
Positive
valbaca, Hacker News commenter
Comment on: Ask HN: Anyone is an "AI Engineer"? What does your job tasks include?Hacker News comment
As the team's AI expert, the author builds RAG on Knowledge Bases with Guardrails and Bedrock Reranker, runs accuracy evaluations, and adds rate limiters around tool limits.
GILD's fact checks, which don't count as sources
Checked Oct 12, 2026.Quotas are set per model and per Region, separately for on-demand and cross-Region inference, and are raised through Service Quotas. The Reserved tier reserves tokens-per-minute capacity for 1 or 3 months, overflows to Standard, and targets 99.5% uptime. Service tiers
Open them in the recordCounted for Teams and technical leaders.
Raised as a concern, 7
Negative
SmoothRunnings, r/aws
Cannot access OpenAI.GPT-5.6-sol in BedrockReddit post
A company already running Claude on Bedrock could not enable GPT-5.6 Sol for a manager, getting AccessDeniedException even from the root account.
Negative
Piotr6543, r/aws
New account with quota 0 on aws bedrock frontier modelsReddit post
A startup moved its infrastructure to AWS on US$5,000 in credits, then found its quota for frontier models set to zero and its increase request auto-denied.
Negative
HeyItsFudge, r/aws
Bedrock is an exclusionist and outdated platform for AIReddit post
AWS support refused a startup access to current Claude models, citing payment history; by the time it replied to an Opus 4.8 request, Opus 5 had shipped.
Negative
daemonologist, Hacker News commenter
Comment on: OpenAI releasing new open model in coming months, seeks community feedbackHacker News comment
Adding any vendor is a compliance hurdle at the commenter's company, and even enabling Bedrock in an existing AWS account had taken months.
Mixed
ghshephard, Hacker News commenter
Comment on: Navier-Stokes - Tristan Buckmaster [pdf]Hacker News comment
At a multi-billion-dollar company already big on AWS, approving Bedrock on dedicated GPUs took 4 to 6 months of legal review, and Fable remains off-limits over retention.
No opinion stated
sharon-wang, Posit engineer and posit-dev/ai-lib maintainer
Claude Fable 5 on Bedrock returns raw 400 (data retention mode 'default' not available)GitHub issue, posit-dev/ai-lib
Selecting Claude Fable 5 on Posit Assistant's Bedrock provider returned HTTP 400 on every message, with an error saying the default data retention mode was not available for the model. A later comment proposed keeping such models out of the picker; by Oct 23, 2026 the cause and the retention modes the model accepts were still unconfirmed.
"Selecting Claude Fable 5 on the Amazon Bedrock provider and sending any message returns HTTP 400 before generation…"
Negative
Ziva, AI agent for game engines
16 days, 4 channels, no AWS Bedrock quota fixEngineering blog post, Ziva blog
Ziva's Bedrock quotas sat 1,000 to 2,000 times below AWS's documented defaults, throttling 14 to 16% of requests, and four escalation channels over 16 days failed to raise them.
"TL;DR: AWS is throttling our Bedrock usage at 1,000x below the minimum quota and won’t increase it."
Discussed without concern, 1
Positive
ErsiHoxholli, MedPolaris on GitHub
[EXT-04] Configure Claude API via AWS Bedrock eu-central-1: EU data residency confirmedGitHub issue
MedPolaris routes Claude through Bedrock in eu-central-1 to keep health data in the EU, with an IAM role in place of API keys. It avoids Anthropic's API.
GILD's fact checks, which don't count as sources
Checked Oct 12, 2026.Many models are available by default once the calling role holds the AWS Marketplace subscribe permissions. Anthropic models need a one-time use-case form on the bedrock-runtime endpoint, and some models require separate account-level access. Request access to models
Open them in the recordCounted for Teams and technical leaders.
Raised as a concern, 7
Negative
hoo29, r/aws
Suspension of Anthropic Models on BedrockReddit post
AWS revoked a UK team's Anthropic model access on Anthropic's direction, and could not say which prompts broke the policy because AWS does not receive the details.
Mixed
ghshephard, Hacker News commenter
Comment on: Navier-Stokes - Tristan Buckmaster [pdf]Hacker News comment
At a multi-billion-dollar company already big on AWS, approving Bedrock on dedicated GPUs took 4 to 6 months of legal review, and Fable remains off-limits over retention.
No opinion stated
sharon-wang, Posit engineer and posit-dev/ai-lib maintainer
Claude Fable 5 on Bedrock returns raw 400 (data retention mode 'default' not available)GitHub issue, posit-dev/ai-lib
Selecting Claude Fable 5 on Posit Assistant's Bedrock provider returned HTTP 400 on every message, with an error saying the default data retention mode was not available for the model. A later comment proposed keeping such models out of the picker; by Oct 23, 2026 the cause and the retention modes the model accepts were still unconfirmed.
"Selecting Claude Fable 5 on the Amazon Bedrock provider and sending any message returns HTTP 400 before generation…"
Mixed
cjonas, Hacker News commenter
Comment on: Claude Opus 5Hacker News comment
The team could not use Opus 5 in its Bedrock account without setting its data retention mode to provider data sharing.
Negative
consumer451, Hacker News commenter
Comment on: Anthropic requires 30 day data retention for Fable and MythosHacker News comment
Because of Fable's retention policy, the author will not use it in products the company sells, and can no longer give customers a simple no-training assurance about Bedrock.
Negative
calgoo, Hacker News commenter
Comment on: AWS Bedrock to require sharing data with Anthropic for Mythos and future modelsHacker News comment
With no guarantee that corporate documents will not be shared, and Bedrock already costing more than Anthropic's API, the team sees no reason to stay on Bedrock.
Negative
nijave, Hacker News commenter
Comment on: AWS Bedrock to require sharing data with Anthropic for Mythos and future modelsHacker News comment
The retention change adds overhead: the team must now vet every Bedrock model and deny those that retain data, where before anything on Bedrock was fine to try.
Discussed without concern, 3
Positive
elpakal, Hacker News commenter
Comment on: Decisions API is in public betaHacker News comment
On Bedrock, the team just switched from OpenAI to Anthropic models because of the zero data retention guarantee.
Positive
kingslayerer, r/aws
Comment on: GLM 5.3 on Bedrock still not available?Reddit comment
Connected the Zed editor to Bedrock because it is the only provider the author trusts not to train on the team's code, helped by the team's AWS credits.
Positive
jdm2212, Hacker News commenter
Comment on: On the Navier-Stokes Millennium Prize ProblemHacker News comment
Three companies the commenter has worked for each combined enterprise agreements, self-hosting, and Bedrock to keep proprietary data out of model training.
GILD's fact checks, which don't count as sources
Checked Oct 12, 2026.Bedrock does not share inputs or outputs with model providers. Claude Fable 5 and 5.1 require the aws_review mode, under which AWS keeps prompts and outputs up to 30 days inside AWS; provider_data_share is a legacy mode that shares nothing today. Data retention
Open them in the recordCounted for Teams and technical leaders.
Raised as a concern, 4
Negative
TheP1000, Hacker News commenter
Comment on: Codex on AWS bedrock bug causing 10x chargesHacker News comment
The team's Codex on Bedrock cache read-to-write ratio was under 5%, making it cost about 10x what it should until a workaround.
Negative
KronisLV, Hacker News commenter
Comment on: Microsoft starts canceling Claude Code licensesHacker News comment
A colleague spent 100 euros in one day on Sonnet 4.6 through Bedrock, chosen to keep data in the EU, against about 20 euros a month for a Mistral subscription.
Negative
joshdev, Hacker News commenter
Comment on: Sonnet 4.6 Elevated Rate of ErrorsHacker News comment
The team found Bedrock double counting cache writes for Anthropic models with thinking enabled, alongside a much higher cache miss rate, inflating usage.
Positive
Ravindra Pandya, reviewing a client's Bedrock project
5 Hard-Earned Lessons from Building a Production App on Amazon BedrockPersonal blog post, DEV Community
A client's document extraction ran as accurately on Claude Haiku as on Opus at about a fifteenth of the cost; logging costs and missing rate-limit handling caused the incidents.
Discussed without concern, 2
Mixed
orwin, Hacker News commenter
Comment on: Fable Took My JobHacker News comment
The team's Bedrock usage cost about US$7,000 last month, while another internal team tests open models on its own hardware.
Mixed
jasonthorsness, Hacker News commenter
Comment on: How Anthropic teams use Claude CodeHacker News comment
Piloting Claude Code at work through Bedrock, the author finds the per-session dollar total disconcerting and worries metering will discourage experimentation.
GILD's fact checks, which don't count as sources
Checked Oct 12, 2026.Bedrock attributes inference cost by IAM principal, application inference profile, Projects, and request metadata. A surprise bill alone does not show that cost tracking was unavailable. Track usage and costs
Open them in the recordCounted for Teams and technical leaders.
Raised as a concern, 2
Mixed
sajithdilshan, Hacker News commenter
Comment on: Sonnet 5.5Hacker News comment
The team runs Anthropic models on Bedrock in EU regions for compliance and cannot try newer OpenAI models because they are not offered in any EU region.
Negative
kgeist, Hacker News commenter
Comment on: Anthropic takes US$5B from Amazon and pledges US$100B in cloud spending in returnHacker News comment
A feature cannot launch in regions where the team must use Bedrock for legal reasons because latency is too poor; self-hosted models respond about three times faster.
Discussed without concern, 3
Positive
a_bonobo, Hacker News commenter
Comment on: OpenAI frontier models and Codex are now available on AWSHacker News comment
Bedrock lets the team control which country its data stays in for many models, a requirement Anthropic's API cannot meet for its non-US operations.
Positive
ErsiHoxholli, MedPolaris on GitHub
[EXT-04] Configure Claude API via AWS Bedrock eu-central-1: EU data residency confirmedGitHub issue
MedPolaris routes Claude through Bedrock in eu-central-1 to keep health data in the EU, with an IAM role in place of API keys. It avoids Anthropic's API.
Negative
KronisLV, Hacker News commenter
Comment on: Microsoft starts canceling Claude Code licensesHacker News comment
A colleague spent 100 euros in one day on Sonnet 4.6 through Bedrock, chosen to keep data in the EU, against about 20 euros a month for a Mistral subscription.
GILD's fact checks, which don't count as sources
Checked Oct 25, 2026.Current Claude models such as Opus 5.5 use Geographic or Global cross-Region profiles. On bedrock-runtime, Opus 5.5 runs on a single-Region endpoint only in London. Geographic profiles keep processing inside the US, EU, Australia, or Japan. Claude Opus 5.5 model card
Open them in the recordStatements this group's sources agree on, then the ones close to agreement.
Teams choose Bedrock when AWS contracts, credits, compliance approvals, and the data boundary already exist. That avoids a new vendor review.
23 supporting sourcesClose to agreement: each needs 14 supporting sources
Teams test models on their own workloads before choosing or switching. Results vary by model, task, and sometimes platform.
7 supporting sourcesBuilders keep an abstraction such as Converse, LiteLLM, or an internal wrapper so they can change models or providers.
5 supporting sourcesQuestions the sources split on, with the count on each side.
Evidence remains mixed
Through Bedrock, 8 sources
Most buy through Bedrock for the existing AWS agreement, credits, and data boundary.
Vendor API, 2 sources
Some move to Anthropic directly after Bedrock quota or reliability problems.
The three groups, then every practitioner by the context they work in, and how emphasis changes with scale.
Three groups drawn from the same sources. Choose a group to select whose experience counts. Within that group, each author counts once in the practitioner sentiment, with their latest view. Signals open on Teams and technical leaders.
70 sources. These accounts focus on procurement, data terms, capacity at production volume, and the managed agent and retrieval services, from the accounts of teams and companies running Bedrock in their products.
79 sources. These accounts focus on the model catalog, quotas, setup, and day-to-day reliability for developers building on Bedrock on their own.
149 sources. This gives the broadest read, but combines solo projects with production teams that can reach different conclusions.
149 sources from practitioners, by the context they work in. Filled rows count for this group.
Emphasizes Model catalog and quota friction
Emphasizes Account access and capacity
Emphasizes EU data residency and prompt-caching savings
Emphasizes Agents on AgentCore and Claude in production, with low default quotas to plan for
Emphasizes Buying models under an existing AWS agreement
What changes with scale. Individual builders focus on the catalog and quota friction. Team and company accounts focus on procurement, the AWS data boundary, and the data terms that decide which models they can use, and the largest, such as DoorDash and Fin, run Bedrock as one of two routes to the same models.
Where this group's sources were published.
Counted for Teams and technical leaders, from 70 sources. Change group
90 sources for this group, 20 of them documentation
Older evidence stays when it still applies. Accounts tied to retired models, earlier Regions or access rules, or changed data terms remain in the history with a Needs a recheck label.
See sources by originWho each source is, how it knows, whether it still applies and what it counts toward.
Newest first, on its own page. Every count above opens its sources there.
Read all 169 sourcesAbout this read
A running review of what teams building AI features on Amazon Bedrock report, from individual builders to company-wide platforms. Each finding links to its sources, and each conflict shows both sides.
Counts cover only the sources GILD reviewed.
Choose a group to select whose experience counts. Within that group, each author counts once in the practitioner sentiment, with their latest view. GILD files each source in a group from how the account describes its author. A role or employer marked self-described is what the source states about themselves. Documentation checks facts for every group and never counts toward sentiment.
A source's date and whether it still applies are separate: a recent post can describe an old version, and an old one can still hold.
Flagged for a recheck, of the sources that take a side: teams and leaders 2 of 57, individual builders 4 of 51, all practitioners 6 of 108.
Each row opens its sources for the group you are reading.
| Finding | Teams and technical leaders | Individual builders | All practitioners | Sources |
|---|---|---|---|---|
| Current readCurrent sentiment | 25 positive, 12 mixed, 20 negative | 18 positive, 12 mixed, 21 negative | 43 positive, 24 mixed, 41 negative | Sources |
| PraiseModel Choice | 9 of 11 positive | 8 of 16 positive | 17 of 27 positive | Sources |
| PraiseManaged Agents, RAG & Guardrails | 3 of 6 positive | 1 of 4 positive (under the minimum) | 4 of 10 positive | Sources |
| PraiseCost Efficiency | 5 of 5 positive | 5 of 7 positive | 10 of 12 positive | Sources |
| PraiseAWS Integration | 7 of 7 positive | 4 of 4 positive (under the minimum) | 11 of 11 positive | Sources |
| PraiseDeveloper Experience | 0 of 2 positive (under the minimum) | 0 of 5 positive | 0 of 7 positive | Sources |
| PraiseStability | 2 of 3 positive (under the minimum) | 3 of 5 positive | 5 of 8 positive | Sources |
| PraiseSpeed | 2 of 2 positive (under the minimum) | 4 of 5 positive | 6 of 7 positive | Sources |
| PraiseModel Quality | 4 of 4 positive (under the minimum) | 2 of 5 positive | 6 of 9 positive | Sources |
| PraiseTool Use & Structured Output | 1 of 2 positive (under the minimum) | 2 of 2 positive (under the minimum) | 3 of 4 positive (under the minimum) | Sources |
| PraiseContext Window | 0 of 0 positive (under the minimum) | 2 of 2 positive (under the minimum) | 2 of 2 positive (under the minimum) | Sources |
| ConcernQuotas, Capacity & Latency | 12 of 15 raise it | 8 of 10 raise it | 20 of 25 raise it | Sources |
| ConcernSetup & Model Access | 7 of 8 raise it | 5 of 5 raise it | 12 of 13 raise it | Sources |
| ConcernCost Surprises | 4 of 6 raise it | 5 of 5 raise it | 9 of 11 raise it | Sources |
| ConcernRegional Availability | 2 of 5 raise it | 4 of 6 raise it | 6 of 11 raise it | Sources |
| ConcernLag Behind Vendor APIs | 4 of 4 raise it (under the minimum) | 5 of 7 raise it | 9 of 11 raise it | Sources |
| ConcernData Terms & Retention | 7 of 10 raise it | 1 of 1 raise it (under the minimum) | 8 of 11 raise it | Sources |
| ConcernLatency | 4 of 4 raise it (under the minimum) | 2 of 2 raise it (under the minimum) | 6 of 6 raise it | Sources |
| ConcernInconsistent Results | 4 of 4 raise it (under the minimum) | 4 of 4 raise it (under the minimum) | 8 of 8 raise it | Sources |
| ConcernTool Calling Failures | 0 of 0 raise it (under the minimum) | 10 of 10 raise it | 10 of 10 raise it | Sources |
| ConcernLong-Context Limits | 0 of 0 raise it (under the minimum) | 3 of 3 raise it (under the minimum) | 3 of 3 raise it (under the minimum) | Sources |
| ConsensusBought through the AWS agreement | 23 supporting | 6 supporting (below threshold) | 29 supporting (below threshold) | Sources |
| ConsensusTest on your own task | 7 supporting (below threshold) | 5 supporting (below threshold) | 12 supporting (below threshold) | Sources |
| ConsensusKeep a layer in front | 5 supporting (below threshold) | 5 supporting (below threshold) | 10 supporting (below threshold) | Sources |
| DisagreementShould a team buy models through Bedrock or from the model vendor directly? | Through Bedrock 8, Vendor API 2 | Through Bedrock 3, Vendor API 3 | Through Bedrock 11, Vendor API 5 | Sources |
| DisagreementShould a team build on Bedrock's managed agents and retrieval, or run its own on Bedrock inference? | Managed services 3, Own code on Bedrock models 1 (under the minimum) | Managed services 1, Own code on Bedrock models 1 (under the minimum) | Managed services 4, Own code on Bedrock models 2 | Sources |
| Current readEvidence mix | 90 sources | 99 sources | 169 sources | Sources |
GILD's checks of claims against official documentation, kept apart from the source counts.
