Skip to content
Hallway
0:00 / 0:00

#vpc#amazonvpc#hyperplane

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

Amazon Web Services

849K subscribers • 14 videos on Hallway

YouTube
  • Recommended by 3 people: 3 on Hacker News.
  • Presented by Eric Brandwine, Amazon Web Services
  • Made by the vendor. The company whose product it covers made or sponsored it.
  • May be out of date. Uploaded 11 years ago, in an area where tools change fast.

Intermediate. Assumes working knowledge.

54K views11 years ago3 recommendations

Cloud and DevOpsDistributed systemsAWSNetworking and protocolsScaling and large-scale architecture

Eric Brandwine explains the design, scalability, and security mechanisms behind Amazon VPC virtual networking.

In this session, we walk through the Amazon VPC network presentation and describe the problems we were trying to solve when we created it. Next, we walk through how these problems 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 and 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 like VPC endpoints.

Why it's here

3 people recommend this

What people say. Highly recommended as the definitive explanation of how AWS handles Layer 3 virtualization and customer isolation.

ignoramouson Hacker News • Recommends

On “Nginx to Be Acquired by F5 Networks”

Here's the ever excellent Eric Brandwine explaining what AWS does at L3 wrt VPC: link to this 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 allegedly based on S3's load balancer).
View on Hacker News

colmmaccon Hacker News • Recommends

On “VPC Endpoints for Your Own Applications and Services”

There's lots on link , and talks on youtube ( link to this 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 are free and you can create and edit them programmatically (add subnets, change routes, manage ACLs and security groups) - so they're a useful way to manage an environment of things like EC2 instances, containers, Elastic Load Balancers, RDS databases, Lambda functions, and more, without needing to…
View on Hacker News

thinkharderdevon Hacker News • Recommends

On “Redis 6.0 GA”

You can't snoop on traffic between hosts in the same VPC. Here is a good video explaining why link to this 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 instance) will never even see the packets that are not intended for it. Of course this gets slightly more complicated because AWS added some tools for traffic mirroring. So theoretically someone with the right access could setup a mirror to a host they control in the VPC and sniff the traffic that w…
View on Hacker News