AWS re:Invent 2015 | (NET403) Another Day, Another Billion Packets

Channel:Amazon Web Services · Length:42:25 · Published:2015-10-10 · Views:54824

Watch on YouTube

Summary

Eric Brandwine's AWS re:Invent 2015 session on how Amazon VPC networking works. It covers the problems the design solved, why traditional approaches do not scale, and the mechanisms used for customer isolation and VPC endpoints.

Why HN recommends it

Considered a favorite deep dive into how AWS does virtual networking at L3 and why VPC hosts cannot snoop each other.

Here's the ever excellent Eric Brandwine explaining what AWS does at L3 wrt VPC — HN, 2019

Networking & internet infrastructure · Cloud, DevOps & reliability

Subtitles (excerpt)

my name is Eric these days I'm with the AWS security team but when I joined Amazon 8 years ago I was with the team that defined and launched VPC and that's what we're going to be talking about today clicker works so this is a reprise of a version of this talk that I gave at reinvent two years ago I'd like to manage expectations a lot of the content is the same there is some new stuff but if you're expecting a completely new talk I'd rather you leave angry now than leave angry at the end of The Talk the problem that we're trying to solve with VPC is simple we're AWS we have the cloud the cloud is full of all sorts of AWC goodness services like ec2 and elastic load balancing and the elastic Block store and our relational database service and Amazon redshift or columnar uh data store and elasticache customers have data centers these are data centers they've owned for years they're expensive Capital Investments they're not going to go away immediately and so as good Engineers we go to the Whiteboard and we draw an arrow this is what we wanted to do we wanted to plug customer data centers into the cloud this is going to be a really important deployment scenario for us we have customers you hear

On Hacker News

Here's the ever excellent Eric Brandwine explaining what AWS does at L3 wrt VPC: [VIDEO] Here's the super versatile Colm Mac explaining what AWS does at L4: [LINK] --- Google has been very open about their network infrastructure, here's a nice summary from 2015: [LINK] and not mentioned in that blog... their NetworkLoadBalancer, Maglev: [LINK] (AWS equivalent of which would be HyperPlane: [LINK] … — ignoramous, 2019-03
You can't snoop on traffic between hosts in the same VPC. Here is a good video explaining why [VIDEO] . The tl;dr; is that your guest OS (the EC2 instance) is not connected to the physical layer 2 network. The host OS hypervisor is and when it receives a packet from the physical NIC, if that packet is not directed to the guest OS then it won't be passed to it. So the NIC on the guest OS (your EC2… — thinkharderdev, 2020-05
There's lots on [LINK] , and talks on youtube ( [VIDEO] is a fav). But the TLDR is this: VPC stands for "Virtual Private Cloud" and it gives you your own virtual data center on AWS. You get a private network that uses whatever IP range you'd like, and you can connect to it privately via VPN or Direct Connect (physical links). You can also connect it to the internet with Elastic IP Addresses. VPCs… — colmmacc, 2017-11

Related videos