AWS Confirmed the Crash. Then Denied It. Then Billed Us.

David Lyon — Mon, 07 Jul 2025 16:17:37 +0000

In May, I published a detailed technical breakdown of a fatal, platform-level crash in AWS Lambda — a Node.js function inside a VPC making outbound HTTPS calls that would silently crash after returning a 201.

No logs. No errors. No stack trace. AWS eventually reproduced it themselves.

This post isn't about the bug.

It's about what AWS did next.

What Happened After the Reproduction

Even after AWS reproduced the crash using their own test code, their response wasn’t engineering.

It was damage control:

They blamed our code
They revoked a previously granted $4,000 credit
They silently billed our founder’s personal card
They filtered technical escalations through sales
They offered the credit back — this time as a settlement tied to silence
And they asked our CEO, off-record, not to publish

We published anyway.

The Real Postmortem: Culture, Not Code

This isn’t a teardown of runtime behaviour. That’s already done.

This is about support failure, accountability avoidance, and AWS’s cultural instinct to deflect rather than own fault.

If you’re building serious workloads on Lambda: read this.

Because when support fails, logs go dark, and engineering won’t speak — you are on your own.

Read the full follow-up post here

AWS Lambda Silent Crash – A Platform Failure, Not an Application Bug

David Lyon — Thu, 05 Jun 2025 12:34:40 +0000

What happens when a production-ready startup proves a runtime failure beyond doubt – and is still told it’s their fault?

Over a seven-week investigation, I uncovered and proved a silent, platform-level crash in AWS Lambda — affecting Node.js functions in a VPC making outbound HTTPS calls. The failure occurred mid-execution, after the function had returned a success response. No logs. No errors. No telemetry. No way to catch it.

From day one, I did what AWS claims to value in a partner.

I stripped the function down to minimal reproducible code.
I tested across runtimes, regions, and infrastructure baselines.
I rebuilt on EC2 and proved that the issue vanished entirely.
I shared logs, traces, metrics, and internal observations.

I escalated through every official channel:

Support dismissed it.
My Account Executive ignored it.
Formal complaints were met with silence.
Internal re-escalations led nowhere.
AWS Activate — the startup programme — refused to engage.
And executive outreach yielded nothing but a two-line response weeks later.

At every stage, I remained professional. I kept the tone restrained. I offered AWS every opportunity to engage constructively.

Instead, they claimed the bug was in my code — despite the function crashing after returning a 201.
They claimed I had forgotten a reject() — despite the error occurring deep inside https.request(), and their own reproduction missing the handler.
They suggested I move to EC2 — by then, I already had.
I asked for Lambda engineering — they gave me sales. Then silence.

Even AWS Activate, whose sole purpose is to support startups like ours, refused to take part. Their response wasn’t technical — it was procedural. A polite copy-paste directing us back to the same failing support system we were already trapped in.

This wasn’t just a Lambda bug. It was a platform-level failure, misdiagnosed through a broken support process, and left to rot in plain sight.

AWS’s internal systems failed. Their support model failed. Their startup engagement model failed. And above all, their cultural commitment to ownership — the thing they claim defines them — was nowhere to be found.

So, we left.
We migrated everything.
Lambda was decommissioned.
Critical services were refactored for Azure.
And our engineering culture now lives on a platform that still understands trust has to be earned — not assumed.

If you're building on Lambda: know this.
It may fail silently.
And if it does — AWS may blame you, even after they reproduce the failure themselves.

This is just the beginning of the story.

For the full deep dive into the silent AWS Lambda crash, our complete diagnostic process, AWS's contradictory responses, and why we ultimately decided to migrate our entire infrastructure, please read the full article on our website:

Read the Full Post: AWS Lambda Silent Crash – A Platform Failure, Not an Application Bug