On May 20, 2026, Amazon Bedrock — the cloud service AWS describes as the foundation of its generative AI strategy — went down for 15 hours and 54 minutes.
Six weeks before that outage, Andy Jassy used his 2025 shareholder letter to tell investors that Bedrock had been rebuilt by six engineers in 76 days using AWS’s own agentic coding tool, Kiro. He framed it as a productivity miracle. “Normally, this sort of activity might take a team of 40 people about a year to carefully build,” Jassy wrote. “Instead, the Bedrock team spun up a separable group of six very skilled engineers who were excited about starting over and building on our agentic coding service (Kiro), and delivered this new engine (which we call ‘Mantle’) in 76 days.”
The narrative was repeated at re:Invent. It made the rounds in Network World, CIO, Business Insider, and a half-dozen newsletters by people who don’t ship code. Six engineers, 76 days. AI did it. The future of software development is here.
There was just one problem.
The Bedrock engineers on the ground had already debunked the narrative six months before Jassy ever said it. And the May 20 outage — coupled with the public outage record since Mantle’s launch — makes them look prophetic.
The Reddit Thread
In October 2025, an Amazon software engineer posted to r/amazonemployees with this question:
I recently heard at the office that the team owning Bedrock had refactored their backend in a month using AI. Apparently, the engineers were too slow implementing the features leadership wanted, so they gave it a try and it worked. Is this true?
The thread title: “Was AWS Bedrock entirely refactored by AI in one month?”
That title is the entire story. It is a Bedrock engineer hearing the internal hype version of the Mantle narrative — already shaped by the same marketing instincts that would later produce Jassy’s shareholder letter — and asking publicly whether his coworkers are lying.
The answers from inside the building, six months before the CEO spin cycle, are extraordinary.
What the Engineers Said
A Bedrock veteran responded:
More than a month. Hard to give it a number because more engineers were added to the project later, but it started in May. It was A/B tested a month or two ago iirc. And it wasn’t a refactor as much as a rewrite. And yes they used AI, but “they” in this case was a DE and like 8 TT PEs from EC2. So it’s not like they told Q to “refactor Bedrock.” And it wasn’t the entirety of Bedrock’s backend.
Translate the acronyms. DE: Distinguished Engineer. TT PE: Top Talent Principal Engineer. EC2: the team that has been at AWS longer than most of the cloud existed.
Now run the engineer’s account against the CEO’s. Jassy said “six very skilled engineers.” The engineer said one Distinguished Engineer plus eight Top Talent Principal Engineers loaned in from EC2, with more added later. Jassy said “76 days.” The engineer said the work started in May 2025 and was still in A/B testing in August or September, which is roughly four to five months. Jassy said “this new engine,” implying a wholesale inference-engine replacement. The engineer said it was “mostly the way routing and load balancing worked” and that it was not the entirety of Bedrock’s backend. Jassy said “delivered.” The engineer’s colleague said huge parts of Bedrock had not been migrated. Jassy implied broad coverage. Another engineer on the same thread said the rewrite only handled “shitty open source models that are like 2% of total traffic. Will their refactor scale to Claude too? Time will tell.”
Every load-bearing number in the shareholder letter has a more accurate version stated by an actual Bedrock engineer six months earlier.
But the most damaging revelation came when the original poster found the internal broadcast video that the principal engineer used to walk the company through the project. After watching, the OP returned to update the thread:
The principal engineer says in the video that they used AI precisely to generate the unit tests for all the code they had written without.
The engineers wrote the production code without tests. They then asked AI to generate tests for the code that was already shipping. Another engineer responded with the joke that writes itself:
def unit_test(input):
if ai_generated_func(input):
return True
else:
return True
Two return values. Both True. The tests cannot catch what they were never designed to catch. They are not testing the code — they are testing whatever the AI generated as a description of the code it didn’t write.
This is the inversion at the heart of the entire narrative. The official story is “AI rewrote Bedrock in 76 days.” The actual story is “elite engineers rewrote a piece of Bedrock in roughly five months, then asked AI to backfill tests for code they had shipped without them.”
Those are not the same claim. One belongs in a productivity case study. The other belongs in a post-incident review.
What Mantle Actually Is
Read AWS’s own product documentation, not the shareholder letter, and a much narrower picture emerges.
Mantle is the bedrock-mantle endpoint. It exposes OpenAI-compatible APIs — Responses, Chat Completions, and Messages — for a subset of models. The legacy bedrock-runtime endpoint is still there. Most production Claude inference still flows through it.
From the AWS Bedrock user guide: “Amazon Bedrock provides the OpenAI Responses API via the bedrock-mantle endpoint.” The verb is “provides,” not “replaces.” A new endpoint sits next to the existing one. Customers on Claude do not see Mantle in their request paths. Customers using Anthropic’s flagship models — the ones that account for the bulk of Bedrock’s revenue and the entire reason Anthropic and Amazon signed a multi-billion-dollar partnership — are still on the legacy backend the Reddit engineers described as a “dumpster fire.”
That is the rebuild. A new endpoint for a narrow set of OpenAI-compatible models. Not the whole inference engine. Not the whole platform. The engineers were right.
What Production Users Actually See
If Mantle were the success the shareholder letter described, production reviews would show measurable improvement over the legacy Bedrock experience. They do not.
Bedrock’s public outage record since Mantle’s December 2025 launch reads like an indictment. On May 20, 2026, increased error rates and latencies kept the service degraded for 15 hours and 54 minutes. Earlier that month, on May 6 through May 8, three back-to-back warning periods totaled roughly 16 hours plus two consecutive days of degraded service. On April 27, 2026, Bedrock AgentCore was down for 12 hours and 12 minutes. And before any of those, on October 19 and 20, 2025, the us-east-1 DynamoDB and DNS cascade took Bedrock down alongside 113 other AWS services for 9 hours plus extended degradation — the same incident that insurance analysts estimated produced $581M in covered losses.
The May 20 outage is particularly hard to ignore. Six weeks after the CEO told shareholders that Mantle made Bedrock the backbone of an inference platform processing more tokens in Q1 2026 than in all prior years combined, that same backbone was unreachable for the better part of a working day.
Throttling has become endemic enough that AWS now has a permanent re:Post knowledge-center article on the Bedrock 429 ThrottlingException. The published default quota for Claude 3 Opus on-demand was 50 requests per minute. Customers on the AWS re:Post forum routinely report being silently throttled to 1 request per minute — a 98% reduction from the documented number. One customer report:
It’s now day 5 of arguing with AWS billing support over their failure to supply the default quota value. They’re asking ridiculous questions, wasting my time, being deliberately obstructive after I already justified my use cases.
TrueFoundry — a vendor that sells a gateway in front of Bedrock and therefore has every commercial reason to praise it — published its 2026 Bedrock review in February. The summary:
Aggressive throttling, opaque latency spikes, and the limitations of managed Knowledge Bases often frustrate teams trying to scale beyond a PoC.
Their specific findings track the lived experience of anyone running real load through Bedrock. Default quotas are “shockingly low,” capped at something like 50 requests per minute or 500 tokens per minute on certain region–model combinations, and any increase requires a manual support ticket. Multi-tenancy produces noisy-neighbor latency variance from 2 seconds at 8 AM to 6 seconds at 2 PM on the same prompt. CloudWatch metrics are built for infrastructure rather than LLM workloads, so there is no native cost-per-conversation, no token usage broken out by user, and no multi-step agent tracing. There is no semantic caching, meaning every duplicate question is billed in full. There is no automatic model fallback, so a 500 from Claude crashes your application unless you wrote the retry path yourself. And there are no granular cost guardrails, which is why a single team can drain a monthly budget in a day.
A whole new category of vendors — TrueFoundry, Portkey, LiteLLM, and others — exists precisely to patch over the gaps Bedrock still has not closed. These are not growing-pains complaints from launch week. These are the production verdicts roughly five months after Mantle shipped.
The Pattern
This is not a Bedrock problem. This is a CEO-narrative problem, and it is the third or fourth time we have seen exactly this script in the last eighteen months.
Klarna told the world AI customer service was replacing 700 human agents, then quietly started rehiring humans when customer satisfaction collapsed. Salesforce’s Marc Benioff announced an AI hiring freeze for engineers, took the headcount win, and then quietly resumed hiring once the productivity claims failed to materialize. Amazon laid off roughly 30,000 corporate employees in late October 2025, and on the same news cycle Andy Jassy said AI efficiency gains would “reduce our total corporate workforce.” Six months later, in his shareholder letter, he produced a case study: six engineers did the work of forty.
The pattern is identical every time. A CEO needs to justify a headcount decision — to investors or to the board — that has nothing to do with AI. The CEO finds or constructs a story that nominally proves AI replaces engineers. The story gets repeated by every business outlet that does not have an engineer on staff. By the time the engineers come out of NDA and tell you what actually happened, the headcount has already been cut and the narrative has moved on.
Mantle is now that story for Amazon. Six engineers, 76 days, AI did it. The fact that the rebuild covers 2% of traffic, did not include Claude, took longer than reported, was led by a Distinguished Engineer with eight Principal Engineers loaned in from EC2, and used AI primarily to backfill missing tests — none of that fits in a shareholder letter.
The Practitioner’s Take
I have been shipping production .NET code for thirty years. I write a lot of code with AI now. I run agentic systems built on Microsoft Agent Framework and Semantic Kernel, with custom MCP servers for clients who actually have production traffic. So when someone tells me a small team plus AI can rebuild an inference engine in 76 days, I do not dismiss it — I ask what they actually built.
The honest version of the Bedrock–Mantle story is impressive in its own right. A Distinguished Engineer plus eight Top Talent Principal Engineers from EC2 used Kiro effectively to rewrite a piece of an inference platform in roughly five months. That is a great outcome. It is the kind of outcome you should expect when you put nine engineers with a combined century-plus of operational experience into a focused project with strong tooling. It is not a productivity miracle. It is elite engineers doing what elite engineers do, with better tools than they had three years ago.
The dishonest version — six engineers, 76 days, AI did it — is what shareholder letters are for. The May 20, 2026 outage is what production is for.
The two stories do not reconcile, because they cannot. One was written for shareholders. The other was experienced by customers.
If you are building agentic systems on top of Bedrock, the right takeaway is not “the rewrite failed.” The right takeaway is to build for the production reality, not the marketing reality. Implement automatic fallback to a second model, a second region, or a second provider. Cache aggressively at your own gateway, because Bedrock will not do it for you. Monitor at the application layer, because CloudWatch will not tell you why your tokens cost what they cost. Assume throttling will get worse before it gets better. Assume the outage log will keep growing. Assume Mantle’s coverage will expand at the pace AWS engineering can deliver, not at the pace the CEO promised.
And if you are a board member reading the next shareholder letter, ask one question before you let the narrative do its work: where are the engineers, and what do they say happened?
The Bedrock engineers asked in October 2025. The CEO answered in April 2026. The outage answered in May 2026.
Three answers. One was correct.