AWS re:Invent 2017: Another Day, Another Billion Flows (NET405)

In this session, we walk through the Amazon VPC network and describe the problems we were solving when we created it, and the features we’ve been adding as we scale it. We cover how these problems and features are traditionally solved, and why those solutions are not scalable, inexpensive, or secure enough for AWS. Finally, we provide an overview of the solution that we’ve implemented. We discuss some of the unique mechanisms that we use to ensure customer isolation, get packets into and out of the network, and support new features such as NAT and VPC endpoints.

[GoonCity]

This might be the one reinvent presentations from years ago that is timeless to this day.

[johnleeuw]

Truly excellent presentation. Super informative, even 5 years down the road. Thank you Colm!

[GoonCity]

Making your own network protocol is a legit genius idea for disambiguating of the same routes & addresses, and scaling to the amounts of VPCs

[deepankargoswami]

Great use of first principal thinking from AWS engineering team.

[fernandolichtschein]

I agree with you in the route thing, you can always cite George Maharis. I used to watch the TV series. Radia's book is awesome.

[mmm]

In regard with NLB, destination IP of return traffic from ec2 target group is client IP(not NLB IP). In route table, default route is internet gateway. So, does this mean, return traffic doesn't go via NLB?

[indigoskywalker]

this sounds like openflow or typical sdn

[williammeng]

NFV is Another Day, Another Billion Flows，nice

[samjackgreen]

I don't if this is using AI or something, but YouTube has called a chapter "S3 low bouncer" instead of load balancer 😂