Plays with YouTube's privacy-enhanced embed

AWS re:Invent 2018: [REPEAT 1] A Serverless Journey: AWS Lambda Under the Hood (SRV409-R1)

Name: AWS re:Invent 2018: [REPEAT 1] A Serverless Journey: AWS Lambda Under the Hood (SRV409-R1)
Description: An AWS re:Invent 2018 session in which Holly Mesrobian and Marc Brooker explain how AWS Lambda is built, including its sandboxing, isolation and scaling architecture. It covers what happens under the hood when serverless code runs.

Amazon Web Services Talks advanced partly dated

Open on YouTube First HN thread

2 HN users recommended this talk in 2 different months between 2019 and 2019.

2007–2026

2 recommendations 1 citation HackerTube score 2

HN cites it as the authoritative description of Lambda internals and isolation, by the engineers who built it.

An AWS re:Invent 2018 session in which Holly Mesrobian and Marc Brooker explain how AWS Lambda is built, including its sandboxing, isolation and scaling architecture. It covers what happens under the hood when serverless code runs.

Pull quote: “You can watch this talk to learn more” (HN, 2019)

Also tagged: aws lambda internals, aws lambda, serverless, isolation, firecracker, reinvent

What Hacker News said

3 labeled comments from the HN archive; up to 20 are kept per video, favoring different commenters. Each one links back to the original thread.

Recommends staticassertion January 2019 under Exploiting the Math.expm1 typing bug in V8

Explains Lambda sandboxing internals and isolation.

I believe AWS does share customer information within a device, but with a lot of sandboxing below that. You can watch this talk to learn more: [this video] I think the threat model is basically that you'd need a KVM kernel 0-day + the ability to exploit it, so a point of privilege such as outside of the firecracker sandbox.

View on Hacker News

Recommends appwiz June 2019 under Learning to Build Distributed Systems

Talk on Lambda internals from reInvent 2018.

Here are a couple videos from reInvent 2018: Jaso talking about DynamoDB internals [link] Marc talking about Lambda internals [this video]

View on Hacker News

Citations, criticism and jokes

Cites it discodave March 2019 under On Internal Engineering Practices at Amazon

Cited to show Lambda runs on EC2.

Read the full comment

AWS SDE here. The short answer is, in order to get your team to adopt something, you need to make the case that it's better for customers (including things like migration costs). If the modern thing is more efficient, is higher availability, increases velocity, and so on then the case can be made. Some specific examples based on things you cite: * For an example of something OSS or "modern" coming from AWS, checkout Firecracker (written in Rust): [link] * With regards to "reinventing wheels" Apollo + EC2 solves a lot (not all) of the problems that containers solve, and existed for years before containers became the hotness. * Docker, which brought containers to the masses launched in 2013. * EC2 launched in 2006 (7 years before Docker). * Apollo (and the build system Brazil) predated EC2 by many years. * Amazon.com was migrating to EC2/AWS before 2012 ( [link] ) * Another example, Lambda, which launched in 2014 runs on EC2 ( [this video] ). * New services get to build in AWS and use Lambda, ECS, DynamoDB etc based on their business needs.

View on Hacker News