←back to thread

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

(lyons-den.com)
115 points nonfamous | 1 comments | 15 Jul 25 01:22 UTC | HN request time: 0s | source
Show context
nemothekid ◴[15 Jul 25 02:43 UTC] No.44567382[source]▶
If I'm reading this correctly, then AWS Support dropped the ball here but this isn't a bug in lambda. This is the documented behavior of the lambda runtime.

The document is long, and the examples seem contrived, so anyone is free to correct me but as I understand it the lambda didn't crash, after you returned 201, your lambda instance was put to sleep. You aren't guaranteed that any code will remain running after your lambda "ends". I am not sure why AWS Support was unable to communicate this OP.

If you are using Lambda with a function URL, you aren't guaranteed that anything after you return your http response remains running. I believe Lambda has some callbacks/signals you can listen to, to ensure your function properly cleans up before the Lambda is frozen, but if you want the lambda to return as fast as possible it seems you are better off having your service publish to an SQS queue instead.

replies(5): >>44567412 #>>44567432 #>>44567463 #>>44567479 #>>44567534 #
semiquaver ◴[15 Jul 25 02:51 UTC] No.44567432[source]▶
This document is bizarre. The author is so confidently verbose about something they are clearly misunderstanding, and have been told as much dozens of times. It’s humbling, in a way, to think of times I’ve felt this strongly about something and to consider the possibility I could have been this wrong.
replies(2): >>44567508 #>>44567672 #
johnfn ◴[15 Jul 25 03:48 UTC] No.44567672[source]▶
It's pretty clearly written by GPT.
replies(1): >>44567682 #
x3n0ph3n3 ◴[15 Jul 25 03:52 UTC] No.44567682[source]▶
Can you share some of the tell-tale signs you pick up on?

Edit: I see he's the CTO of an AI company.

replies(3): >>44567712 #>>44567768 #>>44567777 #
appreciatorBus ◴[15 Jul 25 04:15 UTC] No.44567768[source]▶
He’s already added an entry about the whole incident to his resume:

https://lyons-den.com/CV/David_Lyon_CTO_CV_2025.pdf

EDIT: he has added three(!) separate mentions of the same incident to his résumé

replies(4): >>44567820 #>>44571537 #>>44571637 #>>44572336 #
encomiast ◴[15 Jul 25 14:41 UTC] No.44571637[source]▶
The whole site is sketchy. A PhD and a JD. All these high level positions at well-known places. A website with very vague claims about heroically saving things. Almost no google presence other than this site. And 4 LinkedIn connections. Maybe I'm just cynical, but it's pegging my BS meter.
replies(2): >>44572769 #>>44572876 #
dfedbeef ◴[15 Jul 25 16:18 UTC] No.44572769[source]▶
Nope, BS meter is correct. You can find the 2017 commencement documents for New York Law School online and David Lyon is not on the list of JD graduates...
replies(1): >>44609841 #
encomiast ◴[18 Jul 25 21:07 UTC] No.44609841{3}[source]▶
Interesting…both the linkedIn profile and the website appear to be gone.
replies(1): >>44616388 #
1. paulc51 ◴[19 Jul 25 15:35 UTC] No.44616388{4}[source]▶
Archive.org did a round of saving his entire website, including the posts and "papers" just before it was taken down: https://web.archive.org/web/20250715045222/https://lyons-den...

Interesting if the whole character was a scam. The current employer is not disclosed in his CV, qualifications are fake (also flagged on Reddit by someone who says they are an ex colleague https://www.reddit.com/r/aws/comments/1m0198c/comment/n3fiwk...) - what else?